You need to produce a report.

It needs to please funders who want outcome data, trustees who want governance oversight, staff who want recognition, partners who want proof of collaboration, and the public who want to know what your organisation does. And you need to do all of this in one document.

This is not an unusual situation. Many charities, research organisations, and education providers face multi-audience reports. One document, multiple readers, competing needs. The default response is to include everything and hope each audience finds what they’re looking for. That rarely works.

One document doesn’t mean one reader

The fundamental mistake in multi-audience documents is treating them as if they’ll be read linearly, front to back. They won’t. A funder will search for outcomes data and financial summaries. A trustee will look for governance reporting and strategic direction. A member of the public will scan for stories and purpose. A partner will want evidence of shared objectives.

Each reader comes to the document with a unique question. They look for different content and leave when they find it—or when they think it’s not there. Designing a multi-audience report means catering to different entry points and reading styles. It’s about allowing everyone to find their own way in, not pushing them through the same door.

Structure for scanning, not sequential reading

The most effective approach for multi-audience documents is modular structure. Instead of one story for everyone, split the content into clear sections. Each part should be self-contained and easy to read on its own.

This doesn’t mean creating separate documents. It means making clear section boundaries with descriptive headings. This way, each audience can easily find the content that matters to them. A clear contents page helps readers find what they need. Its headings describe the content instead of just naming topics. This way, it guides each reader to their starting point.

Good information architecture for research reports follows the same principle: put the answers where readers expect to find them, not where the writing process happened to leave them.

Layered content serves different depths of interest

Different audiences don’t just want different topics – they want different levels of detail. A funder reading your impact data might want headline percentages on one pass and detailed methodology notes on another. A staff member might want to see their programme highlighted without wading through financial tables.

Layered design handles this. Lead with headline findings and summary data, clearly signposted. Follow with supporting detail for readers who want it. Place technical material, such as methodology notes, full datasets, and audit reports, in appendices or clearly marked sections. This way, they won’t disrupt the main narrative.

Each layer should be complete at its own level. The headline layer should make sense without the detail layer. The detail layer should provide evidence without requiring the reader to have absorbed the headline layer first. This is the same principle that makes a report work without a presenter in the room – each part communicates independently.

Visual hierarchy does the routing your table of contents can’t

A contents page tells readers what’s in the document. Visual hierarchy tells them what’s important and where to look. These are different jobs.

In a multi-audience report, visual hierarchy shows which content is for each reader. You do this without needing to label sections like “for funders” or “for staff.” Distinct visual treatment for data-heavy pages versus narrative pages. Pull quotes that surface key findings for skimmers. Summary boxes that capture the headlines of dense sections.

The goal is that a reader flicking through the document should be able to identify, within a few seconds, which pages are relevant to them. If every page looks the same and has the same layout, the document offers no navigational cues. This makes it harder for the reader to find what they need.

Accessibility makes multi-audience design work

A properly accessible document is, by its nature, a well-structured one. Tagged headings create a navigable outline. Alt text ensures images communicate to all readers. A logical reading order means the document makes sense regardless of how it’s accessed.

For multi-audience documents, this matters doubly. Accessibility features, such as clickable contents, heading-level navigation, and clear tables, help all readers navigate the same document with ease. A sighted reader skimming for section breaks is using the same structural cues that a screen reader user navigates by heading level.

If you’re thinking about making your language accessible, you’re doing well. Plain language helps many audiences at once. It lowers the assumed knowledge needed to understand the content.

Five audiences, one document, one chance to get it right

The challenge of multi-audience report design isn’t about cramming more content into a single document. It’s about organising the content you have so that each reader finds what they need without having to process what they don’t.

Funders, trustees, staff, partners and the public each bring different questions to the same document. The design either helps them find answers quickly, or it doesn’t. There’s rarely a second chance – if the first skim doesn’t reveal relevant content, the reader moves on.

One document, five audiences. The document doesn’t need to be five things. It just needs to be well-structured enough that each reader can make it theirs.