Your FP&A team produces 47 monthly reports for various audiences in the company. The CEO uses 3. The other 44 land in inboxes and die there.
Here's the moment that defines a CFO: do you add report number 48 to solve a new question, or do you audit the 44 nobody reads and kill them before generating more?
Management reporting is that discipline. It's not producing more data. It's producing the specific report each audience uses to decide, at the cadence that serves them, with the right depth. The rest is expensive decoration.
By the end of this module you'll have it down. Let's go.
Your CEO will see ONE chart in your monthly report. Which do you pick?
In plain language
Before the mechanics, the four basic questions.
Why do this at all?
So decisions get made with current and consistent data. A report without an attached decision is waste. A report that shows the wrong data to the wrong audience is worse than nothing — it distracts with noise and erodes the finance team's credibility.
Who uses it?
FP&A builds it in collaboration with each audience. Used by: the CEO/board (monthly summary with implied decisions), functional leaders (weekly report with risks and actions), operating managers (daily report with execution detail).
When does it show up?
At each period close. But also: when a new decision process is being designed (launch, M&A, restructure) and when a report stops being used (audit and kill). The reporting system evolves with the company.
What if we skip it?
Reports accumulate until nobody knows which is the source of truth. Different functions cite different numbers for the same concept (Revenue, EBITDA, churn). The finance team loses time producing content nobody uses, and authority when the numbers don't reconcile.
Meet Andina S.A. (again)
Same Andina from Module 2.6 — LATAM coffee company, $200M revenue, based in Chile. The FP&A team produces 47 monthly reports. There's a margin report, a pricing report, an inventory report, an NPS report, a churn report, a collections report, an accounts payable report, a capex report, a headcount report, a productivity-per-plant report...
The new CFO asks a simple question: "which of these 47 reports actually drives a decision?" Silence.
One week of audit: 12 reports are actively used (CEO, exec committee, board, operational finance). 35 reports are generated by inertia. Some land with someone who archives them unread. Others go to "[email protected]" and nobody knows who's subscribed.
That's 35 reports × 4 hours of team time each month = 140 hours monthly producing something nobody uses. Almost a full FTE, paid to generate PDFs that get deleted.
The problem isn't lack of reports. It's lack of discipline about which report serves which decision. The exit is designing reports audience by audience. The visual below shows it.
Three audiences, three reports
Three audiences. Same underlying data (Andina's operation). Three radically different reports.
Tap each audience and watch the dashboard reorganize completely. The CEO needs 4 numbers and a conclusion. The VP needs the weekly pattern and the actions. The manager needs execution per rep and per deal.
Same business, three reports. That's the central insight of management reporting: the report that serves one audience is waste for another.
Interactive visual
Three views, one business: who is the report for?
Tap an audience. Same data, three different reports.
Revenue YTD
$58.2M
EBITDA margin
15.2%
Cash
$8.0M
Forecast accuracy
96%
Revenue vs forecast — last 6 months
Proposed decision
Q3 variance of −$1.2M from supplier price hike (March). Proposed Q4 price adjustment: +2% on premium capsules. Expects competitor pushback but protects 80bps of margin.
What you're looking at
Same business (Andina S.A.). Three radically different reports. The CEO needs 4 numbers and a conclusion. The VP needs the weekly pattern and the risks. The manager needs action per rep, deal by deal. Designing the wrong report for the wrong audience is the most expensive management reporting mistake — you produce a lot of content nobody uses to decide.
The three reports are built from the same semantic model (same definitions of Revenue, EBITDA, pipeline) but with different cuts and depth for each audience. That's what avoids the "different functions cite different numbers" trap — the source of truth is one, the views are three.
If your team isn't building reports this way (audience first, decision first), it's producing PDFs by inertia. That inertia is one of the largest invisible costs of a mediocre finance team.
The mechanics: how to design a report that serves
- Start with the decision, not the data. Ask "what decision will this audience make with this report?" If there's no clear decision, the report shouldn't exist. If there is one, the report is designed to optimize that decision.
- Define the exact audience. "Monthly report" isn't an audience. "Monthly report for the executive committee, read at the Q-review meeting" is an audience. Each additional word clarifies the design.
- Define the right cadence. Daily for operational problems. Weekly for functional management. Monthly for executive committee. Quarterly for board. Sending daily what's reviewed monthly is noise; sending monthly what's decided daily is slowness.
- Build on a semantic model. One definition of Revenue, EBITDA, churn, NRR — used by every report. If a function cites a different number than what's in the official report, the problem is that there's no semantic model (no source of truth).
- Audit and kill quarterly. Every Q, review which reports get used and which don't. Kill the unused. Document the decision. The silent accumulation of dead reports is what turns an efficient finance team into a PDF factory.
- One decision per report. If the report doesn't generate a specific decision, it's badly designed or shouldn't exist.
- Right density. The CEO doesn't want 47 KPIs on a page; the operating manager doesn't want a single global number. Wrong density is the second most common error after "no decision".
- Trend visible in 3 seconds. Your audience should see the direction (improving / worsening / stable) without having to read. If it requires analysis to understand the direction, the visualization is wrong.
- Comparison against something. An absolute number doesn't inform. Compared against plan, against forecast, against prior period, against benchmark — yes. Every KPI should have its explicit reference comparison.
Adversarial check
Adversarial check
1.The CEO tells you: "I need more detail in the monthly report. Add product-line and regional performance views." How do you respond?
2.Your VP of Sales reports at his all-hands that Q3 Revenue was $19M. Your official report to the board says $18M. Both numbers come from the same source (the ERP). What's the root problem?
3.You join a new company. They show you 47 reports the finance team produces each month. What do you do first?
Exit checklist
Suggested re-review: 6 months, or when the finance team feels saturated producing reports — usually the signal that it's time to audit consumption and kill what's not used.
Optional
Go deeper
Sources and books to dig into the original material