Team Capacity Planner
People, hours each, and a realistic utilization rate give your true weekly and monthly capacity — the number to plan workload against instead of assuming a full 40. Your own team.
Real productive hours your team has
Utilization accounts for meetings, admin, and breaks — 100% is never real.
The Team Capacity Planner calculates true weekly and monthly capacity by multiplying the number of team members by their available hours per week, then adjusting for a realistic utilization rate. The formula is: True Weekly Capacity = (Number of People) × (Hours per Person per Week) × (Utilization Rate). True Monthly Capacity = True Weekly Capacity × 4.33 (average weeks per month). The utilization rate represents the fraction of total working hours that are actually billable or productive, accounting for meetings, admin, training, and downtime. For example, a typical knowledge worker has 40 available hours but a utilization rate of 0.75 (75%), yielding 30 productive hours per week. This calculation is crucial because assuming full 40-hour weeks overestimates capacity by 25% or more, leading to overcommitment and burnout. The variable 'Number of People' includes only full-time equivalents (FTEs) or part-time staff adjusted proportionally. 'Hours per Person per Week' is the contract or standard workweek (e.g., 40, 37.5, 20). 'Utilization Rate' is derived from historical data or industry benchmarks (typically 0.6 to 0.85 for professional services). The product gives the realistic workload the team can sustain without quality loss.
Software Development Team (Tech Startup)
A startup has 5 developers, each working 40 hours per week. Historical data shows a 75% utilization rate due to stand-ups, code reviews, and meetings. Weekly capacity = 5 × 40 × 0.75 = 150 productive hours. Monthly capacity = 150 × 4.33 ≈ 649.5 hours. The team can plan 150 hours of coding, testing, and design per week, not 200 hours.
Marketing Agency (Client Services)
A marketing agency has 3 account managers and 2 designers (5 total), each 40-hour weeks. Utilization is 65% due to client calls, proposals, and internal training. Weekly capacity = 5 × 40 × 0.65 = 130 hours. Monthly capacity = 130 × 4.33 ≈ 562.9 hours. This prevents overbooking clients beyond realistic bandwidth.
Non-Profit Organization (Part-Time Staff)
A non-profit has 4 part-time workers: two at 20 hours/week, one at 30, one at 40 (total FTE = 2.5). Standard hours per FTE = 40. Utilization is 80% (less admin overhead). Weekly capacity = 2.5 × 40 × 0.80 = 80 hours. Monthly = 80 × 4.33 ≈ 346.4 hours. This helps plan grant deliverables accurately.
A good utilization rate varies by role and industry. For knowledge workers (e.g., software, consulting), 70-80% is healthy; above 85% risks burnout and quality decline. For roles with high collaboration or client interaction, 60-70% is realistic. Your team's true capacity should be the number you use for sprint planning, project timelines, and resource allocation. If you consistently exceed 80% utilization, consider hiring or adjusting deadlines. If below 60%, evaluate process inefficiencies or understaffing. Monthly capacity is an estimate; actual weeks per month vary (4-5 weeks). Use weekly capacity as your primary metric. The goal is to plan workload to avoid overcommitment, not to maximize utilization—slack is essential for innovation and unplanned work.
Common mistakes include using a 100% utilization rate, which ignores non-billable time and leads to overestimation of capacity. Another error is forgetting to adjust part-time staff to full-time equivalents (FTEs), skewing the headcount. Some teams apply the same utilization rate across all roles, but developers may have different rates than managers. Also, using 4 weeks per month instead of 4.33 underestimates monthly capacity by about 8%. Edge cases: new hires with lower utilization during onboarding, seasonal fluctuations, and team members on leave. Finally, capacity is a ceiling, not a target—planning to 100% capacity leaves no room for emergencies or creative work.
- Full-Time Equivalent (FTE)
- A unit that indicates the workload of an employed person in a way that makes workloads comparable, where one FTE equals one full-time worker's hours per week (e.g., 40 hours).
- Utilization Rate
- The percentage of total available working hours that are spent on productive or billable tasks, excluding overhead like meetings, training, or admin.
- Capacity
- The maximum amount of work that a team can complete in a given time period, measured in hours or story points, adjusted for realistic availability.
- Overcommitment
- The state where planned workload exceeds actual capacity, leading to missed deadlines, burnout, and reduced quality.
- Slack
- Deliberate buffer time in a schedule to accommodate unplanned work, learning, or recovery, typically 10-20% of capacity.
How do I determine the utilization rate for my team?
Look at historical data from time tracking or project management tools. If unavailable, start with 75% for knowledge workers and adjust based on observed meeting time and admin tasks.
Should I include managers in the capacity calculation?
Yes, but use a lower utilization rate (e.g., 50-60%) since managers spend more time in meetings and coaching.
What if team members have different hours per week?
Convert everyone to full-time equivalents (FTEs) by dividing their hours by 40, then multiply total FTEs by 40 and the utilization rate.
Is monthly capacity accurate for planning?
It's a rough guide; use weekly capacity for sprint planning, as months have varying numbers of workdays.
Can I use this for non-billable teams?
Yes, replace 'billable' with 'productive work' related to your core goals, like feature development or deliverables.
What if my team is remote with flexible hours?
Use their agreed-upon core hours or average weekly hours logged, and still apply a utilization rate to account for async communication.
How often should I recalculate capacity?
Recompute monthly or whenever team size, hours, or utilization changes significantly, like after a new hire or process change.
Why is 4.33 used for monthly capacity?
Because a year has 52 weeks, so average weeks per month is 52/12 ≈ 4.33, giving a more accurate monthly estimate than using 4 weeks.
The Notion Project OS in every bundle tracks capacity against committed work so you stop overbooking the team.
Startup Cost Calculator
Add up what it really takes to launch — and what a bundle replaces.
Service Pricing Calculator
Price every job for profit, not guesswork.
Break-Even Calculator
The exact number of jobs that turns the lights green.
Revenue Goal Calculator
Reverse-engineer the leads behind your number.
Catalog ROI Calculator
The time and money the catalog hands back every year.