Design
What makes a report easy to read
Layout, hierarchy and pacing choices that help readers get through a long document.
Start with the reader. Before choosing a layout, decide who will open the report and what they need from it. A board member scanning for decisions reads differently from a funder checking outcomes. Write that reader down in one sentence and keep it next to the design file. Every later choice, from page count to chart type, becomes easier to judge.
Build a clear hierarchy. Readers should be able to tell a chapter title from a subhead, and a subhead from a caption, without thinking about it. Use a small set of text styles and apply them the same way on every page. When a new style appears, the reader stops and asks what changed, and that pause costs attention.
Give the text room. Narrow columns, generous line spacing and clear margins make long passages easier on the eye. Dense pages often come from trying to save paper or avoid cutting content. If a page feels crowded, the fix is usually to edit the words, not to shrink the type until everything fits.
Let each chart carry one message. A chart should answer a single question, and its title should state that answer. Remove gridlines, legends and decoration that do not help the reader compare values. If a chart needs a full paragraph of explanation before it makes sense, it probably needs to be split or simplified.
Pace the document. A long report needs places to rest: a pull quote, a full-page image, a summary box, a short chapter. Vary the density from spread to spread so readers are not facing the same wall of text for forty pages. Plan this rhythm in the page plan, before the final layout begins.
Make things easy to find. A contents page, running headers and consistent page numbers let readers jump straight to the section they need. Most people do not read a report from cover to cover. They look for one chapter or one figure, so design for that kind of visit as well as for the full read.
Check contrast and size. Body text should be comfortable on a printed page and on a phone screen. Light grey text on a white background looks refined in a mockup and tiring in real use. Test your pages on the devices and the paper your readers will actually use, not only on the designer's monitor.
Review with fresh eyes. Print a few spreads, or open the PDF on a phone, and ask someone outside the project to find a specific figure. How long it takes them tells you more than any checklist can. Fix whatever slows them down, then run the same test again before you send the files to print.