How to Write a Quarterly Business Review Summary

The quarterly business review summary is the document people read instead of attending the meeting, or skim before it. Its job is to say honestly what happened against what you planned, what you learned, and what you need next. Most QBR summaries fail at the first part, because it is uncomfortable to lead with a target you missed, so they open with activity and bury the number.

A summary that hides the miss is not read as confident. It is read as evasive the moment someone finds the number themselves. Here is how to write one that earns trust.

Lead With Results Against Targets

The first thing a QBR summary should contain is the plain comparison: what you set out to do this quarter and what actually happened. If you use a goal-setting framework, this is the score against your objectives; the OKR method is one common way to make that comparison explicit rather than narrative.

Put the results at the top, hits and misses together, before any explanation. A reader who has to hunt for the outcome assumes it is bad, often worse than it is. A reader who gets it straight away trusts the rest of the document. We covered the same principle for executive updates in how to write a status update executives read.

Explain the Miss Without Excusing It

Once the numbers are stated, explain them, briefly and without defensiveness. A miss with a clear cause and a plan reads as competence. A miss wrapped in blame or vague “market conditions” reads as an excuse.

The test is whether your explanation tells the reader something they can act on. “We missed the target because the launch slipped three weeks, which we could have flagged earlier” is useful. “We faced unexpected headwinds” is not. The retrospective habit of naming causes honestly applies here directly; we covered it in how to write a project retrospective.

Separate What Worked From What You Will Change

A good QBR summary is not just a scorecard. It says what worked well enough to keep doing and what you will change next quarter. Keep these separate and specific. “Continue X, stop Y, start Z” is more useful than a paragraph of reflection, because it tells the reader what the next quarter will actually look like.

End With the Ask

Most QBR summaries exist partly to request something: budget, a decision, a hire, a change in priority. State it plainly at the end, tied to the results above. A clear ask, grounded in the quarter’s evidence, is what turns a review into a decision. We covered writing that section in how to write a proposal executive summary.

Before and After

The difference is whether the summary leads with the truth or the spin.

Before:

A productive quarter with strong momentum across the team. We shipped several key initiatives and built a solid foundation for growth, despite some challenges in the market.

After:

We hit 78 percent of our revenue target this quarter (2.1M against 2.7M). The shortfall came from the enterprise launch slipping to next quarter. Mid-market sales beat target by 12 percent and we will double down there. We are asking to move one engineer to the enterprise launch to protect the Q4 date.

The second version tells a decision maker everything in four sentences; the first tells them nothing and signals that the number is bad.

A Wrivio Context for a QBR summary could say:

Rewrite this as a direct quarterly review summary. Keep every figure, percentage, and target exactly as written. Lead with results against targets, state the cause of any miss plainly, and keep the ask specific. Do not soften a missed number into vague positive language.

Press Ctrl+Shift+Space, paste your draft, and check the diff. A rewrite that keeps “78 percent of target” at the front is doing its job; one that promotes it to “strong momentum” and hides the number has made the summary less trustworthy.

Common Questions

What should a QBR summary lead with?

The plain comparison of what you planned against what happened, hits and misses together, before any explanation. Readers who have to hunt for the outcome assume it is worse than it is.

How do I present a missed target?

State the number first, then explain the cause briefly and without defensiveness, and give the plan to address it. A miss with a clear cause and plan reads as competence, not failure.

What should the summary include besides results?

What worked and will continue, what you will change next quarter, and a specific ask, such as budget or a decision, grounded in the quarter’s results.

How long should a QBR summary be?

Short enough to be read before the meeting. Lead with the results and keep explanations brief; the detail belongs in supporting material, not the summary.

Why not open with the positives?

Because opening with activity while burying the number reads as evasive once the reader finds the number themselves. Leading with the honest result earns trust for everything that follows.

Download Wrivio for Windows to turn a defensive first draft into a QBR summary that states the number and keeps your credibility.