Capacity Planning: How to Match Your Team to Demand

Capacity planning is the process of working out whether your people, time, tools and budget can deliver the work you expect to win, and deciding what to change when they cannot. You compare the hours you can realistically deliver with the hours your demand requires, spot the gap early, and close it before customers or staff feel it. This guide shows how to do that in a small or mid-sized business, with a worked example, the main strategies and a clear answer on how capacity differs from capability.

TL;DR

• Capacity is how much work you can deliver in a period. Capability is what your business is able to do well at all. You plan the first and build the second.
• Start with usable hours, not contracted hours: subtract leave, meetings and admin from total potential hours, then leave a buffer for unplanned work.
• Choose a lead, lag or match strategy by the lead time of additions and the cost of turning work away, not by habit.
• Plan on a rolling three- to six-month horizon and review it regularly, so the plan keeps pace with real demand.
• When the same gap keeps reappearing, the cause is usually capability, not headcount. That is where we work.

Table of Contents

• What capacity planning means in practice
• Capacity vs capability: the difference that matters
• The capacity planning formula and a worked example
• A five-step capacity planning process
• Capacity planning methods and strategies
• Closing the gap between demand and capacity
• How to tell whether your plan is working
• Our perspective: when the problem is capability, not capacity
• Where we can help
• Common capacity planning mistakes
• FAQ
• Sources

What capacity planning means in practice

At its simplest, capacity planning means checking that you have the right resources to meet what is coming: team members with the right skills, enough time and the budget to get the work done. It has two failure modes. Overcapacity wastes resources through underuse, and undercapacity leaves you unable to meet demand. Most owner-managed businesses feel the second one first: late delivery, a stretched founder, slow responses to new enquiries. The first one is quieter but just as costly, because idle salaried time is paid for either way.

The output is a resource plan. A professional body for engineers describes it as a plan that aligns workforce, equipment, facilities and materials with projected workloads. For a services firm that usually means three things: a view of demand, a view of usable supply, and a short list of decisions about the gap between them.

You will see several labels for the same idea. Resource capacity planning concentrates on who is available and for how many hours. Team capacity planning applies the same logic to a single team, often one that delivers projects or client work. Workforce planning is the wider discipline: it balances labour supply (skills) against demand (numbers needed) to get the right people with the right skills in the right place at the right time. Capacity planning is the near-term, hours-based slice of that.

Capacity vs capability: the difference that matters

The two words are used interchangeably and they should not be.

A business can have plenty of capacity and weak capability: five people with free time who cannot run a repeatable sales process. It can also have strong capability and thin capacity: a brilliant delivery method that only the founder can run. Adding people to the second case helps. Adding people to the first case just adds cost.

The practical consequence is that capacity planning tells you the size of the gap, and capability tells you whether the gap is worth filling with more people or with a better way of working. If you want to see how capability is mapped around a single commercial decision, our piece on capability mapping for strategists walks through it.

The capacity planning formula and a worked example

There is no single official formula, and published versions are simple by design. One widely used approach defines capacity as total employee work hours per week or, in manufacturing, physical output per period. Another recommends taking total potential hours and subtracting time off and meetings to reach current capacity. Put together, the working formula for a service team is:

Usable capacity = (contracted hours − leave − meetings − internal admin) × target utilisation

The target utilisation matters. Guidance from one project software provider suggests planning for 75 to 80 per cent utilisation to leave room for unplanned work and urgent requests. Treat that as a starting range to test against your own history, not a rule.

Worked example: a five-person advisory team

These figures are illustrative assumptions, so replace them with your own.

1. Contracted hours: 5 people × 37.5 hours = 187.5 hours a week.
2. Average leave across the year: 3 hours a person a week, so 15 hours.
3. Meetings: 4 hours a person, so 20 hours.
4. Internal admin, business development and training: 3 hours a person, so 15 hours.
5. Available hours: 187.5 − 15 − 20 − 15 = 137.5 hours.
6. At 80 per cent utilisation, plannable delivery capacity: 110 hours a week.

Now set demand against it. Suppose confirmed work needs 85 hours a week next month, and a probable project in your pipeline needs another 25. Total demand is 110 hours, which exactly meets supply, with no margin if the probable project arrives late or the scope grows. If a second probable project of 20 hours lands, you are 20 hours short. That is a decision, not a surprise: you now have time to choose how to close it.

