Resource capacity planning for delivery teams

Resource capacity planning is the practice most delivery teams know they need and few do well. The symptoms of poor capacity planning are everywhere: missed deadlines, quality issues, team burnout, and the constant feeling that everyone is working on too many things at once.

The root cause is almost always the same. The portfolio has more work allocated than the team can deliver. Not because anyone made a bad decision, but because nobody has a clear view of total demand versus available capacity.

Capacity planning does not need to be complex. For most delivery teams, it means answering one question with reasonable accuracy: do we have enough people to deliver what we have committed to?

Why capacity planning fails

Most teams attempt capacity planning and abandon it within a quarter. The common failure modes are:

Too granular. Trying to plan capacity at the hour level for every person creates a maintenance burden that nobody sustains. The plan is out of date before the ink dries.

Disconnected from the portfolio. Capacity planning that happens in a separate spreadsheet from the project portfolio is always slightly wrong. The two views drift apart because they are maintained independently.

Ignores non-project work. Teams do not spend 100% of their time on projects. Meetings, admin, support, and unplanned work consume 20–40% of available time. Capacity plans that ignore this over-allocate by default.

No feedback loop. A capacity plan that is created once and never updated is a forecast, not a management tool. Without regular comparison of planned versus actual, the plan becomes fiction.

A practical approach to capacity planning

Here is a framework that works for delivery teams of 10–100 people without requiring a dedicated resource management tool:

Step 1: Define available capacity

For each team member, define their available capacity in simple terms. Most teams use a percentage model:

• Full-time on projects: 70–80% of total time (the rest goes to meetings, admin, and support)
• Part-time on projects: 40–50% of total time
• Leadership roles: 20–30% of total time

Do not try to plan at the hour level. Percentages are accurate enough for portfolio-level decisions and much easier to maintain.

Step 2: Map demand from the portfolio

For each active project, estimate the resource demand in the same units. How much of each person's capacity does this project need this month?

Again, keep it simple. "This project needs 50% of Sarah's time for the next six weeks" is more useful than a detailed hour-by-hour allocation that nobody maintains.

Step 3: Compare demand to supply

Add up the demand across all projects for each person. If anyone is allocated above 85%, they are over-committed. If the team average is above 80%, the portfolio is at risk of delivery failures.

This comparison is the core of capacity planning. It tells you whether your commitments are realistic given your available resources.

Step 4: Make decisions

When demand exceeds supply (and it usually does), you have four options:

1. Defer work. Move lower-priority projects to a future period.
2. Reduce scope. Deliver less on some projects to free up capacity.
3. Add resources. Hire, contract, or reassign people to increase supply.
4. Accept the risk. Proceed knowing that something will slip, and decide in advance what that will be.

All four are valid. The worst option is the implicit fifth: pretend the over-allocation does not exist and hope everything works out.

Step 5: Review monthly

Capacity plans should be reviewed monthly at minimum. Compare planned allocation against actual work. Adjust for changes in the portfolio — new projects, completed projects, scope changes, and team changes.

The 85% rule

A useful heuristic for capacity planning is the 85% rule: never allocate more than 85% of anyone's available capacity to planned work.

The remaining 15% is buffer for unplanned work, support requests, meetings that run long, and the inevitable surprises that every delivery team faces. Teams that plan to 100% utilisation have no margin for error and consistently miss deadlines.

This is not about being conservative. It is about being realistic. No team operates at 100% efficiency, and planning as if they do creates a gap between the plan and reality that grows every week.

Real-world example

A consulting firm with 35 consultants was consistently missing delivery deadlines despite everyone working long hours. The managing partner assumed the team needed to work harder. The operations lead suspected they needed to work on fewer things.

They implemented a simple capacity view: each consultant's allocation across active engagements, expressed as a percentage. The result was stark — twelve consultants were allocated above 100%, and the team average was 94%.

The fix was not working harder. It was deferring three lower-priority engagements to the next quarter and reducing scope on two others. Within a month, on-time delivery improved and overtime hours dropped.

Best practices

Plan at the right granularity. Monthly or fortnightly allocation percentages are sufficient for most teams. Weekly or daily planning creates unsustainable overhead.

Include non-project time. Account for meetings, admin, support, and leave. A person with 40 hours per week does not have 40 hours of project capacity.

Make over-allocation visible. When someone is allocated above 85%, flag it on the portfolio dashboard. Make it a governance issue, not a personal problem.

