MBR / QBR assembly

Stop hand-assembling the monthly business review. Compose it from the decisions, trackers, RCAs and reasoning answers the platform already has.

From the transcript: "MBR, QBR — these are cyclic activities where we need beautification. Something you want to present — there will be certain sentences, certain blocks. If you visually represent it, the non-tech people who are sitting on top can grasp more of it and they can ask more questions."

The Monthly Business Review and Quarterly Business Review are presentation cycles that today eat 1-2 days of analyst time per cycle. The platform has all the inputs — decisions made, trackers run, RCAs done, scenarios modelled — and can assemble a draft MBR/QBR in seconds. Humans polish; they don't compose from scratch.

Who asks

Perf-marketing leader, before each MBR
Function heads across the org
Leadership preparing the board QBR

Frequency

MBR: monthly, on the 5th-7th working day
QBR: quarterly, in the 2nd-3rd week of the new quarter

Data the platform pulls from

It uses what already exists:

Decisions logged during the period (see Decisions)
Trackers active during the period — their headline, trend, classification
Reasoning answers marked "save to report"
Goal progress (see Marketing efficiency)
Source-of-truth metric values at month/quarter close

No new data collection needed — these are the platform's natural artifacts.

How to ask it

"Assemble a draft MBR for September: marketing % vs target, top 3 decisions made, top 3 RCAs, key trackers, what's working / what's not."
"Generate a quarterly business review for Q2 2026. Include the goal scorecard, decision summary, and recommended commitments for Q3."
"For our board QBR: top 5 wins, top 3 risks, the 6-month outlook on each of our 4 strategic goals."

What you'll get back

A structured report (not a chat answer) — multi-slide, copy-pasteable into your deck of choice, citations preserved as footnotes:

1. Headline — one-line state-of-the-business 2. Goal scorecard — for each strategic goal: current value, target, trend, traffic light 3. Decisions logged this period — top 3-5, with rationale and outcome status 4. RCAs that produced lasting fixes — with the metric improvement 5. RCAs still unresolved — and what's blocking 6. Trackers worth flagging — both wins and regressions 7. Scenarios considered — strategic options modelled this period 8. Recommended commitments for next period — concrete asks

Every section pulls from real platform state. Citations make it defensible — board members asking "where did this number come from?" get a footnote, not a stammer.

The logic

MBR/QBR request for period [start, end]:
├── Pull goal values at start vs end → scorecard
├── Pull decisions with logged_date in [start, end]
│   ├── For each, summarise → ranked by stakeholder visibility
├── Pull tracker history in [start, end]
│   ├── Flag classification flips (green→watch, watch→alert)
│   ├── Surface trends > 15% movement
├── Pull "save to report" reasoning answers
├── Pull foresight queries that flagged risks materialising
├── Compose narrative → slides
└── Generate exportable PDF / slide deck

How to make it recurring

This is a report, not a tracker — but schedule it:

Cadence: auto-draft on the 1st working day of the month / quarter
Delivery: report appears in Reports list; perf leader gets a notification
Polish window: 2-3 days to edit before circulating
Export: PDF + slide deck for distribution

What you stop doing

Hand-compiling tracker snapshots into a deck
Re-deriving "what did we do this month?" from Slack history
Hunting through old reasoning runs for the chart you remember seeing
Writing the same boilerplate "Marketing % was X this month" sentence

Pitfalls

Treating it as final. It's a draft. Humans polish — that's where the storytelling lives.
Skipping the polish for QBRs. The board reads sentences, not tables. Edit the headline narrative.
Including everything. A QBR that mentions every tracker and every decision is unreadable. The platform pre-prioritises; trust the cut.
Letting it run unwatched. If the MBR auto-draft sits unedited and gets sent, that's worse than not having it. Set the polish reminder.

On this page