AtlasCalcsUtility Calculation Suite
Free · No sign-up Client-side

PROJECT ESTIMATION · FREE DEVELOPER TOOL

Team Capacity Calculator

PROJECT ESTIMATION · FREE DEVELOPER TOOL October 2026 11 min read

Converts headcount and working time into real available engineering hours after leave, ceremonies, focus loss and onboarding. Free, instant and entirely client-side.

A six-person team rarely has six person-months of delivery capacity in a calendar month.

Converts headcount and working time into real available engineering hours after leave, ceremonies, focus loss and onboarding.

PROJECT ESTIMATIONClient-sideWorked examples2026
Estimate-to-actual variance
1.5–2×
Source: Industry research
Typical team focus factor
70%
Source: Scrum planning
COCOMO organic exponent
2.94
Source: Boehm 1981
Typical contingency
20%
Source: Risk reserve

Quick answer

Converts headcount and working time into real available engineering hours after leave, ceremonies, focus loss and onboarding. The calculator applies capacity = headcount × weeks × (hours_per_week − ceremony_hours) − leave_hours, then × focus × (1 − ramp_loss) and shows every intermediate value.

On this page
  1. 1Quick Answer
  2. 2Interactive Calculator
  3. 3Team Capacity Calculator: Calculation Breakdown
  4. 4Key Takeaways
  5. 5Software Project Estimation Reference Numbers
  6. 6Implementation Approaches
  7. 7Reference Tables
  8. 8Formulas & How to Use
  9. 9Worked Examples
  10. 10Advanced Guide: Team Capacity Calculator
  11. 11Language Playbooks
  12. 12Glossary
  13. 13Mistakes & Pro Tips
  14. 14Use Cases
  15. 15Related Calculators
  16. 16Long-Tail Answers
  17. 17FAQs (29)
  18. 18References

Interactive Calculator

Enter a value — every result updates instantly, in your browser. Free forever, no sign-up.

Private Exact math

Team Capacity Calculator

Every input is evaluated locally in your browser with deterministic arithmetic.

Runs in your browser
Team headcount Engineers able to contribute to delivery.Hours per person per week Contract or standard working hours.Planning window (weeks) Sprint, quarter or project window.Leave per person (days) PTO, holidays and training days inside the window.Ceremonies per week (hours) Stand-ups, planning, review and retrospectives.Focus factor (%) Share of working time spent on planned delivery work.Onboarding / ramp loss (%) Lost capacity from new joiners, handovers or context switching.

Live result

1,361 effective hours

Only 56.7% of gross paid time becomes planned delivery capacity.

Real capacityLeave adjustedFocus factor

Gross capacity

2,400 h

Leave deducted

144 h

Ceremony time deducted

240 h

Available working hours

2,016 h

Team Capacity Calculator: Calculation Breakdown

Every input, intermediate value and result row behind the estimate.

Calculated values and supporting details
Gross capacity
2,400 h

6 people × 40 h/week × 10 weeks.

Leave deducted
144 h
Ceremony time deducted
240 h
Available working hours
2,016 h
Focus-adjusted hours
1,512 h

75% focus factor.

Effective delivery hours
1,361 h
Full-time equivalents
3.4
Effective person-days
170

Step-by-step calculation

  1. 1Gross: 6 × 40 × 10 = 2,400 hours.
  2. 2Deduct 144 hours of leave and 240 hours of ceremonies → 2,016 hours.
  3. 3Apply 75% focus factor → 1,512 hours.
  4. 4Apply 10% ramp/context loss → 1,361 effective hours.
  5. 5That equals 3.4 full-time equivalents for the window.

Key Takeaways

The 30-second version — the exact answers Google loves to feature.

  • 1A six-person team rarely has six person-months of delivery capacity in a calendar month.
  • 2Ceremonies, leave and support work commonly consume 25–40% of paid engineering time.
  • 3Onboarding a new engineer often costs more capacity than it adds for the first one to three months.
  • 4Formula: capacity = headcount × weeks × (hours_per_week − ceremony_hours) − leave_hours, then × focus × (1 − ramp_loss)
  • 5Default scenario: 1,361 effective hours

Software Project Estimation Reference Numbers

Useful benchmarks to sanity-check the output before you commit to a decision.

