What this Team Capacity Calculator does
The Team Capacity Calculator estimates how many hours a group can reserve for planned work during a chosen period. It starts with the team's scheduled working hours, subtracts time off, and then applies a focus factor to account for the portion of remaining time that is realistically available for the work being planned. The result is estimated capacity in hours, a useful planning input for project conversations and workload reviews.
Capacity is different from a promise about delivery. People spend time on coordination, support, reviews, unexpected requests, and other responsibilities. The focus factor provides a simple way to acknowledge that reality, but the calculator cannot know every team's work pattern. Treat the estimate as a transparent starting point and review it with the people doing the work.
This model assumes each person has the same weekly working hours, the same planning period, and a five-day work week for converting person-days off into hours. It also assumes the focus percentage applies to the team's hours after time off is removed. Those assumptions make the calculation easy to inspect and adjust.
How to use the Team Capacity Calculator
Choose a planning period, such as a two-week iteration or a project month expressed in weeks. Enter the number of people contributing, their typical working hours per week, and the total time off across the group during that period. Enter time off as person-days. For example, one person away for two days contributes two person-days, and two people each away for two days contribute four.
Set the focus factor to the share of available time that can reasonably go toward the planned work in scope. If you already track this from past planning periods, use that evidence. Otherwise, agree on a cautious estimate with the team and revisit it after comparing the estimate with actual work time.
- Team members counts people included in the estimate.
- Working hours per person per week records each person's usual weekly schedule.
- Planning period is entered in weeks.
- Team time off is the combined number of person-days off within that period.
- Available focus is a percentage from 1 to 100 for the share left for planned work.
Check that the entries describe the same group and time window. If some people work part time or have different schedules, a single average may hide meaningful differences. You can calculate separate groups with matching schedules and add their results, or use a spreadsheet with individual rows.
How the Team Capacity Calculator formula works
The formula is ((team members × weekly hours × weeks) − (time-off person-days × (weekly hours ÷ 5))) × (focus percentage ÷ 100). First, it multiplies the number of people by weekly hours and weeks to estimate scheduled hours. Next, it converts time-off days into hours using the five-day workweek assumption and subtracts those hours. Finally, it multiplies the remaining hours by the focus percentage expressed as a decimal.
For a worked example, consider five people working 40 hours per week over two weeks, with a combined four person-days off and a focus factor of 75 percent. Scheduled time is 5 × 40 × 2 = 400 hours. The time-off adjustment is 4 × (40 ÷ 5) = 32 hours. After that adjustment, 368 hours remain. Applying the focus factor gives 368 × 0.75 = 276 estimated hours for planned work.
The result is rounded to two decimal places by the display format. The arithmetic itself is linear, so changing an input changes the estimate in a predictable way. It does not convert hours into tasks or points because those units depend on the work and the team's own estimation practices.
Use cases for the Team Capacity Calculator
Project leads can use an hours estimate when preparing a planning meeting, checking whether a proposed workload fits the period, or comparing two staffing scenarios. A team can also make assumptions visible before accepting new requests. Instead of relying on an unspoken sense that everyone is busy, the group can discuss the available time and what has already been reserved.
For example, a project coordinator may estimate capacity for a design and implementation group, then list recurring meetings, support coverage, and known deadlines beside the result. A volunteer project may use the same method with fewer weekly hours and a longer period. The arithmetic remains the same, while the schedule inputs reflect the actual arrangement.
Useful practices include:
- Estimate one team or workstream at a time when schedules differ.
- Record the selected focus factor and why the team chose it.
- Compare estimates with actual availability at the end of each period.
- Update time-off inputs when leave or holidays are confirmed.
- Use the result to begin a conversation about scope and sequencing.
Capacity is most useful when it informs a choice. If planned work exceeds the estimate, the team can discuss reducing scope, moving work to a later period, or changing who is available. The calculation does not decide which option is best. That decision depends on priorities, dependencies, quality needs, and the people affected.
Other factors to consider when calculating team capacity
Weekly hours do not show how time is distributed. A person may be scheduled for a full week but unavailable for project work because of customer support, operational duties, training, or cross-team meetings. The focus factor can absorb some of that time, but it is better to make substantial recurring commitments visible so the estimate can be explained.
People also have different roles and skills. A total of 100 hours does not mean that any task can be completed within those hours. Work may depend on one specialist, require review by another person, or need to happen in sequence. A team can have spare aggregate capacity while still lacking availability for a specific task.
Consider these limits when using the estimate:
- It treats weekly hours as consistent throughout the selected period.
- It converts each time-off day using one fifth of the weekly hours.
- It applies one focus factor to all included hours after time off.
- It does not model holidays separately, partial days, shift patterns, or individual schedules.
- It does not account for task difficulty, dependencies, or changes in scope.
For more accurate planning, keep the assumptions consistent from period to period and compare estimates with observed availability. If a repeated gap appears, adjust the inputs or use a more detailed schedule model. Avoid treating a higher focus factor as a target for individuals. The number is a planning assumption about time for a defined group, not a measure of effort or performance.
Frequently asked questions
What does estimated capacity mean?
It is the approximate number of hours available for planned work after subtracting entered time off and applying the focus factor. It helps frame workload discussions, but it does not predict exactly how much work will be delivered.
Why does the formula use a five-day work week?
The model converts person-days off into hours by dividing weekly hours by five. This fits a standard five-day schedule. For teams with a different schedule, the conversion may not match reality, so use a more suitable spreadsheet calculation or adapt the inputs before relying on the estimate.
How should I choose a focus factor?
Use team experience when available, including time spent on support, meetings, coordination, and interruptions. If there is no history, agree on a cautious planning assumption, record it, and review it later. The factor should not be used as an individual productivity score.
Can I include part-time team members?
Yes, if the working-hours input represents a reasonable average for the included group. When schedules vary substantially, calculate each schedule group separately and combine the estimates, or track each person in a more detailed model.
Does the result tell me how many tasks the team can complete?
No. The result is expressed in hours. Converting hours into tasks requires task estimates and knowledge of dependencies, skills, and the team's way of working. Use the capacity estimate alongside those project details rather than treating it as a task count.