Reporting operations

Preparing an Executive's Monthly Business Review Pack Without Late Data

A monthly business review pack routine, covering the data cut-off, the section owners, the fixed pack order, and the rehearsal that closes the cycle.

4 min readHireExecutiveTeam editorial
Preparing an Executive's Monthly Business Review Pack Without Late Data article illustration
Table of contents
  1. Set the data cut-off before the pack is built
  2. Assign the owners and the variance notes
  3. Assemble the pack in a fixed order
  4. Rehearse the numbers and close the cycle
  5. Related resources
  6. Frequently asked questions

Set the data cut-off before the pack is built

Fix the data cut-off date and time before anyone pulls a number for the monthly business review. A pack built from files extracted on different days will contain totals that cannot be reconciled. Record the cut-off in the pack cover and in the request to each data owner. The same cut-off should apply to every function that contributes.

List the source systems and the report each owner will use, including the finance ledger, the sales pipeline, and the operations dashboard. Two owners who pull from different extracts can produce two versions of the same revenue line. Record the system, the report name, and the extraction time. The list should be agreed in the planning meeting, not assembled during the review week.

Agree which late items will be excluded and how the exclusion will be shown in the commentary. An excluded order that reappears next month without explanation looks like a forecasting error. Record the exclusion, the value, and the owner. The note should let a reader reconcile this month with the last.

Send the cut-off and the exclusion rule to every contributor at the start of the cycle and confirm receipt. A rule that lives only in the assistant's notes is not a rule the organisation can follow. Record the send time and the acknowledgments. The confirmation should include the person who will supply the final number.

Assign the owners and the variance notes

Name one owner for each section of the pack and one reviewer for the whole document. A section without an owner arrives late or arrives as a screenshot that cannot be checked. Record the owner, the reviewer, and the deadline. The names should be visible on the pack plan rather than buried in an email thread.

Ask each owner for the variance explanation at the same time as the number, not after the pack is assembled. A number without its explanation forces the executive to guess in the meeting. Record the variance, the driver, and the confidence. The explanation should be short enough to read aloud.

Separate a timing difference from a permanent change in the business when the variance is described. A delayed order and a lost order need different responses from the leadership team. Record the category and the evidence. The distinction should be consistent across every section.

Challenge any explanation that names a person rather than a process, and ask for the evidence behind it. A pack that blames a team without a record invites an argument the meeting cannot settle. Record the question and the answer. The reviewer should be able to defend each note.

Assemble the pack in a fixed order

Use the same section order every month so the executive can find a number without searching. A pack that is reorganised each cycle adds friction to a meeting that is already short. Record the order in the template and keep it stable. Changes should be proposed between cycles, not during the review.

Put the summary page first and limit it to the decisions the meeting must make. A summary that repeats every chart pushes the decision to the last page. Record the decision, the owner, and the date needed. The page should stand alone if the rest of the pack is never opened.

Keep the detailed tables in an appendix and label each one with its source and cut-off. A table without a source cannot be checked after the meeting. Record the source and the extraction date on the page. The appendix should use the same numbering as the summary.

Check the pack for broken links, hidden rows, and stale charts before it is released. A chart that still carries last month's title undermines every other number in the document. Record the check and the reviewer. The final read should happen on the exported file, not the working draft.

Rehearse the numbers and close the cycle

Walk the executive through the three numbers most likely to be questioned before the meeting begins. A short rehearsal exposes a gap while there is still time to call the owner. Record the questions asked and the answers given. The rehearsal should take less than fifteen minutes.

Keep a list of the questions the leadership team asks during the meeting and add them to the next pack's checklist. A question asked twice is a missing section rather than a difficult audience. Record the question and the owner. The list should be reviewed at the start of the next cycle.

Note the corrections made after the meeting and the time they took to resolve. A pack that is corrected three days later has taught the team to distrust the first version. Record the correction, the cause, and the fix. The pattern should inform the next cut-off.

Close the cycle by archiving the final pack with the source extracts and the attendance record. A pack without its extracts cannot be rechecked when a decision is reviewed later. Record the location and the retention date. The archive should be readable without the person who built the pack.

Read also: meeting prep pack delivery study and board committee calendar.

Frequently asked questions

Should one assistant support the whole executive team?

Sometimes. It works when priorities are clear and executives share one operating rhythm.

What should happen before a consult?

List the meetings, inbox rules, recurring reports, and decisions that need support.

Ready to define the role?

Use a recent leadership week to scope the support that would make the biggest difference. The consultation is a working conversation, not a generic pitch.

Book a consultation