Estimate-to-actual variance
1.5–2×
Source: Industry research
Typical team focus factor
70%
Source: Scrum planning
COCOMO organic exponent
2.94
Source: Boehm 1981
Typical contingency
20%
Source: Risk reserve
Sprint capacity horizon
4–6
Source: Forecasting
Client-side model
100%
Source: No project data stored

Implementation Approaches

Three practical ways teams use team capacity calculator, with the precision and safeguards each one needs.

Recommended

Range-based estimate

Best for: Roadmaps and stakeholder commitments

  • Method: Estimate best case, likely case and worst case, then report a range with the assumptions behind each.
  • Precision: Use historical throughput rather than optimistic effort estimates.
  • Safeguards: Re-estimate at each major uncertainty reduction and keep a contingency reserve.

Top-down model

Best for: Early feasibility and budget screening

  • Method: Use function points, COCOMO or cost per developer-day to bound the project before detailed planning.
  • Precision: Calibrate coefficients with your own historical projects when possible.
  • Safeguards: Treat the output as an order-of-magnitude estimate, not a commitment.

Bottom-up plan

Best for: Sprint and release planning

  • Method: Break work into small items, apply team capacity and velocity, and include review, testing and deployment time.
  • Precision: Use median throughput over the last three to six sprints.
  • Safeguards: Protect focus time and include absence, support and maintenance work.

Quick Reference Tables

Widths, ranges, boundary values and language types — the lookup tables you will come back to.

COCOMO II effort coefficients

Modeabcd
Organic (small, familiar)2.941.052.50.38
Semi-detached (medium)3.01.122.50.35
Embedded (tight constraints)3.61.202.50.32
COCOMO 81 organic2.41.052.50.38
COCOMO 81 semi-detached3.01.122.50.35
COCOMO 81 embedded3.61.202.50.32

Formulas & How to Use This Calculator

Core relationship

capacity = headcount × weeks × (hours_per_week − ceremony_hours) − leave_hours, then × focus × (1 − ramp_loss)

Unit convention

Inputs are team headcount, hours per person per week, planning window (weeks), leave per person (days), ceremonies per week (hours), focus factor (%), onboarding / ramp loss (%). Keep each unit consistent with the result rows; convert before comparing estimates that use different units or time windows.

Validation

1. Reproduce the headline from the displayed rows. 2. Compare the result with a measured, billed or benchmarked value. 3. Re-run with a boundary input and with a scaled input. 4. Record the assumptions, source and date next to the result.

How to use — step by step

  1. Open the Team Capacity Calculator and review the input defaults.
  2. Replace team headcount with your measured or planned value.
  3. Set hours per person per week (Contract or standard working hours.).
  4. Set planning window (weeks) (Sprint, quarter or project window.).
  5. Set leave per person (days) (PTO, holidays and training days inside the window.).
  6. Read the headline result and compare it with the supporting rows in the breakdown.
  7. Test one boundary value and one scaled value to understand the sensitivity.
  8. Copy or record the result together with the units and assumptions used.

Worked Examples

Real numbers and raw bits, fully worked — copy the pattern for your own code or protocol.

Default scenario

Inputs

Team headcount = 6; Hours per person per week = 40; Planning window (weeks) = 10; Leave per person (days) = 3; Ceremonies per week (hours) = 4

Math

capacity = headcount × weeks × (hours_per_week − ceremony_hours) − leave_hours, then × focus × (1 − ramp_loss)

Result

1,361 effective hours · Gross capacity: 2,400 h · Leave deducted: 144 h · Ceremony time deducted: 240 h

Scaled scenario

Inputs

Team headcount = 12; Hours per person per week = 60; Planning window (weeks) = 10; Leave per person (days) = 3; Ceremonies per week (hours) = 4

Math

capacity = headcount × weeks × (hours_per_week − ceremony_hours) − leave_hours, then × focus × (1 − ramp_loss)

Result

4,244 effective hours · Gross capacity: 7,200 h · Leave deducted: 432 h · Ceremony time deducted: 480 h

Advanced Guide: Team Capacity Calculator

Beyond the calculator — how to use team capacity calculator in real engineering, capacity and review decisions.

What the Team Capacity Calculator measures

Converts headcount and working time into real available engineering hours after leave, ceremonies, focus loss and onboarding. It turns ordinary project, infrastructure or runtime inputs into a visible number you can defend in a design review. The calculator is deliberately transparent: the result is derived from capacity = headcount × weeks × (hours_per_week − ceremony_hours) − leave_hours, then × focus × (1 − ramp_loss) rather than from an opaque benchmark, so you can change one assumption and immediately see how the answer moves.

