See a Demo
menu

The Resource and Capacity Tracking Guide for PMO Leaders

The person who looks available is not always available

It is Monday morning. A project has been approved. Leadership wants to know if it can start next month.

The PM checks the schedule and sees several people with availability. The department manager says they are already committed elsewhere.

One person will be on leave. Another has the right role but not the required skill. A third is technically available, but assigning the work would overload them in another system.

So the dashboard says capacity exists, but the organization does not actually have the capacity.

  • The project schedule shows demand, but not complete availability.
  • The resource directory shows people, but not all of their commitments. Development tools show work in progress, but not the wider portfolio.
  • Paid time off reduces availability, but may never make it into the project plan. Proposed work and operational work may not appear anywhere.
  • Actual effort is rarely used to improve the next plan.
MOVE 1

Don't start with utilization; start with the decisions.

The mistake many organizations make is starting with a single number: a utilization percentage, a headcount total, an open-hours report. Those numbers matter, but only because they help answer real staffing decisions.

For PMO leaders, the goal is not to collect more data. The goal is to help leaders make better decisions using that data. Before you build another workload report, start with the questions leadership is already asking:

  • Do we have enough capacity to deliver the committed work?
  • Can we start this new project when requested?
  • Which people, roles, or teams are becoming bottlenecks?
  • Who has the right skills and availability for this assignment?
  • Who is overallocated now, or will be soon?
  • Where do we need to hire, contract, or cross-train?

No single capacity percentage answers these questions.

“Can we start the project?” requires the proposed schedule, expected effort, required roles and skills, availability of suitable people, current assignments, leave, operational commitments, planning-stage demand, and the other work already competing for those same people together, not one at a time.

The data lives in separate systems — an HR system, Jira, a work management tool — but it can't stay siloed there. A person can look available in the project plan, fully committed in a department spreadsheet, and different again in Jira, depending on which system you ask

The first step is to define the questions your PMO must be able to answer consistently. Once the questions are clear, the required data becomes much easier to identify and connect from the systems you already have.

Reading on your phone? Take the playbook with you.

Download the PDF
MOVE 2

The resource and capacity model

Every capacity decision depends on the same connected model.

Project resource and capacity model in fours parts: Foundation, Supply, Demand, and Decisions

Each layer produces information the next depends on.

Foundation defines who could ever be assigned. Supply defines how much of their time is realistically usable. Demand defines what's competing for that time, when, and how urgently. Decisions determine which commitments get the capacity that exists — because the end question is never just "can we rebalance," it's "which work deserves the constrained capacity we have."

Want to know where your PMO stands?   Score it in 2 minutes  ↓
MOVE 3

12 Capacity Data Points to Track

Once you understand the resourcing data model, the next step is to ask three questions: Do we capture this? Where does it live today? Is it connected to the rest of the resource picture?

01

People

Foundation
HR systemResource spreadsheet
What it is
The individuals and non-person resources (employees, contractors, vendors, equipment, rooms) available to perform work.
Leadership question it answers
Who can perform the work?
If it's missing
Capacity is discussed in totals without knowing who can actually be assigned.
02

Roles & skills

Foundation
Resource spreadsheetHR system
What it is
The function a resource performs and the capabilities or experience required for the work.
Leadership question it answers
Who is qualified, not just free?
If it's missing
Staffing becomes name-based and dependent on whoever managers already know.
03

Departments, teams & pools

Foundation
Org chartHR system
What it is
The organizational structures through which capacity is owned, reviewed, and shared.
Leadership question it answers
Where does capacity exist, and who controls it?
If it's missing
Cross-team planning depends on individual managers reconciling separate lists.
04

Schedules & availability

Supply
HR systemPersonal calendars
What it is
Standard work patterns, part-time schedules, regional calendars, and capacity start/end dates—when someone is actually part of usable supply.
Leadership question it answers
When is this person actually part of available supply?
If it's missing
Every report assumes everyone has the same schedule for the whole planning horizon.
05

Capacity & utilization target

Supply
SpreadsheetA manager's judgment
What it is
Total working time available, adjusted for how much of it should realistically be assignable to project work.
Leadership question it answers
How much of a person's time should we expect to allocate?
If it's missing
Organizations treat 100% of working hours as project-assignable.
06

Leave & non-project work

Supply
HR/PTO systemSpreadsheet
What it is
PTO, holidays, support work, meetings, administration, and business-as-usual responsibilities.
Leadership question it answers
What reduces usable project capacity?
If it's missing
People appear free on paper while carrying invisible commitments.
07

Project demand & requirements

