Why we built Report Review

Your annual report is supposed to talk to investors, regulators and the public. But if you've been through a reporting cycle, you know the real audience is often the dozen or so people who have to approve it before anyone outside the organisation sees a word.

That's not a failing. It's how the process works. The CEO needs to be comfortable with their review. Legal needs to manage risk. The board needs to endorse the document. Individual teams want their work reflected accurately. These are all reasonable requirements.

The problem is that each round of internal review quietly reshapes the report. And by the time it's published, it's been shaped more by the people who approved it than by the people it's meant to reach.

How the audience shifts during production

In the planning phase, the conversation is usually about stakeholders. What do shareholders need to know? How do we tell our story this year? What are the key messages? The brief is outward-facing and the intentions are good.

Then production starts and the focus moves inward. The CEO's review goes through several rounds until the tone feels right to them, regardless of whether a first-time reader would find it clear. Legal softens anything that could be read as a commitment. The chair wants particular achievements highlighted. Each division advocates for its own content. The sustainability team needs their section to reflect well on internal programs.

None of this is unreasonable. But together, these changes add up. The report gets shaped around internal comfort rather than external understanding. The language becomes careful rather than clear. The structure follows the organisational chart rather than reader logic. The highlights reflect what leadership is proud of rather than what stakeholders need to know.

What gets lost along the way

When reports are written for approvers rather than readers, a few things happen consistently.

The story falls apart. When each section is drafted and approved by different people, the connection between strategy, performance and outlook can break. As we covered in What makes an effective annual report?, the best reports tell a single, connected story across every section. But that's hard to achieve when nobody owns the overall narrative because everybody owns their piece of it. The chair's message says one thing, the CEO's review says another, and the operating review doesn't connect to either.

The language goes into safe mode. Every review cycle tends to make writing more cautious, more hedged, more abstract. Each edit makes sense on its own. Together, they drain the report of meaning.

Self-assessment disappears. Nobody in an approval chain wants to draw attention to setbacks or risks. So those sections get softened or buried until they say very little. But experienced readers — investors, analysts, regulators — notice what's missing. A report that only celebrates success actually undermines its own credibility.

Research backs this up. Studies on annual report readability show that complex, hedged language directly affects how investors perceive a company.^1,2 Reports that are easier to read signal transparency; dense, hedged language signals the opposite. (We explored this research in more detail in What do investors actually want from your annual report?.) The approval process is often what creates this complexity — not because anyone intends it, but because each round of review adds another layer of caution.

Keeping the reader in focus without ignoring internal realities

The organisations that produce the best annual reports aren't the ones with the biggest budgets or the fewest internal stakeholders. They're the ones that have built processes to maintain an external focus throughout the approval cycle.

That doesn't mean ignoring internal needs. It means managing them deliberately, so the final product still works for the people it's actually published for.

The difference between 'good enough' and genuinely good

Most annual reports are good enough. They're compliant, professional and reasonably well-produced. They get signed off, published and filed. Nobody complains.

But good enough is a low bar for what is usually an organisation's most important public document. The difference between a report that ticks boxes and one that genuinely communicates isn't design or page count — it's whether the production team kept the reader in focus from start to finish.

That takes deliberate effort. It means treating the annual report as a communication project, not just a compliance project. It means recognising that the approval cycle is necessary but doesn't define quality. And it means investing in the writing, the narrative and the reader experience with the same seriousness you bring to the financials.