Team Capacity Planner: How to Plan Team Workload

A team capacity planner is a simple tool that answers one of the most important questions in any service business: how much work can your team realistically take on before something breaks? The short answer is that team capacity equals the productive hours your people can deliver in a given period, minus time off and non-billable overhead. Once you know that number, you compare it to the work you have committed and instantly see whether you are overbooked, under-booked, or balanced.

If you have ever promised a client a delivery date and then watched your team scramble through evenings and weekends to hit it, you have felt the cost of planning by gut feel. A team capacity planner replaces guesswork with arithmetic. This guide walks through the exact formula, what every input means, several fully worked examples, how to read the result, and the mistakes that quietly wreck plans. Whether you run a two-person studio or a thirty-person agency, the same logic applies.

What Is a Team Capacity Planner?

A team capacity planner is a calculation (often built into a spreadsheet, project tool, or app) that estimates the total amount of productive work your team can complete in a chosen timeframe - a week, a sprint, or a month. It turns abstract "how busy are we?" feelings into a hard number of hours or days.

Capacity planning sits at the intersection of three things: the people you have, the time they are actually available, and the work waiting in your pipeline. Get the balance right and projects ship on time, margins hold, and nobody burns out. Get it wrong in either direction and you either overload your team or leave billable time on the table.

The planner is not a one-time exercise. It is a living view you revisit each planning cycle, because people take leave, projects slip, and new work arrives. Think of it as a budget - but for time instead of money.

Capacity vs Bandwidth vs Utilization

These three terms get used loosely, so it helps to separate them. Capacity is the total productive hours available. Bandwidth is the slang version of the same idea - "do we have bandwidth for this?" Utilization is the percentage of capacity that is actually filled with billable or planned work. A team can have plenty of capacity but poor utilization if the work is badly allocated.

The Team Capacity Formula

The core formula is straightforward and the same regardless of team size:

Team capacity = (Number of people x Working hours per period) − Planned time off − Non-billable overhead

If you want the result expressed as a usable, billable figure, you can also apply a target utilization rate:

Billable capacity = Available hours x Target utilization rate

And to check whether you are over or under committed:

Capacity balance = Available capacity − Committed work (demand)

A positive capacity balance means you have room to take on more. A negative balance means you have promised more than you can deliver and need to renegotiate scope, deadlines, or staffing.

Understanding Each Input

Each input deserves attention, because the accuracy of your plan depends entirely on honest numbers.

Number of people

This is the count of team members who deliver the work in the period. Be careful with part-timers and people split across functions. A part-time designer at 50% counts as 0.5 of a full-time equivalent (FTE). Anyone who is purely management or sales and does no delivery work should be excluded from delivery capacity.

Working hours per period

This is the standard productive hours per person for your chosen period. A common starting point is a 40-hour week, but many teams plan around a realistic 7 productive hours per day rather than a full 8, because nobody is heads-down for every minute. For a month, multiply your weekly figure by the number of working weeks.

Planned time off

Subtract public holidays, booked annual leave, and a sensible allowance for typical sick days. This is where most spreadsheets drift from reality - a team that looks like it has 160 hours in a month might really have 130 once a public holiday and a few days of leave are removed.

Non-billable overhead

Internal meetings, admin, training, business development, and recruitment all consume real hours that cannot be billed or assigned to client delivery. For most service teams this lands somewhere between 15% and 30% of the working week. Be honest here; pretending overhead is zero is how plans collapse.

Target utilization rate

If you are calculating billable capacity, apply a realistic utilization target - often 70% to 85% for sustainable delivery teams. Pushing utilization toward 100% leaves no buffer for the inevitable surprises, and it is a reliable recipe for burnout.

Worked Examples

Numbers make this concrete. Here are three realistic scenarios worked step by step.

Example 1: A small design studio (weekly)

Maya runs a three-person design studio and plans her workload one week at a time. She wants to know how many billable hours the studio can deliver next week.

• People: 3
• Working hours per person per week: 40
• Raw hours: 3 x 40 = 120 hours
• Planned time off: one designer takes a day off = 8 hours. Remaining: 120 − 8 = 112 hours
• Non-billable overhead: the studio loses about 25% to admin, calls, and revisions internally = 112 x 0.25 = 28 hours. Available delivery hours: 112 − 28 = 84 hours

