Quarterly Business Review Template (Free QBR Template + Agenda)

Most QBR templates are a blank slide deck with six headings and a lot of hope. Everyone fills in their section the night before, the meeting runs 40 minutes over, and nobody can say afterwards what was actually decided.

That's the gap. The template isn't the problem. The problem is that it was built to present a quarter, not to decide the next one.

This quarterly business review template is built the other way around. It starts with the decisions you need to make, then works backwards to the data, the agenda and the follow-up. You can copy it straight into a doc, a deck or Tability. If you want the background first, our guide on what a QBR is and how to run one covers the basics.

What a good quarterly business review template needs

A QBR template has one job: make sure the right conversation happens in the room. In practice, that means four things.

• One page of results. If you can't see how the quarter went in a minute, the template is too heavy.
• Space for the why. Numbers without explanation are just a scoreboard. Every miss and every win needs a one-line cause.
• A decisions section. This is the bit most templates skip. It's also the only part anyone remembers.
• Owners and dates. Anything that leaves the room without a name against it won't happen.

Think of it like a flight briefing. The pilot doesn't read out every instrument. They cover what's changed, what's risky and what happens next.

The QBR template, section by section

Here's the structure we recommend. Each section includes what to put in it and how long to spend on it for a 2 hour review.

1. Quarter at a glance (10 minutes)

One page. List your top five results against target, with a red, yellow or green status for each. If you run OKRs, this is your key results. If you don't, use the five KPIs you'd be embarrassed to miss.

Template prompts:

• What were our top five commitments last quarter?
• Where did we land against each one (target, actual, status)?
• What is the single biggest surprise, good or bad?

2. What drove the results (30 minutes)

This is the real review. For each of the five results, write one or two sentences on the cause. Be specific. 'Pipeline was light' is a symptom. 'We lost two reps in week three and didn't backfill' is a cause.

It helps to separate leading and lagging indicators here. Revenue tells you what happened. Pipeline coverage and win rate tell you why.

3. Wins, misses and lessons (20 minutes)

Keep this short and honest. Three wins, three misses, and one lesson for each. Resist the urge to hide a miss behind a long explanation. Leadership teams can smell it, and it wastes the time you need for the next section.

4. Risks and blockers (15 minutes)

What could derail next quarter? Name the risk, the owner, and what you need from the room to fix it. This is where cross-team dependencies show up, so invite the people who own them.

5. Next quarter's priorities (30 minutes)

Maximum three to five priorities. Each one needs an owner, a measurable outcome and a first milestone. This is where you set the next quarter's goals, and it's the best place to apply the simple OKR writing approach if you're new to it.

6. Decisions and asks (15 minutes)

Write the decisions down as they're made. Headcount, budget, scope, trade-offs. If a decision gets deferred, record who will decide and by when.

A copy-and-paste QBR template

Here's the template in a format you can paste into any doc.

• Quarter: Q_ 20__ | Team: ____ | Presenter: ____
• Results vs target: Result 1 to 5, each with target, actual and status (red, yellow, green)
• Why it happened: one or two sentences of cause per result
• Top 3 wins: what worked and whether we should repeat it
• Top 3 misses: what happened and what we learned
• Risks and blockers: risk, owner, what we need from the room
• Next quarter priorities: priority, owner, success measure, first milestone
• Decisions made: decision, owner, date
• Action items: action, owner, due date

Download our free QBR template

Prefer something ready-made? Our customisable QBR template offers a structured framework to evaluate your financial metrics, operational efficiency, sales and marketing efforts, customer success initiatives, and strategic projects. It has clear sections for data input, analysis, goal setting, risk assessment, and action planning. Whether you're presenting to executives, investors, or department heads, it keeps the review clear, coherent and focused on decisions. 

DOWNLOAD QBR TEMPLATE

Rather not copy numbers into a doc every quarter? Tability reporting keeps your results up to date as the quarter runs, so there's nothing to rebuild before the review.

Build your QBR with an LLM

If you'd rather be interviewed than fill in a blank doc, you can have an LLM do it. Paste the prompt below into ChatGPT, Claude, Gemini or any other chat. It asks a few short questions, then gives you a filled-in QBR and an agenda sized to your meeting.

It also asks whether you use Tability. If your LLM is connected to Tability through the Tability MCP server, it can pull this quarter's goals, check-ins and blocked initiatives, then check with you before it uses any of them. It only reads data. It never changes anything in your workspace.

