The quarterly business review tells you where you ended up. The monthly business review is how you avoid ending up there in the first place.

Most ops teams run QBRs and skip MBRs entirely, or they run MBRs that have drifted into 90-minute status updates where everyone reports numbers nobody acts on. Both are a waste. Done right, a monthly business review is the highest-leverage meeting in your operating cadence — the place where problems get fixed when there's still time to fix them.

Here's a monthly business review template that actually drives decisions, and the principles behind why it works.

What a monthly business review is (and what makes it different from a QBR)

A monthly business review is a structured leadership meeting that evaluates company performance against plan at the 30-day interval — specifically to catch problems early enough that course corrections are still possible.

The QBR is for strategic alignment at the quarter boundary. The MBR is for operational course correction in real time. Different purposes, different formats, different decision types.

In a QBR, the question is: Where are we and where are we going next quarter? In a monthly business review, the question is: What is off track right now, who owns fixing it, and what decision do we need to make before month-end to avoid a bigger problem?

The most common failure mode is treating the MBR like a mini-QBR — retrospective, report-heavy, high on update and low on action. That's the template to avoid.

The monthly business review template

Pre-read (distributed 24 hours before)

The pre-read compresses 80% of the status information so the meeting itself can focus on decisions. One page. Three sections:

• Metrics scorecard: 5–8 company-level metrics with actuals vs. plan and vs. last month. Revenue, pipeline, key product metrics, customer health signals. Anything green stays in the pre-read. Only yellow and red metrics get meeting time.

• Goal status: Current OKR progress by department, with a one-line note on anything that has moved in the last 30 days — up or down. Not a full OKR report. A pulse check.

• Decision agenda: The two or three things that need a decision in the room. If there's nothing that genuinely requires a decision, the MBR is optional that month. (This is rare, but it happens.)

The pre-read isn't optional for attendees. Anyone who hasn't read it before the meeting doesn't get meeting time to catch up.

MBR agenda (60 minutes)

0:00 — 0:10 | Metrics review (10 min)
Quick scan of the scorecard. The facilitator reads through the numbers; attendees speak only to anything that changed unexpectedly or requires context. Green metrics don't get discussed. The goal is to confirm shared understanding in 10 minutes, not to review every metric with commentary.

0:10 — 0:30 | Off-track items (20 min)
Any goal or metric that's yellow or red gets a structured 5-minute discussion: What happened? Is this recoverable this month? What does recovery require? Who owns it? This is the core of the MBR. It's where small problems get contained before they become quarterly problems.

The rule: one owner per item. "We're working on it as a team" isn't an owner. Name the person. Assign the action. Move on.

0:30 — 0:50 | Decision items (20 min)
The two or three agenda decisions get deliberate time. Each decision owner presents the question briefly (pre-read should have the context) and the options on the table. The goal is a decision in the room, not a longer discussion. If a decision can't be made in 10 minutes, it either needs more data (assign that explicitly) or more people aren't aligned than expected (that's a different conversation).

0:50 — 1:00 | Action readout (10 min)
Every owner from the off-track discussion and every decision made in the room gets a written action item read back aloud: owner, action, deadline. Someone is distributing this within one hour. Not end of day.

Monthly business review preparation checklist

• [ ] Week 1 of the month: OKR and KPI data refreshed. Goal owners flag anything off track proactively — don't wait for the MBR to surface bad news.

• [ ] T-5 days: Facilitator (CoS or VP Ops) compiles metrics scorecard with actuals vs. plan.

• [ ] T-3 days: Decision agenda items confirmed. Any item without a clear question and at least two options isn't ready for the meeting.

• [ ] T-24 hours: Pre-read distributed. Confirmation required from attendees.

• [ ] Morning of: Confirm attendees have read the pre-read. Confirm AV if needed.

• [ ] T+1 hour: Written action log distributed to all participants and relevant stakeholders.

Common MBR failure modes

The MBR becomes a second all-hands. When the meeting grows beyond 10 people and the format shifts from decision-making to information-broadcasting, it stops being useful. Keep the MBR tight: the people who own decisions and the people who need to make them.

Every metric gets equal time. Green metrics don't need discussion. The facilitator's job is to keep the meeting focused on yellow and red. If every number gets a walkthrough regardless of status, the meeting runs long and the critical items get rushed.

Goal data is stale. An MBR built on OKR data nobody's touched in three weeks is a meeting built on fiction. The data in the room has to reflect what's actually happening. If goals require manual updates to stay current, they'll drift — and the monthly review will systematically underreport problems until they're too big to fix. Brev keeps goal data current automatically by pulling from the tools where work actually happens, so the scorecard going into the MBR is real.

No action readout. An MBR without a written action log is a conversation. Good conversations don't move companies forward. The readout is mandatory.

MBR vs. QBR vs. WBR: when to use each

Ops teams that run all three cadences often have the same confusion: what actually belongs in each meeting?

• Weekly business review (WBR): Operational check-in. What happened this week? What's blocked? What needs to move before next week? Focused on near-term execution. Typically 30–45 minutes.

• Monthly business review (MBR): Performance vs. plan at the 30-day mark. What's off track? What decisions are needed to course correct before month-end? 60 minutes. Decision-focused.

• Quarterly business review (QBR): Strategic alignment at the quarter boundary. How did we perform? What are the next 90 days? Two hours. Longer time horizon, higher strategic altitude.

The cadences reinforce each other. WBRs keep the week moving. MBRs catch month-level problems before they become quarter-level problems. QBRs set the strategic direction the other two run toward. Companies that skip the MBR often find that problems which should have been caught in month two don't surface until the QBR — when options are limited.

FAQ: monthly business reviews

How long should an MBR be?
60 minutes for most companies. If your MBR is consistently running over, the pre-read isn't doing its job — people are catching up in the room instead of before it.

Who should attend the monthly business review?
Department leads who own key metrics, plus the executive team. Keep it under 10 people where possible. Observers can read the post-meeting summary.

What's the difference between a monthly business review and a monthly ops review?
In most companies, these are the same meeting with different names. Some distinguish them: ops review focuses on internal execution (delivery, headcount, cost), while the business review focuses on external-facing metrics (revenue, pipeline, customer). If you have both, they should probably be combined or sequenced back-to-back to avoid duplication.

What happens if we skip a month?
Problems accumulate. A well-run monthly business review is a pressure release valve — it surfaces issues early and assigns owners before problems compound. Companies that go two or three months without an MBR consistently find they're having harder conversations in the QBR than they should be.

A monthly business review doesn't need to be a long meeting or a complex process. It needs to answer one question: what's off track, and who's fixing it? Try Brev's Cadences & Rhythms and Artifacts & Reviews to automate your entire process. A tight pre-read, a decision-focused agenda, and a written action log within an hour are the whole thing. Read more from the Brev blog on how ops teams are building meeting cadences that actually hold companies accountable.