The Weakest Link in Sustainability Reporting

Your data is ready. Now the three-week email exchange begins.

There is a moment in every reporting cycle that nobody plans for and everybody recognises. The data is collected. The figures are checked. The narrative is written and approved. And then the whole thing has to become a document that someone outside the team can actually read.

That handover is the weakest link in sustainability reporting, and it is almost never discussed, because it is not a compliance problem. It is a production problem. It just happens to consume the weeks immediately before the deadline, when there is no slack left.

How the handover usually goes

The pattern is remarkably consistent across organisations of very different sizes:

• Figures are exported from the reporting system or the spreadsheet into a Word document.
• The document goes to a designer, internally or at an agency, who rebuilds it in a layout tool.
• A PDF comes back for review, and the review finds three numbers that have since been restated.
• Corrections are sent by email, applied by hand, and a new PDF is returned.
• Somebody notices the chart on page 12 still shows the old figure, because charts were rebuilt manually.
• This repeats until the deadline, not until the document is right.

Each individual step is reasonable. The aggregate is a process in which the final, published, externally scrutinised artefact is assembled by copying numbers between applications under time pressure.

Why this is a data integrity problem, not a design problem

It is tempting to file this under aesthetics. It is not. The moment a figure is retyped into a layout tool, it leaves the system that knows its source, its method and its approval history. From then on it is just text on a page.

That matters in two ways. First, restatements are common late in the cycle, and every restatement has to be propagated by hand into a document that has no link back to the underlying data. Second, the published figure and the audited figure can quietly drift apart, and the only control preventing that is somebody proofreading carefully at eleven at night.

Organisations that have been through an assurance process usually have a story about a number that was correct in the system and wrong in the PDF.

The cost nobody puts in the budget

The direct cost of layout is visible: a design agency invoice, often somewhere in the thousands for a sustainability report. That number gets budgeted and approved.

The indirect cost rarely does. It is the senior sustainability lead spending three weeks in a review loop, the finance controller re-checking figures that were already signed off, the communications team chasing versions, and the compressed schedule that pushes everything else aside. For most teams, that is the larger number by some distance, and it repeats every year.

The question worth asking before the next cycle

Not how do we make the report look better, but how many times does a figure get copied by a human between the source system and the published PDF.

If the answer is more than zero, that is where the review loops, the version confusion and the late-night proofreading come from. Every manual transfer is a place where the published report can stop agreeing with the data behind it.

It is a solvable problem, and solving it changes the shape of the reporting calendar more than any amount of extra time spent on data collection. We will have more to say about that shortly.