FROM THE TEAM AT
Start a conversation ↗
← Field Notes

FIELD NOTES

The Owner’s Reporting Pack

What belongs in a monthly pack that connects results, cash and decisions.

A management pack can be accurate, detailed and delivered on time while leaving the most important question unanswered: What should we do differently?

The problem is often a gap between financial results and operating responsibility. One page explains revenue, another shows activity, another forecasts cash. The people in the room have to reconstruct the connections before they can make a decision.

A useful pack reduces that translation work. It gives management a shared view of what happened, why it happened, what may happen next and who owns the response.

Begin with the meeting, not the template

Before redesigning the pack, list the decisions the meeting is supposed to support.

An operating review may need to decide where to add capacity or which referral pathway needs attention. A finance review may need to decide whether to change a hiring assumption or the timing of a commitment. A board may need to understand a change in the forecast and the choices management is making in response.

Those decisions have different information needs. A standard template can help organize them, but it should not decide them.

Ask each regular participant which part of the existing pack changes a decision. Ask which important question still needs a separate spreadsheet or a follow-up email. The answers identify what deserves space in the next version.

Build a connected sequence

One practical reporting structure moves through five questions.

1. What changed?

Show a small set of financial and operating measures against the relevant comparison. State the period and whether the numbers are final, preliminary or revised.

Avoid using a favorable comparison simply because it is available. A month affected by a timing difference may need an additional view before management can interpret it. Explain the reason rather than allow the page to imply a trend it does not establish.

2. Why did it change?

Connect the variance to drivers the team understands: volume, mix, price, staffing, capacity, timing or another relevant factor.

Distinguish an observed explanation from a hypothesis. If the team believes a referral change caused a revenue movement but has not checked the path, label it as something to test. The pack should make the uncertainty visible enough to resolve.

3. What is likely to happen next?

Connect the forecast to explicit assumptions. Who owns each material assumption? What evidence would change it? When will it be reviewed?

A forecast does not become more useful simply by extending the spreadsheet further into the future. Its usefulness depends on whether management can see how the assumptions connect to the business and to the decisions it controls.

4. What does it mean for cash?

Show the timing of receipts, payments and commitments in a form appropriate to the business. Separate an accounting result from the timing of cash and explain important differences.

A scenario should identify what changed, rather than present several unlabeled versions of the same workbook. Management needs to know which assumption drives the difference and which action it can take.

5. What happens now?

Close the loop with a decision or an explicit reason to wait. Record the owner, next action, expected review date and evidence needed.

The action log should return at the next review. Otherwise, the pack becomes a history of discussions rather than a means of managing the business.

Give every important measure a definition

Financial and operating teams can use the same word for different things. Revenue may mean booked, billed or collected. A new customer may be counted at an inquiry, a contract or the first completed service.

A compact metric dictionary makes these differences inspectable. For each core measure, record:

Use the dictionary to resolve the first meaningful disagreements. Do not postpone a useful pack until the company has documented every possible metric.

Separate assembly from judgment

Map the work required to create the current pack. Which steps collect data? Which reconcile it? Which interpret it? Which merely reformat something already available?

Reducing repetitive assembly can make room for better review. It does not remove the need for a responsible person to understand the numbers. A pack that updates automatically still needs checks for source changes, incomplete periods and unusual events.

The handover should explain how the pack is produced, which parts require judgment and what to do when a reconciliation fails. That is part of making reporting dependable rather than dependent on one person.

An illustrative decision page

Consider a company where demand is increasing but completed work is flat. A financial page alone shows the result. An activity page alone shows the demand. A connected decision page might show the path between them.

It would align inquiries, scheduled work, completed work and available capacity over a consistent period. It would state which parts of the comparison are incomplete. The operating owner would explain the likely constraint and propose the next check or intervention.

The useful outcome is not an attractive chart. It is a decision about where to investigate or act, with someone accountable for returning with evidence.

This example is illustrative. It is not a claim about an Altitude engagement or a measured client outcome.

A pack review checklist

| Test | Question to ask |

| --- | --- |

| Decision | What decision does this page help someone make? |

| Definition | Could two readers calculate the measure the same way? |

| Reconciliation | Can the result be traced to its source? |

| Explanation | Is the driver observed, inferred or still unknown? |

| Ownership | Who can explain the result and act on it? |

| Follow-through | What will return at the next meeting? |

If a page cannot pass the decision test, shorten it, move it to supporting detail or remove it. If a decision lacks a usable page, design the information around that need.

Make scrutiny easier

Consistent definitions, supporting schedules and a record of changes also help the business respond to outside questions. They can make the information easier to understand when lenders, buyers or advisers ask for support.

Preparation is different from an independent audit, review or quality-of-earnings opinion. Define the role of management and each adviser clearly. A reporting project should not imply assurance it does not provide.

A practical first assignment

Start with one reporting cycle. Review the existing pack, identify the unanswered decisions and agree a first version of the metric dictionary. Give the reporting calendar an assembly owner, a review owner and a clear action rhythm.

The pack earns its place when it helps the people in the room understand the same business and decide what happens next.

Explore financial reporting or start a conversation.

A tool to take into the meeting

A reporting decision log (CSV) is an illustrative blank template. Add your own definitions and evidence locally. It contains no client data and sends nothing to Altitude.