Separate confirmed demand from pipeline demand. Weighted pipeline (hours multiplied by your honest win probability) gives a more usable number than treating every proposal as certain.

A five-step capacity planning process

People search for “the 7 steps” or “the 8 steps”, and published lists differ. The logic underneath is the same, and five steps cover it for a business of this size.

1. Fix the unit and the horizon

Choose the unit that fits how you sell: hours for client work, tickets or placements for a recruiter, units for a producer. Then choose a horizon. A rolling three- to six-month window is suggested as a better fit than rigid annual plans, because long, very specific plans tend to be wrong when the future is uncertain.

2. Clean your data

Before any forecast, the input data has to be set up and cleaned so the forecast can use it. That is the stated prerequisite in enterprise resource-management documentation, and it applies equally to a spreadsheet. Pull actual hours from timesheets rather than estimates, and note which work was planned and which was not.

3. Forecast demand

Start from confirmed work, add weighted pipeline, then add a realistic allowance for repeat and unplanned requests from your history. Forecasting methods range from expert judgement and historical data analysis to regression, scenario planning and time-series modelling, as one resource-planning guide lists. For most small firms, historical data plus scenario planning (a low, expected and high case) is enough.

4. Measure usable supply and find the bottlenecks

Apply the formula above, person by person where roles differ. Then look beyond the total. Check whether anyone is overloaded or whether tasks depend on one person’s special skill. A team with 20 spare hours in total still has a problem if the missing hours are in the one skill the work needs.

5. Close the gap, then review

Decide the response (see the strategies below), record the assumption behind it, and schedule the next review. Plans stay accurate through constant feedback and review. A monthly check of forecast against actual hours is enough to catch drift.

Capacity planning methods and strategies

Three strategies describe when you add capacity relative to demand, as set out by a professional engineering body:

The same source notes that the right choice depends on the lead time of additions, the cost of unsatisfied demand and competitive dynamics. In plain terms: if a good consultant, recruiter or developer takes four months to find and onboard, waiting for demand to prove itself (lag) means being short for at least four months.

Hard and soft planning

Numbers alone are not enough. The CIPD distinguishes “hard” workforce planning, which is about numbers, from “soft” strategic planning, which gives a framework for judging information in context and identifying what drives performance. Use the formula to find the gap, and judgement to decide what kind of person, process or tool should fill it.

Planning under uncertainty

Modern practice treats capacity planning as an agile cycle with quick adjustments based on project feedback and changing market conditions. If your demand is volatile, for instance because you rely on a few large clients, shorten the horizon and widen your scenarios. Some firms use data-driven forecasting to cope with this, and AI-assisted capacity planning for enterprises is one route when volumes and data justify it. For a ten-person firm, a disciplined spreadsheet reviewed monthly usually does more good than a new tool.

Closing the gap between demand and capacity

When demand exceeds usable supply, you have a limited set of levers. In rough order of speed:

• Reschedule. Move start dates where clients can accept it, and tell them early.
• Reprioritise. Drop or delay work that earns least. The reasoning in our guide to choosing what to build next applies to commercial work as much as product work.
• Flex supply. Use associates, overtime within sensible limits, or temporary support.
• Hire or train. The slow, durable option, which is why it belongs in a lead strategy.
• Change the work. Standardise, template or automate the repeated parts so each hour goes further.

When supply exceeds demand, the options mirror these: redirect time to business development, to internal capability or to a service you have been postponing. Spare capacity is only valuable if you spend it on purpose.

Physical space is part of capacity too. If you run hybrid teams, desk and room numbers can create the same over- and undercapacity problem as hours do, and office space planning for hybrid teams is worth working through before you sign or renew a lease.

How to tell whether your plan is working

A plan that nobody checks is a document, not a control. Measure it by regularly reviewing outcomes and evaluating the actions and solutions you chose. Four simple measures do most of the work:

1. Forecast accuracy: planned hours against actual hours by month.
2. Utilisation: actual billable or delivery share of available hours, compared with your target range.
3. Delivery against date: how often work finishes when promised.
4. Unplanned share: the proportion of hours spent on work you did not forecast. If it keeps exceeding your buffer, the buffer is wrong.

Keep resources, timelines and utilisation in a single source of truth so everyone argues about decisions and not about whose spreadsheet is right. Treat it as a continuous cycle rather than a one-off exercise. Equally, do not over-engineer: the cost of building a plan should not outweigh its benefit.

