Resource and Capacity Planning for Project Portfolios

Here is the quiet way most project portfolios fail. Leadership approves a set of projects that each look reasonable on its own. Nobody adds up the people those projects require. Three of them need the same senior engineer. Two need the only person who understands the legacy system. The plan is fine on paper and impossible in practice, and the first anyone hears of it is when deadlines start slipping for reasons no single project can explain.

Capacity planning prevents that. It is the discipline of comparing the demand your portfolio creates against the supply of people you actually have, and refusing to commit beyond it. It is unglamorous and it is the single most reliable predictor of whether a portfolio delivers. That comparison sits at the center of portfolio management and the modern PMO, because every other portfolio decision quietly assumes the people exist to deliver it.

Demand versus supply, in plain terms

Demand is the total effort your approved and proposed projects require, ideally broken down by role and over time. Supply is the effort your people can realistically contribute, after you subtract holidays, support duties, meetings, and the operational work that never shows up in a project plan. Capacity planning is simply keeping demand below supply, role by role, period by period.

The reason this is hard is that demand is easy to see and supply is easy to overestimate. Every project advocates for its own resourcing. Nobody advocates for the truth that a person is already 130 percent committed.

Plan at the level of the constraint

Averages lie. A portfolio can look 80 percent utilized in total while the two people who matter most are buried. Effective capacity planning happens at the level of constrained roles and named specialists: the architect everyone needs, the one data engineer, the product lead who is on every steering committee. Find the constraints and plan against them, because they, not your headcount average, set the true throughput of the portfolio. Seeing demand against named specialists across every project at once is usually the feature that justifies adopting PPM software, since spreadsheets hide exactly this kind of cross-project conflict.

Set utilization targets you can actually sustain

A common mistake is planning teams to full utilization. It feels efficient and it guarantees failure, because real work includes interruptions, rework, onboarding, and the unplanned requests that always arrive. Sustainable utilization for project work is usually well below 100 percent. The exact number depends on how much support and operational load the team carries, but planning to the brink leaves no room to absorb the inevitable, and the result is missed dates and burnout. If you want the arithmetic laid out cell by cell, our capacity planning template walks through the columns and formulas, including the overhead deduction that makes 100 percent a fiction in the first place.

Connect capacity to prioritization

Capacity planning and prioritization are two halves of the same decision. A ranked list of projects is only meaningful once you draw the line at where capacity runs out. Everything above the line is funded and staffed. Everything below it waits, no matter how appealing. If you have not yet built that ranking, start with how to prioritize a project portfolio, then bring the result here and test it against real supply. Once capacity confirms the plan is possible, the next step is resource allocation: assigning named people to the funded work and resolving the conflicts that assignment creates.

Portfolio resource management: the wider discipline

Portfolio resource management is the practice of allocating a shared pool of people, skills, and money across every project in the portfolio, rather than staffing each project as it is approved. Capacity planning is the arithmetic inside it. Portfolio resource management is the wider job: owning the pool, setting the allocation rules, and deciding who loses when two priorities want the same specialist in the same month.

The difference matters because most organizations do the arithmetic and skip the ownership. They can produce a capacity view and still have no one empowered to reassign a scarce architect off a favored project. Portfolio resource planning works when three things are true: one person or forum owns the pool, the allocation rules are written down, and the rules apply to senior sponsors as well as junior ones. Without the third, the process degrades into whoever asks loudest. The decision rights that make this stick belong in project portfolio governance, and the artifact that records the rules is the resource management plan. When the contested specialists are shared across departments rather than inside one function, the authority to settle it usually has to come from an enterprise PMO, because no departmental office can overrule another.

Make the capacity conversation routine

Capacity is not a one-time model. People leave, projects slip, and new demand arrives constantly. The portfolios that stay healthy review demand versus supply on the same cadence they review priorities, usually inside the same governance forum. That way, the moment a new project would push a constrained role over the line, the tradeoff is explicit: something else has to move. For how to run that forum, see project portfolio governance, and for how a PMO turns these signals into decisions, start with the PMO overview. The rules that make this repeatable across projects, who estimates, who acquires people, and how conflicts get settled, belong in a resource management plan.

From headcount to net capacity: the deductions nobody makes

The number most portfolios plan against is headcount, or headcount times a nominal 40 hour week. That number is wrong by a wide margin in one direction, always, and it is why plans that looked feasible in October are unrecoverable by February.

Net capacity is what is left after you subtract everything a person does that is not project delivery. The deductions are individually obvious and collectively enormous.

Swipe to see more →

Publish the deduction percentages you use and where they came from, then revise them against what actually happened last quarter. A team that consistently delivers 55 percent of its nominal hours to projects is not underperforming, it is telling you your model is wrong. Treat every range above as a starting calibration, not a constant. For the spreadsheet mechanics of laying this out column by column, the capacity planning template covers the arithmetic; the point here is which deductions belong in it at all.

The context switching tax is real and it compounds

A person assigned to four projects at 25 percent each does not deliver four quarter projects. Each additional concurrent commitment adds handover overhead, separate meetings, separate context to rebuild, and separate stakeholders to keep informed, and none of that scales down with the percentage. The allocation spreadsheet says 100 percent. The delivered output is meaningfully less.

The practical control is a hard cap on concurrent project assignments rather than a percentage adjustment, because percentages get negotiated and caps do not. Two concurrent projects for delivery roles, three as an absolute ceiling, and one for anyone on a genuine deadline. When a fifth request arrives for a person already on three, the answer is not a smaller percentage, it is that something has to come off the list. Enforcing that is the point of a named owner for the pool, and it is the rule that gets abandoned first when a senior sponsor pushes. Resolving those competing claims is covered in resource contention.

