How to calculate team capacity before accepting more work

What is capacity, and why is headcount not enough?

Two teams may each have five people yet differ greatly in project delivery capacity. One has already allocated most time to existing customers; the other has free time but lacks a quality reviewer. Counting staff does not tell a business which additional commitments it can accept.

This framework estimates one week's workload. It is a resource-discussion tool, not a productivity standard or a way to track every employee minute. Research and creative tasks with high uncertainty should use estimate ranges and smaller trial scopes.

The formula: available hours and required hours

Hours genuinely available for new work = total planned working hours − routine-work hours − unavailable hours − hours committed elsewhere. The subtracted categories must not overlap. Unavailable hours may include leave, training or scheduled meetings if these are not already included in routine work.

Required hours = total estimated hands-on time for new tasks. Separate hands-on time from waiting time: a task requiring two hours of work may take three calendar days while awaiting data or approval. An hours table cannot fully capture these dependencies.

Hypothetical example: five people still fall short by 20 hours

A five-person team expects 200 hours in the week. Routine work consumes 110 hours; leave, training and meetings use 20 hours, counted separately from routine work. The team has 70 hours left for new work. Three tasks are expected to require 90 hours, leaving a 20-hour shortfall if scope stays unchanged.

New workload / genuinely available hours = 90 / 70, approximately 129%. This signals that the plan exceeds estimated resources, not that employees are inefficient. It does not yet establish a need for another hire: scope can be reduced, scheduling changed or waiting stages addressed.

Check by role so bottlenecks are not overlooked

Suppose the team has 70 hours left overall, but the quality reviewer has only eight hours while new outputs require 12 hours of inspection. A four-hour shortfall in this role can block the entire project even while others have time. Everyone's hours cannot simply be added together and treated as interchangeable.

Create a table for hard-to-replace roles: specialist work, review, approval or customer contact. Adding capacity where there is no bottleneck may not improve the completion date. Before hiring or outsourcing, identify the stage that actually determines how quickly outputs can be put into use.

A role-based planning template

Fill the table with data for a specific week. Without historical time records, use low and high estimates, note confidence levels and compare them with reality after completion. Do not turn an estimate into a firm promise when inputs are insufficient.

Four responses when workload exceeds capacity

Reduce scope by defining the minimum usable output; extend the schedule for less urgent work; transfer resources if the recipient has the necessary skills; or add capacity after identifying the bottleneck. Every option has a cost and needs an accountable decision-maker.

Do not automatically treat overtime as a permanent resource. If a plan works only through continuously longer hours, revisit commitments, input quality and the amount of open work. Time buffers for variability should also be chosen using historical experience rather than applying a fixed percentage to every team.

After one week, compare results to improve estimates

Record three things: actual output, actual hands-on time and waiting time. If discrepancies are large, ask why before increasing targets. Scope may have changed, inputs may be missing, tools may have failed or the owner may have handled a commitment absent from the table.

The table is valuable when it helps founders decide what else they can accept and what they must stop. When the team trusts that data is used to improve planning, people can report difficulties early rather than quietly accept an impossible schedule.

Suggested actions