The gap analysis came back the way it always does.
A long list of datapoints nobody owns, held by people who have never been asked for them, in systems that were built for something else.
So the calendar fills. Datapoint reviews. A controls conversation with finance. A definition that moved, so the baseline gets rebuilt again.
When disclosure becomes the work, progress becomes paperwork.
Where most companies actually are
There is a data process forming. There is a system selection, or a spreadsheet everyone agrees is temporary and which will not be. There is an assurance conversation with audit and a responsibility chart with more names on it than the last one.
This is real work and it is going fine. The Corporate Sustainability Reporting Directive requires large companies operating in the EU to disclose on a double materiality basis, and getting ready for that is a genuine project. The timelines and thresholds have already moved once, with the 2026 Omnibus amendments raising the size cutoffs and pushing the next reporting wave to fiscal 2027 data, so check where your company stands against the European Commission's corporate sustainability reporting page rather than a summary that was true last quarter.
It is also the part your team already knows how to do. You built your career on targets, reporting and plans, and this is that skill set at full stretch. The next part is not.
How disclosure slows a company down
Watch the mechanism, because it is not laziness and it is not bad faith. The disclosure deadline is fixed and public. The implementation work has no deadline at all. So the fixed date wins every planning conversation, and keeps winning.
Collection arrives without context, so suppliers and frontline staff get asked for numbers they do not recognize, for reasons that never connect to their Tuesday. Tools come first, because a platform is easier to buy than a relationship. Baselines move, because an acquisition or a better method resets the starting line and a fresh cycle begins. Audit anxiety pushes teams to optimize for defensibility rather than for movement. And budget tilts toward software and accountants rather than the people who could change a process.
At the end of it there is a document. It is accurate, it is assured, and it describes a company that has not changed.
Every hour spent reconciling a definition is an hour not spent getting a supplier to change a process or a plant to cut waste. That trade never appears on a project plan, which is why it keeps getting made.
What double materiality quietly implies
Financial materiality asks how sustainability issues affect the company. Impact materiality asks how the company affects people and the environment.
Read the second one slowly. It is written as a disclosure requirement, but what it describes is your operations. You cannot improve an impact number by describing it more precisely. Someone has to buy differently, run the line differently, or specify the product differently.
Which means CSRD, on the impact side, hands you a public account of the distance between what your company says and what your company does. The disclosure is not the deliverable. The disclosure is the pressure.
The question nobody asks about the measures
There is a scientific question hiding under all of this, and it rarely gets asked because it is uncomfortable.
Are your measures sensitive to change?
When something real shifts on the ground, would your metrics detect it? Do they tell you what to do next, or only what happened last year?
If the honest answer is not really, more precision will not help you. Precision about last year is still about last year.
What you are not reporting
Here is the other half of the same problem.
Your quarterly update says Scope 1 and 2 on track, Scope 3 behind target, supplier engagement slower than expected, employee participation low. The message anyone reads off that page is: we are failing.
What the page leaves out is everything that moved. The three suppliers who did engage. The site that found a way to cut waste and told nobody. The designer who chose a different material without being asked.
None of it gets counted, because it is not at scale and it does not close the gap. But those moments are the only proof you have that change is possible in your organization, with your constraints and your people.
Add a section to the next report called Progress This Quarter. Not progress toward target. Progress that happened, with names on it and a line about how.
Then ask the question that turns it into a method: what made that possible? A champion with the right relationships? A process with less friction than the others? A team with enough slack to try something? Those are conditions, and conditions can be reproduced elsewhere.
Reporting only what is missing burns your team out, drains leadership confidence, and leaves progress that could have spread sitting in one building.
How to run the implementation half
Put ownership in the function, not in the sustainability team. One representative per business unit who owns the process, with an outcome target rather than a task list. A datapoint that lives with your team is a data request forever. A datapoint that lives with the plant manager becomes something somebody tries to move.
Run minimum viable reporting. Meet the requirement with the smallest compliant process you can defend, and put the capacity you save into implementation. This is a choice, and right now most teams are making it by accident in the other direction.
Consolidate the asks so each one carries more than one benefit. Your supplier is receiving requests from your team, procurement, quality and three other customers. Line them up on one desk and look at the pile. Then send one ask that answers a cost or risk question they already have.
Count gateway behaviors weekly, and measure outcomes after momentum. Contract clauses updated. Supplier sessions held. Spec reviews completed. These are the practices that produce the outcome, they are visible now, and they tell you whether anything is happening between reporting cycles. Once the practice is reliable, invest in the higher-fidelity outcome measures. In that order you will know what is worth measuring, and you will have something worth disclosing.
Test the yes before you rely on it. When someone commits to a step, ask how confident they are it will happen by next week, on a scale of one to ten. Anything under a seven means something is going to get in the way. Encouragement will not move that number. A smaller step, or a real conversation about what is blocking it, will.
Let the person one step ahead do the talking. A peer who made the change last quarter is more persuasive than the person holding the framework. Your job is to get them in the same room and then be quiet.
What the report is for
Disclosure describes the company you are.
Implementation decides the company you will describe next year.
If the second one is what you are being held to now, and nobody trained you for it, that is worth naming out loud rather than absorbing quietly. It is the part of this job the Real Change Partner was built for.
Where is disclosure currently consuming time you need for implementation? And what progress happened in your organization this quarter that you did not count?