Explain month-end variance without the spreadsheet hunt
A cited variance narrative explains material movements, separates timing from structural change, and assigns follow-ups.
The problem
Leaders see actual versus budget but spend the review meeting discovering what moved instead of deciding what to do.
What you get
A working system with the steps, tools, checkpoints, and expected return made explicit.
- Setup
- 60 minutes
- Back each week
- 2 hours
- Difficulty
- assisted
Expected return
The working case
A planning estimate, not a guaranteed result. Measure the first four weeks against your own baseline.
96
hours returned per year
At 2 hours/week across 48 working weeks.
1
week to earn back setup
Compare the setup estimate with the weekly time returned.
Operating contract
Input
The source material, constraints, and examples a human would need to do this work well.
Checkpoint
A person reviews judgment calls, sensitive content, unfamiliar tools, and irreversible actions.
Success signal
Track time returned, corrections required, and exceptions. Keep it only if the measured result compounds.
Before you start
- ·Closed period actuals
- ·Approved budget and materiality policy
The steps
- 01
Export approved budget, actuals, prior period, and account-owner commentary.
- 02
Set materiality thresholds in dollars and percentage by account class.
- 03
Generate a narrative only for material variances, referencing exact rows.
Copy this prompt
Explain variances above [threshold]. For each: amount, percentage, exact source row, likely timing vs structural classification, and question for the owner. Do not invent causes. Data: [tables]
- 04
Controller validates every explanation before the management pack is released.
What it runs on
- Excel
Source-controlled finance model.
- Google Docs
Reviewable narrative.
Where this goes wrong
- Correlation is not a cause; missing owner commentary stays an open question.
- Never upload payroll or customer-level finance data to an unapproved model.
Definition of done
Run it for four weeks. Then make it earn its place.
- □ Baseline the manual time before launch.
- □ Keep a human approval step for consequential output.
- □ Record corrections and exceptions, not just successes.
- □ Expand, revise, or retire it after the first review.
Build the system around it
Related workflows
If this one stops working, tell us. Three reports in a month and it leaves the library until a person has looked at it again.