A budget versus actual review is a short, fixed meeting where the people who own each part of the plan compare what was planned with what happened, and every difference that matters gets one written line of explanation with a name against it. Run it on the same agenda every period, require the written explanation before the meeting rather than during it, and keep a dated record of what was said and who is following up.
The point of the meeting is not to discover what the numbers are. Everyone should know that before they walk in. The point is to collect an owned, written explanation for each difference and to leave with a short list of follow-ups that have names and dates on them.
This article is general information about process and recordkeeping. It is not accounting, tax, audit, legal or investment advice. How any transaction is recorded or classified is a judgment for a qualified accountant who knows your business, and which reporting standards and obligations apply varies by organization and by jurisdiction, so those questions belong with a qualified professional.
What a budget versus actual review is for, and what it is not for
A budget versus actual review does three jobs. It confirms that the people who own budget lines have looked at their own lines. It produces a written explanation for each difference worth explaining. It assigns the follow-up work.
It does not do the preparation. If the meeting is where people first see the comparison, the meeting becomes a reading session and nothing gets decided. Circulate the comparison before the meeting and treat attendance as confirmation it was read.
It also does not settle how anything is recorded. When a difference turns out to be a question about treatment or classification rather than about activity, that question leaves the room and goes to the qualified accountant who handles your books. Note it as referred and move on.
The fixed agenda for a budget versus actual review
Use the same agenda every period, in the same order. A fixed agenda is what lets the meeting stay short, because nobody has to work out what happens next.
- Confirm the comparison everyone is working from. Name the version and the date it was produced. If someone is holding a different version, stop and fix that before discussing anything.
- Confirm last period's follow-ups. Each open item from last time is marked done, still open with a date, or dropped with a reason. This goes first on purpose, because it is the item most likely to be skipped if it goes last.
- Walk the differences, owner by owner. Not line by line through the whole plan. Each owner speaks only to their own differences, reads out the written explanation already submitted, and takes questions.
- Capture new follow-ups as they arise. One line each: what, who, by when. Written down in the room, read back before moving on.
- Note anything referred out. Questions that are matters of treatment, obligation or judgment get listed as referred, with the name of the person they are going to.
- Agree the record and close. The notes are confirmed out loud, then circulated.
Keeping it short
Set a standing length and hold it. The discipline that keeps the meeting short is not talking faster, it is requiring the written explanations in advance so the meeting is about questions rather than narration.
Where a difference needs real discussion, take it out of the meeting. Name the two or three people who need to be in that conversation, record it as a follow-up, and keep the main review moving.
Who brings what
Give every attendee one clear thing to bring. Ambiguity about who prepares what is the usual reason the meeting drifts.
| What they bring | |
|---|---|
| Budget line owner | A written explanation for each of their own differences, submitted before the meeting |
| Finance preparer | The comparison itself, a named version, and the list of differences that need an explanation |
| Meeting chair | The agenda, last period's follow-up list, and the timekeeping |
| Note taker | The record template, filled in live and circulated afterward |
| Referred-question holder | The status of anything referred out in earlier periods |
The chair and the note taker should not be the same person. The chair is listening for whether an explanation is actually an explanation, and that does not survive also writing everything down.
Which differences require an explanation is a threshold your organization sets for itself with its qualified advisors, and that threshold belongs in your own written documents rather than being decided freshly in each meeting. The important thing is that the rule exists, is written, and is applied the same way every period.
How a variance gets explained in one written line
Hold every owner to a single written line. The discipline of one line is what forces the explanation to be about a cause rather than a restatement of the difference.
A usable line names what happened, when, and why it differs from what was planned. "Plan assumed one supplier for the full period; a second supplier was added mid-period after the first could not cover the volume" is an explanation. "Spend was higher than plan" is not; it just repeats the comparison in words.
The line should also say whether the cause is finished or ongoing, because that is what determines whether a follow-up is needed. "One-off, now complete" and "ongoing, continues next period" lead to very different conversations.
If the owner cannot write the line, that is the finding. Record it as "cause not yet established", assign it as a follow-up with a name, and move on. A written admission that a cause is unknown is far more useful than a vague sentence that reads like an answer.
Keep the lines in one place, period after period, against the same budget lines. Read in sequence, those lines become the plainest history of the business your records hold.
Who follows up, and how that gets tracked
Every follow-up gets one owner by name, one action stated as a verb, and one date. No shared ownership, no "the team will look at it", no open-ended actions.
Track them in one list that persists between meetings rather than in the notes of each separate meeting. The list carries the item, the owner, the date it was raised, the date it is due back, and the current status. The agenda item that opens each review is a read-through of that list.
Close items explicitly. An item that has been overtaken by events gets marked dropped with a reason and a date, not quietly deleted. The record of what was dropped and why is part of what makes the list credible next time someone reads it.
Where a follow-up is a referred question, the owner is whoever is responsible for asking it and bringing the answer back, not the outside professional who answers it. That distinction keeps items from stalling.
The record of the meeting
The record is the output. Treat it as the deliverable rather than as a courtesy.
Keep it to one page per period, with a fixed shape so it can be compared across periods: the date, who attended, the version of the comparison used, each explanation line as it was written, the follow-ups with owners and dates, and the referred items. Store it where the comparison itself is stored so the two can be read together.
Date it and name the note taker. Circulate it to everyone who attended and to anyone whose budget line was discussed in their absence. Silence after circulation is not agreement, so give people a clear way to correct the record and note any correction as a correction rather than editing it away.
Keep every period's record rather than overwriting. A run of these pages is what lets a new person understand how this business explains itself, and it is what lets you answer a question about an earlier period without reassembling it from memory. It is also the fastest handover material you will ever produce for whoever runs the meeting after you.
Review the agenda itself once in a while. If an item is never used, retire it. If the meeting keeps needing something that is not on the agenda, add it and keep the old version.
For a one-page agenda and record layout you can adapt rather than build from scratch, start with the Free Resources page on this site.