Editable capacity planning template
Capacity planning tracker for demand gaps and action
Build the forecast from visible assumptions, then make every gap point to a date, affected work, owner, and response.
Free for up to five users. No credit card required.
Adapt fields, workflows, and dashboards without code. Explore 1,000+ app templates and use cases
Sign in to inspect the sample App, then install it with sample data to test the records and review path.
How this tracker helps
A capacity planning tracker compares usable supply with committed and forecast demand over a defined horizon. The useful output is not only a gap value; it is the dated decision to move, split, reassign, source, or decline work.
- Supply inputs remain inspectable
- Forecast differs from commitment
- Gap becomes owned action
Planning equation
Make the arithmetic and assumptions readable
The example uses hours, but keeps the capability and timing context beside them.
| Line | Calculation or rule | Example use |
|---|---|---|
| Baseline supply | Agreed working capacity in the horizon | 32 hours per week |
| Availability reduction | Approved leave, training, support, and other non-project commitments | 16 hours of training |
| Usable capacity | Baseline minus known reductions and buffer | Capacity available for planned work |
| Committed demand | Confirmed allocations in the same dates | Protected client delivery |
| Forecast demand | Uncertain work shown separately or weighted | Pipeline renewal review |
| Gap | Usable capacity minus applicable demand | 6-hour overload requiring a decision |
Planning horizons
Use different precision for weekly and quarterly decisions
Do not force named-person detail into uncertain long-range planning.
Two-week operating view
Named people, exact dates, approved leave, current allocations, and active exceptions.
Rolling 12-week view
Named people plus role placeholders, likely starts, project phases, and probability-aware demand.
Quarterly structural view
Teams, role families, skill pools, scenarios, hiring or contractor assumptions, and portfolio choices.
Gap response
Give each red signal an explicit lever
A tracker is successful only when it changes a decision.
Move or phase the work
Change dates while preserving the original promise and affected stakeholders.
Change the staffing mix
Use another person, role level, or split of skills without ignoring handoff cost.
Reduce scope
Separate essential work from work that can be deferred.
Add capacity
Record contractor, hiring, overtime, or cross-training as an assumption until approved.
Decline or defer demand
Make the portfolio decision visible when no responsible plan exists.
Practical questions
Questions teams ask when building a capacity tracker
Make every assumption visible and every gap point to a dated decision rather than a decorative red cell.
Which inputs should sit beside the hours in a capacity tracker?
Hours are a practical denominator, but they are not sufficient by themselves. The example keeps skill, role level, time zone, availability, dates, priority, and delivery health beside the hours so that a mathematically available person is not mistaken for the right person. Keep skills, availability changes, demand certainty, dates, and protected commitments visible so the gap remains actionable.
Will the tracker automatically eliminate every capacity gap?
No. It surfaces capacity, skill, date, workload, and conflict evidence for a human decision. Automatic optimization can be valuable at larger scale, but it needs agreed constraints, priorities, and specialist capability. Jodoo is strongest when the operating rules and approval path need to be shaped by the business. Its job is to expose the assumption and route a choice; automation can follow after the allowable trade-offs are agreed.
Is an Excel capacity planning template included?
This page prioritizes the connected Jodoo App because the planning process requires changing availability, demand, approval, allocations, and exceptions. If you export data to a workbook, keep the same definitions and do not treat a static file as the live source of truth.
How should we weight pipeline demand?
Use an agreed probability or scenario convention and show the unweighted amount as context. Do not blend weighted pipeline with confirmed work so completely that readers cannot distinguish the assumption.
Can the tracker show skill gaps?
Yes. Work demand includes required skills and role level, and people profiles include skills and availability. The example exposes the inputs for a human staffing decision rather than claiming automated skill matching.
Start with populated records
Open the working tracker before adapting it
Review normal, pending, overloaded, changed, and completed examples, then keep only the fields and views your team needs.