A climate and nature transition should feel like a coordinated programme of organisational change - a company moving deliberately from one state to another, the way it does for a merger or a move into a new market. Far more often, it feels like the opposite: a long run of small, disconnected efforts - a policy updated here, a supplier switched there, another data request, another report - each sensible on its own, none of them ever quite cohering into the change of state the target quietly assumed.
The distance between those two experiences is the distance between a plan and a list. And it is the distance the standards have, at last, begun to name.
When the SBTi rebuilt its Corporate Net-Zero Standard, it moved the centre of gravity from the target to the plan behind it. The Transition Plan Taskforce wrote what became the reference framework for what such a plan should contain, and the ISSB folded that work into the disclosure standards regulators now build on. The detail varies by jurisdiction, and in most places you are not yet compelled to produce a plan - the UK asks listed companies to disclose one if they have it and explain its absence if they do not, the EU much the same. But the direction is settled, and so, revealingly, is the definition. Across the frameworks it reads almost identically: a target names where you intend to end up; a transition plan sets out the route - the actions, the investment, the governance, and the dependencies that get you there.
By that definition, much of what gets filed as a transition plan is not yet a plan.
It is a narrative. A restatement of the target, a page on ambition, a list of initiatives underway, a governance diagram, and a chart that steps neatly down to net zero. Every part of it is real. But a list of good initiatives and a downward-sloping line is not a route, any more than a list of cities is an itinerary. The standards asked for actions, investment, governance and dependencies, arranged into a way of getting from here to there. What most companies disclose is the destination, described more thoroughly.
I have argued before that a climate transition is the same order of undertaking as a merger, a market entry or a major cost programme - that it deserves the same resourcing and the same seriousness. Here I want to take that comparison at its word and ask what those programmes actually do, as a matter of method, that a filed transition plan usually does not. Three things stand out.
A plan is an ordering, not a list
The first is sequence.
No competent transformation tries to do everything at once. It works out the order, and the order matters more than the list, because the moves depend on one another. Some are no-regrets and close to self-funding, and they come first precisely because they release the capacity to do the rest: the efficiency work, the consumption you can simply stop, the switches a company controls outright. Some are dependent, and cannot be brought forward however urgent they look - you cannot electrify a fleet before the charging and the grid exist to carry it, you cannot redesign a product around a low-carbon material that is not yet made at scale, you cannot decarbonise a process whose alternative is still in a pilot plant. And some carry option value that a plan should protect rather than spend: sinking capital into a long-lived asset a foreseeable rule will strand is a way of losing twice.
The standards even name this. They ask for the dependencies a plan relies on. But naming dependencies in a disclosure and sequencing around them in a programme are different acts. A cost-transformation office lives or dies on the second: what has to be true before this move can be made, what this move makes possible next, and what it would cost to take them in the wrong order. That is the intelligence a real plan is built from, and it is the part a downward-sloping line quietly assumes away. A plan that names everything and sequences nothing is a wish with a chart attached.
A plan builds value on the way, not only at the end
The second is value.
The common failure is to treat a transition as pure cost - a long bill paid now against a benefit that arrives, if it arrives, at the far end. A transition financed that way is fragile. It competes with every other call on capital in every budget round between now and the destination, and the first difficult year is the year it is cut. A transformation that survives is one that funds itself as it goes: each phase releasing enough value to pay for the next, each move building a capability or an asset the following move needs.
That is not wishful either. The early, efficient wave of decarbonisation genuinely lowers cost, and the discipline is to keep that surplus inside the transition rather than letting it leak back into the general budget - because it is exactly what pays for the expensive last mile, the part no efficiency saving will cover. A transition plan should therefore show where value is created at each stage, not only at the destination. Sequenced well, it can be close to self-funding for a long way. Sequenced as a single leap toward a distant endpoint, it becomes a cost centre with a deadline, and cost centres with deadlines are what organisations quietly abandon.
A plan belongs to the whole company
The third is ownership, and here the standards are blunter than they are usually given credit for: a credible transition plan cannot be owned by the sustainability function alone.
It follows directly from the first two points. Sequencing is a decision about capital and operations, so finance and the COO have to own their parts of it. The dependencies live in the supply base, so procurement owns those. The product moves belong to R&D and design. The demand side - whether the market will pay for the changed product, and how it is sold - belongs to commercial and marketing. The sustainability function cannot hold any of these on its own, and a plan that assumes it can is the narrative kind, because only a narrative can be written by one department. A real one is negotiated across the building, the way an integration plan or a cost programme is, because every function is being asked to change something it owns.
This is the Chief Sustainability Officer's actual job in the transition era, and it is not authorship. It is to be the programme owner and the partner to the CEO, the CFO and the COO who holds the whole sequence together - the person who can say what has to happen first, what it unlocks, and what it is worth. That is a different role from writing the report, and it needs a different mandate.
You cannot plan what you cannot see
Underneath all three sits the same requirement, and it is the one the filed plans most often lack.
Sequencing needs to know the dependencies, and where the sector itself is heading, so that you move with the market rather than ahead of a supply chain that is not ready or behind a rule that has already changed. Value-modelling needs a picture of the future state clear enough to cost. Whole-company ownership needs a shared view everyone can act from, or the functions each plan against a different assumption. None of that comes off a reporting line. A reported footprint tells you where you have been; a plan is a claim about where you are going and how, and it needs intelligence built for that - the sector pathway resolved down to what a specific site can actually change and when, the dependencies made visible, the future state modelled, and provenance solid enough to stand behind a capital decision.
That is the difference between a plan and a wish. A wish is a destination and a downward line. A plan is a route you can see well enough to sequence, fund and share - and you cannot plan what you cannot see.
Running it like the transition it is
So the honest test of a transition plan is not whether it exists, or whether it discloses the five things the framework asks for. It is whether it is an ordering rather than a list, whether it builds value on the way rather than only at the end, whether it is owned across the company rather than inside one function, and whether it rests on intelligence that can actually see the route. On that test, a great many filed plans are not yet plans.
The reassuring part is the one the flagship of this series began with: companies already know how to do this. They run mergers, integrations, market entries and cost transformations this way every year - sequenced, self-funding where they can manage it, owned across the whole organisation, and modelled before they commit. The transition era is simply the moment the climate and nature transition is run with the same method, rather than described with a chart.
That is the work we built Reverberate to serve: modelling the route rather than restating the destination - where a sector is heading, what a company can change from where it stands, in what order, at what cost and to what gain - so that a transition plan can be what the word always promised. Not a document about the future. A way of getting there.
Sources
The Transition Plan Taskforce (TPT) Explained - Seedling. The TPT Disclosure Framework as the reference standard, the ISSB/IFRS S2 definition that a target states the destination while a transition plan explains the route (actions, investment, governance, dependencies), and the UK's disclose-or-explain approach.
The new Corporate Net-Zero Standard Version 2.0 - Science Based Targets initiative. V2.0, published 11 June 2026, moving the centre of gravity from the target to the transition plan behind it; validations open February 2027.
SBTi Corporate Net-Zero Standard v2 - South Pole. On the reinforced role of transition plans under SBTi V2 and the point that a credible climate transition plan cannot be owned solely by the sustainability function.