What the Team Capacity Calculator does
The Team Capacity Calculator estimates how many project delivery hours a team can contribute during a chosen planning period. It starts with scheduled hours, subtracts each person’s recurring non-project time, and applies the share of the remaining time reserved for project delivery. The result is a team total in hours.
This is a planning estimate based on the inputs you provide. It can help a project lead compare planned work with a rough supply of team time before discussing scope, sequencing, or ownership. It does not predict exactly how much work the team will finish. Tasks differ in effort, uncertainty, and coordination needs, and an hour available on paper does not guarantee an hour of uninterrupted work.
The model assumes each listed team member has the same scheduled hours, non-project hours, and delivery allocation. If people have different schedules or responsibilities, calculate separate groups with consistent inputs and add the resulting hours. The estimate also treats the inputs as steady throughout the period. It does not automatically include holidays, one-off absences, new work, or changes in staffing.
How to use the Team Capacity Calculator
Choose one planning period, such as the next four weeks, and enter the people who will contribute during that period. Use a consistent unit of hours per week. Include recurring meetings, administration, support, and other duties in non-project time when they reduce the time available for the work being planned.
- Team members: Enter the number of people represented by the shared assumptions.
- Scheduled hours: Enter the typical scheduled work hours for one person in a week.
- Non-project time: Estimate each person’s weekly hours for duties outside the project delivery work being planned.
- Planning period: Enter the number of weeks covered by the estimate.
- Delivery allocation: Enter the percentage of the remaining time that you expect to reserve for project delivery.
Review the result labeled Estimated Project Hours. Compare it with the effort assumptions behind your plan, using the same period and team scope. If your project plan is expressed in days or points, convert it only with a team-specific convention that you have established. The calculator does not define a universal conversion between hours, story points, or completed work.
For example, imagine a six-person team planning four weeks. If each person has 40 scheduled hours per week, 8 hours of recurring non-project work, and 75% of the remaining time allocated to delivery, the formula is (6 × 4 × (40 − 8) × 75) ÷ 100. The calculation is 6 × 4 × 32 × 0.75, which gives 576 estimated project hours. This example assumes everyone in the group shares those values.
How the Team Capacity Calculator formula works
The formula is (team members × planning weeks × (hours per person per week − non-project hours per person per week) × delivery allocation percentage) ÷ 100. First, it finds a person’s weekly hours remaining after the listed non-project time. It then multiplies those hours by the number of people and weeks. Finally, it applies the delivery allocation percentage to estimate the portion reserved for project work.
For instance, 40 scheduled hours minus 8 non-project hours leaves 32 hours per person each week. For six people over four weeks, that produces 768 hours before the allocation adjustment. Applying 75% gives 576 hours. The allocation percentage is a planning assumption, not a measure of individual productivity. It gives the team a way to account for other project work, interruptions, or time deliberately kept outside the delivery plan.
The input ranges allow scheduled hours from 10 to 40, non-project time from 0 to 10, a period from 1 to 26 weeks, and an allocation from 0% to 100%. Because the maximum non-project input is below the minimum scheduled-hours input, the weekly remaining-hours calculation cannot become negative. A zero allocation produces zero project hours, as expected. The displayed decimal places reflect calculation precision, not certainty about future work.
Use cases for team capacity planning
A capacity estimate can support several ordinary planning conversations. It gives participants a shared starting point and makes assumptions visible enough to discuss. For example, a team might use it to:
- Review whether a proposed set of project work fits the hours available in the next planning period.
- Compare a few staffing or allocation scenarios before choosing a plan to discuss.
- Make recurring support or coordination duties visible when they compete with project work.
- Explain why a plan changes when the team size, time period, or expected allocation changes.
- Record a baseline estimate and revisit it when staffing or responsibilities shift.
Keep scenario comparisons grounded in realistic assumptions. A higher delivery allocation creates a larger estimate, but it may leave less time for operational duties, collaboration, or unexpected work. The arithmetic shows the effect of the entered percentage. It cannot establish whether that percentage is practical for a particular team.
Factors to consider when estimating capacity
People’s working patterns are rarely identical. Part-time schedules, planned leave, onboarding, specialist responsibilities, and rotating support can make one shared average misleading. You can represent distinct groups separately when their schedules differ, then total the resulting project-hour estimates. For planned absences or a short-term staffing change, adjust the relevant group or period inputs and clearly label the assumptions.
Also consider how the team defines project delivery. Some teams include planning, reviews, and coordination in delivery time. Others count only time spent directly on assigned tasks. Either convention can support a useful estimate if it is applied consistently. Avoid subtracting the same meeting or support hours twice, once as non-project time and again through a lower allocation percentage.
Capacity is not the same as a commitment or a forecast of completed work. Dependencies, review queues, unclear requirements, equipment, and decision delays can affect progress without changing the number of scheduled hours. Use this result as one planning input alongside team knowledge and the work itself. Revisit it when actual availability changes, and explain what changed so that later comparisons remain useful.
Frequently asked questions
What does estimated project capacity mean?
It means the total hours produced by the calculator’s stated assumptions for the selected team and period. It describes estimated time reserved for project delivery, not a guaranteed amount of completed work.
Should meetings count as non-project time?
Count recurring meetings in non-project time if they sit outside the delivery work you are estimating. If your team includes project planning and reviews in delivery, keep them there instead. Choose one consistent treatment to avoid counting the same hours twice.
How do I account for people with different schedules?
Calculate each group separately using the people, weekly hours, non-project time, allocation, and period that fit that group. Add the group results for a team total. This keeps the shared-input assumption visible.
Does this estimate account for holidays or unexpected absences?
No. The formula assumes the entered weekly hours apply across the full planning period. For a period with known leave, adjust the inputs to reflect expected availability, or split the period into portions with different assumptions.
Can I use the result to promise a delivery date?
The result alone cannot establish a delivery date. It does not account for task effort, dependencies, uncertainty, or work sequencing. Use it to inform a planning discussion, then assess the actual work and constraints with the people responsible for delivering it.