You are an assistant helping the user prepare a quarterly business review (QBR). A QBR is a structured look back at the quarter and a plan for the next one. Your job is to interview them, fill in the template below, and give them something they can send to attendees at least two days before the meeting.

Ask questions in small batches (two to four at a time), never one giant form. Use multiple choice where you can. If the user doesn't know something, mark it "TBC" and move on. Don't invent numbers, owners or dates. Anything you can't source from the user or from Tability stays as a visible placeholder.

Write in plain, direct language. No jargon, no filler, no em dashes.

### Step 1: Set up (batch 1)

1. Which quarter is this review for (for example Q4 2026)?
2. Whose review is it: a team, a department, or the whole company?
3. Who is presenting, and who will be in the room (rough roles are fine)?
4. How long is the meeting: 60 minutes, 90 minutes, or 2 hours?

### Step 2: Tability connection (batch 2)

Ask this explicitly:

"Are you connected to Tability, or would you like to pull your goals and progress from there? If yes, I can bring in this quarter's data and check with you before using any of it."

- If the user says no, or you have no Tability tools available, skip to Step 3. Mention once that they can connect Tability's MCP server later to automate this (https://www.tability.io/ai/mcp-server).
- If yes and Tability tools are available, do the pull below. If yes but you have no Tability tools, say so plainly and continue manually.

**Pulling from Tability (read-only, never write anything back):**

1. Look up the user's workspace and search plans for the current quarter. If more than one plan matches, list them and ask which to use.
2. For the chosen plan, read the objectives and key results (outcomes), including targets, current values and status.
3. Read the latest check-ins for each key result, and search initiatives for anything blocked, at risk, or completed this quarter.
4. Present what you found as a short summary, one line per key result: name, target, current value, status, most recent check-in note.
5. Then ask, for each group, whether to include it:
   - "Include these key results as the Results vs target section? (all / pick some / none)"
   - "Use the check-in notes as a starting point for 'why it happened'?"
   - "Include blocked or at-risk initiatives in Risks and blockers?"
   - "Include completed initiatives as candidate wins?"
6. Cap results at five key results. If there are more, ask which five matter most for this audience.
7. Never include anything the user declined. Never expose data from plans they didn't pick.

### Step 3: Fill the gaps (batch 3 onwards)

Cover only what Tability data (if any) didn't already answer. Skip anything already known.

**Results vs target** (max 5): For each result, what was the target and the actual? Is it green, yellow or red? If they have more than five metrics, help them pick the five the audience cares about.

**Why it happened**: One or two sentences of cause per result. Offer a draft based on what you know and ask them to correct it.

**Wins and misses**: What are the top three wins, and should they be repeated? What are the top three misses, and what was learned?

**Risks and blockers**: What could derail next quarter? For each: owner, and what's needed from the room.

**Next quarter priorities**: Up to three priorities. For each: owner, success measure, first milestone. Ask whether each ties back to company or team strategy, and if not, flag it.

**Decisions and asks**: What decisions do you need from attendees in the meeting? Who owns each, and by when?

If the user's answers are thin, push back gently once. For example: "That miss reads as an outcome, not a lesson. What would you do differently?"

### Step 4: Produce the QBR

Output two things in this order. Use clean markdown tables where shown, so it pastes into Google Docs, Notion or Word.

**1. The filled-in template**

```
QBR: Q_ 20__ | Team: ____ | Presenter: ____

1. Quarter at a glance
   Results vs target (max 5): | Result | Target | Actual | Status (R/Y/G) |

2. What drove the results
   One or two sentences of cause per result.

3. Wins, misses and lessons
   Top 3 wins: what worked, repeat it? (yes/no)
   Top 3 misses: what happened, what we learned

4. Risks and blockers
   | Risk | Owner | What we need from the room |

5. Next quarter priorities
   | Priority | Owner | Success measure | First milestone |

6. Decisions and asks
   | Decision / ask | Owner | Date |

Action items
   | Action | Owner | Due date |
```

**2. The meeting agenda**, scaled to the meeting length they chose. The full two-hour version is:

| Section | Minutes |
|---|---|
| Quarter at a glance | 10 |
| What drove the results | 30 |
| Wins, misses and lessons | 20 |
| Risks and blockers | 15 |
| Next quarter's priorities | 30 |
| Decisions and asks | 15 |

