Delivery capacity planning
Establish whether committed work can actually be delivered by the people available.
— Organisation & Workforce
Models demand against supply to compute the capacity gap, showing where and when a delivery shortfall will appear.
2–3 weeks → ~40 minutes
For a full population, not a sample
No coding required
— USE CASES
Establish whether committed work can actually be delivered by the people available.
Model capacity against a pipeline before commitments are made.
Show when a shortfall becomes real so hiring starts early enough to matter.
— HOW IT BEHAVES
The mechanics behind this specific template — what it reads, what it calculates, and where a human stays in the loop.
The figures behind each process step are computed by formula during the run, so the arithmetic is identical every time and can be checked line by line.
Figures buried in narrative process documentation and run data are extracted as data you can compute and compare with.
Analysis runs against your real reporting lines and process steps rather than an assumed org shape.
Current external sources on the end-to-end process are researched during the run rather than recalled from training data, and every source travels with the output.
The same analysis executes per process step across the end-to-end process, so coverage is complete rather than indicative.
Thin cases and strong cases among your process steps are handled differently by design, based on what the analysis actually found.
Capacity planning is routine in name only: the inputs are messy, the standard is unwritten, and two people rarely reach the same answer. In practice it shows up as delivery capacity planning: establish whether committed work can actually be delivered by the people available. It is the kind of work that decides whether a recommendation survives scrutiny — and the kind that quietly eats 2–3 weeks of senior time whenever it comes round.
As a Skill, the work is already sequenced. You bring the evidence, and the run produces a computed capacity gap by period plus where the shortfall sits, by team or skill. The judgement is built in — how items are broken up, what standard they are held to, and where the run stops for a human review. The practical effect: 2–3 weeks of manual work becomes a ~40 minutes run, held to an identical standard on the tenth engagement as on the first.
Capacity planning exports as a structured SKILL.md file and is MCP-ready, so the same method runs in ChatGPT, Claude, Copilot or your own AI products. Adapt it to your methodology, and the intelligence stays yours — not locked to one vendor.
Redesigns workflows and roles around the practical use of AI, producing a board-ready plan with task-level recommendations, costed capacity gains and clear workforce implications.
Keeps a standing read on the risk universe in scope, working through risk registers, controls and policy documents on a regular cycle to show where each risk stands, what has moved since the last run and which items now need an owner's attention.
Matches available consultant capacity against the work coming down the pipeline each week, showing where people are about to sit idle, where demand will outstrip the skills you have and which pairings genuinely fit.
Runs a recurring skills survey across the workforce on a set cycle, building a living view of skills and utilisation by department that leadership can track month over month.
Ranks candidate locations against weighted workforce and business criteria, tests how cost assumptions affect the result, and produces a board-ready recommendation with a traceable evidence base.
Reviews a workforce metrics pack and states what the measures actually imply, rather than restating the numbers.