The formula and its units

The core relationship is capacity = headcount × weeks × (hours_per_week − ceremony_hours) − leave_hours, then × focus × (1 − ramp_loss). Every field is labelled with its unit and expected range next to the input, and the breakdown repeats the intermediate values so a reviewer can verify the arithmetic. When you compare two results, make sure both were computed with the same units and the same time window; most apparent differences in software project estimation estimates are really unit or scope mismatches.

A worked check with the default inputs

With the default inputs (Team headcount = 6; Hours per person per week = 40; Planning window (weeks) = 10; Leave per person (days) = 3; Ceremonies per week (hours) = 4), the calculator reports 1,361 effective hours. Change Team headcount and the headline moves to 4,244 effective hours. That sensitivity is useful: if a small input change produces a large output change, the assumption deserves a source or a range rather than a single guess.

Inputs, assumptions and defaults

The inputs are Team headcount (Engineers able to contribute to delivery.); Hours per person per week (Contract or standard working hours.); Planning window (weeks) (Sprint, quarter or project window.); Leave per person (days) (PTO, holidays and training days inside the window.); Ceremonies per week (hours) (Stand-ups, planning, review and retrospectives.); Focus factor (%) (Share of working time spent on planned delivery work.); Onboarding / ramp loss (%) (Lost capacity from new joiners, handovers or context switching.). Defaults are realistic starting points, not recommendations for your system. Replace them with measured values wherever possible: production metrics, billing exports, compiler sizeof output, provider documentation or historical project data. Keep the assumptions beside the result so the estimate can be reproduced later.

Reading a low or high result

A low result usually means small scale, generous headroom or optimistic assumptions; a high result means the opposite. Neither is automatically good or bad. Ask which input dominates the change, then compare the result with a second method such as a benchmark, a bill, a query plan or a pilot. Agreement between two independent methods is much stronger evidence than a single formula.

Common mistakes in software project estimation

Planning with gross hours and then wondering why the sprint overflows. Subtracting leave twice because it is already inside the focus factor. Ignoring on-call and support rotations that remove engineers from delivery. Document the units, the measurement window and the scope, and re-run the calculation when the workload or architecture changes.

How to validate the result

Validate with three checks: reproduce the headline from the displayed rows, compare the estimate with a measured production value, and test a boundary case (zero, one, the maximum or a doubled input). If the three checks disagree, the model or the input is wrong. Record the validation date and the data source so the next reviewer can repeat it.

Where this fits in Software Project Estimation

This tool supports delivery cost, team capacity, COCOMO effort, sprint planning, maintenance and technical-debt payback. Use it during design, capacity review, incident follow-up or cost planning. Pair it with the related calculators to cover adjacent assumptions, and keep the output with the design decision so future changes can be compared against a known baseline.

Limitations and precision

No estimate is more accurate than its inputs. The calculator assumes steady-state behavior, consistent units and the defaults described in the field help. Real systems have bursty traffic, fragmentation, retries, background jobs and measurement error. Where the result informs a commitment or a budget, add a range and a contingency rather than treating the headline as a guarantee.

Related calculations to run next

The most useful companion tools are Agile Sprint Capacity Calculator, Sprint Velocity Calculator, Software Development Cost Calculator, Development Time Estimator. Together they cover the neighbouring assumptions — for example scale, overhead, failure headroom and cost — so you can present a complete estimate rather than a single isolated number.

Language & Platform Playbooks

The same bit pattern behaves differently in every language. Here is how to adapt the conversion safely.

COCOMO

Use calibrated coefficients when possible. COCOMO is best for order-of-magnitude estimates, not sprint commitments. For team capacity calculator, use the same units and time window described in the calculator so the result lines up with your platform data.

Function points

Count inputs, outputs, inquiries, internal files and external interfaces, then apply the complexity adjustment factor. For team capacity calculator, use the same units and time window described in the calculator so the result lines up with your platform data.

Agile planning

Forecast from historical throughput with a range, and re-plan when scope or team composition changes. For team capacity calculator, use the same units and time window described in the calculator so the result lines up with your platform data.

Finance

Convert effort to cost with fully loaded rates that include benefits, tools, facilities and management overhead. For team capacity calculator, use the same units and time window described in the calculator so the result lines up with your platform data.

Glossary: Key Terms Explained

