How to run a monthly business review with data
Run a monthly business review from a stable metric dictionary and pre-read. Reconcile actuals to source, compare with plan, forecast, and prior periods, focus meeting time on material exceptions and driver evidence, convert discussion into explicit decisions and owners, and begin the next cycle by reviewing prior actions. The report should preserve definitions and automate repeatable preparation without automating judgment.
Where errors enter the process
Monthly reviews often spend most of the meeting debating whose number is correct or walking through every page. Decisions and actions disappear after the call, and report preparation repeats manually.
A method you can follow
- Lock calendar and ownership: Set data cutoff, source owners, refresh deadlines, review date, and restatement policy.
- Prepare reconciled pre-read: Update the scorecard, material variances, drivers, forecast, risks, and prior action status.
- Run an exception meeting: Spend time on gaps, trade-offs, and decisions; move background questions to follow-up owners.
- Close the loop: Record decision, owner, due date, success measure, and data question for the next cycle.
From the field · Small-business owner
Run a useful monthly review for a local retail business
Sales, staffing, stock, cash, and customer feedback live in separate spreadsheets. Meetings drift into anecdotes because definitions change and nobody can trace last month's promised action to this month's result.
Columns used in the example
period · metric · actual · target · prior_period · owner · action · due_date
Follow it with your own file
- Refresh only after source and control checks pass.
- Start with prior actions and material exceptions, not every chart.
- Separate performance outcome, quantified driver, hypothesis, and decision.
- Record owner, due date, and evidence required for each action.
Check: Published totals must reconcile to source systems, KPI definitions must match the dictionary, and every action should reappear with status in the next review.
Sign-off questions
- Data cutoff stated
- Metrics reconciled
- Prior actions updated
- importance applied
- Decisions captured
- Owners and dates assigned
Separate preparation from decision time
Source reconciliation and basic clarification belong before the meeting. The pre-read should arrive early enough for leaders to challenge evidence and propose alternatives.
During the review, the report becomes a shared decision record rather than a presentation script.
Keep continuity without ignoring change
Stable definitions make trends meaningful. When the business changes, update the dictionary deliberately and show the impact of the change rather than silently rewriting history.
Add diagnostic pages when an exception emerges, but do not allow the permanent report to grow without editorial discipline.
Evidence worth tracing
- Teams bring different versions of the same KPI.
- Pages change structure every month.
- The meeting has no explicit decisions log.
- Prior actions are not reviewed.
MBR artifacts and owners
| Artifact | Purpose | Owner |
|---|---|---|
| Metric dictionary | Prevent definition disputes | Data and finance |
| Pre-read | Prepare evidence | Report owner |
| Decision log | Record commitments | Meeting lead |
| Action tracker | Close follow-through | Named action owners |
Doing these steps in Prepyr
Upload a CSV working copy in Prepyr. Describe the result you need: Run a monthly business review using reconciled metrics, named owners, and repeatable follow-up. Check the columns selected, preview any proposed changes, and compare the output with the source before applying or exporting it.
Prepyr steps used here: Recurring reports · Saved workflows · KPI dictionary · Email sharing
The essential checks
- Use a stable scorecard and metric dictionary.
- Distribute the reconciled pre-read before the meeting.
- Discuss exceptions and decisions rather than reading charts aloud.
- Carry owners and due dates into the next review.
A shorter, more decisive operating review whose numbers are trusted and whose actions remain visible from one month to the next.
Questions readers usually ask next
How long should an MBR be?
Long enough for material decisions, often 60 to 90 minutes; reduce scope before extending a recurring meeting.
What is the difference between MBR and dashboard?
A dashboard monitors; an MBR explains exceptions, makes decisions, and tracks accountability.
Should reports update after the cutoff?
Use a controlled restatement policy so late changes are visible and do not silently alter the reviewed record.