The complete guide to quarterly business reviews (QBRs) for leadership teams

A quarterly business review (QBR) is a half-day meeting in which the leadership team looks at the quarter that has just closed, scores it honestly against the plan, and decides what changes for the next one. Done well, it produces a short written list of decisions: what to stop, what to keep, where to move people and money, and who owns each priority for the coming quarter. Done badly, it is a sequence of slide decks in which every function reports green and nothing moves.

This guide covers the internal leadership QBR: what it is for, how to prepare it, a timed agenda, how to score objectives, the decisions it has to produce and how it connects to the monthly reviews either side of it. If you want the working document, the quarterly business review template follows the same structure.

What a QBR is, and what it is not

The term is used for two different meetings. In customer success and account management, a QBR is a meeting with a client to review the value they have received and agree next steps. That meeting is about the relationship. The leadership QBR discussed here is internal. Its audience is the people who run the company, and its subject is whether the company did what it said it would do this quarter, and what that implies for the next one.

It is also not the board meeting, although the two often share data. A board pack explains the quarter to people outside the business. A QBR is where the people inside it decide what to do about it. Merging the two produces a meeting that is too polished to be honest.

What the QBR is for

A leadership QBR has five jobs. An agenda that serves none of them is usually serving the comfort of the people presenting.

• Close the quarter honestly. Score each objective and major initiative against what was committed at the start, not against what people later hoped.
• Learn something specific. Work out why the misses happened: the wrong target, the wrong plan, the wrong owner, or something genuinely outside the team's control.
• Reset priorities. Confirm the few things that matter next quarter and, just as important, what drops off the list.
• Reallocate resources. Move people, time and budget to where the plan now needs them.
• Recommit owners. Leave with one named owner for each priority, who has accepted it in the room.

A useful test: if the QBR did not change at least one priority, owner or allocation, it was a reporting meeting.

Preparation: what has to exist before the room

Most of the value of a QBR is created in the two weeks before it. The meeting itself is for discussion and decisions, and that only works if nobody is seeing the numbers for the first time.

The data pack

One document, owned by one person (often the COO, the finance lead or a chief of staff) and circulated at least three working days before the meeting. Keep it short enough to be read properly. It should contain:

• A financial summary against plan and against the same quarter last year.
• The company KPIs from the executive dashboard, with the trend across recent quarters rather than a single snapshot.
• The OKR scorecard, already scored by each owner.
• The status of each major initiative.
• The top risks, and any decisions leaders want the room to take, submitted in advance.

OKR scoring

Each objective owner scores their key results before the meeting, in writing, with one line of evidence and one line on what they learned. Scoring in the room wastes time and invites negotiation. The room should spend its time on the objectives where the score is surprising, not on reading scores aloud.

Initiative status

For each major initiative, a single line: delivered, partly delivered, not delivered or stopped. Then one sentence on why and one sentence on what is needed now.

The QBR agenda

Half a day works for most leadership teams of five to nine people; a first QBR may need a full day. Protect the second half: the priorities and resourcing blocks are where decisions happen, and they are the first to shrink when the numbers review overruns.

How to score OKRs without turning it into theatre

The scoring method matters less than the consistency with which it is applied. Many teams use the 0 to 1.0 scale popularised by Google, where a stretch objective landing at around 0.6 to 0.7 is treated as a good result. Others use a simple three-level scale: achieved, partly achieved, missed. Either works, provided everyone uses the same one and a few rules hold:

1. Score against the key result as it was committed, not a version quietly revised mid-quarter.
2. Separate committed objectives, which are expected to land in full, from aspirational ones, which are not.
3. The owner scores first, in writing, with evidence. The room challenges the evidence, not the person.
4. Discuss the gap, not the number. The useful question is what the team now knows that it did not know at the start of the quarter.
5. Keep scores out of bonus calculations. Once a score decides pay, people set targets they know they will hit.

If the distinction between objectives and the metrics that run the business is unclear in your team, it is worth settling first. Our piece on OKRs vs KPIs covers it.

The decisions a QBR must produce

Leave the room with a written decision log, read back before anyone stands up. At a minimum it should contain:

• Next quarter's priorities. Three to five, each with a single owner.
• The stop list. Initiatives that end or pause, so the capacity they held is genuinely released.
• Resource changes. People, budget or time moved between teams.
• Target changes. Any KPI thresholds or targets that change, with the reason.
• Escalations. Decisions too large for this room, with who takes them to the board and by when.

A QBR is measured by what changes the following Monday, not by how complete the slides were.

Follow-through: from the QBR to next quarter's plan

The weakest point of most QBRs is the week after: the operational week resumes and the log is forgotten. Follow-through needs its own sequence:

1. Within two working days. The decision log is circulated and each owner confirms their part in writing.
2. Within a week. Owners draft the objectives and initiative plans for their priorities, using the 90-day plan structure.
3. Within two weeks. The plan is agreed by the leadership team and shared with the company in plain language.
4. Every week. Priorities are tracked in the weekly leadership meeting, by exception.
5. Every month. The monthly review checks that the QBR decisions were actually carried out.

Monthly vs quarterly business reviews

The two reviews do different jobs and should not be confused. The monthly business review (MBR) is about performance and course correction inside a quarter whose priorities are already set. The QBR is the point at which the priorities themselves can change. A company that only has QBRs discovers problems too late; a company that only has MBRs never resets.

The monthly business review template is built to sit inside the same rhythm. How the weekly, monthly and quarterly layers fit together is covered in how to create an operating cadence.

Example: the QBR at Marés Altas

Marés Altas is a fictional company used for illustration: a food distribution business with around a hundred and twenty people, a leadership team of six and a quarterly planning cycle in its second year.

The operations director owns the data pack and circulates it on the Wednesday before a Monday QBR. Of the five objectives set for the quarter, three are scored as achieved, one as partly achieved and one as missed. The miss is the launch of online ordering for restaurant clients. The owner's written note is direct: the integration with the warehouse system took longer than planned, and the team underestimated how much of the work sat with an external supplier.

The room does not spend time on the three achieved objectives. It spends forty minutes on the missed one and reaches a clear conclusion: the objective was right, the plan was wrong, and the dependency should have been raised in the second monthly review rather than discovered at quarter end. In the priorities block, the team decides to keep online ordering as the top priority, pause the planned expansion into a new region for one quarter, and move two people from that project onto the integration.

The decision log has six lines: four priorities with owners, one item on the stop list and a standing check on external dependencies in every monthly review. Nothing dramatic, all of it specific.

Common ways QBRs go wrong

• Everyone presents. The meeting becomes a sequence of functional updates, and the cross-functional decisions never get time.
• Everything is green. Leaders score generously because a miss feels like a personal judgement rather than information.
• No stop list. New priorities are added and nothing is removed, so the team starts the quarter already overloaded.
• The real decisions happened before. If the CEO has settled the priorities privately, the QBR is a performance and the team knows it.

These are design problems more than people problems. Setting up the planning and review cycle properly is the core of our quarterly planning and OKRs work.

If your quarterly review produces slides rather than decisions, the Operating Assessment is a good place to start. It looks at how your leadership team plans, reviews and follows through, and shows where the cadence is breaking.