QBR stands for quarterly business review: a recurring meeting, held once per quarter, where a team or company scores the quarter against its goals, examines what missed and why, and decides what to continue, stop, or re-resource in the next one. Done well, it is the moment strategy and reality get reconciled. Done the usual way, it is ninety minutes of status slides.
This post covers the internal QBR in detail: the agenda, the attendees, the deck, and the relationship to the monthly review. It closes with the part most guides skip, which is why the QBR so often discovers problems a quarter after they started.
What does QBR stand for?
The abbreviation carries two related meanings, and search results mix them freely.
The internal QBR is the one this post is about: leadership and goal owners reviewing the company's or a team's own quarter. It goes by other names in specific frameworks, the quarterly in EOS, the quarterly planning session in OKR shops, but the mechanics are the same. The glossary entry has the compact definition.
The customer QBR belongs to sales and customer success: a vendor sits down with a customer each quarter to review value delivered, adoption, and the roadmap. It borrows the name and the cadence, but it is an account management ritual, and its agenda is about the relationship rather than the operating plan. If that is what you came for, the structure below still transfers surprisingly well: scores first, then decisions.
What a QBR is actually for
A quarter is long enough for a strategy to go wrong and short enough to correct it. The QBR exists to force that correction on a schedule: it is the one meeting whose explicit job is to compare the plan against what happened and to change something as a result.
That last clause is the test. A review that ends without a single decision, no goal retired, no initiative re-resourced, no target revised, was a presentation. The scores were known before the meeting; reading them aloud added nothing. The value of the ritual is concentrated entirely in what changes because of it.
The QBR agenda that produces decisions
The agenda that works spends its time in inverse proportion to how comfortable each part feels. A workable ninety-minute shape:
Scores, ten minutes. Every goal enters the room already scored, circulated in a pre-read. The meeting confirms the numbers; it does not discover them. If scoring happens live, the QBR becomes a data-entry session with an audience.
Misses and causes, forty minutes. The bulk of the meeting goes to the two or three goals that missed, and the question is always why, not who. The useful causes are specific: the dependency that slipped in week three, the team that was quietly pulled onto something else, the assumption that turned out wrong. Vague causes ("execution challenges") get sent back for a real one.
Decisions, thirty minutes. Each miss leads somewhere: continue with changes, stop, or double down. Each decision gets an owner and a date. This is also where next quarter's trade-offs are argued, because adding a priority without removing one is how the next QBR inherits this one's problems.
Commitments, ten minutes. The decisions read back, owners named, done.
The QBR template in our library carries this agenda plus the matching deck structure, as a free download. For how the shape changes with scale, there is a separate walkthrough of a QBR agenda for a 100-person company.
Who attends, and for how long
The goal owners and the one leader who can actually decide to continue, stop, or re-resource. That is the whole list. Every added observer who cannot decide tilts the room back toward presentation, because people perform for audiences and argue with peers.
Ninety minutes is enough for a single team when the pre-read did its job. A company-level QBR across several departments runs longer, but the discipline holds: if the meeting needs three hours, the usual culprit is scoring happening live, or status being read aloud to people who could have read it themselves.
QBR vs MBR
The monthly business review is the QBR's early-warning partner, and the two answer different questions. The MBR checks trajectory: is each number trending at the pace needed to hit the quarterly target, and what small correction does this month need? The QBR scores the completed quarter and re-plans. A useful way to hold the relationship: the MBR exists so the QBR is never the first time a problem is noticed. Both have templates in the library, the MBR template alongside the QBR one.
The QBR deck
The deck is the agenda in slide form, and it stays honest by the same rule: one slide per agenda block, nothing that merely reports. Scores on one slide, already known from the pre-read. One slide per significant miss, stating the cause. One slide per proposed decision, with options. One slide of next quarter's commitments with owners. A deck that runs past fifteen slides is usually carrying status that belonged in the pre-read.
Why QBRs find problems too late
Here is the structural problem with the whole ritual, and it does not go away with a better agenda.
A QBR runs on summaries. Each goal arrives as a color, a percentage, and a sentence of commentary, typed by the person who owns it, under mild social pressure to round up. Between the actual work, hundreds of tasks, reassignments, and conversations across a quarter, and the slide, almost everything is compressed away. The signal that would have predicted the miss usually existed in week four: the project that went quiet, the thread where an engineer flagged the approach, the team whose capacity drifted to something urgent. None of it survives the compression, so the review discovers in week thirteen what the work knew in week four. We wrote up the mechanics of that loss in the QBR built on traceable work.
The fix is not more meetings. A monthly review narrows the window from thirteen weeks to four, but it runs on the same compressed summaries, so it inherits the same blindness at smaller scale.
Making the QBR a formality
The alternative is to let the review read the work instead of the summaries. When goals and KPIs are connected to the projects and tasks beneath them, pace against plan is observable continuously, and the moment a goal stops being backed by active work is visible the week it happens rather than the quarter after. That gap between a goal and the effort actually pointed at it is execution risk, and it is detectable long before a review would surface it.
That is what Vindaris is built for: the Work Graph connects strategy, goals, and KPIs to the work in the tools teams already use, flags the Key Result that cannot be reached at its current pace, and keeps the context, down to the task threads, attached. The QBR still happens. It just stops producing surprises, because the misses were flagged, discussed, and acted on while there was still quarter left to save. The scores arrive at the meeting as confirmation, and the ninety minutes go where they always should have gone: to decisions.