Meeting rhythm helps here. A short weekly capacity check and a deeper monthly review keep the plan alive without swallowing time. Our note on how often each meeting should happen sets out a workable cadence.

Our perspective: when the problem is capability, not capacity

We see the same pattern in founder-led professional services firms and recruitment businesses. The capacity plan says the team is stretched, so the instinct is to hire. Sometimes that is right. Often the stretch comes from work that only one or two people can do, from sales and delivery that are not aligned, or from processes that live in someone’s head.

Before adding headcount, we ask three questions. Which decisions or tasks always route back to the founder? Which work is repeated but never standardised? Which gap keeps returning every quarter however many people we add? If the answers point to the same few places, the next hire will inherit the same bottleneck. That is a capability gap, and the cheaper, more lasting fix is to design the process, put it in writing and embed it.

This is why we work in stages: Build, Iterate, Optimise, Embed and Grow. You start with a launch-ready foundation, then improve what the evidence shows is weakest, and finally make it part of how the business runs. For founder-heavy firms the same logic is explored in scaling a founder-led recruitment business without scaling the founder, and for the structure behind it in operating model design.

Capacity planning remains essential. It tells you where the pressure sits. We would simply add one habit: when a gap persists for two planning cycles, stop asking how many more hours you need and ask what the business cannot yet do reliably.

— Chris

Where we can help

If your capacity plan keeps showing the same strain, we can help you work out whether it is a resourcing issue or a capability one, and build the fix. Our Foundation stage gives you a launch-ready base, and our approach is described in how we deliver a launch-ready Foundation in four weeks. After that, ongoing support is available through Managed Capability at £999 per month, £2,850 per quarter or £10,000 per year, with the full detail on our pricing page.

If you would rather talk it through first, you can book a discovery call and we will look at where your capacity is going and what is holding it back.

Common capacity planning mistakes

• Planning on contracted hours. Thirty-seven and a half hours in the contract is not 37.5 hours of delivery. Subtract leave, meetings and admin first.
• No buffer. A plan at 100 per cent utilisation breaks the first time an urgent request arrives.
• Treating the pipeline as certain. Weight it by honest probability.
• Ignoring skills. Total hours can look healthy while the one skill you need is fully booked.
• Planning once a year. Long, precise plans age quickly. Roll the horizon forward.
• Forgetting your own time. Founders often leave out the hours they spend selling, managing and firefighting, then wonder why the numbers do not add up.

FAQ

What is the formula for capacity planning?

There is no single standard, but a practical version is: usable capacity equals contracted hours minus leave, meetings and admin, multiplied by a target utilisation. Published guidance suggests subtracting time off and meetings from total potential hours. Compare the result with forecast demand in the same unit and period to see the gap.

What is the difference between capacity and capability?

Capacity is how much work you can deliver in a period, usually measured in hours or units. Capability is what your business can do well and repeatably, through its skills, processes and systems. Capacity gaps are closed by adding or flexing resources, while capability gaps are closed by designing and embedding better ways of working.

What is the difference between capacity planning and resource planning?

They overlap heavily. Resource planning assigns specific people and tools to specific work, while capacity planning looks at whether total supply can meet total demand over a period. In a small business you will usually do both in the same spreadsheet, starting with capacity to see the size of the gap and then resourcing to assign the work.

How often should I review a capacity plan?

Check forecast against actual hours at least monthly, and keep a rolling three- to six-month horizon so the plan moves with demand. Review sooner whenever you win or lose a large client, or when someone leaves or joins. A plan treated as a continuous cycle stays far more accurate than one rewritten once a year.

Sources

• Workforce planning factsheet, CIPD
• Capacity planning, IEEE Technology Navigator
• Creating Demand Forecast Models, Oracle PeopleSoft documentation
• What Is Capacity Planning? IBM
• Capacity Planning: Process, Strategies and Team Success, Asana
• Capacity Planning Defined, NetSuite
• Resource Capacity Planning Guide, Smartsheet
• Capacity Planning: Types, Strategies and Best Practices, monday.com
• The lean portfolio leader’s guide to capacity planning, Atlassian
• Office space planning for hybrid teams
• AI capacity planning for enterprises

Recommended

• Scaling a founder-led recruitment business without scaling the founder
• Capability Mapping for Strategists: Build Around One Decision
• Meeting Cadence: How Often Each Meeting Should Happen
• Cross-Functional Alignment: How to Get Teams Pulling Together