Monthly Business Review: The Agenda, the Deck and Each Slide
If someone talks through the slides for forty minutes, the meeting has already failed. Send the numbers ahead, spend the hour on the exceptions, and leave with named actions.
A monthly business review (MBR) is a recurring meeting where the people who own a business's numbers check them against plan, discuss what is off course, and leave with named actions. A good one has a pre-read, a 60-minute agenda, and a deck of about eight slides. Its output is a list of decisions, not a presentation. Below is the agenda I would use, each slide, and the comparison mistakes that waste the hour.
If what you need is a written monthly report rather than a meeting, start with our monthly report template. For the quarterly version, see the QBR deck, slide by slide.
A 60-minute agenda
| Minutes | Item | Rule |
|---|---|---|
| 5 | Last month's actions | Done, not done, or dropped. No stories. |
| 5 | Scorecard | Everyone has read it. Only ask whether anything is wrong. |
| 30 | Exceptions | Each metric outside its threshold, and its owner explains it. |
| 15 | Decisions | What changes because of what you just heard. |
| 5 | Actions | One name and one date for each, read back aloud. |
Notice what is not there: a walkthrough. Send the deck at least a day ahead and treat it as read. The hour is too expensive to spend on narrating numbers people can read themselves.
The MBR deck, slide by slide
1. Actions from last month
A table of what was promised, who owned it, and the status. Putting this first changes behavior more than anything else on this page, because people know it opens the next meeting.
2. One-paragraph summary
Three sentences: how the month went against plan, the one thing that needs attention, and any decision required today. Write it last. Our guide to writing an executive summary has the method.
3. Scorecard
Four to six metrics, with the same ones every month. An illustrative layout:
| Metric (example) | Actual | Plan | vs plan | vs same month last year |
|---|---|---|---|---|
| Net sales | $412k | $430k | −4% | +11% |
| Gross margin | 46% | 45% | +1 pt | +2 pts |
| New customers | 318 | 300 | +6% | +9% |
| Marketing spend | $61k | $55k | +11% | +3% |
4 to 6. One slide per exception
Only metrics outside the threshold get a slide, each with a breakdown that shows where the variance came from: which product, channel, customer or rep. The title states the finding, such as Net sales missed plan by 4% on two delayed wholesale orders, not Net sales.
7. Outlook
Where next month and the quarter are heading, and any risk the room should know about now rather than in six weeks.
8. Decisions and actions
Left blank before the meeting and filled in during it. This slide becomes slide 1 next month.
Definitions and full tables go in an appendix. They need to exist, and they do not need meeting time.
Which comparisons hold up
- Against plan is the main one. It answers the question the meeting exists for.
- Against the same month last year removes seasonality.
- Against last month is the one I would drop from the scorecard. It is the most intuitive comparison and the noisiest. Seasonality and calendar length both move it, so a real problem and a short month look the same.
A month with 23 working days and a month with 20 can differ by 15% on working days alone. If your business sells on weekdays, compare per working day, or put the day count on the slide.
Set exception thresholds in advance. Something like 5% from plan on revenue, 2 points on margin is enough. Without a threshold, the meeting drifts toward whichever chart looks most interesting.
What goes wrong
- Holding it before the close. You discuss a number that changes the following week, and credibility goes with it. Label anything preliminary on the slide.
- Definitions drifting. The first ten minutes go to why sales and finance have different revenue figures. Net versus gross sales is the classic case. Settle each definition once and print it in the appendix.
- Actions with two owners. They do not get done. One name per action.
The clearest sign a review has failed is who does the talking. When the person who built the deck speaks for most of the hour, everyone else has become an audience, and an audience does not own anything. Having owned a P&L, I found the useful moment was usually when a number owner said, before I asked, that something was off and what they intended to do about it. You cannot put that on a slide. You can only make room for it by refusing to spend the meeting reading numbers aloud.
Building the MBR deck from your data
The expensive part of an MBR is usually the two days before it. Quiriz for PowerPoint and Quiriz for Google Slides build the deck from your connected data and files. Describe it in one line, such as monthly business review for October: net sales, margin, new customers and marketing spend, with the biggest variances broken down, and you get a plan of slides and questions to edit before anything is built. Next month, Refresh all asks every question again, in place.
Definitions live in Company Context, so net sales in the scorecard matches net sales in the exception slide.
What it cannot do. It can show that net sales missed because two wholesale accounts dropped. It cannot know that those orders slipped because a customer delayed a launch, because that lives in someone's head. It also cannot compare against a plan that is not in your data, so upload your plan as a dataset if you want that column. The explanation and the decision are what the meeting is for, and those stay with your team.
Spend the two days before the MBR on something else
Try questions on sample company data with no signup, then build your first review deck.
Try Quiriz free →