Quarterly Business Review Template: Turn the Last 90 Days Into Decisions

Quarterly Business Review Template: Turn the Last 90 Days Into Decisions

A quarterly business review template should turn performance evidence into a short list of decisions for the next 90 days. The useful output is not a polished deck. It is an agreed view of results, causes, priorities, owners, measures, and actions that the team can follow after the meeting ends.

Updated September 5, 2026

Most quarterly business reviews become expensive history lessons.

Leaders sit through charts they could have read before the meeting. Teams explain why targets were missed. A few risks are discussed. Then the final ten minutes produce a vague list of priorities with no owner, no tradeoff, and no change to the operating plan.

That is not a review. It is a presentation about the past.

A useful QBR does three jobs:

• It creates one trusted account of what happened.
• It identifies the few causes that deserve management attention.
• It converts those causes into owned decisions for the next quarter.

This guide gives founders, sales leaders, operations managers, general managers, and project leaders a copyable quarterly business review template. It also shows how to prepare the meeting, choose meaningful measures, assign decisions, and automate the repetitive reporting work without automating management judgment.

What is a quarterly business review?

A quarterly business review, usually called a QBR, is a structured meeting that examines the last 90 days and agrees what the business will change during the next 90 days.

Companies use the same term for several different meetings:

• An internal business QBR reviews company or department performance.
• A sales QBR reviews pipeline, conversion, forecast accuracy, and sales execution.
• A customer QBR reviews delivered value, adoption, risks, renewal health, and expansion opportunities.
• A supplier QBR reviews service levels, quality, cost, risk, and future commitments.

The participants and measures change, but the operating logic stays the same: compare expectations with evidence, explain material gaps, decide what changes, and assign ownership.

The best QBR is therefore closer to a decision workshop than a status meeting. Status tells you what happened. A decision changes what happens next.

Use one question to test every section in your review: what should the leadership team do differently because this information is true? If a slide or paragraph cannot answer that question, move it to the pre-read or remove it.

Why do most QBR meetings waste leadership time?

Poor QBRs are usually designed around information delivery. Good ones are designed around decision quality.

The research shows how costly unclear meetings can become. Atlassian reported on May 31, 2024 that, in a survey of 5,000 knowledge workers, 77 percent frequently attended meetings that ended with a decision to schedule another meeting. It also found that 54 percent frequently left meetings without clear next steps or task ownership. Source captured September 5, 2026: https://www.atlassian.com/blog/productivity/page-led-meetings

The same research included a smaller internal experiment with 104 Atlassians. Eighty-five percent of trained, page-led meetings accomplished their goals, compared with 69 percent of control meetings. The lesson is not that every QBR needs a particular document tool. It is that a concise pre-read, a stated objective, and disciplined facilitation materially improve the odds of a useful outcome.

Asana's Anatomy of Work Global Index, published in January 2023, surveyed more than 9,615 knowledge workers across six countries. Respondents estimated that 58 percent of their day went to coordination activity rather than skilled and strategic work. Senior leaders reported losing 3.6 hours each week to unnecessary meetings, while knowledge workers reported 2.8 hours. Source captured September 5, 2026: https://investors.asana.com/news-releases/news-release-details/asana-anatomy-work-global-index-2023-smart-collaboration-and/

Microsoft's June 17, 2025 Work Trend Index special report found that the highest-volume group of Microsoft 365 users received 275 meeting, email, or chat interruptions per day across a 24-hour period. It also found that 60 percent of meetings were unscheduled or ad hoc, and PowerPoint edits rose 122 percent in the final ten minutes before meetings compared with the prior three hours. Source captured September 5, 2026: https://www.microsoft.com/en-us/worklab/work-trend-index/breaking-down-infinite-workday

Those numbers explain three common QBR failures:

• Preparation happens at the last minute, so teams report whatever is easiest to collect.
• The meeting is used to transfer information, so decision time disappears.
• Actions are recorded in notes but never enter the systems where work is managed.

The fix is a better operating design: a stable template, an early data cutoff, an exception-based pre-read, and a decision register that becomes real work immediately after the meeting.

What should a quarterly business review template include?