Function point
A unit of software size based on inputs, outputs, inquiries, files and interfaces.
COCOMO
Constructive Cost Model, a parametric effort-estimation model based on size and mode.
Velocity
The average amount of work a team completes per sprint.
Focus factor
The share of working time available for planned delivery work.
Contingency
A reserve added to an estimate for known uncertainty.

Common Mistakes & Pro Tips

Mistakes that break conversions

  • Planning with gross hours and then wondering why the sprint overflows.
  • Subtracting leave twice because it is already inside the focus factor.
  • Ignoring on-call and support rotations that remove engineers from delivery.
  • Mixing units or time windows when comparing two team capacity calculator results.
  • Treating the default values as a recommendation instead of a starting point.
  • Reporting a single number without the assumptions, range or measurement date behind it.

Pro tips for production code

  • Agree the focus factor with the team and keep it stable across sprints.
  • Track effective hours against completed work to calibrate the factor over a quarter.
  • Measure the dominant input before refining the model; the largest uncertainty deserves the most attention.
  • Keep a short record of the inputs, result and date so future comparisons are meaningful.
  • Validate the estimate with a second method — a benchmark, a bill or production telemetry.
  • Pair this result with the related calculators (Agile Sprint Capacity Calculator, Sprint Velocity Calculator, Software Development Cost Calculator) for a complete picture.

Who Should Use This Calculator?

  • ▸ Sprint capacity planning.
  • ▸ Quarterly roadmap feasibility checks.
  • ▸ Justifying hiring or contractor budget.
  • ▸ Capacity review: turn team headcount into a defensible planning number.
  • ▸ Design review: compare two architectures or configurations with the same assumptions.
  • ▸ Incident follow-up: quantify the gap between the estimate and observed behaviour.

Related Programming Calculators

Keep going — every tool below links directly into this workflow.

People Also Search For

Tap a long-tail question to jump to the matching FAQ answer.

Frequently Asked Questions (29)

Long-tail answers: each question targets a real Google search about team capacity calculator — click to expand.

Showing 29 of 29 answers.