Demand
Project planIntake form
What it is
How much effort the work requires, when it's needed, how important it is relative to competing demand, and what roles or skills it takes.
Leadership question it answers
Do we have the right capacity, not just enough capacity—and where does it rank?
If it's missing
Availability in October doesn't solve a shortage in August—and without priority, capacity gets balanced instead of protected for what matters most.
08

Planning-stage & future demand

Demand
Intake spreadsheetSales pipeline
What it is
Expected work that has not yet become an active, approved project.
Leadership question it answers
What will capacity look like after probable work is approved?
If it's missing
Every approved project creates an unexpected staffing crisis.
09

Placeholder demand

Demand
PM toolNowhere
What it is
Demand represented by role, resource type, department, or skill before a named person is assigned.
Leadership question it answers
What resources will we need even though staffing isn't final?
If it's missing
Demand disappears until the organization is already expected to deliver it.
10

Planned allocations

Demand
PM toolAllocation spreadsheet
What it is
The amount of a resource's time expected to be consumed by a project, task, or period—top-down or bottom-up.
Leadership question it answers
Where is available capacity already committed?
If it's missing
Managers see assignments but not how much workload they represent.
11

Actual effort, workload & utilization

Decisions
Timesheet systemJira/Azure DevOps
What it is
What people actually spend, what they're currently carrying, how effectively capacity is being used, and how reality compares with the plan.
Leadership question it answers
Are people doing what the plan assumed, and how busy are they really?
If it's missing
Capacity planning never learns from execution. The same unrealistic estimates repeat every project.
12

Staffing gap & response

Decisions
Meeting notesA manager's judgment
What it is
The difference between required demand and available qualified capacity and the decision it forces.
Leadership question it answers
What must change for the organization to deliver?
If it's missing
Reports identify overload but never turn into a hiring, reassignment, or timing decision.

Where to start

You do not need all twelve building blocks on day one. Adopt them in the order of the resource data model.

  1. Establish the foundation (Who do we have?)
    People, roles, skills, departments, teams, pools.
  2. Connect available supply (When are they really available?)
    Schedules, capacity, utilization targets, PTO, non-project work.
  3. Connect work demand (What is competing for capacity, and what matters most?)
    Effort, timing, priority, role requirements, planned allocations, planning-stage and placeholder demand.
  4. Close the loop with execution. (Are our assumptions improving?)
    Actual effort, utilization, staffing gaps, workforce decisions.

MOVE 4

Connect demand to capacity before you commit

Collecting the twelve building blocks is not enough.

Most organizations already have many of these numbers somewhere. The problem is that the data stops connecting as approvals, dates, and staffing promises are made.

  • If proposed work is not connected to future demand, the organization approves work without understanding the staffing impact.
  • If project schedules are not connected to resource allocations, the timeline moves but the capacity forecast does not.
  • If availability is not connected to skills, a resource may look free without being qualified for the work.
  • If PTO and non-project work are not connected to availability, a person may look free during time they will not actually spend on project work.
  • If work in Jira or Azure DevOps is not connected to the portfolio, development teams may look available from the PMO's view while carrying full delivery commitments elsewhere.
  • If planned effort is not connected to actual effort, the same unrealistic estimates repeat project after project.
  • If priority is not connected to allocation decisions, capacity gets balanced by convenience instead of protected for what matters most.

Two stubborn failure patterns

Invisible work.

People are carrying commitments that never appear in the capacity system: business-as-usual work, support, unplanned requests, meetings, work tracked in an external system, shadow projects, informal leadership responsibilities. These are real, costly, and nowhere in the report.

False precision.

The report shows a person at 72% utilization. The number is exact. It's also built on incomplete estimates, missing PTO, invisible operational work, or outdated assignments. So the picture underneath is not exact at all.

This is why another workload dashboard usually does not solve the problem. A dashboard can only show the data it can reach. If skills, PTO, priority, and work in external systems live in separate places without a reliable connection, the dashboard becomes another reporting layer on top of disconnected information.

Not after exports.
Not after a manager’s spreadsheet.
Not after a planning meeting.
With one connected capacity picture.

Connection is what turns data into a capacity story the PMO can defend. When the data is connected, leaders can see how proposed work became visible demand, how demand became a staffing plan, how a plan became an assignment, how actual effort revealed a gap, and how everything rolls up into portfolio-level visibility executives can trust.

That is the difference between collecting resource data and building a resource and capacity backbone.

For resource data to actually work, it can't just sit in different places.

Availability, skills, PTO, assignments, and demand all need to connect to each other in one place so the numbers can be trusted, not just collected.

Here's what that looks like in practice.