The template below is designed for an internal company or department QBR. Customer, sales, and supplier reviews can use the same structure with different measures.

Copy those rows into a document, spreadsheet, presentation, or work-management tool. The format matters less than the discipline.

Keep the main scorecard short. Five to nine measures force a team to distinguish business outcomes from operational noise. Supporting detail can sit behind the scorecard for anyone who wants to investigate.

Every measure should show four things:

• Target: what the team expected.
• Actual: what happened.
• Trend: whether the result is improving, flat, or deteriorating.
• Confidence: whether the data and forecast are dependable.

Do not use green, amber, and red as substitutes for numbers. A red marker should point to a specific variance, cause, owner, and requested decision.

How should you prepare a QBR before the meeting?

Start preparation two weeks before the meeting, not the night before.

Ten business days before the QBR, confirm the meeting's scope, participants, decision rights, and data cutoff. Tell every section owner what evidence is required and which questions they must answer. Reuse the same definitions from the previous quarter unless leadership intentionally changes them.

Seven business days before the meeting, collect data from the systems that own it. That may include the CRM, finance software, customer support platform, project tracker, analytics tools, and operating spreadsheets. Record the source and extraction date for every measure. If two systems disagree, surface the disagreement instead of silently choosing the better-looking number.

Five business days before the meeting, section owners explain material variances. Ask for evidence, not a confident narrative. A useful variance note has four parts:

1. What changed against target or trend?
2. What evidence supports the explanation?
3. Which part can the team control?
4. What decision or action is recommended?

Three business days before the meeting, send a concise pre-read. Participants should arrive already familiar with the results. Ask them to comment on factual errors and identify decision questions before the meeting.

One business day before the meeting, freeze the core pre-read. Correct material errors, but do not allow cosmetic editing to consume the final hours. Microsoft's finding about the 122 percent spike in last-minute PowerPoint edits is painfully recognizable because many teams optimize appearance when they should be improving decisions.

Assign these meeting roles:

• Sponsor: has authority to approve priorities and tradeoffs.
• Facilitator: protects the agenda and keeps discussion on the decision question.
• Evidence owner: explains the measure and its limitations.
• Decision owner: makes or escalates the final choice.
• Recorder: captures the decision, rationale, owner, date, and review trigger.

The facilitator and recorder should be different people. It is difficult to manage a contested discussion while producing an accurate operating record.

How should you run the QBR agenda?

A 90-minute agenda is enough for many small businesses or department reviews when the information has already been read.

Use this sequence:

1. Five minutes: state the quarter in one sentence and confirm the decisions required.
2. Ten minutes: review last quarter's commitments and unresolved actions.
3. Fifteen minutes: scan the scorecard, discussing only material exceptions.
4. Twenty minutes: examine the two or three most important causes and risks.
5. Twenty-five minutes: make the proposed decisions and state the tradeoffs.
6. Ten minutes: confirm next-quarter outcomes, owners, and measures.
7. Five minutes: read back decisions, actions, dates, and escalation points.

Do not give every department equal airtime. Equal airtime feels fair but wastes attention. Give time to the issues with the largest effect on revenue, customers, cost, delivery, risk, or capacity.

When a discussion drifts, ask one of four questions:

• Is this a fact to correct in the pre-read?
• Is this a cause we need to test?
• Is this a decision we can make now?
• Is this an action that belongs outside the meeting?

Park detailed investigations with an owner and deadline. Do not let uncertainty become an excuse for no decision, but do not pretend a weak assumption is a fact. A conditional decision can be responsible: proceed if the next two weeks of data meet a defined threshold; otherwise return to the alternative.

End by reading the decisions aloud. Agreement often disappears when a general discussion is translated into an explicit commitment. That discomfort is useful. Resolve it in the room.

Which QBR metrics should you choose?

Choose measures that describe outcomes, drivers, and operating health.

For a company-level QBR, the scorecard might include revenue against plan, gross margin, cash collected, cash runway, qualified pipeline coverage, customer retention, cycle time, delivery quality, and capacity in the most constrained team.

For a sales QBR, use qualified pipeline created, stage conversion, sales-cycle length, average deal value, forecast accuracy, follow-up completion, and lost-deal reasons. Avoid celebrating activity measures such as emails sent when they are disconnected from qualified opportunities or revenue.

