Skip to content

Management Reporting Consultant

Management Reporting Consultant

A board pack is not a data dump with a cover page. It is an argument about the state of the business, carried by a small number of figures everyone in the room accepts. Most leadership reporting fails on the second half. After nineteen years in operations, most recently as Senior Director of Business Excellence at Publicis Groupe, this is what I have found belongs in management reporting, and what does not.

By Ashish Kumar Agnihotri·Last reviewed

Leadership reporting has a particular failure signature. The pack is long, arrives late, and is read properly by two people. Its first forty pages are functional detail nobody at board level can act on, and its last four contain the questions that actually matter, discussed for eleven minutes at the end of a three-hour meeting. Somewhere inside, two numbers contradict each other, and the room spends twenty minutes establishing which is right rather than deciding what to do. Volume is being used as a substitute for judgement. A longer pack feels safer to the person assembling it, because everything is technically in there, and it is precisely that instinct which makes the pack unusable.

My view of this comes from having sat on both sides of it. At Publicis Groupe, Business Excellence covered quality and delivery across 500+ clients, teams of 2,000+ and more than USD 750 million in annual media spend, for brands including Disney, Samsung, Adobe and P&G. Reporting at that scale is not an administrative task, it is the mechanism by which anything gets governed at all. Earlier, at Raymond, I built HR scorecards and business intelligence across 23 business units, and in 2012 I worked on benchmarking for the Election Commission. Different institutions, one recurring lesson: reporting is credible only to the extent that its definitions are settled in advance.

So the work I do on management reporting is mostly editorial and structural rather than technical. Decide the handful of numbers the board governs by. Define them precisely, name their owners, and publish the bridge between operational and financial views so disagreements are resolved by rule rather than debate. Fix the calendar so the pack arrives with time to read it. Then write the narrative that says what changed, why, and what is being done. Engagements begin with a fixed-fee diagnostic and continue, where useful, as a monthly retainer scaled to scope. Never hourly.

In depth

What you need to know about management reporting consultant.

What management reporting is for

It exists to let a small group of people who are not inside the daily work govern it anyway. That purpose sets the standard for everything in the pack. If a page does not inform a decision the board or leadership team can actually take, it does not belong in front of them, however interesting it is. Three questions define the job: are we where we expected to be, what has changed since we last met, and what needs a decision now. A pack that answers those three in twenty pages is doing more work than one that answers none in eighty. The test is not comprehensiveness. It is whether a competent non-executive who reads the pack on a Sunday evening arrives on Monday able to challenge the right things.

What belongs in a board pack

A short, stable core, arranged in the same order every time so readers build familiarity. A one-page summary written by the chief executive, saying what happened and what is being asked of the board. The scorecard, five to nine metrics against target with trend, each with a named owner. A financial section reconciled to the management accounts, with cash and the forward view given at least as much weight as the profit and loss. A risk page listing what changed rather than restating a permanent register. A short set of decisions requested, each with options and a recommendation. Then appendices for anyone who wants depth. Predictability of structure matters more than most people credit. When the shape changes each month, the board relearns the document instead of interrogating the business.

What does not belong

Departmental operating detail that no board-level decision depends on. Metrics without owners, which are decorative. Charts whose axes or definitions shift between meetings, which quietly destroy trend comparison. Commentary that describes movement without explaining cause: revenue was down eight per cent tells the room nothing that the chart did not. Anything included solely so that a function appears represented. Long strategy narrative that repeats the last three packs. And numbers whose source cannot be named on request, which is the fastest way to lose a room. Most of this material is not wrong, it is simply misplaced, and it belongs in the functional operating layer where the people who can act on it already work. Moving it there is usually less contentious than deleting it, and achieves the same result.

Narrative and numbers

Numbers show what happened. Narrative explains why and what follows. A pack with only numbers forces every reader to construct their own explanation, and they will construct different ones. A pack with only narrative cannot be challenged. The useful convention is tight: each metric that has moved outside tolerance gets three sentences, no more. What moved, what caused it, what is being done and by when. That constraint does more for reporting quality than any formatting change, because three sentences cannot hide behind vagueness. Writing them is uncomfortable for the owner, which is exactly the point. Where the cause is genuinely unknown, the correct commentary says so and names the person investigating, with a date. Boards handle uncertainty well. They handle confident fog badly.

Reconciliation and one version of the truth

Operational and financial numbers rarely match, and usually should not. Operations counts work when delivered, finance when invoiced or recognised, and the timing gap between them is real. Trouble begins when the pack presents both without acknowledging the difference, and a board discovers the inconsistency itself. The remedy is a published bridge: one standing page showing operational volume, the timing and adjustment items, and the reported financial figure, with every difference explained by a rule rather than a negotiation. Alongside it sits the metric dictionary, giving each number its formula, source, owner and exclusions. Once both exist, meetings stop relitigating whose figure is correct. This is a small artefact with a large effect, and it takes far longer to agree than to write.

The calendar, and the meeting it feeds

