Key takeaway
A quarterly business review produces slides, a discussion, and a list of things people agreed to do. The slides are forgotten within a week. The action log is what the customer experiences between reviews, so it deserves the preparation time that usually goes into the deck.
The action log is the deliverable
A quarterly business review produces slides, a discussion, and a list of things people agreed to do. The slides are forgotten within a week. The action log is what the customer experiences between reviews, so it deserves the preparation time that usually goes into the deck.
Treat the log as a small contract. Each line states what will change, who owns it on each side, when it is due, and how both parties will know it happened. Without those four fields, an action is a sentiment with a deadline attached.
Write actions as observable outcomes
Improve reporting adoption is not an action. It is an aspiration. A testable version names the report, the audience, the current count, the target state, and the date: finance analysts open the weekly margin report at least twice in the four weeks after enablement, confirmed by the product analytics export.
Not every QBR action can be measured that cleanly, and that is fine. When the outcome is qualitative, name the artifact that will demonstrate it. A documented workflow, an approved configuration, or a recorded training session is evidence. A promise to keep an eye on it is not.
Split ownership across the two sides
Every action needs a customer owner and an internal owner, even when only one side does the work. The customer owner confirms the outcome matters and accepts the result. The internal owner delivers or coordinates. One name per side prevents the quiet assumption that the CSM will chase the customer into compliance.
Where authority sits elsewhere, record the authority rather than the proxy. If the customer's security review must approve a configuration, the owner is the security lead, not the well meaning administrator who attends the QBR. Naming the real owner early saves a month of reminders.
Carry prior actions into the next review
The first agenda item of every QBR should be the previous action log, not the new value story. For each open action, the review states the current state, the evidence, the reason for any delay, and the revised date. Actions that quietly disappear between quarters teach the customer that the log is decorative.
Close actions with evidence, not status changes. Completed means the artifact exists and the customer owner has seen it. If an action was completed internally but never delivered, it is still open. If it was delivered and the customer chose not to adopt it, the action is closed as declined, with that decision recorded.
Handle the blocked and the obsolete
Some actions stop because a dependency failed, a priority changed, or the original problem no longer exists. Each case needs its own disposition: blocked with a named dependency, deferred with a decision date, or retired with a reason. Retiring an action is legitimate when both owners agree and the rationale is written down.
Obsolete actions are the most common source of QBR cynicism. A line that has rolled forward for three quarters without movement tells the customer that nobody is paying attention. The review should force a decision on any action older than two cycles: recommit, renegotiate, or retire.
Set a closure standard per action type
Different action types need different proof. A configuration change closes with a settings export and a customer confirmation. A training action closes with attendance and an assessment or a recorded walkthrough. A process action closes with the updated document and the date it took effect.
Publish the closure standard in the log template. When the standard is visible at creation, nobody argues about it at closure. The CSM checks the evidence, the customer owner confirms, and the line moves to closed with the artifact linked rather than described. The log also records actions the customer declined, because a decision not to act deserves the same visibility as a completed task.
Run a two week mid cycle check
Quarterly cadence is too slow for action management. Two weeks after the review, the CSM reviews every open line and contacts owners only where the date is at risk. The check takes twenty minutes per account and prevents the end of quarter scramble where half the log is marked complete without evidence.
Use the check to update the customer in one short message: what moved, what is at risk, and what decision is needed. A brief, regular update is more credible than a polished summary written the night before the next QBR.
Design the log for the customer
The customer should receive the action log as a standalone document, not a screenshot inside a deck. Use the same columns every quarter, sort by due date, and include a status line a sponsor can read without translation. Internal shorthand and ticket identifiers belong in a separate column.
Where an action depends on a technical detail, add a one sentence explanation in customer language. The sponsor who approves the next phase does not need the ticket number, but they do need to know whether the change alters their team's daily work. The log is a communication artifact as much as a tracking tool.
Report closure honestly in the review
The QBR should show four numbers: actions created, actions closed with evidence, actions open within date, and actions overdue. Resist the temptation to report a single completion percentage, because it hides the difference between an action delivered and an action merely marked done.
When closure is low, say why. A quarter with three overdue actions caused by a customer reorganisation is a different story from a quarter with three overdue actions caused by unclear ownership. The first needs patience, the second needs a process change, and the log should make the difference visible.
Common questions
What fields does a QBR action need?
Observable outcome, customer owner, internal owner, due date with timezone, evidence standard, current state, dependency, and disposition history.
Who closes an action?
The internal owner supplies evidence and the customer owner confirms the outcome. The CSM records closure but does not self certify delivery.
What happens to actions that keep rolling forward?
Any action older than two review cycles requires an explicit decision to recommit, renegotiate the date, or retire it with a written reason.
How should completion be reported?
Report created, closed with evidence, open within date, and overdue separately. A single percentage obscures the difference between delivery and status updates.
Sources and context
Sources provide public context. Their inclusion does not imply endorsement of this site or a guaranteed business result.
Apply this to your customer journey
Define a support role with visible boundaries.
Bring one recurring workflow. We will help map the approved inputs, review owner, evidence, and escalation points.
Book a free consultation