What is a realistic focus factor?
Teams that track it often land between 60% and 80% for planned feature work. A 100% focus factor assumes zero support, email, incidents or unplanned work, which is not credible for a production team.
Should capacity be calculated per sprint or per quarter?
Use the same window as the commitment. A sprint capacity helps planning; a quarterly capacity smooths leave and ramps. Keep the formula identical so the numbers are comparable.
What does the Team Capacity Calculator calculate?
Converts headcount and working time into real available engineering hours after leave, ceremonies, focus loss and onboarding. The output includes the headline value, the intermediate rows and the formula, so you can audit the result rather than accepting a black-box number.
What formula does the Team Capacity Calculator use?
It uses capacity = headcount × weeks × (hours_per_week − ceremony_hours) − leave_hours, then × focus × (1 − ramp_loss). The calculator evaluates the formula with the values shown in the input panel and displays each intermediate term in the breakdown.
What should I enter for team headcount?
Engineers able to contribute to delivery. The default is 6; replace it with a measured value whenever one is available, and keep the same unit for every comparison.
What should I enter for hours per person per week?
Contract or standard working hours. The default is 40; replace it with a measured value whenever one is available, and keep the same unit for every comparison.
What should I enter for planning window (weeks)?
Sprint, quarter or project window. The default is 10; replace it with a measured value whenever one is available, and keep the same unit for every comparison.
What should I enter for leave per person (days)?
PTO, holidays and training days inside the window. The default is 3; replace it with a measured value whenever one is available, and keep the same unit for every comparison.
What should I enter for ceremonies per week (hours)?
Stand-ups, planning, review and retrospectives. The default is 4; replace it with a measured value whenever one is available, and keep the same unit for every comparison.
What should I enter for focus factor (%)?
Share of working time spent on planned delivery work. The default is 75; replace it with a measured value whenever one is available, and keep the same unit for every comparison.
What should I enter for onboarding / ramp loss (%)?
Lost capacity from new joiners, handovers or context switching. The default is 10; replace it with a measured value whenever one is available, and keep the same unit for every comparison.
How do I interpret the Team Capacity Calculator result?
The headline is 1,361 effective hours. Only 56.7% of gross paid time becomes planned delivery capacity. A single number is less useful than the trend and the assumptions behind it.
What units does the Team Capacity Calculator use?
The inputs are Team headcount, Hours per person per week, Planning window (weeks), Leave per person (days), Ceremonies per week (hours), Focus factor (%), Onboarding / ramp loss (%). Units are shown on every field and repeated in the result rows. Do not mix decimal and binary units or seconds and milliseconds without converting first.
What are common mistakes when calculating team capacity calculator?
Planning with gross hours and then wondering why the sprint overflows. Subtracting leave twice because it is already inside the focus factor. Ignoring on-call and support rotations that remove engineers from delivery. Re-run the calculation whenever the workload, architecture or pricing changes.
When should I use the Team Capacity Calculator?
Sprint capacity planning. Quarterly roadmap feasibility checks. Justifying hiring or contractor budget. It is a client-side planning tool, not a substitute for production monitoring or a benchmark.
How can I validate the Team Capacity Calculator result?
Reproduce the headline from the displayed rows, compare it with a measured or billed value, and test a boundary input such as zero, one or double the normal value. If the checks disagree, correct the input or the model before using the result.
What is a worked example of the Team Capacity Calculator?
For Team headcount = 6; Hours per person per week = 40; Planning window (weeks) = 10; Leave per person (days) = 3; Ceremonies per week (hours) = 4, the result is 1,361 effective hours (Gross capacity: 2,400 h; Leave deducted: 144 h).
What related calculators should I use with the Team Capacity Calculator?
Use Agile Sprint Capacity Calculator, Sprint Velocity Calculator, Software Development Cost Calculator, Development Time Estimator to cover the adjacent assumptions. Running several related estimates is more reliable than over-tuning one number.
Is the Team Capacity Calculator free and private?
Yes. The calculator runs entirely in your browser, requires no sign-up and sends no inputs to a server. That makes it safe for approximate capacity planning, although production secrets and customer data should never be pasted into any web page.
Can I use the Team Capacity Calculator for production planning?
Use it as a first-pass model and confirm the result with production measurements, provider documentation or a staging benchmark. Add headroom for uncertainty, and record the date and data source so the estimate can be reviewed later.
How sensitive is the Team Capacity Calculator to team headcount?
With the default value the result is 1,361 effective hours; when team headcount is changed to 12, the result becomes 4,244 effective hours. Use this comparison to identify which input deserves the most careful measurement.
Why do software estimates usually run over?
Estimates often omit integration, testing, review, deployment, meetings, support and rework, and they assume uninterrupted focus time. Planning fallacy and scope growth add more. Use historical throughput, include non-coding work and report a range rather than a single number.
What is a good sprint capacity?
Capacity should be based on the team’s measured velocity and available focus time, not on theoretical hours. A typical focus factor is 60–75% of nominal working hours after meetings, support, leave and ceremonies.
Can COCOMO predict a small project accurately?
COCOMO is calibrated for larger projects and is sensitive to the mode and cost drivers. For a small team, historical velocity and bottom-up task estimates are usually more reliable. Use COCOMO as a sanity check and calibrate coefficients with your own data.
What does a typical Team Capacity Calculator output look like?
The default scenario shows 1,361 effective hours with rows for gross capacity, leave deducted, ceremony time deducted. The exact wording of each row is shown in the technical breakdown above.
How precise is the Team Capacity Calculator?
The arithmetic is exact for the values entered, but the result is only as good as the inputs. Engineering estimates typically carry ±10–30% uncertainty, and capacity models can be further off when traffic is bursty. Report a range and the main assumptions rather than a single deceptively precise number.
Does the Team Capacity Calculator include overhead?
It includes the overhead represented by its input fields: team headcount, hours per person per week, planning window (weeks), leave per person (days), ceremonies per week (hours), focus factor (%), onboarding / ramp loss (%). If your system has additional overhead — retries, replication, fragmentation, taxes or contingency — add it explicitly and document the adjustment.
How often should I re-run the Team Capacity Calculator?
Re-run it when the workload changes materially, when a provider or platform changes its limits or pricing, and at least once per planning cycle. Keep each result with the date and inputs so you can compare the trend instead of only the latest snapshot.
What is the best first step after using the Team Capacity Calculator?
Write down the three assumptions that most affect the result, then verify the largest one with a measurement. For software project estimation, that usually means checking a production metric, a bill or a documented limit before changing configuration.

Resources & Authoritative References

Further reading

Authoritative sources

Was this calculator helpful?

Last updated: October 2026 · Free forever · No sign-up · Part of Programming Calculators at Atlascalcs.com · All math runs in your browser