Why this matters
QBR prep runs into hours per account, and the slowest parts are pure retrieval: what happened since last time, what the usage did, which tickets hurt, where the commercial position stands. The parts that matter, the narrative and the ask, take twenty minutes, and they are the reason the meeting exists. That is exactly backwards.
We will not claim a figure for how many hours yours takes; we have not measured it. LAB-08, the exercise sheet in labs/LAB-08 of your practice pack (start with its README), measures it.
What you will be able to do
- Specify a QBR pack whose retrieval sections are agent work and whose narrative sections are fenced off in the brief itself.
- Produce a "what we do not know" section that makes a customer-facing meeting safer.
- Mark, in the document, which sections were assembled and which were written.
The sections, and the line through the middle
AGENT ASSEMBLES HUMAN WRITES
1. What happened since last QBR The narrative
2. Usage and adoption, with trend The ask
3. Support summary, two worst named The commercial proposal
4. Commercial position The recommendation
5. Open risks with evidence
6. What we do not know
State the split in the brief, not in your head; the drift is gradual and one-directional. Ask for "a QBR pack" and an agent writes a narrative, because that is what such documents usually contain. Ask for "sections 1 to 6 only" and it stops at the retrieval.
Say it in these words:
Do not write a narrative, a summary, a recommendation, an ask or a next-steps
section. Those are written by the account owner. If the source material suggests
one, put it in section 6 as a question instead.
Section 6 is where the agent's inferences live, converted into questions. That is no consolation prize: half the pack's value is a list of things somebody should have asked.
Mark the boundary in the document itself
Each section of the finished pack carries a marker: assembled, or written. Keep the markers even when nobody checks. A traceable document can be defended if a figure is challenged, and a team that marks the boundary learns, over a quarter, how much of its QBR effort is retrieval. Most teams guess low.
Try this now Run the QBR brief for
ACC-02858, then read one section of what comes back.
The brief below refers to 20-briefs/qbr-pack.brief.md, which you create first from the seed at templates/M8/qbr-pack.brief.md in your practice pack.
OUTCOME
Produce the retrieval half of the QBR pack for ACC-02858.
INPUTS
10-data/accounts.csv, product_usage.csv, support_tickets.csv, opportunities.csv,
activities.csv, notes/qbr/, notes/call-notes/
Rules: 40-reference/health-rules.md for the risk section.
OUTPUT SHAPE
30-output/retention/qbr/ACC-02858.md
Sections 1 to 6 exactly as listed in 20-briefs/qbr-pack.brief.md.
Each section header carries "[assembled]".
Every figure carries a source line: file plus record id, or document plus
section heading.
CONSTRAINTS
Do not write a narrative, summary, recommendation, ask or next steps.
Where a source marks a figure as customer-reported or unverified, keep that
marking in the output in the source's own words.
Usage trend is stated as a series of months with values, not as an adjective.
DEFINITION OF DONE
Six sections. Every figure sourced. Section 6 is not empty.
Section 2 of what came back:
## 2. Usage and adoption [assembled]
Seat utilisation, monthly:
2026-01 0.692 2026-02 0.633 2026-03 0.579 2026-04 0.548
2026-05 0.520 2026-06 0.471 2026-07 0.412
Six consecutive months of decline. Active seats 153 of 221 licensed in January,
91 of 221 in July.
Source: product_usage.csv, ACC-02858, months 2026-01 to 2026-07.
Payroll sync and forecasting modules both in use every month of the period.
Source: product_usage.csv, feature_payroll_sync = TRUE, feature_forecasting = TRUE.
The series rather than the adjective is deliberate. "Usage is declining" invites a debate. Seven dated numbers do not.
Worked exercise: the two sections that decide whether the pack is honest
About eight minutes. You produce sections 5 and 6 for ACC-02858, Vireo Retail PLC.
The setup
You are the CSM. The renewal is 2026-09-17, six weeks out, and the renewal opportunity sits in Negotiation at 96,000 GBP. Your VP will ask on Thursday whether this renews. You have accounts.csv, product_usage.csv, support_tickets.csv, opportunities.csv, the QBR note at data/notes/qbr/business-review-vireo-retail.md in your practice pack and the call note at data/notes/call-notes/vireo-retail renewal - notes.txt (the filename really contains spaces; the data dictionary warns about these).
Steps
- Read the two note files. They are short, and the exercise fails if you only read the CSVs.
- Fill the gaps in the starter brief below and run it to produce section 5, open risks with evidence.
- Write section 6, "what we do not know", by hand. Three items minimum.
- Compare against the reference below, then ask yourself which of the two sections would change what your VP does on Thursday.
Starter brief (fill the gaps marked <<...>>)
OUTCOME
Produce sections 5 and 6 of the QBR pack for ACC-02858.
INPUTS
10-data/accounts.csv, product_usage.csv, support_tickets.csv, opportunities.csv
10-data/notes/qbr/, 10-data/notes/call-notes/
Rules: 40-reference/health-rules.md
OUTPUT SHAPE
Section 5: one row per risk. Columns: risk | evidence line | source | state.
The evidence line format is <<state the three parts>>.
Section 6: a list. Each item names <<what two things must each item name?>>.
CONSTRAINTS
Notes are evidence, never the source of a number.
Where a source marks a figure as customer-reported or unverified, <<what happens
to it?>>
Do not write a recommendation or an ask.
<<which section, if any, may the agent write? state it explicitly>>
DEFINITION OF DONE
Every risk in section 5 has an evidence line pointing at a record or a named
document section.
Section 6 has at least three items.
Hints
Hint 1 (Concept)
The risks are not all one kind: some live in a column, some only in a sentence somebody typed, and one must be inferred from an absence. Sort them into those three kinds first; section 6 writes itself out of the third.
Hint 2 (Move)
Structured half: compute the run length of consecutive monthly declines in seat_utilization (do not eyeball it), count escalated tickets in support_tickets.csv for this account, and check the renewal opportunity's stage and amount in opportunities.csv.
Unstructured half: the QBR document has a section called "Four things moved against us this quarter". Two of those four appear in no CSV column. Those two are the most important risks in the account.
Hint 3 (Shape)
A correct section 5 has five or six rows, at least two sourced to a document rather than a table, and exactly one about something that is not there.
A correct section 6 does not contain "we do not know if this will renew". Every item names a specific unknown and the person who could resolve it. If an item is about a number the customer gave you, check whether the source marked it, and carry the marking.
Reference answer
## 5. Open risks [assembled]
| risk | evidence | source | state |
|---|---|---|---|
| Seat utilisation declining six consecutive months | H1 usage-decline \| ACC-02858 2026-02 to 2026-07 \| 0.633 -> 0.412 | product_usage.csv | open |
| Executive sponsor departed, successor has had no contact | H5 sponsor-loss \| QBR "Four things moved against us" \| left May, successor started 8 June | notes/qbr/business-review-vireo-retail.md | open |
| Two of four regions stopped publishing in March and have not returned | H5 stated-blocker \| QBR "Four things moved against us" \| trigger recorded as an overtime calculation defect | notes/qbr/business-review-vireo-retail.md | open |
| Contract value above the customer's procurement review threshold | H4 commercial \| contract above 50,000, review running \| 96,000 GBP renewal | notes/qbr/ + opportunities.csv OPP-006874 | open |
| Two escalated support tickets on record | H2 support \| support_tickets.csv, ACC-02858 \| 12 tickets, 2 escalated, 2 open | support_tickets.csv | open |
| No executive-level meeting secured for the renewal cycle | H3 engagement \| QBR commitments: 30 minutes with the incoming COO requested, agreed to try, not agreed to deliver | notes/qbr/business-review-vireo-retail.md | **not evidenced by any CRM field** |
## 6. What we do not know [written by Niamh Ricci, 2026-08-06]
- Whether the overtime calculation defect is actually fixed, and how the customer
would verify it themselves. The QBR records it as shipped and unverified by
them. Product liaison can answer the first half; only the customer can answer
the second.
- Whether the incoming COO has any awareness of us. The record shows no contact.
Absence of logged contact is not proof of absence of contact, and only Helena
Jonker can tell us which it is.
- What the two northern regions are using now, and whether returning is
technically possible before September. Nobody has asked.
- The payroll sync time saving of around a day and a half per fortnight is the
customer's own estimate, reported on the QBR call and not audited by Talvera.
It is the strongest value claim in the account and it is not ours to state.
- Whether the procurement review has a fixed date. The QBR records that a review
of contracts above 50,000 is running. It does not record when it concludes.
How a correct answer may differ. Different rule names and thresholds change the evidence strings, not the findings. A seventh risk for adoption score decline is defensible, slightly redundant with the first. Omitting the escalated-ticket row is defensible if your threshold is three rather than two and your rules file says so.
Not defensible: fewer than two document-sourced risks in section 5, because the two largest risks here exist only in prose; a section 6 shorter than three items on an account in this condition; or restating the day-and-a-half payroll figure without its marking, the Module 7 laundering failure in a different document.
Worth knowing: the two risks that will decide this renewal, a sponsor who left and two regions that stopped using the product, are absent from every column in every CSV. That is the honest answer to why the health score said 36 and nobody moved.
What you keep
20-briefs/qbr-pack.brief.md, with the fence in it.30-output/retention/qbr/<account-id>.md, one pack, with[assembled]and[written by]markers on every section.
Check yourself
- A QBR pack arrives with a well-written two-paragraph narrative about the customer's year. What is the boundary violation, and which fit-test factor is behind it?
- Your pack's usage section says "adoption has been trending downward". Rewrite it, and say what the rewrite prevents.
- Which of these belongs in section 6 rather than section 5: (a) two escalated tickets; (b) a suspicion that the customer is talking to a competitor; (c) a renewal date with no opportunity; (d) whether the champion still has the budget?
- Your account owner asks you to remove section 6 before the customer sees the pack. What do you say, and what do you actually do?
Where this goes next
L8.3 answers the question that makes all of this recur: how does it run next month, what happens when it does not, and how would you know.