What happens to your ESG reporting when the person who does it leaves?

What happens to your ESG reporting when the person who does it leaves?

Every sustainability function has one person who knows where the numbers come from. They built the spreadsheet. They know which meter reads high, which supplier never replies, why the baseline moved last year.

Then they resign.

Over the following months the organisation discovers how much of its reporting lived inside one person's head. This is the risk nobody puts on a register, and it does more damage to reporting quality than any framework change.

Why does ESG reporting break when someone leaves?

It breaks because the data survives. The reasoning does not. The files get handed over intact, and the judgement that produced them walks out of the building. A year later there are numbers nobody can defend and a boundary nobody can explain.

Sustainability roles turn over faster than the reporting cycles they serve. Where a role changes every 12 to 24 months with no system underneath it, each new person rebuilds the method from whatever files they inherit, makes different calls, and the trend line becomes fiction.

The pattern is familiar in large multi-site organisations: one carbon manager, years in post, excellent with a spreadsheet, holding the only complete picture of the estate's energy data. Nobody else can see it. The data lives in their files and their memory, and nobody has ever needed it to live anywhere else. This is the real cost of running a footprint out of spreadsheets, and it has little to do with the formulas.

What actually gets lost?

Three things, and only one of them survives a handover. Call it the Three Layers of Sustainability Memory.

• The numbers. Consumption figures, invoices, meter reads, survey responses. These survive. They are in a file, and files get transferred.

• The method. Which emission factor, which boundary, which estimation approach, which cut-off. This partially survives, usually in a methodology note written once and never updated.

• The reasoning. Why that factor over the alternative. Why the base year was restated. This never survives, because it was never written down anywhere.

Layer three is the one that matters. Everyone assumes the risk is losing the data. The data is usually fine. What kills year two is that nobody can reconstruct why year one was built the way it was, and under assurance, "the previous person did it like this" is not an answer.

There is a hard consequence attached. The GHG Protocol requires base year emissions to be recalculated when the calculation methodology changes (Source: GHG Protocol Corporate Standard, 2004). A successor who picks a different emission factor, because nobody recorded why the original was chosen, can trigger a restatement of your baseline. That is how lost reasoning becomes a lost trend line.

Why doesn't a handover document fix it?

Because it gets written at the worst possible moment. A handover document is drafted during a notice period, by someone already mentally gone, describing decisions they made eleven months earlier and cannot now reconstruct. It records what was done. It skips why, because the why felt obvious at the time.

Then nobody reads it until they hit a problem, at which point they do not know what to search for.

The standards are ahead of most companies here. ISO 14064-1 requires organisations to retain documentation supporting the design and development of the GHG inventory so it can be verified (Source: ISO 14064-1, 2018). That covers how the inventory was built, the layer that goes missing. Most teams read it as "keep the evidence" and file the invoices.

A good methodology note beats nothing. But documentation as an exit task guarantees the thinnest version of it. The reasoning has to be captured while the work happens, or it is gone.

This is where an agent changes the shape of the problem. When Ella runs a carbon calculation, the reason gets attached at the point the decision is made. Ella will tell you "I used a spend-based factor for that site because no invoice data came back, and I've flagged it for replacement." That sentence is the handover. It exists whether or not anyone remembers to write it.

How do you hand over ESG reporting properly?

1. Freeze the boundary in writing. Every entity, site, lease and joint venture, with the reason each is in or out. Boundary choices under the GHG Protocol are the first thing an auditor pulls (Source: GHG Protocol Corporate Standard, 2004).

2. Attach a reason to every emission factor. The factor is easy to find again. The reason it was chosen over a location-based or supplier-specific alternative is not.

3. List the exclusions and the justification. The supplier who never replied. The category estimated on spend. The Scope 3 Standard already expects excluded categories to carry a written rationale and an estimate of their magnitude (Source: GHG Protocol Scope 3 Standard, 2011).

4. Name the data owners as humans. Not "Facilities". A person, a building, a data type, a cadence.

5. Record the disputes. Every reporting year has two or three arguments about what counts. They are the most valuable and least recorded thing in the process.

6. Run a cold-start test. Hand the pack to someone who has never touched it and ask them to reproduce last year's number. Whatever they cannot reproduce is your real gap, and you want to find it while the person who knows is still employed.

When does this work, and when doesn't it?

It works when the person is still in post, the boundary is stable, and you report against one or two frameworks. A disciplined pack written across a normal reporting year will carry a competent successor through.

It works badly once the person has gone, when the footprint leans on Scope 3 estimates, or when a restructure forces a base year recalculation. Then the pack is archaeology, and it will be wrong in ways nobody detects for a year.

It also breaks down at volume. Carbon plus B Corp plus an EcoVadis scorecard plus whatever your largest customer sends over cannot be held by hand, because the same evidence gets described four ways for four audiences and the versions drift apart. That is before counting the hours each cycle takes.

That is the case for holding the reasoning in a system instead of a person. Across 150+ companies, the ones that survive turnover keep the evidence base and its justifications somewhere the organisation owns, so a leaver takes their expertise and leaves the reporting standing.

See how Ella keeps the reasoning attached to your ESG data as the work happens.

Reference Links

https://ghgprotocol.org/corporate-standard https://ghgprotocol.org/sites/default/files/2022-12/Base%20Year%20Adjustments.pdf https://ghgprotocol.org/corporate-value-chain-scope-3-standard https://www.iso.org/standard/66453.html