Team Operations
Capacity Planning: Build a Realistic Team Workload Plan
Build a team capacity plan from real availability, fixed work and effort ranges, with an original one-week planning example.
What you will learn
- Calculate capacity after leave and fixed commitments.
- Compare low/high work estimates with available hours.
- Identify a skill bottleneck that a team total can hide.
Capacity planning compares the work you want to accept with the people, time and skills available to do it. Start with actual availability, subtract existing commitments once and keep estimates as ranges. An empty calendar slot is not automatically usable project capacity.
Choose a period and a unit
Use a practical planning window such as one week and a consistent unit such as person-hours. Asana's capacity-planning guide describes comparing required work with available resources and checking bottlenecks. The worksheet below is an original small-team example.
Keep availability, commitments and demand separate. Availability is the time a person can reasonably supply in the window. Commitments are work already accepted. Demand is work being considered. Counting the same meeting in both a capacity deduction and a task estimate will understate capacity; forgetting it entirely will overstate capacity.
Do not plan people at a fictional 100% of paid hours. Record leave, recurring obligations and support coverage using the team's actual agreements. An uncertainty allowance is a planning choice, not an industry benchmark.
What is an example of capacity planning?
| Person | Starting hours | Leave | Fixed meetings | Support coverage | Available for planned work |
|---|---|---|---|---|---|
| Ava | 40 | 8 | 6 | 6 | 20 |
| Leo | 40 | 0 | 6 | 4 | 30 |
| Team | 80 | 8 | 12 | 10 | 50 |
The team calculation is 80 − 8 − 12 − 10 = 50 available hours. This does not mean every 50-hour package fits. Ava and Leo have different skills, accepted responsibilities and availability patterns.
Compare demand as a range
| Proposed work | Low estimate | High estimate | Important assumption |
|---|---|---|---|
| Reporting setup | 20 hours | 26 hours | Input files have the expected structure |
| Customer handoff | 14 hours | 20 hours | Receiving owner can review this week |
| Operating cleanup | 9 hours | 13 hours | No unexpected access problem |
| Total | 43 hours | 59 hours | All estimates are fictional planning assumptions |
The low case leaves 50 − 43 = 7 hours. The high case exceeds capacity by 59 − 50 = 9 hours. Presenting only the midpoint would hide that downside.
Next assign the work to actual people. If a task needs Ava's specialist review, Leo's spare hours cannot automatically replace it. Check the sequence too: a reviewer available Friday cannot unblock a task due Wednesday.
For a more specific low-case allocation, suppose reporting setup needs 12 of Ava’s hours and 8 of Leo’s. The customer handoff needs 10 of Ava’s and 4 of Leo’s, while operating cleanup needs 9 of Leo’s. That assigns 22 hours to Ava and 21 to Leo: 43 overall, but Ava is over capacity by 2 hours. The team has 7 hours left in aggregate and still cannot deliver that allocation as written.
The decision is about capability and timing, not arithmetic optimism. Narrow Ava’s specialist work, move an appropriate review to a genuinely qualified available person, or defer part of the output. Do not assume Leo can perform the specialist task merely because he has time.
Copyable AI prompt
Try this with Aurora AI in Finta, Codex, or Claude. Use only material you are authorized to share, and review the draft before using it.
Prepare a one-week capacity ledger from [authorized availability], [leave], [fixed commitments], [support coverage] and [work estimates with ranges]. Define the unit and avoid double-counting. Return per-person and team capacity, low/high demand, skill and timing bottlenecks, and accept/narrow/defer options. Reconcile arithmetic, mark assumptions and preserve unknown estimates. Draft only; do not assign people, approve overtime or change deadlines.Choose what not to accept
Discuss four options: accept with stated assumptions, narrow an output, defer a lower-priority commitment or add genuinely available capability. Record what is displaced. “Priority one” does not create time.
Track actual effort and reasons for variation so the next estimate improves. Do not interpret a person taking longer than an early assumption as proof of poor performance. Missing inputs, changed scope and rework may explain the difference.
Use the productivity guide for output/input definitions and the project-management guide for accepted scope. Explore Finta's Capacity Planner to prepare a reviewable plan from authorized inputs. Human owners still decide commitments and resolve trade-offs.