Project Management guide · Cost and resources
Capacity Planning in Project Management: Guide and Example
Capacity planning is the process of comparing the work an organisation or team needs to do with the time and skills it actually has available. It shows in advance where demand will exceed capacity, so you can reprioritise, hire or reschedule before projects slip.
Key takeaways
- Capacity planning compares demand with real productive capacity.
- Subtract leave and non-project time before comparing.
- Plan by skill, not just by headcount.
- Review monthly and keep a small unallocated buffer.
Capacity vs demand vs allocation
| Term | Meaning |
|---|---|
| Capacity | The productive hours a team or person can supply in a period |
| Demand | The hours of work requested by projects and business-as-usual activity |
| Allocation | Which work is assigned to which person; see resource allocation |
| Utilisation | Allocated hours divided by available hours, as a percentage |
Allocation works at task level within one project. Capacity planning usually works across a whole team, department or portfolio and over months rather than days.
How to do capacity planning step by step
- Choose the scope (a team, skill group or department) and the planning horizon, for example the next quarter.
- Calculate gross capacity: people x hours per week x weeks.
- Subtract planned leave, public holidays and training.
- Apply a productive-time factor for meetings, admin and support work.
- Gather demand from every project and from business-as-usual work, by skill.
- Compare demand with capacity for each skill and period to find gaps or surplus.
- Close gaps by reprioritising, rescheduling, hiring, contracting or cutting scope, then review monthly.
Worked example: one month for a team of five
A design team has five people working 40-hour weeks. The month has four working weeks. Planned leave totals 40 hours. Experience shows about 20% of time goes on meetings, admin and support.
| Step | Calculation | Hours |
|---|---|---|
| Gross capacity | 5 people x 40 h x 4 weeks | 800 |
| Less leave | 800 - 40 | 760 |
| Productive capacity | 760 x 80% | 608 |
| Demand source | Hours |
|---|---|
| Project A (website redesign) | 320 |
| Project B (brand refresh) | 240 |
| Business-as-usual requests | 120 |
| Total demand | 680 |
Demand of 680 hours exceeds productive capacity of 608 hours by 72 hours, roughly 12% over. Options include moving 72 hours of Project B into next month, bringing in a freelancer for about two weeks, or asking the business to pause lower-priority requests. Expressed in full-time equivalents, the gap is 72 / (160 x 80%) = 0.56 FTE for the month.
Approaches to capacity planning
| Approach | Description | When to use |
|---|---|---|
| Lead strategy | Add capacity before demand arrives | Growth is certain; delay is costly |
| Lag strategy | Add capacity only once demand is confirmed | Budgets are tight; demand is uncertain |
| Match strategy | Add capacity in small steps as demand grows | Most project organisations |
| Team-based (Agile) | Fix team size and prioritise work into it | Stable product teams; see agile capacity planning |
Common mistakes
- Counting people at 40 productive hours a week.
- Ignoring business-as-usual and support work, which quietly consumes capacity.
- Planning by headcount rather than by skill, so a surplus of testers hides a shortage of developers.
- Treating the plan as a one-off exercise instead of reviewing it monthly.
- Letting every project assume it has first call on shared specialists.
Who owns capacity planning?
In many organisations the project management office or resource managers own the capacity view, while project managers supply demand forecasts. Portfolio decisions about which projects to start should be based on this view; see managing multiple projects.
Free templates for this topic
Frequently asked questions
What is capacity planning in project management?
It is comparing the work demanded by projects and day-to-day operations with the productive time and skills available, so gaps can be fixed in advance.
How do you calculate team capacity for capacity planning?
Multiply people by working hours and weeks, subtract leave and holidays, then apply a productive-time factor such as 75-80% for meetings and admin.
What is the difference between capacity planning and resource planning?
Capacity planning looks at total supply versus demand across a team or portfolio; resource planning and allocation assign specific people to specific tasks.
What is a good utilisation rate in capacity planning?
There is no single right figure, but planning people at around 70-85% for project work usually leaves room for meetings, support and surprises.
What is the difference between capacity and availability in capacity planning?
Availability is the time someone is at work and not on leave; capacity is the productive part of that time that can be given to planned work.
How often should capacity plans be updated?
Monthly is common for portfolios, and weekly or every sprint for individual teams.
What are lead, lag and match strategies in capacity planning?
Lead adds capacity ahead of demand, lag waits until demand is confirmed, and match adds capacity in small steps as demand grows.
How does capacity planning work in Agile?
Teams estimate their capacity for each sprint from availability and past velocity, then commit only to the work that fits; see agile capacity planning.
What does capacity planning do when demand exceeds capacity?
You must reprioritise, reschedule, add people, outsource or reduce scope; otherwise work slips and people burn out.
What tools are used for capacity planning?
Spreadsheets for small teams, or the workload and portfolio views in project management software.
How does FTE relate to capacity planning?
FTE expresses capacity and demand in full-time-person units, which makes gaps easy to compare; see full-time equivalent.