Start from the decision the review must make
A quarterly business review is not a collection of department updates. It is a decision forum with a defined set of choices: where to invest, what to stop, which assumptions have changed, and what the next quarter must prove. Write those questions before requesting a single slide.
Ask the executive what decision the binder should support and what would make the meeting a success. If the answer is “keep everyone aligned,” narrow it. Alignment is an outcome, not an agenda.
A review that ends with no recorded choice will be repeated next quarter with the same material.
Translate the questions into a binder outline. Each section should exist because it informs a decision, not because a function expects to present. Sections that cannot be tied to a question become an appendix or a pre-read, which keeps the main book short enough to use.
Set the binder architecture before content
Choose a stable structure and keep it across quarters. A common shape is performance against plan, customer and pipeline signals, operational risks, people and capability, and decisions requested. The exact sections matter less than the consistency, because readers learn where to look.
Give every section a named owner, a page limit, and a template. The template should force a headline, three supporting points, and a clear implication. A department that cannot state its implication has not finished its analysis, and the binder should show that gap rather than hide it in prose.
Build a cover index with page numbers and owners. When the executive wants to jump to a topic during the meeting, the index is faster than a search. Keep the same numbering in the pre-read and the final book so references remain valid after edits.
Collect from owners with a fixed template
Send the request with the decision questions, the template, the page limit, and the deadline. Ask for the underlying data file as well as the formatted page. The data file lets the editor check a number without asking the owner to rebuild the exhibit.
Set a short intake conversation for each owner. Ten minutes is enough to confirm the headline, the implication, and the source of the numbers. Owners often write the history of their function because it is easier than stating a conclusion; the intake conversation pulls them back to the decision.
Track submissions by section and by evidence, not by “done.” A section with a polished layout but no source notes is not ready. Mark it as received with a gap, and tell the owner what is missing before the review cycle begins.
Reconcile numbers to one source
Choose one system of record for each metric and state it on the page. Revenue, pipeline, headcount, and cost should not be defined differently in different sections. Where definitions legitimately differ, label them and explain the difference in a footnote.
Reconcile the headline numbers before the executive sees the book. Compare the finance submission with the operating dashboard and the prior quarter’s restated figures. If the numbers disagree, resolve the definition or disclose the variance; do not average them into a comfortable middle.
Keep a reconciliation tab that shows the number used, the source, the date pulled, and any adjustment. The tab is for the production team, not the executive, but it is the evidence that the binder is internally consistent. It also shortens the next quarter’s work.
Edit for the executive, not the department
The editor’s job is to remove repetition, sharpen headlines, and make the decision request explicit. Departments write for their peers; the executive needs the implication. Rewrite the first page of each section so it can be read in thirty seconds.
Cut exhibits that do not change a conclusion. A chart that shows a stable trend may be useful context, but it should not displace the two exhibits that explain a variance. Put supporting detail in an appendix with a clear label.
Check the language for blame and ambiguity. “The team failed to deliver” is not a finding; “the launch slipped six weeks because the integration test environment was unavailable” is. Precise language helps the executive decide without reopening the investigation.
Version and distribute the pre-read
Freeze the content, then produce the pre-read. Use a version label, a date, and a page footer on every page. Distribute a PDF rather than an editable file, and keep the editable master in one controlled location.
Send the pre-read with a short note that names the decisions requested, the page where each appears, and the time allotted. Do not expect the executive to discover the ask. A good distribution note is itself a briefing.
Control late changes. If a number changes after the freeze, issue a corrected page with a change log rather than replacing the whole book silently. Readers who printed the earlier version need to know which page is authoritative.
Capture decisions and follow-ups
During the review, record the decision, the owner, the due date, and the evidence that will show completion. Distinguish a decision from a direction to investigate. “Look into pricing” is not a decision, and it should not be logged as one.
Send a one-page decision summary within one business day. Include the questions that were not answered and the date they will return. An unanswered question is a legitimate outcome, but it needs an owner and a next step.
After the meeting, update the binder index with links to the decision summary and the follow-up tracker. At the next quarter’s kickoff, review the prior commitments before requesting new material. The binder becomes a record of what the business decided, not just a snapshot of what it reported.
Background sources consulted for this workflow: Deloitte Insights; Consulting Advisory Services; Insights and Resources; Global Internal Audit Standards.