Reports and Annual Reports

What it is

A report collects information so a reader can understand what happened, why it matters, and what remains uncertain. An annual report may combine narrative, performance figures, governance information, and future plans. The designer’s task is not to make all pages equally attractive. It is to help different readers find the material they need and judge it accurately.

Some reports have formal disclosure or sector-specific requirements. Those requirements depend on the organisation and jurisdiction and should be determined by the responsible legal, finance, or reporting team. Design can make required information clearer; it cannot decide what may be omitted. The same principle applies to sustainability or impact claims: the visual story must remain faithful to the evidence.

Start with the reader and the content inventory

Identify the audiences and their tasks. An investor may compare year-on-year figures; an employee may look for a strategy update; a community member may seek evidence behind an impact claim. Map the likely entry points rather than assuming everyone reads from page one. Collect draft text, tables, data sources, image rights, mandatory wording, and approval owners before building a visual system.

Create a content model: sections, recurring page types, chart types, notes, references, and appendices. Mark what is stable and what is likely to change late. Annual reporting has a production rhythm; a system that only works with final copy is fragile. Plan for variable table lengths, revised figures, translations, and late disclosures.

Build a trustworthy hierarchy

Make the argument navigable

Use descriptive headings, short summaries, clear section openings, and a contents structure that works in both print and digital editions. The reader should be able to distinguish a claim from its supporting data and a forecast from a historical result. Avoid a sequence of vague inspirational chapter titles that hides the actual subject matter.

The SEC’s plain-English guidance is directed at disclosure documents, but its broader design lesson is useful: clarity of language, hierarchy, and page design work together. A dramatic full-bleed image can be appropriate, yet it should not bury the definition or caveat a reader needs to interpret the adjacent number.

Give data honest visual treatment

Choose charts for the comparison the reader needs to make. Keep units, periods, baselines, definitions, and source notes near the figures. Do not use colour or scale to turn a small change into a dramatic one. When a metric changes definition or its data is incomplete, explain that visibly. Data visualisation covers these choices in more detail.

Tables remain valuable when exact values matter. Design them for scanning and comparison, with clear row and column labels and enough contrast. If a visual summary simplifies a complex table, keep a clear route to the full information. The report’s credibility depends on both layers agreeing.

Design a system for long-form reading

Set grids, type roles, colour use, folios, captions, pull quotes, tables, and chart conventions before polishing hero spreads. Check long paragraphs, footnotes, and dense appendices. A good long-form typography system protects reading comfort over many pages, while a consistent editorial system can keep recurring content recognisable.

For digital delivery, plan navigation, searchability, bookmarks, reading order, selectable text, and accessible descriptions for meaningful graphics. A PDF that looks perfect on a large monitor may be difficult to use on a phone. Consider whether a responsive web report or structured HTML companion better serves some readers. Test the real export, not just the layout file.

Control production and review

Agree who owns every number, chart, caption, and claim. Use a versioned data source so revised figures can be traced to their origin. Review proofs at realistic print size and digital viewport. Check cross-references, page numbers, links, table alignment, image permissions, colour conversion, and whether a late text edit has moved a note away from the figure it qualifies.

Ask a reader outside the production team to locate three pieces of information and explain one chart. If they cannot tell what changed or why it matters, the issue may be structure rather than styling. Keep the editable files and source data together for corrections and future editions.

Practical checks

• Can readers find the sections and figures relevant to their task quickly?
• Are claims, estimates, measures, and limitations clearly distinguished?
• Do charts and tables preserve units, dates, definitions, and sources?
• Does the digital edition have usable structure and readable mobile access?
• Can every final figure and claim be traced to an approved owner or source?

Common mistake

Treating the report as a showcase of impressive spreads. Visual ambition is valuable when it helps readers understand evidence; it becomes a liability when it makes a dense document harder to verify or navigate.