Resource Capacity Forecasting: Planning Past This Quarter

Knowing you're overallocated this week is the easy half of the problem. The harder half is knowing whether you'll be able to staff the pipeline three months from now, before the projects in it are even approved.

Resource capacity forecasting models committed capacity against available capacity across a future horizon, typically one to two quarters out, using the pipeline of proposed and approved work rather than only what's already staffed. It answers a question a utilization report can't: not "is anyone overloaded today" but "will we be able to staff what's coming, and when does the gap first show up."

Direct answer: A capacity forecast compares two lines moving forward in time: committed capacity (what your current resource pool can deliver) and pipeline demand (what the approved and likely-approved project list will require). Where those lines cross is the point a staffing gap becomes real, and hiring lead time determines how far before that crossing point you need to act.

Why Utilization Reports Don't Forecast Anything

A utilization report is a snapshot: it tells you who is overloaded this week, based on assignments that already exist. That's a useful and different question from forecasting, and conflating the two is the most common capacity mistake a PMO makes.

Utilization is a lagging indicator; it can only see work that's already been assigned. Forecasting is a leading indicator: it has to account for the projects still sitting in demand management or portfolio scoring that haven't been staffed yet, because those are the projects that will consume next quarter's capacity even though no assignment exists for them today. A team can look perfectly healthy on this week's heatmap and still be three approved projects away from a staffing crisis nobody has modeled.

What Resource Capacity Forecasting Actually Models

A forecast needs two sides of the same ledger, converted to a shared unit so they can actually be compared.

The supply side is committed capacity: the resource pool, by role or skill, at its real availability after accounting for planned time off, training, and existing commitments, plus any confirmed hiring or attrition already on the calendar. The demand side is the pipeline: every approved project's estimated effort, plus proposed projects weighted by how likely they are to be approved, not just the projects that already have staff assigned. FTE-weeks or person-days are the usual common unit; without one, demand and supply are two lists that can't be subtracted from each other.

The gap between the two lines is not a single number. It usually appears first in one role or skill area, months before the aggregate headcount looks short, which is why a forecast broken down by skill catches problems an aggregate FTE count misses entirely.

Building a Rolling Capacity Forecast

1. Pull committed capacity from confirmed assignments across every active project, not one project manager's view of their own team.
2. Add the pipeline: every proposed and approved-not-yet-started project, weighted by approval probability if it's still moving through demand management scoring.
3. Convert both sides to a common unit, FTE-weeks or person-days, so demand and supply can be compared directly instead of eyeballed.
4. Overlay hiring and contracting lead time. A role that takes ten weeks to fill needs its forecast trigger to fire ten weeks before the gap actually opens, not the week it opens.
5. Re-run the forecast monthly, and immediately whenever a project large enough to move the pipeline gets approved or cancelled.

Reading a Forecast: A Worked Example

The diagram below shows the pattern a forecast is built to catch: committed capacity holds roughly flat while pipeline demand climbs, and the two lines cross before the team's current workload looks like a problem on any single week's heatmap.

Reading this pattern in a numeric table makes the trigger point concrete. A ten-week hiring lead time means the forecast has to trigger action in month two, two months before the lines actually cross in month four.

Month	Committed capacity (FTE-weeks)	Pipeline demand (FTE-weeks)	Gap
1	180	150	None
2	178	165	Trigger hiring if lead time is 8+ weeks
3	176	178	Gap closing, no headroom left
4	175	190	15 FTE-weeks short
5	174	205	31 FTE-weeks short

Where the Gap Shows Up First

Aggregate FTE counts hide the more common failure mode: the organization has enough total headcount, just not the right skill mix. A forecast broken out by role or skill, senior backend engineers versus junior QA, for example, catches a specialist shortage months before the blended number looks short, because a surplus of one skill can mathematically cancel out a shortfall in another on an aggregate view while leaving the actual bottleneck completely unaddressed.

Start from your team's current resource utilization heatmap as the baseline for committed capacity, then project the pipeline forward from there. The heatmap gives you an accurate today; the forecast is what you build on top of it to see three months out instead of this week.

Turning a Forecast Into a Decision

A forecast that identifies a gap without a decision attached to it is just a chart. Once the crossing point is visible, there are three responses, and the lead time on each is different: hire or contract for the specific skill gap (slowest, needs the earliest trigger), delay or re-sequence a lower-priority project in the pipeline (fast, but has its own downstream cost), or accept a defined period of overallocation with an explicit end date rather than an open-ended one.

The same committed-vs-pipeline distinction that separates capacity planning from task-level resource planning applies here: a forecast tells the portfolio committee whether to approve the next project, while a resource manager uses it to plan hiring and reassignment months ahead of the point where overallocation would otherwise show up as a silent surprise on next quarter's heatmap.

Start your forecast from real utilization data Run the free Resource Heatmap on your current portfolio to get an accurate baseline for committed capacity in about 30 seconds, no signup required. → Open the Resource Heatmap