Where outcome evidence is missing, leave it unknown. The meeting can still help the client decide what to investigate and what to prioritize next quarter without turning delivery activity into an invented business result.
Prepare a promise-to-evidence comparison
Choose the quarter's agreed deliverables from the approved scope. Pair each one with its completion evidence and the client goal it was meant to support. Include the period covered by any measurement so a reader can tell whether it belongs to this quarter.
For this customer review, start the questions with the client's goals. If you also prepare an internal version, ask about the delivery constraints and information needed to scope the work. Keep the same evidence in both; a change of audience does not turn an unknown outcome into a result.
A fictional maintenance client's review packet
Illustrative example: the client, scope, work records, quarter, and priorities below are fictional. No real customer result, satisfaction quote, or contract renewal is claimed. The period is July 1-September 30. The client's stated goal is to help staff find current maintenance instructions.
| Promised work | Delivered work and sample evidence | Client outcome |
|---|---|---|
| Review instruction pages monthly | Three review records dated within the sample quarter | Whether staff found instructions more easily: unknown |
| Correct outdated contact references | Change record showing the listed references were updated | Whether staff contacted the right team more often: unknown |
| Prepare an instruction index | Index document supplied in the sample packet | Actual staff use of the index: not supplied |
Three review records support a statement about recorded reviews. They do not prove every page was accurate throughout the quarter. An index being delivered does not establish that staff used it. Keep those distinctions visible when you discuss the work.
A proposed 60-minute customer QBR agenda
- Confirm the client's current goal, 8 minutes. Ask whether finding maintenance instructions is still the priority or whether needs have changed.
- Review promised and delivered work, 15 minutes. Inspect the comparison and source records. Identify missing deliverables or unclear completion evidence.
- Discuss outcomes and feedback, 15 minutes. Ask how staff are using the material. Record actual feedback and any evidence the client can provide; leave unanswered questions open.
- Choose next-quarter priorities, 15 minutes. Compare proposals against the updated goal, available scope, and evidence gaps.
- Confirm follow-up, 7 minutes. Read back decisions, proposed work needing approval, owners, and check dates.
The timing is an example allocation. Keep urgent service-resolution details in the appropriate support workflow so they do not consume all the time intended for the quarter's priorities.
Propose two scoped next steps
For this sample, the next-quarter choices are deliberately limited:
- Investigate index use. Ask the client to arrange a short staff walkthrough using the existing index. Proposed output: observations of the paths staff take and the points where they cannot find a needed instruction. Participation, method, owner, and date need confirmation.
- Resolve ownership for outdated pages. Identify the pages whose owners are missing, ask the client to confirm owners, and propose a review sequence. This does not promise a new maintenance scope until it is approved.
Ask which proposal best answers the client's current problem. If the goal has changed, revise the proposals before calling them next-quarter commitments. An action such as “account lead drafts the scoped walkthrough for approval” can be agreed without implying that the client has renewed a contract or approved all future work.
Read the promise, delivered-work record, and outcome status together. A customer view might ask “What would make the index useful to staff?” An internal view might ask “What information do we need to scope a walkthrough?” Both must continue to show index use as unknown until evidence is supplied.
Draft an evidence-conscious QBR packet
Write a customer QBR meeting agenda in US English.
Review period and meeting length: [enter]
Client's stated goals: [paste]
Approved promised work and scope reference: [paste]
Delivered work and evidence links/dates: [paste]
Outcome metrics with definitions, periods, and denominators: [paste or UNKNOWN]
Actual client feedback: [paste or NOT SUPPLIED]
Known gaps or changed goals: [paste]
Next-quarter proposals and approval requirements: [paste]
Authoritative client report, contract, and action tracker: [enter]
Make a timed agenda for confirming goals, reviewing delivery evidence,
discussing outcomes/feedback, selecting priorities, and confirming follow-up.
Times must sum to the meeting length. Keep promised work, delivered work,
and client outcomes in separate fields. Missing outcomes remain UNKNOWN.
Do not invent ROI, satisfaction quotes, causal improvement, usage, approvals,
or renewal. Label proposed scope and use OWNER/DATE TO CONFIRM when needed.
Suggest two scoped next steps linked to the actual gaps.
Return a text packet. If requested, add an HTML reading copy with customer
and internal question views. Changing views must preserve identical evidence
and unknowns. The copy must not collect feedback or replace the approved
report, contract, or action tracker.
Close by reading the client's actual decisions, the work still proposed, and the evidence someone will bring next. Update the approved report and action tracker through your established process. At the next review, you should be able to see whether a proposal was approved, tried, and observed rather than merely carried forward on another slide.
Optional: inspect the briefing in NOS
If you prepare a separate HTML briefing, NOS can save and display the promise-to-evidence comparison. Use that reading copy to check whether unknown outcomes are still clear before the client conversation. Keep approved metrics, scope, and commitments in their maintained records.