How far out capacity planning is actually reliable

Plans fail credibility when they claim more precision than the horizon supports. Naming a specific person for a specific week nine months out is not planning, it is decoration, and everyone reading it knows so. Match the grain to the horizon instead.

Swipe to see more →

The common error is planning the far horizon at near horizon grain, which produces a document nobody trusts and everybody ignores. The rarer and more damaging error is the reverse: planning the next six weeks at role level, so nobody notices that one named person is on the critical path of three things at once.

The overcommitment ratio, and the number where plans start failing

Here is the single figure worth putting in front of a governance forum. For each constrained role, take the total demanded FTE across every approved and proposed project in the peak month, and divide it by the net available FTE for that role in that month. Peak month, not the average, because the average always looks fine.

Swipe to see more →

Report it per constrained role, never as a portfolio total. A portfolio at 0.78 overall with its lead architect at 1.6 is not a portfolio at 0.78. Averages are exactly what hides the problem this metric exists to expose, and the roles that break are almost never the ones with the most people.

Four ways to close a capacity gap, and how fast each one works

When the ratio comes back above 1.0, there are only four moves. They are not equally useful, and the one most organizations reach for first is the slowest.

Swipe to see more →

Whichever move you pick, you have to be able to see the gap per role per month before you can argue for any of them, which is the whole job of a resource capacity planning tool: demand from the approved initiatives, the FTE each role actually has, and the shortfall in the months it appears.

Notice that the first two are portfolio decisions and the last two are functional ones. That is why capacity gaps escalate badly in organizations where the PMO can model the problem but only a functional leader can act on it. Whoever owns the pool needs the authority to do row one, or the model is just documentation of an outcome nobody prevented. If the answer is repeatedly to contract the same skill quarter after quarter, that is a hiring decision that has not been made yet, and the skills matrix is where the pattern becomes visible.

The monthly capacity review, step by step

1. Refresh supply first, before looking at any demand. Update leavers, joiners, ramp status, and any change in support load. Doing demand first anchors the conversation on what people want rather than what exists.
2. Recompute net capacity per constrained role using the current deductions, not last year's.
3. Roll up demand from approved projects, then separately from proposed ones, and keep the two visible as separate layers. The gap between them is what the approval decision actually costs.
4. Calculate the overcommitment ratio per constrained role for each of the next six months and identify the peak.
5. For any role above 1.0, prepare the specific option set from the four moves above, with the recommendation named. Bring options, not a red cell.
6. Take it to the same forum that approves projects, in the same meeting, so the capacity consequence and the funding decision happen together rather than a month apart.

Step six is the one that makes the difference. Capacity reviewed in a separate forum from prioritization becomes advice that governance is free to ignore, and it will be ignored, because the pressure in the room is always to approve. Running both in the same session is a structural fix covered in the portfolio review meeting.

Six patterns that break capacity planning

Swipe to see more →

Frequently asked questions

What is capacity planning in project management?

Capacity planning in project management is the practice of comparing the hours or FTEs your people can realistically supply against the hours the planned work demands, over a defined horizon. Its output is a clear answer to one question: can we staff what we have committed to, and if not, what has to move.

What is the difference between capacity and resource planning?

Capacity planning is the aggregate view: does the organization have enough supply, by role, to cover demand over the coming months. Resource planning is the assignment view: which named person works on which project next week. Capacity decides whether the portfolio is feasible; resource planning executes that decision person by person. You need the first before the second is worth doing.

What are the different types of capacity planning?

In a portfolio context there are three working grains: strategic capacity planning by role over quarters (can we staff the roadmap), tactical planning by team over weeks or months (who is overallocated soon), and sprint-level planning inside agile teams. Most organizations only do the third, which is why cross-project overcommitment keeps surprising them.

What is a good utilization rate for project teams?

Plan project teams to roughly 70 to 85 percent of net capacity, not 100. Real weeks include interruptions, rework, support requests, and meetings nobody scheduled, and a plan that allocates every hour has no way to absorb them. Chronic utilization above 85 percent predicts slipped dates and burnout; chronically below 50 usually means work is happening off the books.

How do you calculate resource capacity for a portfolio?

Start with total nominal hours per role, subtract paid time off, sick time, meetings and admin, support and business as usual load, and ramp for new joiners, to get net capacity. Then total the demanded hours per role across every approved project over the same period. Compare the two per constrained role, per month, and take the peak month rather than the average, because averaging is what conceals the shortages that actually cause slippage.

How many projects can one person work on at once?

Two concurrently for delivery roles, three as an absolute ceiling, and one for anyone on a genuine fixed deadline. Beyond that, handover overhead, duplicated meetings, and the cost of rebuilding context consume more than the extra allocation delivers. Enforce it as a hard cap on the number of assignments rather than as a percentage adjustment, because percentages get negotiated down and caps do not.

What is the difference between capacity planning and demand management?

Demand management is about what work is coming in: capturing requests, qualifying them, and shaping the pipeline before anything is approved. Capacity planning is about whether the supply exists to deliver what has been approved. They meet at the approval decision, where a new demand should be tested against the capacity it consumes. Running them separately is how portfolios approve more than they can staff. See demand management for the intake side.

How far in advance should you plan resource capacity?

Match the grain to the horizon. Plan named people by week for the next four to six weeks, teams by month for the next two quarters, and roles by quarter for the next four. Beyond a year, plan only a total capacity envelope. Naming individuals nine months out claims a precision the data does not support and costs the plan its credibility.

Where this fits alongside the rest of resource management

Swipe to see more →