Information architecture: How your annual report holds together

Most annual reports are long. Even a slim one runs 80 pages. A government annual report can run 300. A reader who can't find what they need quickly stops trying — and the work that went into producing the content stops paying off.

Information architecture is the third of eight categories in our Report Review communication effectiveness framework. It's where we look at how the report is structured, sequenced and navigated.

What we mean by information architecture

Information architecture covers two things:

• how information is organised — sequence, hierarchy and layering for different reading depths
• how readers move through it — table of contents, bookmarks, cross-references, glossary and page navigation.

A well-architected report supports three very different readers at once.

The same report has to work for three different reader journeys.

Most reports serve one of these — usually the third — and disappoint the other two.

How an information architecture assessment creates value

Structural problems are the hardest to fix late. Once design teams lock the layout and typeset the financial statements, moving sections gets expensive. An information architecture assessment surfaces structural issues early enough for the team to act.

Get the structure right and the rest of the report works harder. Get it wrong and design, writing and narrative all have to work harder to compensate.

Why information architecture goes wrong

Most annual reports follow compliance categories rather than communication logic. Strategy in one section, performance in another, risk somewhere else, governance further back. The table of contents reflects the organisation's reporting structure, not how a reader would navigate.

A few patterns we see consistently:

• the table of contents follows internal structure, not reader needs
• PDF bookmarks are missing, inconsistent or stop at the wrong level
• cross-references between sections are minimal
• acronyms and technical terms aren't glossed
• the HTML version is a direct dump of the PDF, with no thought for screen reading
• page numbering, section markers and running headers are inconsistent.

We covered the DART-specific structural challenges in Tips for uploading your report to the DART. The same principles apply to any HTML or accessible version of an annual report.

What we look for

When we assess information architecture in a Report Review, we look at how a reader would navigate the document — across PDF, HTML, accessible Word and any other published version.

We're looking at things like:

• whether the report layers information for different reading depths (scan, read, detail)
• the sequence of sections — does the story unfold naturally?
• table of contents quality and how closely it matches the document
• PDF bookmark setup and reliability
• cross-reference frequency and accuracy
• heading hierarchy depth and consistency
• glossary and acronym list quality
• how the digital version handles structure.

Reports that score well share a recognisable quality: the document seems to know where it's going. Reports that score poorly leave you flipping back and forth, unsure whether you've already read this bit. (Sign 3 in Your annual report is compliant. But is it effective? covers the navigation failures we see most often.)

A self-assessment you can run

Four short tests on your most recent annual report. They take under fifteen minutes between them.

Four tests that surface what readers actually experience.

If a reader can't find what they need in two minutes, the architecture isn't doing its job. The reader gives up. The work that went into the content goes unread — and the research on what investors actually want from your annual report shows how quickly that erodes engagement.

Why structure pays off more than design

A common assumption is that better design will fix navigation problems. It won't. Design can polish a well-architected report. It can't rescue a poorly architected one.

Information architecture is structural, not decorative. Get it right and modest design works. Get it wrong and even the best design layer can only mask the issue.

This matters more every year as reports stretch across more formats. The PDF, the accessible Word version, the HTML on the Transparency Portal, the press release — they all draw on the same structural skeleton. A weak skeleton means weak versions, no matter how polished the PDF looks.

What the Review covers — and what it doesn't

A Report Review assesses the architecture. It doesn't redesign it.

You receive a graded score for information architecture, specific commentary on where the structure works and where it breaks, and prioritised recommendations the production team can act on.

Our annual report writing and production service handles implementation separately. Structural changes need planning at the start of a cycle — which is why an early-cycle Review delivers the most leverage. The broader case for an independent review sits in Why we created Report Review.