# PMO Capacity Planning: Why Your Portfolio Is Overcommitted and Nobody Knows It

**Category:** PMO
**Author:** AI Assistant
**Published:** 2026-05-12
**Read Time:** 6 min read

## Summary
The UK government's 734-project, £718bn pipeline proves portfolio-level capacity planning works. Your PMO is still allocating resources project-by-project. Here is how to fix it. PMO module from £49/month.

## Full Content
# Your PMO Approved 15 Projects. You Have Capacity for 9. Nobody Noticed Until Three of Them Failed.

**The UK Government's latest infrastructure pipeline, published March 2026 by NISTA, lists 734 projects worth £718 billion over 10 years. It includes resource forecasts, skills requirements, and regional demand projections. It is the most sophisticated portfolio-level capacity plan in the country. Most private sector PMOs cannot tell you how many projects they are running, let alone whether they have the people to deliver them.**

That gap is not a technology problem. It is a governance problem.

Portfolio-level capacity planning is the discipline of matching resource supply to project demand across the entire portfolio, not project by project, but as a connected system. When done properly, it prevents the single most common cause of project failure: overcommitment.

When done badly, or not at all, it produces a predictable pattern. Too many projects approved. Not enough people to deliver them. Resources stretched across multiple workstreams. Quality drops. Deadlines slip. The PMO reports everything as "amber" because nobody wants to be the person who says "we have committed to more work than we can physically deliver."

## The Overcommitment Problem

PMI research consistently shows that high-maturity PMOs drive strategic execution. But most PMOs never reach high maturity because they are optimised for project approval, not portfolio capacity.

The typical PMO approval process works like this:

1. A project is proposed with a business case.
2. The business case is reviewed against strategic priorities.
3. If approved, resources are "allocated" from a resource pool.
4. The project starts.

The failure happens at step 3. "Allocated" usually means "named on a spreadsheet." It does not mean "actually available to do the work." The same senior engineer appears on four project plans simultaneously. The same subject matter expert is "20% allocated" to five projects, which is 100% of their time, except they also have a day job.

**The result:**

- 60% of projects experience resource conflicts that the PMO does not detect until delivery is impacted.
- Senior resources spend 30% of their time context-switching between projects, which research shows reduces productivity by up to 40%.
- Projects that should take 6 months take 10, not because the work is harder, but because the people doing it are spread too thin.

## What Portfolio-Level Capacity Planning Actually Looks Like

The UK Government's NISTA pipeline is instructive. It does not just list projects. It forecasts:

- **Worker numbers** required per project, per phase, per region.
- **Skills demand** mapped against available supply.
- **Timing dependencies** showing when demand peaks will occur.
- **Constraint analysis** identifying where supply gaps will create bottlenecks.

This is not project management. It is portfolio intelligence. And it requires four capabilities that most PMOs lack.

### 1. Demand Aggregation

Every project plan includes resource requirements. But those requirements sit in individual project plans, not in a portfolio view. Demand aggregation means pulling every resource requirement from every active and planned project into a single model.

When you do this, the overcommitment becomes visible immediately. You can see that your 10 business analysts are allocated to 18 months of work that needs to be delivered in the next 12 months. You can see that your two infrastructure architects are both needed full-time on three different projects in Q3.

Without aggregation, each project plan looks feasible. In aggregate, the portfolio is impossible.

### 2. Capacity Modelling

Once you can see demand, you need to model supply. How many people do you actually have? What are their skills? What is their real availability (excluding leave, training, operational support, and the inevitable unplanned work)?

Most PMOs use "headcount" as a proxy for capacity. That is like using "number of cars" as a proxy for motorway throughput. A headcount of 50 tells you nothing about whether those 50 people have the right skills, the right availability, and the right allocation to deliver the portfolio.

### 3. Scenario Planning

With demand and supply modelled, you can run scenarios:

- **What if we delay Project X by one quarter?** Does that free enough capacity to de-risk Project Y?
- **What if we hire two additional developers?** How many projects move from "at risk" to "green"?
- **What if we cancel the lowest-priority project?** What capacity does that release for the rest of the portfolio?

These are strategic decisions. They cannot be made project-by-project. They require a portfolio view.

### 4. Governance Integration

Capacity data must feed into the approval process. When a new project is proposed, the PMO should be able to answer: "Do we have the capacity to deliver this without impacting existing commitments?"

If the answer is no, the governance board has three options: defer the new project, cancel an existing project, or accept the risk of overcommitment. All three are valid decisions. But they must be conscious decisions, not accidental ones.

## The Simplif-i PMO Approach

Simplif-i's PMO module was built for organisations that need portfolio-level visibility without enterprise-level complexity.

**Portfolio dashboard.** All active projects in one view. Not a list of project names. A connected dashboard showing resource allocation, delivery status, risk exposure, and budget consumption across the entire portfolio.

**Resource management.** Cross-project resource visibility. When the same person is allocated to multiple projects, the system shows total allocation as a percentage. Over-allocation is flagged automatically. No manual cross-referencing.

**Delivery tracking.** Milestones, dependencies, and blockers tracked per project and across the portfolio. When one project's delay impacts another project's start date, the cascade is visible immediately.

**Risk and issue management.** Centralised risk register with financial quantification. Every risk has a cost impact, a probability, and an owner. Risks that threaten portfolio delivery are escalated automatically.

**Governance integration.** New project proposals assessed against current portfolio capacity before approval. The governance board sees the impact of approval on existing commitments.

**Connected to everything else.** A project that requires a vendor contract? The Contracts module tracks it. A project with compliance implications? The GRC module tracks it. A project tied to an M&A integration? The M&A module tracks it.

**Pricing:** PMO module from £49/month. Full platform: £149/month founding member pricing.

## A Practical Starting Point

You do not need to build a NISTA-scale capacity model in week one. Start with these three steps:

**Step 1: Count your commitments.** List every active project and every project approved but not yet started. For each, list the key resources required and their allocation percentage. Total it up. If any resource is allocated at more than 80%, you have a capacity problem.

**Step 2: Identify your constraints.** Which roles or individuals appear on the most project plans? These are your bottlenecks. Every decision about project timing and priority should start with these constraints.

**Step 3: Change the approval conversation.** The next time a new project is proposed, before discussing the business case, ask: "Which existing project are we willing to slow down to make capacity for this one?" If the answer is "none," then either the new project waits or you are accepting overcommitment.

The PMOs that treat capacity as a strategic input will deliver more. The PMOs that treat it as an afterthought will keep wondering why everything is late.

**Start a free trial at simplif-i.com. 7 days. Full access. No credit card required.**

---
Source: https://simplif-i.com/api/blog/readable/pmo/pmo-capacity-planning-portfolio-overcommitment
Web Version: https://simplif-i.com/blog/pmo/pmo-capacity-planning-portfolio-overcommitment
© Simplif-i - Unified Business Management Platform