Say an integration pulls hours from Jira into a report. Now you can see the hours. But you still can't tell if that person is overloaded because the report doesn't know what else they're assigned to, whether they're about to go on PTO, or how urgent the work is.

The hours showed up. They just didn't bring their context with them.

That's the real difference: moving data gets a number from one screen to another.
Connecting data means that number still knows what it's related to once it gets there.

Every integration you add without connecting data becomes one more thing someone has to reconcile by hand.

MOVE 5

Recognize when your work management tool has reached its capacity limits

Work management platforms are excellent for organizing tasks, assigning owners, and supporting team collaboration. But organizing work is not the same as managing organizational capacity.

Test your system

When a project manager assigns a task, does that person's availability, PTO, workload, and portfolio-wide capacity update without anyone exporting data or checking a spreadsheet?

If the answer is no, your work management tool has likely reached its capacity limits.

Signs You've Reached the Resource-Planning Ceiling

Checked three or more? These are architecture problems, not effort problems.

None of these are effort problems. They are architecture problems.

The resource building blocks were never designed to work together in your current connections. The solution is not another dashboard, another export, or another integration. The solution is a resource and capacity backbone where people, skills, availability, PTO, demand, priority, and actual effort are connected from the beginning.

When the resource and capacity backbone is connected, staffing decisions become something leaders can trust instead of something a manager has to reconstruct every time a project gets approved.

MOVE 6

Align the capacity picture to the people who need it

Different people need different answers from the same resource and capacity backbone.

PMO Leaders

Key questions: Can the portfolio be delivered with current capacity? Which projects compete for the same constrained roles? Where should work be delayed or reprioritized?

Required visibility: Portfolio-wide demand, planning-stage projects, staffing gaps.

Resource Managers

Key questions: Who is overloaded? Who has capacity? Are assignments balanced fairly? Where do I need more people or different skills?

Required visibility: People, teams, skills, availability, PTO, utilization targets.

Project Managers

Key questions: Who can complete this task during the required dates? Will this assignment create overload? Can I replace an unavailable resource?

Required visibility: Capacity from the task list, assignment warnings, suggested resources.

Executives

Key questions: Do we have enough capacity to deliver our commitments? Which initiatives are at risk from resource constraints? Where will hiring or contracting be required?

Required visibility: Demand vs. capacity trends, critical constraints, workforce gaps.

Team Members

Key questions: What am I expected to complete, and what's highest priority? Am I being assigned more than I can realistically deliver?

Required visibility: One cross-project work list, realistic assignments, notifications.

Workforce Planning/HR

Key questions: Which skills will be needed, and when? Is the gap temporary or sustained? Should we hire, contract, or develop internally?

Required visibility: Role and skill demand by period, unfilled placeholders, gaps.

When the data is disconnected, each of these groups builds its own version of the truth and the versions disagree. When the backbone is connected, everyone is looking at the same numbers through different windows.

MOVE 7

Can you trust your resource and capacity forecasts?

You have seen the data model, the twelve building blocks, and the ways connections break. Now assess where your organization stands. Score your PMO below.

Score each question: 0 = no, 1 = partially or manually, 2 = yes, automatically.

RESOURCE FOUNDATION & SUPPLY

1. Do we maintain every resource with the correct role, department, schedule, and capacity?

2. Can we identify people by the skills or resource types a task requires?

3. Do PTO, holidays, and individual schedules reduce availability automatically?

CURRENT WORK DEMAND

4. Does every active project include realistic estimates, timing, and priority?

5. Can we combine task-level demand with top-down allocations?

6. Is business-as-usual and non-project work visible in the capacity picture?

FUTURE DEMAND

7. Are proposed and planning-stage projects included before they're approved?

8. Can we represent demand with placeholder roles before named people are assigned?

EXECUTION & DECISIONS

9. Are project managers warned before an assignment creates overload?

10. Can managers identify a qualified alternative based on fit and availability?

11. Can we model timing or staffing changes without altering the live plan?

12. Can leadership tell whether a gap requires reprioritization, delay, reassignment, hiring, or contracting?

Answer all 12 questions to see your score.

0–8: Disconnected

Resource information lives in separate schedules, spreadsheets, and manager knowledge. Start with the resource foundation and current demand.

9–16: Partially connected

You can see basic workload, but manual handoffs hide leave, planning-stage projects, or skill constraints. Focus on every question you scored 1.

17–24: Connected

Your organization can see demand and availability across current work. The next opportunity is future planning, scenario modeling, and workforce forecasting.

This is not a measure of how hard your resource managers work. It measures how much of the process is supported by connected structure rather than manual reconstruction.

