Why post-consent deserves the same rigour as consenting itself

That was the starting point for a recent roundtable co-hosted by Xodus and Burges Salmon, bringing together environmental and legal specialists to examine what post-consent actually requires. The conclusion was consistent across the room: this is a complex, multidisciplinary phase that spans environmental, engineering, contractual, commercial, and legal issues, and it takes longer and requires more resources than most developers plan for.

Crucially, it does not simply sit neatly in pre-construction. Rather, it runs through pre-construction, construction and operations simultaneously, with procurement, design refinement, compliance, and stakeholder engagement all proceeding in parallel.

The process of discharging conditions

At the centre of post-consent sits the discharge of conditions and commitments – agreeing management plans, protocols, method statements, and monitoring plans with regulators and statutory advisors and the project engineering teams. Done well, this blends smoothly into and runs alongside overall project execution. Done badly, it becomes the reason construction cannot start on time, creating a significant project constraint with major commercial implications.

The risks involved include the lengthy consultation processes, delays caused by late or incomplete discharge submissions, and conditions that were never fully aligned with the engineering design or construction programme.

The roundtable discussion on how to solve this concluded that projects should look to phase discharge with the construction programme itself, tied to stages such as landfall, transmission, and generation. This allows documentation to be agreed with regulators early rather than submitting everything at once and overloading those who have to comment or approve it.

Design has to be flexible, but not indefinitely

A related tension runs underneath all of this in that projects are consented against early-stage designs that have to cover a range of potential options, and engineering evolves well past the design freeze for the consent application. A rigid approach to consent conditions can mean that every change becomes a costly, time-consuming amendment, whereas too much flexibility can erode the confidence in original environmental assessments and the regulators’ understanding of the final project.

The practical answer, agreed upon collectively, is to stress-test the design envelope early and build contingency in from the outset. Audit against it regularly so misalignments materialise before they become critical. While not every change needs a formal consent variation, every change needs to be justified, evidenced and traceable – a different discipline to simply managing change as it arises.

Some of this pressure sits upstream of the developer. Projects are currently assessed in detail before their design has matured, which pushes towards conservative assumptions and can add directly to the post-consent burden. A two-stage consenting approach, similar to the onshore model that includes in-principle approval before gaining detailed consent, was raised at the roundtable as one way to ease that.

What most developers underestimate: project memory

One of the most striking findings from the roundtable was not about process at all, but about memory.

A significant amount of the thinking behind a project happens years before construction starts. By the time post-consent work is underway, the people who made those decisions have often moved on. Commitments get reinterpreted, sometimes several times, as teams change.

This is why effective decision logs and detailed project history are crucial. Not as administrative record-keeping, but as the infrastructure that lets a team answer, years later, why a particular commitment has been implemented in a particular way, as well as being an important contribution to project risk identification and management.

The central recommendation on this topic was clear: maintain clear audit trails and centralised records from project inception and run post-consent 'reset' sessions to realign teams. It's also why the industry is starting to move this work off spreadsheets and into dedicated digital systems – the core thinking behind Xodus' own XAMIN Permits & Consents software platform.

How these recommendations add up

None of this is overly complicated, but it is important. Post-consent needs to be resourced and planned for its actual scale, and before construction pressure has built. Condition discharge and risk management strategies need to be fully integrated with the project programme, and decision logs treated as crucial infrastructure with the support of the right digital tools, rather than an admin spreadsheet after-thought.

If developers get this right, they are likely to reach construction on schedule. Those who wait until pressure builds may encounter unacceptable project risks that are very difficult, if not impossible, to manage.

Written by David Bloxsom, Environmental Specialist, Xodus Group.

For more news and technical articles from the global renewable industry, read the latest issue of Energy Global magazine.

Energy Global’s Summer 2026 issue

The Summer issue of 2026 is out now! The new issue starts with a regional report on Latin America and the Caribbean, considering the benefits and challenges of renewable energy development in the region. The issue also covers topics such as lubricants, digitalisation, the importance of ports, battery storage technology, and more! With contributors from industry leaders including ABB, WindEurope, Sungrow, among others, this is an issue not to miss.

Read the article online at: https://www.energyglobal.com/special-reports/24082026/why-post-consent-deserves-the-same-rigour-as-consenting-itself/