What is Capacity Planning?

How to Calculate Team Capacity

Capacity calculation starts with gross available hours, then subtracts non-project time:

• Gross capacity — team size × working hours per week (e.g., 8 people × 40 hours = 320 hours/week)
• Subtract meetings and admin — typically 20–25% (320 × 0.75 = 240 hours available for project work)
• Subtract leave and holidays — account for planned time off per person per period
• Subtract ramp-up time for new projects — first week on a new project is rarely full productivity
• Net capacity — the realistic hours available for committed project work

Matching Capacity to Demand

Once you know capacity, compare it to the planned work (demand). If demand exceeds capacity, you have three options:

Reduce demand — push a project start date, reduce scope, or decline new work.

Increase capacity — bring in contractors, redistribute work from overloaded to underloaded team members, or authorize overtime (short-term only).

Renegotiate timelines — extend deadlines on lower-priority projects to create room for higher-priority ones.

Capacity planning works best as a rolling process — reviewed weekly as new projects are added and existing timelines shift. A weekly 15-minute capacity check is worth more than a monthly deep-dive that's already stale by week two.

Tools for Capacity Planning

Effective capacity planning requires two data sources: planned work (what projects are coming and how many hours they need) and actual utilization (how much time the team is currently spending per project).

Time tracking provides the actual utilization data. Without it, capacity planning is guesswork — you can plan 200 hours of project work but if you're not tracking, you won't know if 200 hours or 280 hours were actually spent.

Work reports that show hours per person per week, per project, make it possible to compare planned vs actual and catch overloads before they become crises.

Weekly Capacity Review Process

Capacity planning only works if you do it consistently. A monthly review is too infrequent — by the time you spot an overcommitment, it's already a crisis. A weekly 15-minute review is the right cadence for most teams running 3-8 simultaneous projects.

The review has three steps. First, pull available hours for the coming two weeks — account for any planned time off, public holidays, or known non-project days.

Second, sum up all committed project work for those two weeks. Use task estimates from your project board, not gut feel. If you don't have estimates, the review won't work.

Third, compare the two numbers. If committed work exceeds 85% of available hours, you have a problem to resolve before the week starts — not after people start missing deadlines. Resolution options: push a lower-priority project's tasks to the following week, reassign tasks from overloaded to underloaded team members, or have a conversation with a client about timeline adjustment.

• Pull gross available hours for the coming two weeks per team member
• Sum all committed project hours from task estimates on the board
• Flag anyone over 85% capacity and resolve before the week starts
• Document every rebalancing decision made during the review
• Run the review at the same time each week — Friday morning works well for many teams

Capacity Planning for a Growing Team

Adding a team member changes your capacity math in ways that aren't immediately obvious. The raw numbers look good — 8 people becomes 9, that's a 12.5% capacity increase. But a new hire at a 10-person agency typically delivers at 40-60% productivity for the first 4-6 weeks. Onboarding takes time. Pairing them with a senior team member pulls that person's capacity down too.

This means the first month after hiring, your effective capacity might actually decrease slightly before it increases. Don't commit new projects expecting immediate full capacity from a new hire.

Capacity planning also changes when the team grows past 10 people. Below 10, one person can usually hold team capacity in their head. Above 10, you need a system: a spreadsheet, a resource management module, or work reports showing hours per person per week.

• New hires typically deliver 40-60% productivity in weeks 1-4
• Senior pairing for onboarding reduces that person's capacity temporarily
• Expect a 2-4 week capacity dip before a new hire adds net capacity
• Teams above 10 people need a system, not memory, to track capacity
• Build capacity tracking habits early — retrofitting them at 15+ people is painful

Capacity Planning Mistakes

Most capacity planning failures come from the same set of mistakes.

Using gross hours, not net hours. A team member working 40 hours per week is not available for 40 hours of project work. Subtract meetings, internal admin, email, and non-project obligations. Realistic project capacity is 28-32 hours, not 40.

Ignoring the planning fallacy. People consistently underestimate how long tasks take. Buffer your estimates by 20-30% on tasks with high uncertainty.

Not accounting for context switching. A team member assigned to five projects simultaneously is not working at full speed on any of them. Context switching can consume 20-40% of productive time.

Treating the plan as a contract. Capacity plans are forecasts, not commitments. New client requests, tasks taking longer than estimated, unexpected absences — all of these change the capacity picture. Update the plan weekly.

Not involving the team. Capacity planning done only by managers misses what team members know about their own workloads.

• Using gross hours (40/week) instead of net project hours (28-32/week)
• No buffer for estimation errors — add 20-30% to uncertain task estimates
• Ignoring context switching costs when someone is on 4+ projects
• Treating the plan as fixed rather than updating it weekly
• Planning without input from the team members doing the work