← ccPlanning Academy · Capacity planning track

Presenting the capacity plan

Free visual lesson · about 5 minutes · short quiz at the end

ccPlanning academy · capacity planning

Presenting the capacity plan

A perfect plan that doesn’t get the budget approved is just a spreadsheet.

The big idea

The capacity plan is a business case.

Its audience is finance and HR, and they don’t speak in FTE and shrinkage — they speak in cost, risk and return. To get the heads approved, translate the plan into their language: what it costs, what it protects, and what happens if you don’t.

Lead with the ask and the why

“We need to hire 24 by September — here’s why.”

Open with the decision you need and the headline reason, not the model. Finance wants the bottom line first: the number, the timing, the cost, the consequence. The spreadsheet is your evidence, held in reserve for the questions.

The cost of inaction

Quantify what “no” costs.

The strongest capacity case isn’t “hiring costs £X” — it’s “not hiring costs more.” Missed service, abandons, lost revenue, overtime burn, attrition from overload. Put a number on the do-nothing path and the hire often becomes the cheap option.

Frame it in their metrics

Translate FTE into money and risk.

“12 FTE short” means little upstairs. “Service drops to 65%, ~4,000 abandoned calls a month, an estimated £X in lost sales” lands. Use the cost-of-attrition, cost-per-contact and EBITDA-impact figures to speak finance’s language, not planning’s.

Show the scenarios

Give a recommendation, not just options.

Present low/expected/high so they see the risk, then say which you recommend and why. Decision-makers want a clear position to react to — “I recommend planning to expected and holding an overtime buffer for the high case” — not a menu with no guide.

Make the timing unmissable

Emphasise the decision deadline.

Because of lead times, the dangerous date is when the decision must be made, not when the heads are needed. Spell it out: “to have them productive for peak, recruitment must start in week 30 — a decision is needed by week 28.” Deadlines force decisions; vague need-by dates drift.

Same fact, two framings

“12 FTE short” vs the version that lands

To a planner, “we’re 12 FTE short in Q4” is precise. Upstairs it’s noise. Reframed: “without 12 hires, service falls to ~65%, around 4,000 calls a month go unanswered, an estimated £X in lost sales — and the hire costs a fraction of that.”

Identical analysis, two outcomes. The second gets approved because it’s in their currency, not yours.

The takeaway

Sell the plan in cost, risk and timing.

Lead with the ask, quantify the cost of inaction, translate FTE into money and service, recommend a scenario, and make the decision deadline impossible to miss. The capacity plan only delivers value when someone approves the heads — and that’s a communication job as much as an analytical one.

That’s the track — now test yourself ↓

1 / 8

Slides done? Here’s the same idea in a bit more depth — the part worth keeping.

In depth: a plan that isn’t approved is just a spreadsheet

You can build a flawless capacity plan and still fail, because the last step isn’t analysis — it’s persuasion. The plan’s real audience is finance and HR, and they don’t think in FTE, shrinkage and occupancy; they think in cost, risk and return. Getting the heads approved means translating the plan out of planning’s language and into theirs, and treating the whole thing as a business case rather than a technical document.

Lead with the decision, quantify the do-nothing path

Open with the ask and the headline reason — “we need to hire 24 by September, here’s why” — not the model; the spreadsheet is evidence held in reserve for the questions. Then make the strongest move in any capacity case: put a number on inaction. The compelling version isn’t “hiring costs £X,” it’s “not hiring costs more” — missed service, abandoned contacts, lost revenue, overtime burn, attrition from overload. Once the do-nothing path has a price tag, the hire often becomes the obviously cheaper option. And frame everything in their metrics: “12 FTE short” means little upstairs, but “service drops to 65%, ~4,000 abandoned calls a month, an estimated £X in lost sales” lands.

Recommend, and make the deadline unmissable

Show the low/expected/high scenarios so leadership sees the risk, but don’t hand over a menu with no guide — give a clear recommendation and your reason for it. Decision-makers want a position to react to. Finally, because of lead times, the dangerous date is when the decision must be made, not when the heads are needed: spell out “to have them productive for peak, recruitment must start in week 30, so a decision is needed by week 28.” Concrete deadlines force decisions; vague need-by dates drift until it’s too late to act.

The principle to remember: sell the plan in cost, risk and timing. Lead with the ask, quantify the cost of inaction, translate FTE into money and service, recommend a scenario, and make the decision deadline impossible to miss. Approval is a communication job as much as an analytical one.

Quick quiz

Five questions. Pick an answer to each, then check your score.

1. How should you think about the capacity plan when presenting it?

The audience speaks cost and risk, not FTE and shrinkage — translate into their language.

2. What’s the strongest framing for a capacity case?

Put a number on the do-nothing path and the hire often becomes the cheap option.

3. How should you express a 12-FTE shortfall to finance?

Use cost-of-attrition, cost-per-contact and EBITDA figures to speak finance’s language.

4. How should scenarios be presented?

Decision-makers want a position to react to, not just options.

5. Which date should you emphasise most?

Deadlines force decisions; vague need-by dates drift — spell out when the decision is due.

Build the numbers with the planning value calculator and EBITDA impact calculator, or revisit the Communication Skills track.

You’ve finished the capacity planning track. Ready for your certificate? Take the final exam →