Preparing a Monthly Operating Review Packet When the Numbers Arrive Late

Fix the packet deadline and the data cut

Set the data cut and the packet deadline before the month closes. The operating review needs a fixed point even when the ledger is still moving. Record the cut and the owner. A packet without a cut becomes a different document every day.

List the owners of each number and the system that produces it. A late number usually has a named owner and a dependency, not a mysterious delay. Record both. The escalation should go to the owner, not to the whole finance team.

Decide which sections can be drafted before the numbers arrive and which must wait. The narrative, the prior-month comparison, and the action log can often be prepared early. Record the sequence. The packet should not start from zero on the final day.

Agree with the presenter which decisions the review must support. A packet that reports every metric without a decision is a data dump. Record the decisions and the audience. The structure should follow the conversation.

Build the packet in layers

Draft the stable sections first, including the agenda, the prior actions, and the known risks. These sections rarely change at the last minute. Record the version and the owner. The packet then has a frame before the numbers land.

Add the numbers in a separate layer with a visible source and timestamp. A reader should know which figures are final and which are preliminary. Record the source and the cut. The label prevents a preliminary number from becoming a commitment.

Write the commentary after the numbers are in, not before. A narrative that was written in advance can contradict the data. Record the author and the time. The commentary should explain the variance, not repeat the table.

Keep a change log for every version sent to the presenter. A late number can change a conclusion, and the presenter needs to know what moved. Record the change and the reason. The log prevents a stale talking point.

Handle late numbers without hiding them

Name the late number at the top of the packet with the expected arrival time and the impact. A missing number that is buried in an appendix looks like an error. Record the owner and the fallback. The reader should know what is provisional.

Use the prior month or the plan as an explicit placeholder only when the presenter agrees. A placeholder that looks like actual data is dangerous. Record the label and the approval. The packet should never imply a number it does not have.

Escalate a number that will miss the review, not every number that is late by an hour. A material miss needs a decision about deferral or a verbal update. Record the threshold and the approver. The escalation should be proportionate.

Prepare a short verbal update for the review when the data cannot be final. The presenter should be able to say what is known and what is not. Record the script and the owner. A clear gap is better than a false precision.

Close the review with a usable record

Record the decisions and the owners in the action log during the review, not after it. A decision that is remembered but not written is likely to be repeated. Record the action and the date. The log is the packet's most durable output.

Send the final packet and the action log to the attendees within the agreed window. A packet that arrives after the next meeting is an archive, not a tool. Record the distribution and the date. The review should end with a shared record.

Note which numbers arrived late and why, without turning the note into a blame exercise. A pattern of late data may point to a system or a calendar. Record the cause and the owner. The next packet should start earlier where it can.

Review the packet design once a quarter and remove a section nobody uses. A long packet can hide the decision the review is meant to make. Record the removal and the reason. The packet should get clearer, not only longer.

Related resources

• Studying Operating Review Packet Late-Data Dependencies
• Running a Weekly Executive Calendar Audit Without Becoming a Gatekeeper
• Measuring the cost of context switching in an executive calendar

Frequently asked questions