For an operations QBR, use cycle time, backlog age, first-time-right rate, exception volume, service-level performance, cost per completed unit, and hours consumed by recurring manual work.

For a customer QBR, use agreed business outcomes, adoption of valuable capabilities, support trends, unresolved risks, renewal health, and the customer's next-quarter objectives. Do not turn the meeting into a product-usage lecture.

Separate lagging measures from leading indicators. Revenue and churn confirm what already happened. Pipeline quality, onboarding completion, backlog age, and customer-risk signals can help the team act before the financial result is final.

Reject vanity measures with a simple test: if this number improves, can we explain what business outcome should improve next? If not, it may be interesting but it does not belong on the main scorecard.

How can you turn QBR observations into real decisions?

Every important observation needs one of four outcomes:

• Continue: the current approach is working and remains funded.
• Correct: the outcome matters, but execution or ownership must change.
• Change: the team will take a different approach.
• Stop: the work no longer justifies time, money, or attention.

Write each proposed decision before the meeting using this structure:

Decision: State the choice in one sentence.

Evidence: List the few facts that materially affect the choice.

Options: Show the credible alternatives, including doing nothing.

Tradeoff: State what the business gains and what it gives up.

Owner: Name the person accountable for execution.

Measure: Define how leadership will know the decision worked.

Review trigger: Set a date or condition that reopens the decision.

For example, weak language says, “Improve lead follow-up next quarter.” Strong language says, “Sales operations will require every qualified inbound lead to receive an owned next action within one business day starting September 15; the sales lead will review weekly completion and meeting conversion for six weeks; if completion remains below 90 percent, the team will redesign assignment and escalation rules.”

The second version can enter an operating system. The first can only enter meeting notes.

Limit the quarter to three to five major outcomes. A list of twelve priorities is an admission that leadership did not prioritize. Record what will be delayed or stopped so the team can see the cost of the decision.

What does a decision-first QBR look like in practice?

Imagine a 25-person business services company that missed its quarterly revenue target by 12 percent.

The weak QBR spends forty minutes reviewing monthly sales charts. Marketing reports lead volume. Sales reports calls made. Operations explains that delivery capacity is tight. Leadership asks everyone to push harder next quarter.

The decision-first QBR starts with the variance. Revenue missed by 12 percent. Existing-customer revenue was on plan, but new-customer revenue missed by 24 percent. The team then traces the driver: qualified opportunities were adequate, but too many proposals stalled after the first meeting.

Evidence from the CRM and a sample of lost opportunities shows three recurring problems:

• Proposal follow-up had no consistent owner.
• Commercial questions waited several days for answers.
• The sales forecast treated inactive proposals as likely revenue.

The meeting makes three decisions:

1. Every proposal receives a named commercial owner and next action before it is sent.
2. Pricing exceptions use one approval path with a four-business-hour target.
3. Forecasted proposals without a customer-confirmed next step move to a lower-confidence category.

Each decision has an owner, start date, measure, and six-week review point. Sales operations updates the CRM rules. Finance owns the pricing approval queue. The sales leader reviews proposal movement and forecast accuracy weekly.

That QBR did not create more motivation. It changed the system producing the result.

Which parts of a QBR should you automate?

Automate collection, checking, comparison, and follow-through before you automate interpretation.

Useful automation can:

• Pull agreed measures from the CRM, finance, support, and project systems on a fixed date.
• Apply consistent definitions and flag missing or stale records.
• Compare actuals with targets and the prior quarter.
• Identify material variances that need explanation.
• Prepare a first draft of the scorecard and pre-read.
• Gather unresolved actions from the previous decision log.
• Create approved actions in the team's work-management system.
• Send owners reminders before due dates.
• Produce a monthly view of progress against QBR commitments.

Keep human judgment around causes, tradeoffs, priorities, sensitive customer conclusions, personnel decisions, and financial commitments.

AI can summarize evidence or draft variance explanations, but the owner should verify every material statement. An elegant summary of unreliable data is still unreliable. If the CRM stages are inconsistent or finance definitions change each month, repair that foundation first.

