Forecast / Money Pre-Read How-to: Walk Into the Review Ready
The pack lands in your inbox the night before the monthly business review. Yellow cells, variance columns, and a forecast that somehow moved again. Your job in this play is not spreadsheet mastery. It is decision readiness: know the story, own what moved in your scope, and walk in with asks, not panic.
This is workplace finance literacy for managers and directors. It is not tax, accounting, or investment advice. Formats and definitions vary by company and accounting standards. Use your Finance partner for real decisions.
Play card
| Time box | 25-40 minutes (solo); optional +10 minutes with Finance |
| Players | You as the reader; optional Finance partner for clarifying questions |
| Goal | One-page pre-read note: story, owned variances, risks, asks, decisions you may face |
| Done when | You can say the story in two sentences and name what you will ask or propose |
Related depth: Finance for Non-Finance Managers, Budget vs Forecast vs Actual, P&L Explained Simply, and the companion P&L in 10 Minutes play. Stage context: Director / VP hub.
When to use (and when not)
Use this play when: you have a forecast pack, flash, or financial report before an MBR, forecast lock, board cascade, or leadership money review; you own or co-own lines in the pack; you need questions ready, not a deep dive.
Do not use this play when: the pack is a full reforecast redesign, audit finding, or accounting policy change; you need a partner session to rebuild assumptions; legal or tax judgment is required. Book Finance instead of winging it.
Pack arrives late or incomplete? Run a compressed 15-minute version: story pass on what exists, list missing artifacts, and open the meeting with “here is what I could not pre-read.” Do not invent numbers to fill gaps.
Prep: what should be in the pack
Ideal artifacts (names vary):
- Budget: the plan you committed to (often annual or period plan).
- Forecast: the current best estimate of how the period will end.
- Actuals: what has already posted for closed periods or month-to-date.
- Variance notes: why forecast or actual differs from budget (or prior forecast).
- Assumptions: volume, price, hiring, timing, one-time items.
Plain-language glossary
| Term | Plain meaning |
|---|---|
| Budget | The plan you planned against |
| Forecast | Updated expectation of the outcome |
| Actual | What already happened / posted |
| Variance | Difference between two of the above |
| Flash | Early or incomplete view; treat as provisional until Finance says final |
Timed steps
1. Story pass (8 minutes)
Skim for narrative, not every cell. Ask: Are we ahead or behind the story leadership sold? Is this a growth problem, an efficiency problem, a timing problem, or a one-time spike? Write one sentence: “The story is ___.”
2. Ownership / variance pass (10 minutes)
Circle only lines in your scope. Separate:
- Controllable soon: hiring pace, contractors, tools, travel, vendor renewals, discounting you influence.
- Noise / allocations: shared IT, rent, brand, corporate allocations you do not approve.
- One-time items: true-ups, catch-up invoices, unusual credits.
For each owned variance, note: what moved, why you believe it moved, and whether the forecast assumption still holds.
3. Ask list (5 minutes)
Draft 3-5 clarifying questions for Finance or the room. Prefer precision over volume.
4. Decision readiness (5-10 minutes)
List decisions you may be asked to make in-room: cut, delay hire, reforecast a line, accept a risk. Mark any that need a second pass after the meeting. Do not commit to permanent cuts or hires on first sight of a noisy flash.
Script: questions that sound serious
Use calmly; tone matters as much as content.
- “Which variance is timing versus true run-rate change?”
- “What assumption under this forecast would break first if X slips?”
- “Is this line direct to my org, or an allocation?”
- “Are we looking at flash or final, and what still might move?”
- “If we pull this cost down, what customer or delivery risk are we accepting?”
- “Cash versus P&L: is leadership reacting to accrual noise or a cash issue?”
Required output: one-page pre-read note
Copy this and fill it before you join:
PRE-READ NOTE - [Meeting / Date]
1) Story (2 sentences):
2) Owned variances that matter:
3) Risks / one-time items to name aloud:
4) Asks for Finance or peers:
5) Decisions I may be asked - ready / need second pass:
Managers who only read yellow highlights arrive as spectators. Managers who write these three core lines (story, owned move, ask or proposal) arrive as owners.
Hypothetical pack excerpt (labeled sample)
All figures fictional; for teaching only.
| Line (sample) | Budget | Forecast | Variance | Your note |
|---|---|---|---|---|
| Team opex | 400 | 440 | +40 | Two contractors extended; controllable |
| Allocated IT | 80 | 95 | +15 | Allocation; do not own the vendor |
| One-time true-up | 0 | 25 | +25 | Call out as non-run-rate |
Watch-outs
- Confusing cash with P&L (accrual timing can look like a crisis or a fake win).
- Treating one-time items as the new normal in the forecast.
- Forecast optimism without named assumptions.
- Inventing “industry benchmarks” or margin targets you cannot source.
- Committing to cuts or hires in the room without a second pass and stakeholder check.
- Owning allocations you cannot move.
How this differs from P&L in 10 Minutes
P&L in 10 Minutes builds income-statement literacy (story + levers on a statement). This play prepares you for a review pack: budget, forecast, actuals, and the questions you will face. Run literacy first if the statement itself still feels foreign; run this play when the pack is already on your calendar.
After the meeting
Update your note with decisions, owners, and revisit dates. Share owned actions with your team within 48 hours. For ongoing money language, stay in the Finance hub and Budget vs Forecast vs Actual.