PERSPECTIVES / Organizational & Corporate Communications
Annual report design requires text and data to work together
Editors, data teams and designers should work from the same content structure.
Research Notes
Editorial, data and design should share one content structure. This article explores the relationship between content, design and use, offering a sequence of judgments to guide project discussions.
Establish version sources first
Chapters, data, charts and images need clear owners and update dates. With clear version sources, later revisions know exactly which pages to sync.
Develop text and layout together
Paragraph length, chart explanations and chapter emphasis all shape the layout. Coordinating early on sample spreads of key chapters surfaces conflicts between content and design sooner.
Make the deliverable support next year
File structures, chart formats and terminology should be easy to update. Preserving content mappings and editorial notes lets the next edition build on existing work.
Bringing it into project discussions
- Accuracy: Do facts, names, data, and charts have clear sources?
- Clarity: Can different readers find information relevant to them?
- Sustainability: Can design and content rules carry forward in the next update?
Bring these questions to real materials and use cases, recording the current version, the rationale for changes and feedback from use. When every adjustment has a clear basis, the team can keep applying these judgments in future work.
Reader's Note
This article presents design methods and project observations written by Qingmei Future for its website. The project links below are provided for reference to existing work and application materials. The methods suggested here do not imply that all listed projects followed the same process, nor do they constitute project outcome data.
CONTINUE READING Further Reading
Find your next step, starting with the question at hand.
When you get in touch about a project, it helps to share your business context, existing materials, primary use scenarios and the problems you want to solve. We'll use this to discuss scope and how we might work together.
Communicate project requirements ↗

















