In South Africa’s energy market, the most dangerous phase of a project isn’t the negotiation. It’s the waiting. Waiting for environmental authorisation. Waiting for municipal council approval. Waiting for NERSA. Waiting for the network operator to confirm a connection date. Waiting for a government counterparty to respond to correspondence sent three months ago.
Projects that were commercially sound, legally structured, and financially ready have stalled – sometimes fatally – because the consent process was treated as a downstream problem. Something to manage when it arrived. Something the lawyers would handle.
The reality is that regulatory consent in South Africa is not a legal problem. It’s a project management problem with legal inputs. And the teams that move fastest treat it that way from day one.
Why consent becomes a bottleneck
Regulatory approvals stall for predictable reasons, and most of them have nothing to do with the merits of the project.
Applications are submitted incomplete. The regulator requests further information. The applicant responds. The clock resets. Months disappear.
Dependencies aren’t mapped. A building plan approval can’t be submitted until an environmental authorisation is granted. The environmental authorisation requires a specialist report that takes twelve weeks. Nobody planned for this sequence at the outset, so the delay compounds.
No single person owns the process. The environmental consultant tracks the EIA. The legal team tracks the grid application. The project manager tracks the municipal approvals. Nobody has a consolidated view, and when something slips, it’s discovered late.
The regulator asks a question that could have been anticipated. The answer requires input from three parties who are now on different timelines. The response goes in late. The clock resets again.
None of this is unusual. All of it is manageable if the structure is right.
The Consent Management Framework
This is not a legal framework. It’s an operational one – with legal inputs at the right points.
Build the master consent map before any application is submitted
Before the first document goes to any regulator, produce a complete list of every approval the project requires: environmental, land use, municipal, grid, sector-specific, and any approvals required by financiers or off-takers. For each approval, record the statutory decision-maker, the prescribed timeframe, the information required, and the consequence of delay.
This map will have gaps. Fill them early, not mid-process.
Sequence the applications deliberately
Some approvals cannot begin until others are complete. Some can run in parallel. Some have long lead times that bear no relationship to their complexity. Map the dependencies and build the application sequence around them, not around administrative convenience.
The environmental authorisation is almost always on the critical path. Start it first, regardless of what else is happening.
Assign a named owner to every approval
Every item on the consent map has a single owner – a named individual who is responsible for the next action, tracking the response, and escalating if timelines slip. This is not the legal team’s job alone. It may be the environmental consultant, the project manager, the technical team, or a specialist advisor. The point is that “someone will handle it” is not an owner.
Establish a weekly consent checkpoint
One meeting. One tracker. Every open approval item reviewed. Next actions confirmed. Escalations surfaced. This sounds obvious, but most projects don’t do it until something has already gone wrong.
Pre-empt the regulator’s questions
Regulators ask predictable questions. Experienced practitioners know what they are. Before submitting any application, ask your specialist: what will they come back on? Then answer it in the application rather than waiting for the request for further information. This alone can save weeks per approval.
Build the “what if” positions in advance
For every critical approval, document in advance what the project does if the decision is delayed by thirty, sixty, or ninety days. Which obligations can be deferred? Which counterparties need to be notified? What does the cashflow model look like under each scenario? Financiers expect this analysis. Having it ready also disciplines the project team to think clearly about what is genuinely time-critical and what isn’t.
The legal team’s role in this framework
Legal inputs are essential at specific points: drafting the application documents and covering correspondence, reviewing the regulator’s information requests, advising on appeal or escalation rights where a decision is unreasonable, and managing the interface between consent conditions and the project’s commercial agreements.
What the legal team should not be doing is owning the consent calendar. That creates a bottleneck of a different kind – one where progress depends on legal availability rather than project momentum.
What this looks like in practice
Projects that run consent management well share three characteristics. The consent map exists and is current. One person has oversight of the whole picture. And the commercial team, the technical team, and the legal team are looking at the same tracker – not separate ones.
The practical result is that delays, when they occur, are identified early. The project team has time to respond: adjusting timelines, notifying counterparties, activating contractual protections. The alternative – discovering a delay when a deadline has already passed – is significantly more expensive.
Why this matters now
South Africa’s regulatory environment for energy projects is not getting simpler. NERSA’s processes, municipal procurement requirements, environmental authorisation timelines, and grid connection queues all create real constraints that no contract can dissolve. The projects that succeed are not necessarily the ones with the fewest regulatory hurdles. They’re the ones that understood the hurdles early, planned around them honestly, and managed the process with the same rigour they applied to the commercial terms.
Bottom line: Regulatory consent is the most common cause of delay in SA energy projects, and the least well-managed. A consent map, clear ownership, and a weekly checkpoint won’t remove the complexity – but they will stop complexity from becoming a crisis. In a market where time is money and timelines are commitments, that difference is material.