Connect capacity to intake. Before approving a new project, check whether the team has capacity to deliver it. If not, something else needs to move.

Track actuals against plan. Monthly, compare what was planned against what actually happened. This calibrates future estimates and reveals systematic biases.

How Praxiox helps

Praxiox connects project assignments to team capacity in one workspace. When a team member is assigned to multiple projects, their allocation is visible across the portfolio. Over-allocation surfaces on the dashboard before it becomes a delivery problem.

The portfolio view shows resource demand alongside project health, so the PMO can make informed decisions about whether to approve new work or defer existing commitments.

For teams building a capacity practice, the PMO use case shows how resource visibility works alongside portfolio governance. The project prioritization framework explains how to make decisions when demand exceeds supply.

Rolling this out

A good rollout starts small enough that the team can keep it up without extra admin. Pick one workflow, one owner, and one review cadence. If it works there, scale it. If it does not, simplify before you widen the scope.

The useful questions are straightforward: what changes, who updates it, and what gets reviewed. If those answers are clear, the process usually sticks because it saves more time than it costs.

1. Pick the part of the workflow that creates the most chasing or copying.
2. Move that information into one place so people are not rebuilding the same status twice.
3. Review it after two cycles and remove anything nobody uses.

The person who owns the rollout should already be close to the work. If someone has to chase updates just to keep the process alive, the setup is still too heavy. Keep the cadence small enough that the team can finish the review in the same meeting they already have.

The features page shows the kind of workflow that keeps the work and the reporting together. The PMO use case shows how the same structure scales across a portfolio.

The point is to make the new habit lighter than the old one. When the first version feels easy, people keep using it. When it feels like a second job, it will stall.

How to tell it is working

The process is working when the team stops asking where the latest version lives. You see fewer reminders, fewer surprise escalations, and fewer meetings spent re-creating the same status.

Watch for three signs:

• people update it without being chased
• meetings get shorter because the status is already visible
• decisions move faster because the facts are current

The real signal is trust. When people stop keeping their own shadow list and start relying on the shared view, the system has begun to work properly.

The features page shows the kind of setup that makes those signals easier to see. The PMO use case shows the same behaviour at portfolio level.

If those signs do not move, the workflow is still too hard to maintain. The fix is usually to simplify the steps people touch every week, not to add another rule.

Practical next step

If Resource capacity planning for delivery teams is still too manual, begin with the most repetitive step in the workflow and remove the copy-and-paste work around it. The aim is not to automate everything on day one. The aim is to make the weekly process easier to maintain than the old one.

Do not try to automate the hardest process first. Start with something frequent, predictable, and easy to understand. Once the team sees a clean win, it becomes much easier to tackle the next workflow.

A good test is whether the automation removes an action people dislike doing manually every week. If it does, the team will notice the difference immediately.

The features page shows how the workflow stays connected to the work. The PMO use case shows how the same structure plays out in a live operating model.

After two cycles, review what people are still doing outside the system. If the answer is “copying status,” “asking for the latest version,” or “keeping a backup spreadsheet,” the process still needs one more simplification pass. If the answer is “nothing,” the change is probably small enough to stick.

Frequently asked questions

What is resource capacity planning?

Resource capacity planning is the practice of comparing the demand for people's time (from active and planned projects) against their available capacity. It helps teams avoid over-commitment and make realistic delivery promises.

How granular should capacity planning be?

For most delivery teams, monthly or fortnightly allocation percentages are sufficient. Planning at the hour or day level creates unsustainable maintenance overhead without proportionally better decisions.

What percentage of capacity should be allocated to projects?

Aim for 70–80% of total available time allocated to project work. The remaining 20–30% covers meetings, admin, support, and unplanned work. Never allocate above 85% without accepting delivery risk.

How do I handle capacity planning for part-time team members?

Define their available project capacity as a percentage of their total time, then allocate against that reduced number. A person who is 50% available for projects has a different capacity ceiling than someone who is 80% available.

What do I do when demand exceeds capacity?

Defer lower-priority work, reduce scope on some projects, add resources (hire or contract), or accept the risk and decide in advance what will slip. The worst option is ignoring the over-allocation.

How often should capacity plans be updated?

Monthly at minimum, with ad-hoc updates when significant changes occur (new projects approved, team members leaving, scope changes on major projects).