For 60 or 90 minutes, shrink "what drove the results" and "next quarter's priorities" first, and keep decisions and asks intact.

### Step 5: Quality check and wrap up

Before finishing, check and tell the user about any of these:

- More than five metrics (too many, nothing gets discussed).
- Any "TBC" or placeholder left in the doc.
- A priority with no owner or success measure.
- A priority with no link to strategy.
- Results shown without a cause.

Close with a short note: send this at least two days before the meeting and ask people to read it first, because a QBR shouldn't start with someone reading slides aloud. Then offer to turn it into a short pre-read email.

If they weren't connected to Tability, finish with one soft line: "If you'd rather not rebuild this every quarter, Tability keeps your results live and can draft the retrospective for you: https://www.tability.io/features/reporting"

## Guardrails

- Only read from Tability. Do not create or edit check-ins, initiatives or plans.
- Don't ask for or store credentials, personal data about individuals beyond names and roles, or anything sensitive.
- Don't fabricate metrics, quotes or causes. Draft suggestions must be labelled as drafts for the user to confirm.

New to Tability? Start free and see how reporting keeps your QBR data current all quarter.

A sample QBR agenda you can reuse

If you only need the agenda, here's the same structure as a timetable. It's built for a two hour QBR meeting, but you can scale it down for a team-level review.

1. Quarter at a glance (10 minutes)
2. What drove the results (30 minutes)
3. Wins, misses and lessons (20 minutes)
4. Risks and blockers (15 minutes)
5. Next quarter's priorities (30 minutes)
6. Decisions and asks (15 minutes)

Send the filled-in template at least two days before the meeting and ask people to read it first. A QBR shouldn't start with someone reading slides aloud.

Common QBR template mistakes

To be frank, most QBRs go wrong before the meeting starts. Here are the ones we see most.

• Too many metrics. Twenty KPIs on a slide means none of them get discussed. Pick five.
• Building it the night before. If you're assembling numbers at 10pm, you're doing the work the system should do. Keep a running status report through the quarter instead.
• No link to strategy. A QBR that only looks backwards is a book club. Tie every priority back to the plan, as covered in our piece on why good strategies fail in execution.
• No follow-up. Decisions made in the room fade fast. Check them weekly, not next quarter.

Make the QBR template easier to fill in with Tability

The painful part of any QBR is gathering the data. You chase updates, copy numbers from three tools, and then argue about whose version is right.

This is where Tability comes in. Your goals, check-ins and statuses live in one place all quarter, so the 'quarter at a glance' section is already written when you need it. There are two ways it helps you write the QBR: it puts all your data in one view, and it can write the report for you.

1. Use a custom dashboard to see all your data at a glance

Build a custom dashboard from your live OKR data, so everything you need for the review is already in one place. Filter it by team, owner or confidence, and the widgets stay up to date as check-ins come in. When all the numbers are sitting in front of you, writing the report is mostly a matter of reading the dashboard and adding the why.

You can also set permissions at the workspace, team or person level, so leadership sees the whole picture while each team keeps its own view.

2. Let AI Mode write the report for you

Take it a step further with Tability AI Mode. Instead of building the report yourself, you ask Tability for one in plain language, something like 'build me a QBR for the marketing team this quarter', and it pulls the data you're looking for. You can ask for it in whatever format you need, whether that's a PowerPoint, a doc or a CSV.

You can also set it up as a scheduled task, so the report lands in your inbox automatically when the time comes. No more chasing updates the week before the QBR.

Around both, Tability reporting gives you AI-drafted retrospectives and a presentation mode, with export to PowerPoint or Google Slides. The strategy map shows how every team's goals roll up to company priorities, which is the link to strategy most QBRs are missing.

You can also cut the reporting time by letting AI summarise progress, and a weekly business review keeps problems from being a surprise in the QBR room.

The result: the QBR becomes a decision meeting instead of a discovery meeting.

FAQ

How long should a QBR be?

Two hours for a company or department level review, 60 to 90 minutes for a single team. If it's running longer, you have too many metrics or too many presenters.

Who should attend a QBR?

The leaders who own the results, plus anyone who owns a dependency or a decision you need. Keep the room small. Share the notes with everyone else.

What's the difference between a QBR and an OKR review?

An OKR review checks progress on your goals. A QBR is wider: it covers results, risks, resourcing and the plan for next quarter. If you run OKRs, the OKR review feeds straight into the QBR.