Reporting quality is largely a scheduling problem. If the pack lands the night before, it will not be read, and the meeting becomes a presentation instead of a discussion. Work backwards from the meeting date: the pack circulated a clear five to seven days ahead, commentary written two days before that, numbers frozen two days before that, and the close sequenced to make the freeze achievable. Then run the meeting on the assumption everyone has read it. No page-turning, no presenting of material already circulated, and the agenda built from the decisions requested rather than from the pack's table of contents. The change most leadership teams notice first is not better numbers. It is recovering a large part of the meeting for the discussion that actually needed the room.

Reporting for investor-backed and multi-entity groups

Private-equity and venture-backed companies carry an additional reporting obligation, and it is a mistake to run two disconnected systems for it. The investor pack should be a defined extract from the same scorecard and the same definitions the leadership team already uses, with covenant and cash reporting added. When it becomes a separate monthly exercise, it consumes the finance team and, worse, invites divergence between what the board sees and what the business runs on. Multi-entity groups face the same discipline one layer down. A common chart of accounts, a shared metric dictionary and a consolidation format that does not change are what make group reporting fast and defensible. Without them, consolidation depends on one person's knowledge, and the close stretches to fit their diary.

How I work on management reporting

The starting point is a fixed-fee diagnostic, usually two to four weeks. I read the last several packs, interview the people who assemble them and the people who receive them, sit in on a review meeting where possible, and trace the critical numbers back to source. The output is a written assessment: what the pack is trying to do, where it fails, which pages to remove, what is missing, and where the calendar has to change. Where a retainer follows, it is monthly and scaled to scope, never hourly. The early retainer work produces the redesigned pack, the metric dictionary and reconciliation bridge, a fixed reporting calendar, and a reset review meeting chaired by your leadership rather than by me.

Questions

Common questions about management reporting consultant.

A management reporting consultant redesigns what leadership and the board see, and how the numbers behind it are produced. The work covers four things: choosing the small set of metrics the business is governed by, defining them precisely and assigning owners, reconciling operational and financial views so the room stops arguing about which figure is right, and fixing the calendar so the pack arrives early enough to be read. The visible output is a shorter pack. The real output is a leadership meeting that spends its time deciding rather than clarifying.

Short enough to be read properly, with appendices for anyone who wants more. In practice a core of roughly fifteen to twenty-five pages works for most mid-sized companies: a chief executive summary, the scorecard of five to nine metrics, a reconciled financial section with cash and forward view, a page on what changed in risk, and the decisions requested. Everything else goes into appendices or back to the functional layer. Length is a symptom, not the problem. Packs grow long when nobody has decided what the board is actually governing.

Five to nine. Fewer and the business optimises one number at the cost of everything around it. More and attention thins until nothing is genuinely governed. Each metric needs a named owner, a target, a tolerance band, and an agreed response when it breaches. The discipline is not in selecting the metrics, which most teams manage in an afternoon. It is in defending the exclusions month after month while every function lobbies to add its own number to the leadership page.

Usually by publishing the difference rather than eliminating it. Operations counts work when delivered and finance when invoiced or recognised, so a gap is legitimate. The fix is a standing one-page bridge showing operational volume, the timing and adjustment items, and the reported financial figure, with each difference explained by a written rule. Paired with a metric dictionary giving every number its formula, source and owner, it removes the argument from the meeting. Agreeing that page takes longer than writing it, and it is the single highest-return artefact in most engagements.

Five to seven clear days before the meeting, and everything else in the calendar should be sequenced backwards from that. Commentary written two days before circulation, numbers frozen two days before that, and the close arranged so the freeze is achievable. Then run the meeting on the assumption it has been read, with no presenting of circulated material. Most leadership teams find the immediate gain is not better analysis but the recovery of a large part of the meeting for the discussion that genuinely needed everyone in a room.

Your team writes it, because the person accountable for a number is the only person whose explanation is worth reading. What I install is the convention: three sentences for every metric outside tolerance, covering what moved, what caused it, and what is being done by when. During the first cycles I edit rather than draft, which is uncomfortable and effective. Where a cause is genuinely unknown, the correct commentary says so and names who is investigating, with a date. Boards handle uncertainty far better than they handle confident vagueness.

It adds covenant and cash reporting, but it should not create a second reporting system. The investor pack works best as a defined extract from the same scorecard and the same definitions your leadership already runs on. When it becomes a separate monthly exercise, it consumes the finance team and allows what the investor sees to drift from what the business actually manages by. The practical rule is one set of definitions, one close, one source of truth, and different views built on top of it for different audiences.

A fixed-fee diagnostic first, priced separately so the assessment stands on its own. Over two to four weeks I read recent packs, interview producers and recipients, observe a review meeting where possible, and trace critical numbers to source, then deliver a written redesign recommendation. If a longer engagement makes sense it runs as a monthly retainer scaled to scope and cadence, never hourly. The early retainer work delivers the redesigned pack, the metric dictionary and reconciliation bridge, a fixed calendar, and a reset meeting chaired by your own leadership.

The next step

A short conversation settles most of this — and a fixed-fee diagnostic settles the rest.

Call