So Maya can realistically commit around 84 hours of client work next week. If three live projects need 30 hours each (90 hours total), she is 6 hours over and needs to push one deadline or trim scope before saying yes.

Example 2: A marketing agency (monthly)

Devon manages an eight-person delivery team at a marketing agency and plans monthly.

• People: 8
• Working hours per person per week: 38 (realistic, not the full 40)
• Working weeks in the month: 4.2
• Raw hours: 8 x 38 x 4.2 = 1,276.8 hours
• Planned time off: one public holiday (8 hrs x 8 people = 64) plus 5 days of booked leave across the team (5 x 8 = 40 hrs) = 104 hours. Remaining: 1,276.8 − 104 = 1,172.8 hours
• Non-billable overhead at 20%: 1,172.8 x 0.20 = 234.6 hours. Available: 1,172.8 − 234.6 = 938.2 hours
• Target utilization of 80% applied to available delivery time gives a comfortable planning ceiling of 938.2 x 0.80 ≈ 750 hours of committed client work, leaving a buffer for overruns.

Devon's pipeline shows 690 hours of committed work for the month. With a planning ceiling near 750, the team has roughly 60 hours of headroom - enough to take a small new project without strain.

Example 3: A two-person consultancy (sprint)

Priya and a partner run a consultancy and plan in two-week sprints.

• People: 2
• Working hours per person per week: 40, over 2 weeks = 80 each
• Raw hours: 2 x 80 = 160 hours
• Planned time off: none this sprint. Remaining: 160 hours
• Non-billable overhead at 30% (heavy sales and proposal load): 160 x 0.30 = 48 hours. Available: 160 − 48 = 112 hours

Their delivery capacity for the sprint is 112 hours. A signed engagement needs 100 hours of delivery in those two weeks, which fits with a thin 12-hour buffer - workable, but they should not add anything else.

How to Interpret the Result

The raw capacity number only matters once you compare it to demand. Here is how to read the outcome.

A positive capacity balance

If available capacity exceeds committed work, you have slack. A small, deliberate buffer (roughly 10% to 20%) is healthy - it absorbs overruns and last-minute requests. A large, persistent surplus, though, signals under-utilization: you are paying for time you are not selling, and you should be filling the pipeline or trimming cost.

A negative capacity balance

If committed work exceeds capacity, you are overbooked. This is the dangerous state, because the shortfall does not vanish - it gets paid for in missed deadlines, quality dips, or unpaid overtime. The fix is to renegotiate timelines, reduce scope, bring in contractors, or decline new work.

What a "good" number looks like

For a sustainable service team, a target utilization between 70% and 85% is generally considered healthy. Below 70% suggests too much idle or overhead time; above 90% leaves no room for the unexpected and tends to burn people out over time. The right figure varies by industry and business model, so treat these as starting benchmarks rather than rules.

When and Why to Use a Team Capacity Planner

You should reach for a capacity planner whenever you commit your team to dated work. The most common triggers are:

• Before quoting a project - to confirm you can deliver within the proposed timeline.
• At the start of each planning cycle - weekly, sprint, or monthly - to allocate work fairly.
• When considering a new hire - capacity gaps are the clearest signal that you need more people.
• When demand spikes - to decide whether to hire, subcontract, or decline.
• During cash flow forecasting - billable capacity is the upper bound on revenue you can earn from delivery.

The "why" is simple: capacity planning protects both your margins and your people. It stops you from overselling, and it stops your best team members from quietly drowning. For more on translating capacity into pricing, see how the Utilization Rate Calculator and Billable Hours Calculator feed into the same picture.

Capacity vs Demand: A Comparison

It helps to see how capacity and demand interact across different states, and how each compares to a related benchmark.

The table makes the point clearly: the goal is not maximum utilization, it is the right utilization. A team running at a steady 75% to 80% can absorb surprises and grow; a team pinned at 120% is borrowing against its own future.

Pros and Cons of Capacity Planning

Like any discipline, capacity planning has trade-offs worth naming.

Pros

• Prevents overcommitment - you stop promising what the team cannot deliver.
• Protects margins - you spot under-utilization before it eats profit.
• Reduces burnout - workload is visible and balanced, not dumped on whoever is closest.
• Improves quoting accuracy - deadlines are grounded in real availability.
• Justifies hiring - capacity gaps make the case for headcount with numbers, not vibes.

