Most quarterly business reviews are expensive calendar events that produce nothing you couldn't have learned from a shared doc.

Every ops leader knows the pattern: an hour of slides, a lot of nodding, a handful of "great question" deflections, and a vague commitment to "dig deeper on that offline." The meeting ends. The quarter continues. Nothing changes.

A quarterly business review template doesn't fix this if it's just a better deck structure. What actually fixes it is changing the question the meeting is trying to answer — from "what happened?" to "what are we deciding?"

Here's a quarterly business review template that works, and the principles behind each piece of it.

What a quarterly business review is (and what it's not)

A quarterly business review is a structured leadership meeting to assess company performance against goals, identify what's blocking progress, and align the executive team on priorities for the next 90 days. At its best, it's a decision-making forum with data. At its worst, it's a reporting theater where everyone presents their best face to leadership.

The QBR is not a status update. If your leadership team is hearing for the first time in a QBR what's behind and what's ahead, your operating system has failed. The quarterly review should synthesize information people already have, not reveal it.

It's also not a post-mortem. Looking backward to understand what happened is valuable. Spending 80% of a four-hour meeting relitigating Q1 is not. The past is context; the next quarter is the point.

The quarterly business review template

Pre-read (sent 48 hours before)

The pre-read is not optional. It's the operating contract. If your leadership team won't read a two-page brief before a two-hour meeting, you don't have an alignment problem — you have a culture problem that the QBR template won't fix.

The pre-read should include:

• Company scorecard: The 5-8 metrics that define whether the business is on track. Revenue, pipeline, headcount, product velocity, customer health — whatever your business runs on. With actuals, targets, and delta from last quarter.

• Goal status by department: Each function's OKRs or KPIs, flagged as green / yellow / red. One line of context for anything yellow or red. No essays.

• Key decisions on the agenda: What does leadership need to decide in the room? List them explicitly. This signals to every participant what they're actually there for.

The pre-read is distributed, reviewed, and questions are submitted before the meeting. Anyone who doesn't read it doesn't get meeting time to get up to speed.

QBR agenda structure (2 hours)

0:00 — 0:15 | Company scorecard review (15 min)
Not a walk-through — a discussion of anomalies. What moved unexpectedly? What didn't move when it should have? The numbers were in the pre-read. This time is for interpretation and surfacing anything that isn't already understood.

Rule: no one presents data that's in the pre-read. Only speak to what the data means and what questions it raises.

0:15 — 0:50 | Department reviews (35 min, ~7 min each)
Each department lead gets 7 minutes: 2 minutes on what moved, 3 minutes on what's blocked or at risk, 2 minutes on the one decision they need from leadership. That's it.

The constraint is intentional. Seven minutes forces prioritization. It's enough time to communicate the essential, not enough to hide in slides.

Format for each department's slot:

• One thing that went well (with a number)

• One thing that's behind (and why — root cause, not blame)

• One decision request or resource need

0:50 — 1:20 | Cross-functional blockers (30 min)
This is the highest-leverage part of the QBR. Every department has something that's blocked because of a dependency on another team, a lack of a decision, or an unresolved conflict. These items rarely surface without a dedicated forum.

The facilitator pre-collects blocker submissions from each team and runs through them one at a time. Each blocker needs: an owner, a proposed resolution, and a deadline. Blockers without owners don't get discussed.

1:20 — 1:45 | Q[X+1] priorities (25 min)
What are the two or three things that absolutely have to happen next quarter for the company to succeed? Not the full OKR list — the must-haves. If you can only do three things next quarter, what are they?

This section often reveals misalignment that's been quietly festering. Different executives often have different answers. Surfacing that disagreement explicitly — and resolving it in the room — is one of the most valuable things a QBR can do.

1:45 — 2:00 | Decisions and action readout (15 min)
Every decision made in the meeting gets read back aloud: who owns it, what done looks like, and when it's due. Every action item assigned gets the same treatment. This is not optional. It's how the meeting converts from conversation to execution.

Someone is responsible for distributing the written action log within one hour of the meeting ending. Not by end of day. Within one hour.

QBR preparation checklist

Use this three weeks before each quarterly business review:

• [ ] Week 3 before QBR: Lock the agenda and distribute to all participants. Collect blocker submissions from each department lead.

• [ ] Week 2 before QBR: Department leads prepare their 7-minute slots. Each slot reviewed by the CoS or ops lead for relevance and concision.

• [ ] Week 1 before QBR: Compile the company scorecard with actuals vs. targets. Write the pre-read. Flag any red metrics that need leadership decision before the meeting.

• [ ] 48 hours before: Distribute pre-read. Require acknowledgment. Collect any pre-submitted questions.

• [ ] Morning of: Confirm AV, confirm attendance, confirm the blocker list is compiled and ordered.

• [ ] Within 1 hour after: Distribute the written action log.

Common QBR failure modes

Even with a good template, quarterly business reviews fail in predictable ways. Here's what to watch for.

Data prep done in the meeting. If someone is pulling up a spreadsheet to answer a question during the QBR, the meeting wasn't ready. The answer to "what's our current churn rate?" should never need to be looked up during a quarterly review. If it does, the operating system between QBRs is broken.

No pre-read. Meetings without pre-reads become lectures. Everyone learns the state of the business in the room, together, for the first time. This wastes the most expensive time in the company and signals that executives don't have shared context between reviews.

Too many participants. A QBR with 20 people in the room is a town hall, not a decision forum. Keep the principal group to the people who own the decisions. Everyone else can read the post-meeting summary.

Goals that nobody's updated. If the OKR data going into the QBR is stale — percentages nobody's touched since last month — the scorecard is fiction. This is a between-quarter operating problem, not a QBR problem. But it makes QBRs useless. Brev solves this by keeping goals updated automatically between reviews, so the data going into the QBR actually reflects what's happening.

No action readout. Without a written action log distributed within an hour, the meeting becomes a conversation with good intentions. Decisions that aren't written down aren't decisions — they're discussion points. The action readout is what separates a QBR from a talk.

How AI changes the quarterly business review

The most time-intensive parts of running a good QBR are the ones that should be automated: compiling the scorecard, updating the goal status dashboard, summarizing department performance against targets, and generating action item logs after the meeting.

Meeting intelligence tools have begun closing this gap meaningfully. The best ones don't just transcribe — they extract action items, tag owners, connect outputs to the relevant goals, and route follow-ups to the right people. Gartner research found that executives spend up to 23 hours per week in meetings, with the majority classified as unproductive. Cutting the prep and post-processing overhead of QBRs is one of the highest-leverage places to apply AI in ops.

Feel free to try out our AI business reviews capability for automated MBR and QBR prep. Brev's cadence management handles the automatic side of this: goals stay updated between QBRs because they're pulling live data from your actual tools, so the scorecard is real when it matters. Meeting intelligence handles the action extraction after. The result: less prep, sharper data, faster follow-through.

FAQ: Quarterly Business Review

How long should a QBR be?
Two hours for most companies at the executive level. Half-day formats can work when the company is at a major inflection point (end of year, post-fundraise, major strategic pivot). Anything over half a day is usually a sign the meeting is doing work that should happen between meetings.

Who should be in the QBR?
The executive team plus any department leads whose decisions affect company-level outcomes. The rule of thumb: if someone doesn't have a decision to make or a blocker to raise, they should read the summary, not attend the meeting.

How often should we hold QBRs?
Quarterly — hence the name. Some fast-moving companies run monthly business reviews (MBRs) in between. The QBR is for strategic alignment. The MBR is for course correction. They're different meetings with different purposes.

What's the difference between a QBR and an all-hands?
Completely different meetings. The QBR is a decision forum for leadership. The all-hands is an information broadcast for the whole company. Running them as variants of each other is a common mistake. They need separate designs, separate agendas, and separate participant lists.

The quarterly business review is one of the few meetings that's worth doing well. A tight template, a real pre-read, and a disciplined action readout are the difference between a meeting that drives the next quarter and one that describes the last one. Read more from the blog on how ops teams are building operating cadences that actually work.