Free Calculator

How Much Can Your Team Really Take On?

Headcount times 40 hours is a fantasy number. The real question is what is left after meetings, overhead, and time off, and how much of that you can safely commit before the plan starts eating weekends.

16 people30
1 wk2 weeks13 wk

2 weeks = sprint, 13 = a quarter

10%40%70%

Meetings, email, admin, context switching

02 days30

Vacation, holidays, known absences, team-wide

Real capacity you can safely commit

0 h

Nominal hours

0

the fantasy number

True capacity

0

after overhead + time off

Capacity lost

0%

of the nominal number

Real hours / person / week

0

of focused work

Nominal vs Reality

The gap between what the headcount promises and what the team can actually deliver is where over-commitment lives. Plan against the right number and "we are always behind" usually goes away.

If you plan to nominal

0 h

the overdraft you set up

Safe commit (with buffer)

0 h

true capacity minus slack

What This Number Means for You

Commit to the real number, not the flattering one.

Overhead is the biggest lever you actually control.

Time off is fixed and headcount is slow to change, but overhead is not. Cutting meetings and protecting focus time converts overhead straight into capacity, no hiring required. The meeting cost calculator and meeting-free day calculator show where the hours are hiding.

More capacity often means delegating, not hiring.

If you are the bottleneck, the fastest capacity gain is handing work down rather than adding people. The delegation guide covers how, and the span of control calculator checks whether the team is even the right size.

About the numbers: Nominal hours = people × weeks × 40. Overhead hours = nominal × overhead%. Time-off hours = days × 8. True capacity = nominal minus overhead minus time off. Safe commit = true capacity × 80% (a buffer for the unknowns that always arrive). This models availability, not individual productivity, and assumes a 40-hour week. Adjust the overhead slider to your reality; if you have never measured it, start at 45% and audit one week. Planning estimates, not a timesheet.

Frequently Asked Questions

Why is real capacity so much lower than the headcount math?
Because the headcount math counts hours that do not exist. Six people times 40 hours looks like 240 hours of work, but meetings, email, context switching, admin, and the ordinary friction of a workday consume a large share before anyone touches the actual work. Realistic estimates of focused, productive time for knowledge workers often land closer to half the nominal week. Planning against the nominal number is why teams feel permanently behind while technically being "fully staffed."
What overhead percentage should I use?
For most knowledge teams, 40 to 55 percent is honest once you count meetings, communication, admin, and interruptions. Manager-heavy or meeting-heavy cultures run higher. If your number feels low, audit one real week: track how many hours actually went to the core work versus everything around it. Almost everyone is surprised, and almost always in the same direction.
Should I really only commit 80 percent of true capacity?
Yes, and arguably less. The recommended commit builds in a buffer for the unknowns that always arrive: the urgent escalation, the sick day, the task that was bigger than it looked. A team planned to 100 percent of even its realistic capacity has no slack, so the first surprise turns into slipped deadlines and weekend work. Slack is not waste. It is the capacity to absorb reality.
How is this different from the project timeline calculator?
This one answers "how much can my team take on in a period" across everything they do. The project timeline calculator answers "how long will this one project take" given the slice of capacity assigned to it. Use this to decide what fits in a sprint or quarter, and the timeline calculator to schedule a specific piece of work inside that budget.
My team is at 120 percent utilization. What do I do?
You are running an overdraft, and the interest is burnout and quality problems. Three moves, in order: cut or defer the lowest-value commitments (the honest ones, not the theoretical ones), reduce overhead by killing or shortening meetings, and stop adding new work until the number is under 100. Over-commitment is not a motivation problem you can push through; it is a math problem, and the math always wins eventually.
Does time off really need its own line?
Yes, because it is the capacity people forget to subtract. A two-week sprint with one person on vacation just lost 10 percent of the team before any other overhead. Vacations, holidays, and known appointments are predictable, so plan around them instead of being surprised by a shortfall you could have seen coming.

Plan to Reality, Not to the Org Chart.

Commit to the real number, protect a buffer, and convert overhead into capacity before you ask for headcount.

Calculator: Project Timeline → Guide: How to Delegate →

Related: Meeting-Free Day → Related: Span of Control →

← All Calculators