Cons

• Requires honest inputs - garbage in, garbage out; optimistic overhead estimates ruin it.
• Needs upkeep - leave, scope changes, and new work mean the plan must be revisited.
• Can feel rigid - treated dogmatically, it ignores the human reality that some weeks differ.
• Estimates are imperfect - project hours are forecasts, so capacity balance is approximate.

The cons are real but manageable. Almost all of them shrink once capacity planning becomes a quick, routine habit rather than a heavy quarterly project.

Common Mistakes

These are the errors that turn a capacity plan into wishful thinking.

Planning around 100% availability

Assuming every person delivers a full 40 productive hours every week is the classic mistake. Meetings, breaks, context switching, and admin are real. Plan around realistic productive hours, not theoretical ones.

Forgetting time off

A single overlooked public holiday or a week of booked leave can wipe out 20% of a small team's monthly capacity. Always subtract known absences first.

Ignoring non-billable overhead

Business development, internal reviews, and training do not disappear because they are not on an invoice. If you treat overhead as zero, your plan will overcommit the team every single cycle.

Confusing capacity with demand

Knowing you have 100 hours available tells you nothing until you compare it to the 80 or 120 hours of work you have promised. Capacity without a demand comparison is half a plan.

Chasing 100% utilization

Maximum utilization looks efficient on a spreadsheet and feels like crisis everywhere else. Without a buffer, the first delay cascades into missed deadlines. Leave deliberate slack.

Never revisiting the plan

A capacity plan built once and never updated drifts from reality within a week. Treat it as a living document tied to your planning cadence.

Best Practices for Planning Team Workload

Follow these steps to build a capacity plan you can actually trust.

1. Pick one planning unit and stick to it. Decide whether you plan in hours, days, or story points, and use the same unit for both capacity and demand.
2. Use realistic productive hours. Start from 6 to 7 productive hours per day, not a theoretical 8, unless your data proves otherwise.
3. Subtract known time off first. Pull holidays and booked leave before anything else, then add a small allowance for sick time.
4. Estimate overhead honestly. Track where non-billable hours actually go for a few weeks, then bake that percentage into every plan.
5. Set a target utilization, not 100%. Aim for a sustainable 70% to 85% and protect the buffer deliberately.
6. Compare capacity to demand every cycle. The number only earns its keep when you check it against committed work.
7. Review actuals against the plan. Each cycle, compare what you planned to what really happened and tune your assumptions.
8. Connect it to billing. Use the same hours that drive capacity to drive your invoicing so the picture stays consistent end to end.

How Capacity Planning Connects to Running a Business

Capacity planning is not a standalone HR exercise - it is wired into almost every financial decision you make. Your billable capacity sets the ceiling on the revenue your delivery team can produce, which directly shapes your cash flow forecast and your hiring plan. If you sell more than you can deliver, you create unhappy clients and unpaid overtime; if you sell less than you can deliver, you erode your margins.

It also feeds pricing. When you know precisely how many billable hours a person produces in a month, you can set rates that cover overhead and still leave profit. That is the same logic behind tools like the Hourly Rate Calculator and the wider Business Capacity Calculator, which scale the single-team view up to the whole business.

The practical link many teams miss is billing. The hours you plan capacity around are the same hours you eventually invoice. When that data lives in one place, your capacity plan, your delivery records, and your invoices all tell the same story. Aviy's invoice analytics surface exactly how much delivered work has been billed and paid, which closes the loop between the time you planned and the revenue it produced. That feedback is what lets you tighten next quarter's plan instead of guessing again.

Summary

A team capacity planner turns a vague feeling of "we're slammed" into a number you can act on. The formula is simple - multiply your people by their realistic working hours, subtract time off and non-billable overhead, then compare the result to the work you have committed. Apply a sustainable utilization target of roughly 70% to 85%, leave a deliberate buffer, and revisit the plan every cycle.

Do that consistently and you protect three things at once: your delivery dates, your margins, and your team's wellbeing. The worked examples above - a design studio, a marketing agency, and a consultancy - show that the same arithmetic scales from two people to thirty. Capacity planning is one of the highest-leverage habits a service business can build, and it costs nothing but a few minutes each planning cycle.

