ESG Report Data Visualisation: Making Charts Clear and Consistent

A useful ESG chart helps readers understand an approved finding and see the context behind it. Begin with the metric, the comparison and the message. Then choose a visual form that makes those relationships clear.

The report’s data owners should confirm definitions, reporting coverage, calculations and any required disclosures. The design team can turn that approved material into consistent charts, captions and page layouts. Keep those responsibilities connected throughout production, particularly when the report has several languages and formats.

Build a brief for each metric

Give every proposed chart a short record before layout begins:

• Metric name and approved definition
• Unit and reporting period
• Entities or activities covered
• Source file and responsible data owner
• Whether values are actual results, estimates or targets
• Any limitations or changes that affect comparison

Keep the source worksheet and the approved display values together. If the report rounds numbers for publication, record that decision so the chart, narrative and summary page use the same figures.

Ask the owner to confirm whether earlier periods have been revised. A corrected historical value needs to reach every place it appears, including translated charts and web versions.

Choose the chart around a question

Different questions call for different presentations.

To compare categories, a bar chart may give readers a straightforward view. To follow a measure through time, a line chart may be useful. When the reader needs exact values, a table may be the most practical choice.

The Office for National Statistics chart-selection guidance starts with the data and the relationships the visualisation needs to communicate.

Write the intended takeaway in one sentence. Then ask whether the proposed chart actually supports it. If the sentence needs several qualifications, separate the views or give the reader a short explanation.

A page of small charts can work better than one crowded graphic combining several measures. Decide how the page will be read before choosing a more elaborate visual treatment.

Keep the comparison honest

Check that the periods, units and coverage support the comparison being shown.

For example, a total and a measure per employee describe different things. A designer should ask the data owner to explain the intended denominator rather than selecting whichever figure creates a more attractive trend.

If operations included in the reporting coverage have changed, agree how that affects the visual comparison and its notes. A new label alone may not explain why two periods are different.

Review the scale as well as the values. The size of a graphic should reflect the data accurately. Avoid decorative perspective or shapes that make a small difference appear much larger.

Use a target marker only when the target, its period and its relationship to the actual values are approved.

Give every chart enough context

A reader should be able to identify what is measured, where or to whom it applies, and the time period shown.

Keep the chart title, units and source close to the figure. Add a concise note when a definition or coverage change matters to interpretation.

The UK Government Analysis Function’s chart-design guidance recommends clear titles, labels and specific source information. Its approach is useful when planning a report’s chart system.

Separate the finding from the data description. A headline can explain the approved observation, while a subtitle identifies the measure and period. Check that the headline remains accurate after any data revision.

A prominent percentage without its basis can leave readers guessing. Ask what the percentage represents and whether that information remains visible in the final layout.

Create a consistent bilingual chart system

Agree a style sheet for metric names, units, abbreviations, dates and number formatting. Use the same conventions throughout the report.

Review terminology with both the data owner and the language reviewer. A translated label must preserve the metric’s meaning, including distinctions such as total, rate and intensity.

Allow enough space for the longer label in each language. Test the complete chart rather than approving isolated text in a spreadsheet.

Also decide how languages will appear: separate editions, a bilingual page or language-specific web views. A dense chart may need a different layout for each edition while retaining the same data and visual logic.

Make the information available beyond the image

Readers may need a text explanation, exact values or both. Include the meaningful information in an appropriate accessible form.

W3C’s complex-image tutorial explains how charts and other information-rich images can be accompanied by short identification and a more detailed text alternative.

For a web table, use structural headers and relationships that software can understand. W3C’s tables tutorial describes the relevant markup.

Review colour use, labels and contrast with the accessibility team. A reader should have another way to identify a series besides its colour. Test the agreed digital experience with the chart, its explanation and any supporting table together.

Keep data approval separate from design approval

Use a review sequence that makes both responsibilities visible:

1. The data owner checks values, calculations, definitions and source notes
2. The design team prepares a representative chart and page treatment
3. Reviewers check the chart’s message, labels and reading order
4. Language reviewers check each complete edition
5. The team compares final exports with the approved dataset

Tie corrections to a named metric and file version. “Change the green chart” becomes unclear when colours or page order change.

If a revised value affects a summary, caption or narrative sentence, mark those items for review as well. Keep a record of what was checked before the file goes to publication.

Test the final reading formats

A chart approved on a large monitor may be difficult to read on a phone or at its printed size. Review it in the actual PDF, printed proof or web layout.

Check line breaks, small labels, source notes and the relationship between the chart and its explanation. Confirm that interactive information also has an appropriate accessible route.

Miracle’s published Hysan annual-report website case provides a visual reference for report presentation. For an ESG brief, bring the approved dataset and the reporting team’s requirements so the chart design can be reviewed against the information it needs to communicate.

What to include in your ESG design brief

Supply the approved data, metric definitions, narrative draft, required languages and intended formats. Identify the people responsible for data accuracy, language review and final publication approval.

Include a representative set of charts so the team can test the design system before extending it across the report. Discuss how the content will also appear on a website through Miracle’s website design and development services.

Send your report brief with the material available, the publication date and the review stages your team needs.