← ccPlanning Academy · Communication track

Presenting the forecast

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

ccPlanning academy · communication

Presenting the forecast

A forecast is a recommendation with a number attached — present it like one.

The big idea

Don’t present the forecast. Present the decision.

Nobody wants a number for its own sake — they want to know what to do about it. Open with the implication and the call you’re asking for, then show the forecast as the reason. The number is evidence, not the headline.

Assumptions first

State what it rests on, up front.

Every forecast stands on assumptions — growth, AHT, shrinkage, a marketing plan. Surface the two or three that matter most before someone asks. It pre-empts the “but did you account for…” that derails the room, and it shows your working honestly.

Confidence, honestly

Give a range, not just a point.

A single number implies false precision. “Most likely 12 short, but 8–16 depending on the campaign” is more honest and more useful — it tells people how much to trust it and where the risk sits. Confidence stated well builds trust; false certainty destroys it the day it’s wrong.

Own the recommendation

Say what you’d do.

“Here’s the data, you decide” abdicates the expert’s job. You’ve done the analysis — offer a clear recommendation and the reasoning. Decision-makers can disagree, but they need a position to react to. A planner with a view is far more useful than a neutral data pipe.

Pre-empt the “what if”

Bring the scenarios with you.

You know the questions coming — “what if volume’s higher,” “what if we don’t hire.” Have a scenario or two ready. Answering the challenge before it’s voiced signals control and saves the meeting from spiralling into hypotheticals you can’t answer live.

Structure

Recommendation, why, assumptions, ask.

A reliable shape: here’s what I recommend, here’s the forecast that drives it, here’s what it assumes and how confident I am, here’s the decision I need from you. Detail waits in the back pocket for whoever asks.

The four-line open

What a good forecast pitch sounds like

“I’d hire 12 by September. The forecast says we’re ~12 short over Q4 peak — most likely 12, but 8–16 depending on the autumn campaign. It assumes 5% growth and current shrinkage. I need sign-off this week to hit the recruitment lead time.”

Recommendation, why, assumptions, ask — in twenty seconds. The detail waits in your back pocket. That’s a forecast that gets a decision, not a “leave it with me.”

The takeaway

Lead with the call, back it with the number.

Open on the decision, surface key assumptions, give an honest range, own a clear recommendation, and bring the scenarios. A forecast presented as a confident, well-caveated recommendation gets acted on — a bare number gets filed.

Now test yourself ↓

1 / 8

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

In depth: a forecast is a recommendation with a number attached

Nobody wants a number for its own sake — they want to know what to do about it. So don’t present the forecast, present the decision: open with the implication and the call you’re asking for, then show the forecast as the reason. The number is evidence, not the headline, and a planner who leads with the recommendation is far more useful than one who hands over data and asks the room to interpret it.

Assumptions and confidence, up front and honest

Every forecast stands on assumptions — growth, AHT, shrinkage, a marketing plan — so surface the two or three that matter most before anyone asks; it pre-empts the “but did you account for…” that derails a room and it shows your working honestly. Then state confidence as a range, not a point: a single number implies false precision, whereas “most likely 12 short, but 8–16 depending on the campaign” tells people how much to trust it and where the risk sits. Confidence stated well builds trust; false certainty destroys it the day it’s wrong.

Own the call and pre-empt the challenge

“Here’s the data, you decide” abdicates the expert’s job — you’ve done the analysis, so offer a clear recommendation and the reasoning, and let decision-makers disagree with a position rather than stare at a neutral pipe. Bring the scenarios with you, too: you know “what if volume’s higher” and “what if we don’t hire” are coming, so answering the challenge before it’s voiced signals control and saves the meeting from spiralling. A reliable structure ties it together — recommendation, why, assumptions and confidence, then the ask — with the detail kept in your back pocket for whoever wants it.

The principle to remember: lead with the call, back it with the number. Open on the decision, surface key assumptions, give an honest range, own a clear recommendation, and bring the scenarios — a confident, well-caveated recommendation gets acted on; a bare number gets filed.

Quick quiz

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

1. What should you open with when presenting a forecast?

Present the decision, not the number — the forecast is evidence, not the headline.

2. Why state key assumptions up front?

Surface the two or three that matter before someone asks — it keeps the room on track.

3. How should you express confidence?

A range is more honest and useful; false certainty destroys trust the day it’s wrong.

4. Should a planner offer a recommendation or stay neutral?

‘Here’s the data, you decide’ abdicates the expert’s job — a planner with a view is more useful.

5. How do you handle the inevitable ‘what if’ questions?

Pre-empt the predictable challenges so the meeting doesn’t spiral into live hypotheticals.