Frequently asked questions

What is a team capacity planner?

A team capacity planner is a calculation that estimates how many productive hours your team can deliver in a chosen period, then compares that figure to the work you have committed. It multiplies your people by their realistic working hours, subtracts time off and non-billable overhead, and shows whether you are overbooked, balanced, or have room to take on more work.

How do you calculate team capacity?

Use the formula: team capacity = (number of people x working hours per period) minus planned time off minus non-billable overhead. For example, three people at 40 hours is 120 hours; subtract 8 hours of leave and 25% overhead and you have roughly 84 deliverable hours. Compare that to committed work to find your capacity balance.

What is a good team utilization rate?

For most sustainable service teams, a target utilization between 70% and 85% is considered healthy. Below 70% usually means too much idle or overhead time; above 90% leaves no buffer for surprises and tends to cause burnout. The ideal figure varies by industry and business model, so treat these as starting benchmarks rather than fixed rules.

How do you plan workload across a team?

Calculate each person's available hours, total them for the team, then allocate committed work against that total while keeping a deliberate buffer. Plan in one consistent unit, subtract known leave first, and avoid loading any single person past a sustainable utilization rate. Revisit the allocation every planning cycle as new work and absences appear.

What is the difference between capacity and demand?

Capacity is the total productive hours your team can supply in a period. Demand is the total hours of work you have committed to deliver in that same period. Capacity planning is the act of comparing the two - a positive balance means you have slack, a negative balance means you are overbooked and need to act.

How do you account for holidays and sick leave in capacity planning?

Subtract them before anything else. Remove public holidays and booked annual leave as hard numbers, then add a sensible allowance for typical sick days based on your team's history. A single overlooked holiday can erase a fifth of a small team's monthly capacity, so accuracy here matters more than almost any other input.

How often should you update your capacity plan?

Update it every planning cycle, whether that is weekly, per sprint, or monthly. People take leave, projects slip, and new work arrives constantly, so a plan built once and left alone drifts from reality within days. Treat it as a living document and review actuals against the plan each cycle to refine your assumptions.

Should you plan capacity at 100% utilization?

No. Planning at 100% utilization leaves no room for overruns, last-minute requests, or sick days, so the first delay cascades into missed deadlines. Aim for a sustainable 70% to 85% and protect the remaining buffer deliberately. Maximum utilization looks efficient on a spreadsheet but reliably produces crisis and burnout in practice.

What unit should I use for capacity planning?

Use whatever unit you estimate work in, and use it consistently for both capacity and demand. Most service teams plan in hours; agile teams may use story points; some firms use days. The single rule is to never mix units, because that quietly produces a plan that looks balanced while actually being over or under committed.

How does capacity planning relate to invoicing?

The hours you plan capacity around are the same hours you eventually bill. When that time data lives in one place, your capacity plan, delivery records, and invoices all agree. Tracking billed and paid work against planned capacity closes the loop, letting you see how much of your planned time actually turned into revenue and tighten the next plan.

Conclusion

A team capacity planner is one of the simplest tools you can adopt, yet it quietly governs whether your business hits deadlines, holds its margins, and keeps its people. The arithmetic never changes: multiply your team by their realistic working hours, subtract leave and non-billable overhead, apply a sustainable utilization target, and compare the result to what you have committed. That single comparison tells you whether to say yes to new work, push a deadline, or hire.

The teams that thrive are not the ones running at 100% - they are the ones who plan capacity honestly, protect a buffer, and revisit the numbers every cycle. Build that habit and the chaos of overbooking gives way to calm, predictable delivery.

Related guides

• Business Capacity Calculator: How Much Work Can You Take?
• Utilization Rate Calculator: How to Measure Billable Time
• Billable Hours Calculator: How to Track and Bill Your Time
• Hourly Rate Calculator: How to Set Your Rate
• Resource Planning Calculator: How to Plan Resources
• How to Scale a Service Business: A Practical 2026 Growth Guide

Sources and further reading

• Capacity planning (Wikipedia)
• Capacity utilization (Investopedia)
• Hiring your first employee (U.S. Small Business Administration)
• Working time rules (GOV.UK)