Get your score and get the getting started guide

We'll email your results and the companion guide, How to Get Started with Capacity Planning — a getting-started walkthrough for building your resource and capacity data backbone in Project Insight, one band at a time.

MOVE 8

Build a connected resource and capacity backbone

You do not need another workload dashboard sitting on top of disconnected resource data.

You need a connected resource and capacity backbone underneath it.

Disconnected resource systems brought together through one structured resource and capacity backbone

A connected backbone doesn't force every team to plan work identically.

  • Some teams use detailed task estimates; others use high-level weekly allocations.
  • Development teams can keep working in Jira or Azure DevOps.
  • Operational work can be represented through top-down planning.
  • Proposed projects can use placeholder roles.

The backbone creates a shared structure through which every source of demand can be compared against the organization's real supply of people, skills, and time—and prioritized when they compete.

How Project Insight builds the resource and capacity backbone

Project Insight connects the resource information required to understand who is available, what work is competing for their time, and what needs to change before the organization commits.

  • Build a realistic resource foundation. Organize people and non-person resources by role, skill, department, team, resource pool, schedule, and capacity.
  • Calculate usable capacity, not theoretical capacity. Account for PTO, holidays, individual schedules, utilization targets, business-as-usual work, and other non-project commitments.
  • Bring current and future demand into one picture. Combine detailed task estimates with top-down allocations, planning-stage projects, and placeholder demand before named people are assigned.
  • Find the right person and test options before committing. Evaluate availability, workload, role, skill match, and department, then model the effects of changing timing, staffing, or priorities.
  • See and rebalance capacity across the portfolio. Roll resource demand up across projects, programs, portfolios, and departments so leaders can identify overload, staffing gaps, and competing priorities.

Keep teams in the tools they already use

Building a trusted capacity picture does not mean forcing every team to plan work identically or move into one application.

Development teams can continue working in Jira or Azure DevOps. Project teams can use detailed task estimates. Other departments can plan with high-level weekly allocations. Operational and business-as-usual work can be represented through top-down planning.

  • When effort is tracked in Jira or Azure DevOps, that work can contribute directly to capacity reporting.
  • When detailed effort is not tracked in the source system, managers can use a top-down overlay to represent the team’s real demand.
  • Proposed projects can create visible demand through placeholder roles before staffing decisions are final.

Project Insight becomes the trusted project command center that connects these different sources of demand to the organization’s real supply of people, skills, and time. Teams can keep working in the tools and planning methods that support their day-to-day work while the PMO gains one portfolio-wide capacity picture.

Why this matters when you're using AI

AI does not solve disconnected resource data. It exposes it.

AI cannot reliably answer questions such as: Who should be assigned? Which team will be overloaded next month? Can this project be approved with the capacity we have? Which roles or skills are becoming constraints? Does the gap require reassignment, reprioritization, delay, hiring, or contracting?

Useful AI analysis requires more than access to assignments or open hours. It needs to understand the relationships between people, roles, skills, schedules, availability, PTO, workload, project demand, priority, and actual effort.

Project Insight’s AI-assisted planning, scheduling, resource recommendations, and what-if simulations work from that connected resource data—not isolated numbers without the context behind them.

What good looks like

When the resource and capacity backbone is connected, capacity planning stops being a manual reconstruction exercise.

  • Project managers check capacity while assigning work, not after.
  • Proposed projects create visible demand before they are approved.
  • PTO and operational work reduce availability automatically.
  • Resource managers see overload across every project, not just one.
  • Placeholder demand reveals hiring and contractor needs early.
  • Schedule changes update the capacity forecast automatically.
  • Leaders know what to approve, delay, reprioritize, hire for, or contract.
  • AI analyzes connected project data instead of trying to interpret scattered fragments.

That is the shift: from workload reports built on incomplete assignments to confident commitments built on a connected resource and capacity backbone.

Let us help you connect your resource and capacity data

See how Project Insight helps you understand who is available, what work is coming, where capacity is tight, and what needs to change before you commit.

Talk to a specialist

A Project Insight specialist will show you how active work, proposed projects, schedules, assignments, PTO, operational commitments, roles, skills, priority, and actual effort can come together in one capacity command center. Bring us one real capacity question.

Talk to a specialist

Download the full playbook

Keep the complete Resource and Capacity Planning Playbook, including the twelve building blocks, seven moves, readiness assessment, and connected capacity-planning framework.

Download the PDF

The Resource and Capacity Data Tracking Playbook for PMO Leaders  |  What to Track Before You Can Trust Your Staffing Decisions  |  A Project Insight Guide

Published August 21, 2026