Communication & Clarity
The challenge isn't disclosure, it's understanding.
Annual reports contain more information than ever.
Strategy, performance, governance, risk, sustainability, financial results, remuneration and regulatory disclosures all compete for attention. Each may be important. Each may be accurate. Each may satisfy its particular reporting requirement.
And the result can still be difficult to understand.
The real communication challenge is not getting information into the report. It is helping readers make sense of it.
More information doesn't necessarily create more understanding
Reporting requirements have grown for good reasons. Stakeholders want greater transparency, Boards and regulators expect greater rigour, and organisations are being asked to explain a wider range of factors that influence performance and future value.
But information has a cumulative cost. As more content is added, the important can become harder to distinguish from the merely necessary. Connections disappear beneath detail. Messages compete with each other. Readers are given more information but less help deciding what it means.
Good reporting doesn't solve that problem by saying less for the sake of brevity. It solves it through judgement: deciding what matters most, giving it appropriate prominence, and organising everything else so readers can find the depth they need without losing sight of the story.
Clarity isn't simplification. It is making complexity understandable.
Every report needs a hierarchy
Not everything in an annual report deserves equal attention.
Some information is fundamental to understanding the organisation: where it is heading, what matters most, what changed during the year and what that means for the future. Other information provides evidence, detail or disclosure that readers may need at greater depth.
When those different kinds of information are treated equally, the report becomes flat. A statutory disclosure can have the same visual weight as a strategic turning point. A significant performance result can disappear among twenty other achievements. The reader is left to establish the hierarchy for themselves.
Communication requires choices about prominence. That hierarchy operates at every level: across the report, within sections and on individual pages. Structure, headlines, standfirsts, writing, design, charts, call-outs and navigation all help signal what matters first and where to go next.
The story needs a spine and ribs
A clear report needs a strong central story, but that doesn't mean forcing everything into a single message.
We think of the central narrative as the spine. It provides direction and coherence: the organisation's strategy, the significance of the year, the most important performance messages and what they mean for the future.
The ribs are the supporting stories and evidence that give that narrative substance. They may explain a strategic priority, a material issue, an important risk, a performance result or a significant development. Each adds something useful, but each connects back to the larger story.
Without a spine, the report becomes a collection of sections. Without the ribs, the central story becomes assertion without enough evidence or depth.
Clarity comes from understanding the relationship between the two.
Write for how people actually read
Very few readers begin at page one and proceed diligently to the end. They skim, search, jump to the section they care about, follow a link, look for a number, read a headline and move on. Some want the central story in minutes; others want to interrogate the evidence behind it.
Good reporting accommodates both.
A skimmer should be able to understand the organisation's direction, the significance of the year and what happens next without reading every word. A deep reader should be able to move from that narrative to the evidence, definitions and detailed disclosure that substantiate it.
Those readers don't need different stories. They need the same story at different depths.
That has implications for writing and design, but also for the architecture of the report itself. Narrative and Reference should work together rather than compete for attention.
Design is part of the thinking
Design is sometimes treated as what happens after the words are approved. In a good annual report, it starts much earlier.
Design determines hierarchy. It helps readers understand relationships, distinguish narrative from supporting detail, compare information and navigate a complex document. It can reveal meaning through a chart, make a key message impossible to miss, or allow several levels of information to coexist without overwhelming the page.
But design can't create clarity that isn't present in the thinking. If everything is considered equally important, the designer has no hierarchy to express. If the story isn't settled, visual emphasis becomes arbitrary. If the relationship between information isn't understood, adding more devices can make the page busier rather than clearer.
Good design doesn't decorate the information. It helps organise understanding.
Digital changes the way clarity works
Even when the annual report is delivered as a PDF, it is now predominantly a digital experience.
Readers encounter individual pages rather than spreads. They search rather than browse sequentially. They expect links to take them directly to supporting information. Increasingly, content is also being extracted, compared and summarised by machines and AI.
That makes structure, terminology, hierarchy and navigation more important, not less. But digital also creates new ways to improve understanding. Video, animation, interactive content and the ability to build information sequentially can make complex ideas easier to grasp and allow readers to engage at different levels of depth. A report needs to work for the person scanning for the main story, the analyst looking for evidence, and increasingly, the technology trying to interpret what the organisation has said.
But the underlying challenge hasn't changed. A good annual report takes a lot of information and makes sense of it.
That's what clarity is for.
Annual Report Essentials
The communication disciplines that transform information into understanding.
Every annual report contains information.
The best annual reports do much more than that. They help readers understand the organisation's strategy, recognise the progress being made and develop confidence in its future direction.
That doesn't happen through better writing alone. It comes from a series of communication disciplines working together to create clarity, credibility and trust.
The articles throughout this section explore these disciplines in more detail. This overview explains the principles that underpin them.
Start with one clear story
Every annual report needs a central story.
That story isn't a slogan or a theme imposed on the year. It emerges from understanding what was significant, how the organisation is progressing against its strategy, what changed and what all of that means for where it is heading.
Without that clarity, individual sections may be perfectly competent but the report can still feel like a collection of information rather than a coherent explanation of the organisation.
Settle the story first. It gives everything else something to organise around.
Read more: The Narrative Spine.
Lead with strategy
Activities do not tell the story. Strategy gives them meaning.
A report can describe dozens of initiatives, investments and achievements without helping readers understand why they matter. Strategy provides the context. It explains what the organisation is trying to achieve and allows readers to judge whether the actions and performance reported during the year are moving it in the right direction.
That doesn't mean strategy needs to dominate every page. It means the report should keep connecting what happened back to what the organisation is trying to achieve.
Give the important things prominence
Not everything in an annual report deserves equal attention.
Good reporting makes deliberate choices about what readers should notice first, understand most clearly and remember longest. A major strategic development shouldn't compete for attention with a routine disclosure simply because both need to appear in the document.
Hierarchy makes those choices visible. It operates across the structure of the report, within individual sections and on every page. Writing and design should reinforce the priorities rather than allowing everything to compete equally for attention.
If everything is important, nothing is.
Read more: Designing for understanding.
Engage before you explain
Annual reports ask readers to absorb complex information. First, you have to persuade them to engage with it.
That doesn't mean entertainment for its own sake. It means creating enough interest, relevance and accessibility for readers to want to know more.
A strong opening, an informative headline, a revealing statistic, an unexpected insight, a well-chosen image or a clear visual explanation can all provide a way into the story. Once readers are engaged, they are more likely to explore the detail behind it.
Good communication doesn't just make information available. It gives people a reason to pay attention.
Make complex ideas easier to understand
Organisations are complicated. Annual reports don't need to pretend otherwise.
But complexity and confusion aren't the same thing.
Good reporting takes difficult ideas and makes them easier to grasp without stripping away the substance. That may mean using plain language, breaking an explanation into logical stages, defining unfamiliar concepts, using an example or finding a visual way to explain something that would take several paragraphs in words.
The objective isn't to dumb things down. It is to do enough of the thinking that the reader doesn't have to untangle the complexity unaided.
Show, don't just tell
Claims become more convincing when readers can see the evidence behind them.
If the organisation says a strategy is working, show the performance that supports that conclusion. If customer experience has improved, provide the measure or evidence. If an investment is building capability, explain what has changed. If a sustainability initiative is creating value, show the outcome rather than simply describing the activity.
KPIs, trends, charts, examples and case studies can all turn assertion into evidence.
The strongest reporting doesn't simply say what we did. It helps readers see what difference it made.
Design for understanding
Design isn't decoration added once the content is finished. It is part of how the report communicates.
Good design establishes hierarchy, reveals relationships, makes comparisons easier and helps readers navigate between different levels of information. It can turn complex data into an understandable chart, make a critical message easy to find or allow detailed evidence to sit alongside a clear narrative without overwhelming it.
That requires editorial and design thinking to work together. The designer needs to understand what matters, and the content needs to be developed with an understanding of how readers will encounter it.
The best design often feels effortless because the reader sees the meaning before they notice the design.
Read more: Designing for understanding.
Write for different reading depths
Readers don't all want the same amount of information, and the same reader may want different depths at different times.
Some want to understand the central story quickly. Others want to interrogate a particular issue, follow the evidence or explore detailed disclosure. Most will move between those modes rather than reading the report from beginning to end.
The answer isn't to create different stories for different readers. It is to make the same story work at different depths.
Headlines, standfirsts, summaries and visual hierarchy can carry the main story quickly. Supporting narrative, evidence and detailed disclosure allow readers to go deeper when they choose.
Read more: Write and design for skimmers and deep-sea divers.
Separate Narrative from Reference
Annual reports contain information that does different jobs.
Narrative explains what matters, what changed, why it matters and what it means for the future.
Reference provides the detailed evidence, definitions, data and disclosures readers may need to substantiate or explore that understanding.
Both are important, but they don't need to compete for attention.
Thinking consciously about Narrative and Reference helps keep the central story clear while preserving the depth and rigour a serious reporting document requires. Sometimes both layers sit within the annual report. Sometimes detailed Reference information belongs in a companion publication. Increasingly, digital links allow readers to move directly between them.
The important thing is that readers know where they are, and where to go when they want more.
Read more: Narrative vs Reference.
Build trust through transparency
A report that only tells the good news is rarely convincing.
Organisations operate in the real world. Plans change. Targets are missed. Trade-offs are made. Risks emerge. Some things work better than expected and others don't.
Good reporting doesn't need to dramatise every setback, but it should give readers a balanced enough picture to make their own judgement. Explain material challenges, acknowledge uncertainty where it exists, provide context for decisions and performance that may not be straightforward, and demonstrate what has been learned from failure or underperformance.
Transparency isn't about volunteering every difficulty the organisation encountered during the year. It is about not leaving out something important simply because it complicates the story.
Often, the complication makes the story more credible.
And design for how reports are actually used
These principles increasingly operate in a digital environment.
Even a conventional PDF is likely to be read on screen, searched, skimmed and entered at different points rather than read sequentially. Readers expect navigation and links to work. Individual pages may be encountered without the pages around them. Information may also be extracted, compared and summarised by machines and AI.
That changes some of the practical requirements of reporting, but not the fundamentals.
Know the story. Lead with strategy. Decide what matters. Make complexity understandable. Support claims with evidence. Create hierarchy. Give readers the depth they need. Be candid enough to be credible.
The technology will keep changing. Those essentials probably won't.
Digital expands the vocabulary of reporting
Delivering an annual report digitally doesn't automatically change the communication. A static PDF viewed on screen may behave much like the printed document it replaced.
But digital opens up possibilities that print cannot.
It gives reporting teams more ways to explain complex ideas, reveal information progressively, bring stories to life, allow readers to explore information at different levels of depth and make the experience more engaging.
The opportunity isn't to make the report more digital. It is to choose from a broader communication vocabulary to make the report clearer, more useful and more compelling.
Choose the right form for the idea
Words aren't always the best way to explain something. Neither is a static graphic.
Digital gives reporting teams more forms to choose from, including video, animation, interaction and layered content. Each can communicate in different ways and create different kinds of engagement.
The opportunity is not to use more digital techniques. It is to choose the form that gives the idea its best chance of being understood.
Sometimes that will still be words and a static image. Digital doesn't make traditional communication techniques obsolete. It simply gives us more choices.
Build understanding progressively
One of digital's most useful capabilities is the ability to control how information is revealed.
A complex business model, strategy or Value Creation Model can be difficult to absorb when every element and connection appears simultaneously. Digital allows the explanation to unfold: establish the central idea, introduce the components, then reveal how they connect.
The same approach can help explain strategic progress, a changing operating environment, a transition pathway or a complex set of data. Instead of presenting readers with the finished picture and asking them to decode it, information can be sequenced to help understanding build progressively.
This is where movement becomes more than decoration. Sequence itself becomes an explanatory tool.
Make interaction earn its place
More interactivity doesn't necessarily mean better communication. Digital techniques can clarify, engage and add energy to a report, but they can also create friction or distract from the message.
The strongest uses of digital improve understanding or make the experience more engaging without getting in the way.
Create different depths without creating different stories
Digital can also help solve one of reporting's perennial communication challenges: different readers want different levels of detail.
Expandable information, pop-ups, interactive diagrams and other forms of layering can allow the primary narrative to remain concise while deeper information is available to readers who want it.
That doesn't mean hiding important information. Material information still needs appropriate prominence. The opportunity is to distinguish between what everyone needs to understand and the supporting detail some readers will want to explore.
Digital makes that distinction easier to execute.
Remember the machine reader
Increasingly, annual reports are being read by technology as well as people. That has implications for how digital reports are structured and built, without diminishing the importance of the human experience.
It's a different dimension of digital communication and one we explore separately.
Learn from how people engage
Digital communication also creates something print never could: feedback about how people actually use the report.
Analytics can show which content attracts attention, what readers interact with and where interest falls away. That shouldn't determine what an organisation reports, but it can provide useful evidence about how successfully information is being communicated.
Those insights can inform the next report, turning digital reporting into an opportunity to learn as well as communicate.
What this means
Digital doesn't automatically make an annual report clearer or more engaging.
What it provides is a broader communication vocabulary: more ways to explain, reveal, connect, explore and engage.
The skill lies in choosing those techniques deliberately. Use digital where it makes something easier to understand, more useful to explore or simply more engaging to experience.
The technology isn't the point.
Better communication is.
Place holder
From information to understanding
Knowing what needs to be communicated is only part of the job. The Practical Guides explore how story, structure, writing, design and digital techniques can make complex information easier to understand, while the Tools help you test whether the report works for different audiences and different ways of reading.
Practical Guides
-
Finding the story is one thing. Getting the organisation to agree on it can be quite another.
Annual reports bring together perspectives from across the organisation. The CE, CFO, sustainability team, business units, communications team, Audit Committee and Board may all see different priorities. Each may be right from where they sit.
The problem comes when those perspectives aren't reconciled until people are reviewing the draft report.
By then, changing the story can mean rewriting sections, restructuring pages and unpicking decisions made months earlier. Worse, the debate can become about words and individual pages rather than the bigger question: what are we actually trying to communicate?
The answer is to build alignment around the story early.
Get the story onto one page
Before substantial drafting begins, articulate the proposed reporting story simply.
This isn't a contents page, creative concept or polished piece of copy. It is a short articulation of where the organisation is going, why that matters, how it intends to get there, what has happened during the year, and what that tells us about the journey ahead.
Ground it in the things the organisation already knows: strategy, material issues, performance, risks and opportunities, significant developments and outlook.
The purpose is to give people something concrete to discuss. It is much easier to respond to a considered proposition than to answer the question, “So, what's our story this year?”
Get the right people involved
Not everyone needs to develop the story.
A small group should do the initial thinking, ideally bringing together people who understand the strategy, performance and wider reporting context. Others can contribute evidence and perspective without collectively wordsmithing the central narrative.
Be clear about roles. Who needs to help shape the story? Who needs to endorse it? Who needs to be consulted? And who simply needs to understand it so they can contribute effectively?
Too many authors can blur the story. Too little involvement from the people who ultimately need to support it can be just as dangerous.
Get senior agreement early
The CE shouldn't encounter the reporting story for the first time in a designed draft. Nor should the Audit Committee or Board be asked to make fundamental judgements about emphasis and direction when the report is almost finished.
Put the proposed story in front of senior decision-makers early enough for them to influence it.
Don't simply ask whether they “like” it. Show them why you believe it is the right story. Explain how it reflects strategy, performance and material issues. Identify the important judgements you have made about emphasis. Be open about difficult or contradictory evidence.
The objective isn't approval of every eventual word. It is agreement on the central narrative the report is going to communicate.
Write down what you've agreed
Once there is alignment, capture it.
That agreed story becomes a useful reference point throughout drafting and design. Share it with contributors so they understand not only what information they are being asked to provide, but how their part fits into the whole.
It also gives the reporting team something to come back to when new requests arrive.
Does the proposed addition materially improve the story? Does new information require us to rethink something? Or does someone simply want their particular initiative to receive more prominence?
An agreed narrative won't eliminate those conversations, but it gives you a rational basis for having them.
Don't make early agreement a straitjacket
The story still needs to survive contact with the evidence.
Performance may change. New information may emerge. A Board discussion may reveal an issue that genuinely deserves greater prominence. As drafting progresses, the evidence may show that the original story needs more nuance.
Change it when there is a good reason.
The purpose of early alignment isn't to lock the organisation into a predetermined message. It is to prevent the story being repeatedly reshaped by late preferences, competing interests or isolated comments that lose sight of the whole.
Bring contributors into the story
One of the easiest ways to produce a fragmented report is to ask contributors to update their section from last year.
Instead, give them the reporting story first. Explain what readers need to understand, what role their section plays and what evidence would help tell that part of the story.
Their expertise should add substance and nuance. It shouldn't require them to work out independently what the organisation is trying to say.
The reporting team then has an important editorial role: bringing those contributions together into one coherent organisational voice rather than preserving every contributor's individual version of events.
Insight
The worst time to discover that your organisation doesn't agree on its story is when everyone is reviewing the designed report.
Build alignment early. Then use that agreement to guide the hundreds of smaller decisions that follow.
-
A strong annual report is not a collection of sections. It is a single, coherent story about where the organisation is heading, why that direction matters, and what this year's performance tells stakeholders about the road ahead.
We call that through-line the Narrative Spine. It isn't a slogan, campaign theme or clever line imposed on the report, but the central story that connects strategy, performance, material issues and outlook, helping readers understand not just what happened, but what it means.
Finding your Narrative Spine
One of the simplest ways to test whether your report has a clear Narrative Spine is to try summarising it in a few sentences.
Can you clearly explain:
where the organisation is heading
why that direction matters
what changed during the year
what those changes mean
what comes next?
If those ideas don't connect naturally, the report is likely to feel fragmented, however well the individual sections are written.
A Narrative Spine doesn't emerge from clever writing. It comes from understanding the organisation's strategy, priorities and performance, then identifying the story that connects them. Writing gives that thinking expression.
Use it as an editorial filter
Once you've identified the Narrative Spine, use it to test every major section of the report. Does the section strengthen the central story? Does it help readers understand the organisation's direction? Does it provide evidence that supports the story, or context readers need in order to understand it?
If not, ask whether the information belongs somewhere else, deserves less prominence or needs to be there at all.
Used this way, the Narrative Spine becomes a powerful editorial filter. It helps reduce repetition, improve focus and ensure that different parts of the report contribute to the same overall narrative.
Read more: Lead with what matters most.
The spine needs ribs
The Narrative Spine isn't the whole story. A report also needs the supporting stories, evidence and detail that give the central narrative substance. We think of these as the ribs: the strategic developments, performance results, material issues, examples and evidence that explain and support the central story.
The distinction matters because a Narrative Spine can become too dominant. If every section is forced to repeat the central message, the report starts to feel manufactured. The spine should provide coherence, not uniformity, allowing different parts of the organisation's story to breathe while still connecting back to the whole.
Consistency builds trust
The strongest organisations don't invent a new story every year. Their strategy evolves, priorities shift, new challenges emerge and progress is made, but readers can still recognise the organisation's long-term direction and understand how this year's decisions and performance fit into that broader journey.
That continuity builds confidence. It enables stakeholders to judge progress over time rather than treating each annual report as a disconnected snapshot.
The Narrative Spine should therefore reflect what is genuinely happening in the organisation, not simply what makes the most convenient story this year.
Common mistakes
One common mistake is allowing different sections to tell different stories. The strategy section emphasises growth, sustainability focuses on environmental commitments, the CEO's review highlights operational achievements and the Chair's report discusses governance priorities, yet the report never explains how they fit together. Readers are left with multiple narratives instead of one coherent one.
Another is developing a central story so broad that it could describe almost any organisation. A useful Narrative Spine needs to be grounded in the organisation's actual strategy, circumstances and priorities. It should explain why this year matters in the context of where the organisation is heading.
The opposite problem is trying to make the Narrative Spine carry too much. It doesn't need to capture every issue or achievement. Its role is to establish the central story, allowing the rest of the report to add evidence, context and depth around it.
Insight
A Narrative Spine turns a collection of sections into one coherent story.
It provides the thread that connects strategy, performance, governance, sustainability and outlook, helping readers understand not just what happened, but what it means and where the organisation is heading.
Next step
Try writing your Narrative Spine in a few sentences before you start shaping the report. Don't worry about polished language. Capture the logic:
Where are we heading? Why does that direction matter? What changed this year? What does that tell us? What happens next?
Then use that short narrative to test the report as it develops. If an important section doesn't connect naturally to the spine, ask whether the spine is incomplete, the section is misplaced, or the relationship simply hasn't been explained clearly enough.
The aim isn't to make everything say the same thing. It is to make sure everything belongs to the same story.
-
Readers shouldn't have to work out what's important.
One of the responsibilities of an annual report is to make that judgement for them.
Too often, reports simply present information. Headlines identify topics rather than messages. Charts display data without explaining why it matters. Important insights sit alongside background information with little indication of their relative significance.
Readers are left to decide for themselves what deserves attention.
The strongest reports don't leave that to chance. They guide readers towards what matters most, then provide the evidence and detail to support it.
Every page should make one point
Before a page is written or designed, ask a simple question:
If a reader remembered only one thing from this page, what should it be?
If the answer isn't immediately obvious, the page probably isn't focused enough.
The strongest pages rarely try to communicate everything at once. They establish one central message, support it with evidence and allow readers to explore the detail if they choose.
That discipline makes reports easier to read, easier to navigate and easier to remember.
Information isn't enough. Emphasis matters.
Readers constantly take cues from the way information is organised.
A meaningful headline tells them the point of the page. An opening summary establishes context. Charts, callouts, quotations and graphics reinforce the evidence. Supporting detail sits naturally behind the main message rather than competing with it.
These aren't design flourishes. They're communication decisions. Together they create a clear hierarchy that tells readers where to begin, what deserves their attention and how the information fits together.
Not everything deserves equal prominence
One of the most common reporting mistakes is treating every message as equally important.
Every achievement is highlighted. Every statistic becomes an infographic. Every page competes for attention.
The result is not greater impact. It is less.
When everything is emphasised, nothing is emphasised.
Good reporting is selective. It distinguishes between the central message, the supporting evidence and the background detail. That doesn't oversimplify the story. It helps readers understand it.
Design reinforces editorial thinking
Good design doesn't decide what's important. It makes those decisions visible.
Typography, page hierarchy, photography, graphics, white space and layout should all reinforce the same communication priorities.
When editorial thinking is clear, design can make the hierarchy immediately apparent. When it isn't, visual emphasis becomes arbitrary: things are made bigger, brighter or more prominent without a clear reason why.
The thinking comes first. Design makes it easier to see.
Read more: Designing for understanding.
Insight
Good communication is not about presenting more information.
It is about making informed editorial choices, then expressing those choices so clearly that readers instinctively understand what matters most.
Next step
Choose three or four pages from your current report and look at each one in isolation.
Ask:
If a reader remembered only one thing from this page, what should it be?
Then look at the page itself. Is that message what the headline communicates? Is it what the visual hierarchy emphasises? Does the supporting information help prove or explain it?
If the page appears to be saying several things equally loudly, decide what should lead and let the rest support it.
Next step
Choose three or four pages from your current report and look at each one in isolation.
Ask:
If a reader remembered only one thing from this page, what should it be?
Then look at the page itself. Is that message what the headline communicates? Is it what the visual hierarchy emphasises? Does the supporting information help prove or explain it?
If the page appears to be saying several things equally loudly, decide what should lead and let the rest support it.
-
One of the simplest ways to improve an annual report is to stop thinking in terms of the "front half" and the "back half".
Instead, think about Narrative and Reference.
Narrative explains what matters, why it matters and what it means.
Reference provides the evidence, disclosures and supporting detail that give readers confidence in that explanation.
Every good annual report needs both. The challenge is making sure each is doing the right job.
Narrative creates understanding. Reference creates confidence.
Narrative is where the organisation explains itself.
It interprets strategy, explains performance, acknowledges challenges and describes where the organisation is heading. It helps readers understand the decisions that have been made, why they matter and what this year's performance tells us about the future.
Reference does something different.
It provides the detailed information that allows readers to explore further, validate important claims and satisfy regulatory, governance or other information needs. Financial statements are an obvious example, but Reference can also include detailed metrics, methodologies, definitions, governance information and specialist disclosures.
One without the other creates an incomplete report. Narrative without Reference risks becoming assertion without enough evidence. Reference without Narrative becomes disclosure without enough explanation.
The strongest reports make the two work together.
It isn't really front half and back half
Narrative and Reference often broadly correspond with what reporting teams have traditionally called the front and back halves of the annual report.
But the distinction is more useful than that.
A strategy section may contain both narrative explanation and supporting metrics. A sustainability page may combine interpretation with detailed evidence. Governance information can provide important insight into how the organisation makes decisions as well as fulfil disclosure requirements. Even financial information can move from Reference into Narrative when a result or trend is important to understanding the story.
So Narrative and Reference aren't locations.
They are jobs that information performs.
That distinction becomes even more useful as reporting moves beyond a single document. A climate disclosure, sustainability data book or other companion publication may operate largely as Reference, while the annual report carries the significance of those issues within the central business narrative.
The question isn't simply where does this information sit?
It's what does this information need to do?
Tell one story at different depths
Most readers do not read an annual report from beginning to end.
Some will skim the opening pages before moving on. Others will focus on a handful of topics. A smaller group will examine particular areas in considerable detail.
The objective is not to tell different stories to different audiences. It is to tell the same story at different depths.
Narrative gives readers the context and meaning. Reference allows them to test, validate and explore.
A reader who stays mainly in the Narrative layer and one who goes deeply into the Reference layer should not come away with different versions of the organisation. The deeper information should substantiate and enrich the story, not contradict or quietly qualify it.
That's one reason consistency between the two matters so much.
Decide what belongs where
Many reports become longer and harder to understand because they repeat the same information in different forms.
Detailed disclosures find their way into narrative pages because somebody thinks they need to be included there. Important messages become buried beneath technical explanation. The same facts appear several times without giving readers any additional understanding.
A useful question is: Is this helping readers understand the story, or substantiating it?
If it is explaining significance, context, direction or what changed, it is doing a Narrative job.
If it is providing detailed evidence, definitions, methodology or disclosure, it is doing a Reference job.
Sometimes information genuinely needs to do both. A headline KPI, for example, may belong in the Narrative because it is important evidence of performance, while the detailed definition, methodology and historical data sit in Reference.
The objective isn't to classify everything rigidly. It is to be clear about why information is there and what role it needs to play.
Don't confuse Reference with less important
Reference isn't where unimportant information goes.
Some Reference information is critical. Financial statements, governance disclosures and detailed performance data may be essential to particular readers and fundamental to the credibility of the report.
The distinction is about communication role, not importance.
Narrative helps readers make sense of the organisation. Reference gives them the depth and evidence to interrogate that understanding.
Treating Reference as second-class content can make it difficult to navigate and unpleasant to use. Good Reference is organised, accessible and designed for readers who know what they're looking for.
Make the connection easy to follow
Separating Narrative from Reference only works if readers can move easily between them.
Where a narrative claim depends on supporting evidence, give readers a clear route to it. That may be a direct link to a financial statement note, a KPI definition, a detailed table, a climate disclosure or another part of the reporting suite.
The reverse matters too. Detailed Reference information should use terminology and structures that connect naturally back to the wider story.
This is particularly important in digital reporting. "See page 87" is less useful than a direct link to the information itself. And sending readers to the beginning of a 60-page companion document isn't much better.
The aim is not merely to tell readers that evidence exists. It is to make the evidence easy to reach.
Use the distinction beyond the annual report
Narrative and Reference becomes particularly useful when deciding what belongs in the annual report and what belongs elsewhere.
The annual report should carry the central business narrative: the organisation's direction, strategy, performance, material developments and what they mean for the future.
Companion documents can provide specialist depth where that serves a useful purpose. Climate disclosures are a clear example. Their detailed requirements make them predominantly Reference, while the annual report should still explain the significance of material climate issues within the wider business story.
The same principle can apply to sustainability data, modern slavery reporting and other specialist information.
This isn't an argument for pushing information out of the annual report. It is an argument for giving each piece of reporting a clear job.
Insight
Narrative explains. Reference substantiates.
The distinction isn't about front and back, important and unimportant, or interesting and dull. It's about giving information a clear role, then helping readers move between meaning and evidence without making them assemble the story for themselves.
Next step
Take your current report structure and mark each section, or each major content block, as primarily Narrative or Reference.
Then look for the trouble spots:
Reference detail that is overwhelming the story
Narrative that makes claims without enough supporting evidence
information repeated because its role hasn't been clearly decided
important connections where readers have no easy route from the story to the detail.
You don't need every piece of content to fit neatly into one category. The exercise is simply a way to reveal where Narrative and Reference aren't yet working together.
-
Item description
-
Item description
-
Item description
-
Item description
Tools
-
A practical workshop for getting the reporting project off to the right start
Every reporting project needs a timetable. Good reporting needs something before that: agreement about what the project is trying to achieve, what is being produced, how decisions will be made and who needs to be involved.
Every organisation's process will be different. Reporting obligations, governance, team structure, approval requirements and external dependencies all affect how the project needs to run.
This workshop isn't a prescribed process. Use it to get the important decisions on the table before the timetable takes over.
1. What are we trying to achieve?
Before discussing deadlines and deliverables, agree what success looks like.
Publishing an accurate, compliant report on time is essential. But what else should this year's reporting achieve? What do stakeholders particularly need to understand? Is there something about the organisation, its strategy, performance or future direction that reporting needs to communicate more clearly?
Agreeing the ambition at the outset gives later decisions something to be tested against.
2. What are we producing?
Define the reporting suite before production begins.
What must be produced? What else genuinely adds value? How will the annual report relate to climate disclosures, sustainability information, modern slavery statements or other supporting material?
Be clear about the purpose of each publication and where the central organisational story will be told. This is also the time to question anything being produced simply because it was produced last year.
How will the report be experienced? Are we producing primarily a printed/static document, a digital or interactive experience, or something that needs to work equally well in both? That decision will influence how we structure and navigate the report, how we write for it, and the opportunities we have to layer, reveal and bring information to life.
3. What needs to be decided before writing starts?
Not every content decision can be made upfront, but some are much easier to resolve before drafting begins.
Consider:
What is the emerging reporting story?
What deserves greatest prominence this year?
What belongs in the central narrative, and what is primarily supporting Reference?
What does the intended format and reading experience mean for how we structure and write the report?
Are there significant issues that will require early management or Board discussion?
What evidence and information will be needed to support the story?
The aim isn't to settle the report before the work begins. It is to avoid using drafting as a substitute for decisions that should have been made earlier.
4. Who needs to be involved, and when?
Map the people who need to contribute, decide, review or approve.
This may include executive sponsors, the Board, subject matter experts, finance, sustainability, legal and regulatory advisers, auditors or assurance providers, and external reporting, writing, design and production partners.
The important question isn't simply who? It is when?
Bringing the right people in early can shape the work. Bringing them in late often means reworking it.
5. Where are the major decisions and dependencies?
Identify the points that could determine the critical path.
When will the reporting story and structure need approval? What requires executive or Board sign-off? When do financial results become available? Where do audit or assurance processes intersect with reporting? Which decisions depend on information or approval from somewhere else?
Then identify what doesn't need to wait. Photography, case studies, data gathering, governance content, design development and other work can often progress in parallel.
A good programme distinguishes between genuine dependencies and habitual sequencing.
6. Where will the pressure come from?
Every reporting project has predictable pressure points.
Executive and Board availability, late financial information, complex data collection, audit timetables, regulatory review and external suppliers can all create bottlenecks. So can internal contributors for whom the annual report is important but never quite the most urgent thing on today's desk.
Identify the likely constraints before finalising the programme. Planning around them is easier than recovering from them.
7. Have we allowed enough time for thinking?
Writing and design are visible parts of annual report production, but they are not necessarily what takes the most time.
Discussion, decisions, review, challenge and refinement often determine both the quality of the report and the length of the process.
Build time for thinking into the programme rather than treating it as something that happens between deadlines.
8. Are we ready to start?
Before the project moves into production, make sure the core team has a shared understanding of:
what success looks like
what is being produced and why
the emerging reporting story and priorities
who is responsible for what
the major decision and approval points
the critical dependencies and likely bottlenecks.
A timetable tells everyone when things need to happen. Good planning makes sure everyone understands why, what and who before the clock starts running.
Related guidance
One report or many?
Who is the annual report really for?
The annual report as the organisation's source of truth
-
A workshop for finding the story the year is actually telling you
A strong reporting story rarely emerges from asking, "What do we want to say this year?"
That starts in the wrong place.
The better starting point is to bring together the different perspectives that should shape the report: the organisation's strategy and direction, the issues that matter to stakeholders, the context in which it is operating, and the evidence of what actually happened during the year.
The reporting story sits somewhere in the intersection.
This workshop is designed to help a reporting team find it.
1. Start with the business perspective
Begin with the organisation itself.
What is the strategy for success? What are the priorities that matter most to delivering it? What was the organisation trying to achieve this year, and what longer-term direction was that intended to support?
Then consider the context. What changed in the operating environment? What pressures, opportunities or decisions became more significant? Did anything happen that changed the organisation's priorities or tested its strategy?
The objective is to understand the year in the context of where the organisation is trying to go.
2. Bring in the stakeholder perspective
Now look through the other end of the telescope.
What issues matter most to the organisation's stakeholders? What has formal materiality work revealed? What are investors, employees, customers, regulators or other significant stakeholders likely to be trying to understand?
Materiality brings an important stakeholder perspective, but it doesn't determine the reporting story on its own. Nor does strategy.
Put the two alongside each other and look for the points of connection, tension and difference.
3. What did the year actually tell us?
Now bring in the evidence.
What changed during the year? Where did the organisation make meaningful progress? Where did performance fall short? What important decisions were made, and why? What assumptions were tested? What unexpected developments changed the picture?
Look across financial and non-financial performance, not just the achievements people are keenest to talk about.
This is often where the reporting story begins to reveal itself. The year may have validated the strategy, tested it, accelerated it or exposed a need to adapt. The significance lies in what happened in relation to the direction of travel.
4. Find the organising idea
Step back from the detail and ask:
What is this year's report really about?
Try to express the answer in one or two sentences before looking for polished language.
A useful organising idea should connect:
where the organisation is heading
what was significant about this year
what the evidence says about progress
what that means for the future.
It should be specific enough to belong to this organisation in this year. If it could comfortably headline a competitor's report, keep working.
And don't worry about making it sound clever. At this stage, clarity is much more useful than copywriting.
5. Test it against the awkward stuff
Now try to break it.
Does the story still work when you consider weaker performance, difficult trade-offs, material risks, stakeholder concerns or things that didn't go to plan?
Does it acknowledge the most significant developments of the year, or quietly step around anything inconvenient?
A good reporting story doesn't need to give equal weight to every issue. But it does need to accommodate reality.
If the evidence complicates the story, make the story more nuanced. If it contradicts it, change the story.
6. Look forward
A reporting story shouldn't end at balance date.
What does the year's performance tell us about what comes next? What has changed in the short-, medium- or long-term outlook? What needs to go right? What priorities, dependencies, risks or opportunities will shape the next stage?
This future perspective is what turns an account of the year into an explanation of the organisation's direction.
7. Build the narrative foundation
Once the organising idea holds up, develop it into a short narrative foundation the reporting team can work from.
Capture:
the strategic direction and context
the significance of the year
the few messages that most need to land
the evidence that supports them
important tensions, trade-offs or qualifications
what it means for the future.
This isn't report copy. It is the settled story base that the report will express and test, and that can also inform other major communications.
Keep it short enough to be useful. If the narrative foundation needs several pages to explain, the central story probably isn't settled yet.
8. Use it, and keep testing it
The narrative foundation should now guide the report.
Use it to test structure, prominence, content and evidence. Does the report make the central story visible? Are the important messages supported? Do individual sections reinforce the whole rather than developing their own competing narratives?
And keep testing the foundation as the report develops. New results, Board discussion, audit findings or late information may change the story.
The narrative foundation is settled thinking, not sacred text.
Workshop output
By the end of the session, aim to have:
a clear articulation of what this year's report is really about
the 3 to 5 messages that most need to land
the evidence that supports those messages
the important tensions or qualifications the story needs to accommodate
a concise narrative foundation to guide the report and other communications.
Related guidance
Every great annual report starts with one clear story
What deserves prominence?
The Narrative Spine
Using materiality well
The annual report as the organisation's source of truth
-
A practical guide to deciding what belongs where
Annual reporting increasingly involves more than one publication.
The annual report may sit alongside climate disclosures, sustainability information, modern slavery statements, detailed data or other regulatory and supporting material. The challenge is not simply deciding how many documents to produce. It is deciding what job each one should do.
Use this guide to test the structure of your reporting suite before content becomes locked into particular documents.
1. Start with the annual report
Begin with the document that needs to give readers the clearest overall understanding of the organisation.
Ask:
What do readers need to understand about our strategy, performance and future direction?
Which risks, opportunities and material issues are important to that understanding?
What information needs to remain in the annual report for statutory, regulatory or governance reasons?
What supporting evidence needs to be close enough to the narrative for readers to understand and trust it?
The annual report should work as a coherent account in its own right. A reader shouldn't need to assemble the central business story from several publications.
2. Identify what has a reason to live elsewhere
Now consider the other information you need or want to publish.
For each potential companion document or resource, ask:
Why should this be separate?
There may be a clear reason:
regulation requires or encourages separate reporting
the information serves a specialist purpose or audience
the level of detail would overwhelm the annual report
extensive data or methodology is more usable elsewhere
the format allows information to be maintained or accessed more effectively.
"Because we produced one last year" isn't a reason.
Nor is importance itself a reason for keeping something in the annual report. A topic can be highly significant while its detailed disclosure sits elsewhere.
3. Separate the story from the depth
It can be useful to think about reporting information as Narrative and Reference, although the two don't map neatly to separate documents.
The annual report contains both. Its Narrative content explains what matters, what changed and what it means. Its Reference content provides financial statements, governance information, metrics, disclosures and other evidence that belongs within the report.
Companion publications may provide additional Reference depth.
So for each significant topic, ask:
What does the annual report need to explain for readers to understand its significance?
Then:
What additional detail belongs here, and what is more useful elsewhere?
For example, a material climate issue may need to be integrated into the annual report's strategy, risk, performance or outlook narrative, while detailed climate disclosures sit in a separate publication.
The objective is not to move Reference information out of the annual report. It is to put information at the depth and location where it does its job best.
4. Map the connections
Once the proposed suite is clear, look at it as one reporting system.
For each major topic, identify:
where the central narrative sits
where the key evidence sits
where additional detail sits
how readers move between them.
Use direct links wherever possible. If the annual report discusses a climate risk, sustainability metric or other issue supported elsewhere, take the reader to the relevant information rather than merely naming another document.
Readers should never have to become detectives.
5. Test for gaps and duplication
Now look across the suite.
Gaps: Is anything important falling between publications because each assumes another document explains it?
Duplication: Are the same explanations, tables or disclosures being reproduced unnecessarily?
Contradictions: Do terminology, measures, targets, boundaries or time horizons change between publications without explanation?
Orphans: Is there a document or body of information that no longer has a clear purpose but continues to be produced?
Some repetition is useful. Important context may need to appear in more than one place so each publication can stand alone. The test is whether repetition helps readers understand, or simply reproduces content.
6. Test the suite from the reader's point of view
Finally, ignore the internal reporting structure and imagine arriving as a reader.
Can you understand the organisation from the annual report without needing to read everything else?
If you want more depth, is it obvious where to go?
Do links take you to useful destinations?
Can you tell why each publication exists?
And, wherever you enter the suite, do you encounter the same underlying organisation, strategy and direction?
If the answer to those questions is yes, the architecture is probably doing its job.
Decision output
By the end of the exercise, aim to have a simple reporting-suite map showing:
each publication or reporting resource
its purpose
the information it owns
where related narrative or evidence appears elsewhere
the links required between publications
any duplication, gaps or legacy content to resolve.
Insight
Every document should earn its place.
A reporting suite doesn't become better by becoming bigger. Separate information where there is a good reason to, then make the connections strong enough that
readers still experience one coherent story.Related guidance
One report or many?
Narrative vs Reference
Climate disclosures in context
Digital reading and machine/AI readability
-
The best annual reporting briefs start with the business, not the report.
Before an agency can help communicate an organisation clearly, it needs to understand where the business is heading, how it is progressing, what it depends on, what's changing around it and what matters most now and for the future.
Some of that will already exist in strategy documents, Board papers, investor presentations and previous reporting. But documents rarely tell the whole story. A good briefing process gets beneath them, drawing out the context, judgement, challenges, aspirations and organisational character that will ultimately make the report distinctive and credible.
Brief the problem, not the solution.
1. Where are you trying to take the business?
What is the organisation ultimately trying to achieve? What is the strategy for getting there, and what are the few priorities that matter most?
How far along that journey are you? What has changed since the strategy was established? What should be different about the organisation if the strategy succeeds?
And who should benefit? Consider the value the organisation aims to create for shareholders, customers, employees, communities and other stakeholders it depends on.
Understanding the destination provides the context for understanding the year.
2. How is the strategy working?
An annual report shouldn't simply restate the strategy. It should help readers understand how it is translating into action and results.
Where are you making good progress? Where is progress slower than expected? What evidence tells you the strategy is working? What have you learned along the way?
Have circumstances required you to change course, accelerate, invest differently or reconsider an assumption? Are some strategic priorities becoming more important while others are receding?
This is often where the real reporting story begins to emerge.
3. What's making the journey harder, or easier?
No organisation operates in isolation.
What are the significant headwinds and tailwinds? Where are the pressures and opportunities coming from? Customers, competitors, regulation, technology, workforce capability, supply chains, access to capital, climate, changing social expectations or something particular to your sector?
Which are short-term conditions to navigate, and which could fundamentally change the business over the longer term?
Understanding the environment around the organisation helps explain not only performance, but the context in which strategic decisions are being made.
4. What does the organisation depend on to succeed?
Think beyond financial capital.
What are the resources, capabilities and relationships the organisation couldn't succeed without? Its people and their knowledge? Customer trust? Suppliers? Communities? Natural resources? Intellectual property? Infrastructure? Access to capital? Its reputation or social licence to operate?
Which of these does the organisation create value for as well as draw value from?
How are those dependencies changing? Which need to be protected, strengthened or replenished if the organisation is to continue creating value over the long term?
These questions can reveal much more about the business than a conventional description of its operations.
5. What choices are you making?
Strategy involves choices, and sometimes trade-offs.
Where are you investing now to create value later? What are you choosing to prioritise, and what are you consciously giving less priority to? Where are there tensions between short-term performance and longer-term ambition?
Are decisions being made today to strengthen workforce capability, customer relationships, communities, environmental resilience or other resources and relationships the organisation will depend on tomorrow?
Not every internal debate belongs in the annual report. But understanding the important choices helps explain the judgement behind the organisation's direction and performance.
6. What could change the future?
Look beyond the current reporting period.
What emerging risks and opportunities could materially affect the organisation over the next few years? What assumptions about the future underpin today's strategy?
How might changes in society, technology, regulation, climate, customer expectations, workforce expectations or resource availability alter the organisation's ability to create value? Where could those same changes create new opportunities?
What capabilities, resources and relationships will become more important? Where is the organisation most resilient, and where is it vulnerable?
Future focus isn't about predicting what will happen. It's about helping readers understand how well the organisation is preparing for what might.
7. What has this year taught you?
A year's results become more useful when they tell us something.
What surprised you? What worked better than expected? What didn't? What do you understand about the organisation now that you didn't understand a year ago?
Have customer behaviour, operational performance, stakeholder feedback, materiality work, sustainability reporting, risk analysis or other processes revealed something that is changing your thinking?
What will you do differently as a result?
These learnings often provide the bridge between reporting past performance and explaining future direction.
8. What do you most need readers to understand this year?
Now turn the business thinking into a communication challenge.
If readers remember only a handful of things, what should they be? Is there something about the strategy, performance, outlook or organisation that isn't well understood? Has the story moved on from last year?
What deserves particular prominence this year, and why? What difficult issue needs context rather than simply disclosure? Where do you need to build understanding, confidence or belief?
Don't worry yet about the headline or creative proposition. Give the agency the intelligence it needs to help find the clearest story.
Define the assignment
Once the business context is clear, the practical brief becomes much easier to write.
What are we producing?
Define the reporting suite and the role of each component. What must be produced, what else genuinely adds value, and where will the central organisational story be told? How will the report be experienced: print, static PDF, digital or a combination?What is fixed, and what is open to challenge?
Identify genuine constraints, including regulatory requirements, governance processes, timing and brand requirements. Also make clear where the agency has room to question established structures, approaches or conventions.What does the agency need access to?
Provide the relevant strategy, performance information, research, materiality work, sustainability information, investor and stakeholder feedback and other source material. Just as importantly, provide access to the people who can explain the thinking behind it.Where do you want the agency to add value?
Be clear about the role you expect it to play. Is it there to help find the story, challenge thinking, shape structure, write, design, develop the digital experience, or work across all of these?What should the organisation feel like?
What personality should readers experience through the report? Confident or understated? Progressive or pragmatic? Ambitious, warm, challenging, precise, entrepreneurial? Think beyond a list of brand attributes. What should someone who knows the organisation well recognise as unmistakably you?What will success look like?
What should readers understand more clearly as a result of the report? What should feel different or work better than it did last year? Success doesn't always require a formal measure, but there should be agreement about what the work is trying to achieve.How will we work together?
Clarify who owns the project and the key decisions, who needs to contribute, when senior management and the Board will become involved, how feedback will be consolidated and where the agency is expected to lead, advise or execute.Insight
The better your agency understands the business, the better it can explain the business.
A strong brief doesn't simply describe the report you need produced. It gives the agency access to the organisation's direction, progress, challenges, choices, dependencies and aspirations, and enough freedom to turn that intelligence into a what report that helps others understand where the business is going and why.