Start with the repetitive path that consumes the most preparation time. Map where each number comes from, who trusts it, how often it changes, and which exceptions require review. Then automate one complete reporting loop. A dozen disconnected shortcuts create more maintenance than one dependable workflow.

Wavicle helps non-technical business leaders design and build reporting workflows around the systems they already use. That can include defining the scorecard, connecting source data, creating validation and approval steps, generating the pre-read, recording decisions, and pushing actions into the team's daily tools. The work starts with the operating outcome, not with a software purchase.

How can you tell whether the QBR improved the business?

Measure the review process as well as the business outcomes.

After each QBR, track:

• Percentage of pre-read sections completed by the cutoff.
• Percentage of scorecard measures with a trusted source and named owner.
• Number of decisions requested and number completed in the meeting.
• Percentage of decisions with an owner, measure, due date, and review trigger.
• Percentage of actions completed by the first monthly review.
• Number of decisions reopened without new evidence.
• Hours spent preparing the review.
• Participant rating of whether the meeting produced clear priorities.

The goal is not to maximize the number of decisions. It is to make the necessary decisions with sufficient evidence and then carry them into execution.

Review the process after two quarters. Remove sections nobody uses. Tighten measures that invite argument because their definitions are vague. Shorten presentations that repeat the pre-read. Add early warning indicators where risks arrived too late.

A stable QBR template should become easier to run each quarter because the data definitions, ownership, and workflow improve. If preparation remains a recurring emergency, the problem is not the template's design. It is the operating system behind it.

What are the most frequently asked questions about quarterly business reviews?

How long should a quarterly business review last?

For many small companies or departments, 60 to 90 minutes is enough when participants receive a concise pre-read three business days in advance. Complex company-wide reviews may need longer or separate sessions. The test is whether the agenda protects enough time for decisions rather than presentations.

Who should attend a QBR?

Invite people who own the measures, can explain material variances, have authority to make the required decisions, or will own the resulting actions. Do not invite people merely because they contributed data. They can review the pre-read or join for a specific decision.

What is the difference between a QBR and a quarterly planning meeting?

A QBR evaluates performance, assumptions, and prior commitments before making changes. A quarterly planning meeting translates those decisions into goals, resources, and work. Small businesses can combine them, but the review should come first so the next plan reflects evidence.

Should a QBR use slides, a document, or a spreadsheet?

Use the format your team can prepare consistently, read before the meeting, and connect to follow-through. A document is often better for context and decisions. A spreadsheet is useful for the scorecard. Slides help presentation but can encourage excessive polish. One linked system can combine all three.

How many KPIs should be in a QBR?

Keep the main scorecard to roughly five to nine outcome and driver measures. Put diagnostic detail in supporting pages. If every available metric appears in the main review, leadership will spend the meeting navigating data instead of deciding what matters.

How is a customer QBR different from an internal QBR?

A customer QBR focuses on the customer's agreed outcomes, value received, adoption, risks, future objectives, and mutual commitments. An internal QBR focuses on company or department performance and resource decisions. Both need evidence, explicit decisions, owners, and follow-through.

Can AI write the quarterly business review?

AI can prepare a draft from trusted source data, summarize trends, and flag exceptions. A business owner should verify the evidence and decide causes, tradeoffs, priorities, and commitments. Use AI to reduce reporting labor, not to avoid accountable judgment.

What should happen immediately after the QBR?

Publish the decision record within one business day. Create actions in the system where the team manages work. Confirm owners and due dates. Schedule the first monthly checkpoint. Update targets, forecasts, capacity plans, and process rules affected by the decisions.

How can Wavicle help you build a QBR reporting workflow?

A template fixes the meeting structure. It does not fix scattered data, inconsistent definitions, last-minute reporting, or actions that disappear after the meeting.

Wavicle can help map the full quarterly reporting workflow, define trusted measures, connect business systems, add review controls, prepare decision-ready outputs, and route approved actions to the people responsible for execution. The result should be less reporting work and faster movement from evidence to action.

Book a free growth consultation at https://wavicle.tech/contact to review your QBR process and identify the first reporting step worth automating.