THE SHELL NIGERIA FILES: 28 AUGUST 2026

The next materially distinct documentary angle is the formal exception from Shell’s own group safety-control requirements. The 24 August instalment mentioned this only in passing and expressly identified it as a separate documentary story; it has not yet received a dedicated article. (Royal Dutch Shell Plc .com)

THE SHELL NIGERIA FILES: 28 AUGUST 2026

Shell’s “Restricted” Safety Exception: Tampered Nigeria Pipelines Were Allowed to Keep Operating Outside a Group HSSE Requirement

A 2009 Shell engineering rule was rewritten specifically for SPDC. Then a 2012 internal application sought an exception from a group safety requirement after acknowledging that pipelines with numerous illegal connections called for “immediate corrective action or shutting in of the line.” The reason included the “considerable system downtime” needed to remove them. According to the newly published record, Shell executives approved the exception in 2013 and later extended it through 2016.

Some of the most consequential documents in a corporate archive do not look dramatic.

They are forms.

Procedures.

Technical standards.

Applications for exceptions.

One of the most important records in the newly disclosed Shell Nigeria files appears to be exactly that kind of document.

HEDA Resource Centre lists it as:

Document 16 — MPR-10 HB 800-804_260421_132649.

The July 2026 report Nigeria: Lifting the Lid identifies it more fully as an Application Form exception to Group HSSE & SP Control Framework Requirement, dated 12 November 2012. HEDA says the documents in its public archive were cited in the Bille and Ogale litigation and were released in redacted form after campaigning organisations sought their publication on public-interest grounds. (Hedang)

At first glance, an application for an exception to an internal corporate standard sounds bureaucratic.

It is anything but.

According to the report, Shell managers acknowledged in the application that pipelines affected by numerous illegal connections fell into a condition requiring “immediate corrective action or shutting in of the line.”

Removing all those connections, however, would “take considerable system downtime.”

So an exception was sought from the requirement that HSSE Critical Equipment be operated “within its operating limits.”

According to the documentary record assembled in the report, the exception was subsequently approved by Shell executives in March 2013, initially until the end of 2014.

It was then extended.

Until the end of 2016.

That is a very different story from Shell merely discovering that criminals had attacked its pipelines.

It is a story about what Shell formally authorised itself to do after it knew the pipelines had been attacked.

Shell’s global safety system

To understand why Document 16 matters, it helps to look at what Shell was telling the world about its safety controls at approximately the same time.

Royal Dutch Shell’s own 2011 Sustainability Report said all employees and contractors, including those working at joint ventures operated by Shell, were required to act in accordance with the company’s Health, Safety, Security, Environment and Social Performance Control Framework.

Shell said the framework established standards and accountabilities throughout the organisation and that comprehensive assurance processes monitored compliance. (Shell)

The same report was even more explicit in its safety section.

Shell said it had standards all operations must follow, that global requirements specified the operational controls and physical barriers needed to prevent incidents, and that Shell companies, Shell-operated joint ventures and contractors had to manage safety in accordance with group policy, applicable law and permits. (Shell)

That sounds straightforward.

Global company.

Global standards.

Global assurance.

Nigeria included.

And there is nothing unusual about a major oil company having such a framework. High-hazard businesses require precisely this kind of system because individual operating companies cannot be allowed to improvise independently on safety-critical matters.

But a control framework is only as strong as the way departures from it are managed.

And that is where Document 16 becomes important.

The problem had already appeared in Shell’s engineering rules

Document 16 was not the first occasion on which Nigeria received special treatment in the technical documentation.

HEDA also publishes Document 9 — MPR-10 HB 711-749_260421_131313. The coalition report identifies it as Shell’s Pipeline Repairs DEP 31.40.60.12-SPDC, dated April 2009.

A DEP — Design and Engineering Practice — forms part of the technical rulebook governing how Shell facilities are engineered and maintained.

According to the report, the pipeline-repair DEP was revised specifically for SPDC’s Nigerian operations.

The changes reportedly permitted two practices of particular significance.

Temporary clamps could be treated as permanent repairs.

And pipelines could continue operating where illegal oil-theft connections remained attached, provided those particular connections were not actively leaking.

The issue here is not the existence of clamps themselves. Previous instalments have already examined Shell’s extensive clamp inventory and pipeline-maintenance problems.

The issue is policy.

Something normally described as temporary could, under the SPDC-specific provision, become permanent.

Something attached illegally to a live hydrocarbon pipeline could remain there while production continued.

That was written into the operating rules.

Four years later, the exception process went further.

The 2012 application confronts the problem directly

The November 2012 exception application matters because it appears to document the conflict between Shell’s general safety requirement and conditions actually prevailing in the Niger Delta.

Illegal tapping was rampant.

That fact is not disputed.

Shell’s pipelines were being drilled, cut and fitted with valves, hoses and other connections by thieves stealing crude oil.

Those criminals created genuine dangers to the infrastructure, communities and environment.

Shell was a victim of that criminal activity.

But victimhood did not eliminate Shell’s responsibility for deciding whether a compromised hydrocarbon system should continue operating.

According to Nigeria: Lifting the Lid, Shell managers acknowledged in the exception application that numerous illegal connections meant affected pipelines met criteria calling for immediate corrective action or shutdown.

The normal solution was obvious:

remove the connections.

The operational difficulty was equally obvious:

doing so across the affected system required substantial downtime.

The managers therefore applied for an exception.

This is the point at which the story becomes especially important.

The issue was apparently not that Shell did not know the standard.

The issue was not that nobody recognised the abnormal pipeline condition.

And it was not simply that criminal interference occurred without Shell’s knowledge.

The exception mechanism existed precisely because the normal requirement and the proposed operating course were in conflict.

An authorised exception is not automatically misconduct

This distinction is essential.

Large industrial companies do allow exceptions, deviations and derogations from technical standards.

They have to.

A standard cannot anticipate every operating circumstance.

Equipment becomes obsolete.

Emergency conditions arise.

A technically equivalent safeguard may be available.

Compliance with the literal wording of one requirement can sometimes introduce a greater risk elsewhere.

Accordingly, a properly managed exception can be entirely legitimate.

Usually the important questions are whether the deviation was technically justified, whether the additional risks were properly assessed, whether compensating safeguards were imposed, whether competent personnel approved it at the appropriate level, whether it was time-limited, and whether it was reviewed before extension.

So the mere existence of Document 16 does not prove that Shell broke the law.

It does not prove that the HSSE Control Framework was fraudulent.

It does not even prove that the pipelines covered by the exception were, in engineering terms, incapable of being operated with acceptable risk if adequate compensating controls existed.

Those matters require the underlying risk assessment and approval record.

But that is precisely why those records now matter.

What were the compensating safeguards?

The publicly accessible report tells us what requirement Shell wanted relief from.

It tells us why removing the connections was operationally difficult.

It tells us the exception was approved and later extended.

What it does not provide in comparable detail is the complete engineering case demonstrating why continued operation remained acceptable.

What additional inspection was required?

Were operating pressures reduced?

Was leak surveillance intensified?

Were helicopter inspections increased?

Were patrols stationed around compromised sections?

Was production restricted?

Were emergency shutdown arrangements altered?

Were individual illegal connections subjected to technical assessment before being permitted to remain?

How frequently were they reassessed?

What conditions would immediately cancel the exception?

And how was the cumulative risk from hundreds of third-party interventions assessed?

Those are not rhetorical questions.

They are the questions an engineering exception should answer.

Without the complete exception package — application, risk assessment, approval conditions, extension justification and close-out record — the public sees the departure from the standard without being able to assess fully the controls supposedly making that departure tolerable.

The exception reportedly covered the Nembe Creek Trunk Line

The significance becomes still greater because the report says the exception allowed continued operation of infrastructure including the Nembe Creek Trunk Line, or NCTL.

That pipeline ran past Bille and is central to the ongoing English litigation.

The report says illegal taps and hoses were left attached while oil continued moving through the system.

That does not mean every tap was continuously leaking.

The 2009 SPDC-specific repair provision, as described in the report, distinguished between connections that were actively leaking and those that were not.

Nor does the evidence establish that Shell installed the illegal connections. The documentary record is clear that organised thieves were responsible for widespread third-party interference.

But once Shell knew those connections existed, a new category of decision arose.

Should oil continue to be pumped through the compromised line?

That decision belonged to the operator and its corporate governance system.

The word “restricted”

The exception application was reportedly marked “restricted.”

That word deserves neither too much nor too little significance.

Large companies routinely classify internal technical, commercial and security material. A “restricted” marking is not evidence that somebody was improperly concealing wrongdoing.

There may have been perfectly ordinary reasons to restrict circulation of a document discussing pipeline vulnerabilities, illegal tapping and operational limitations.

Indeed, publishing detailed information about vulnerable infrastructure could itself assist criminals.

So the classification should not be sensationalised.

What matters is different.

The exception remained outside public view while Shell was publicly making broad statements about the application of its global standards.

The public did not have the information now available through the litigation disclosure.

That creates a legitimate transparency question even if the internal classification itself was entirely proper.

What Shell was telling the public

Shell’s 2011 Sustainability Report said its global HSSE standards applied across its operations and described comprehensive assurance procedures for monitoring compliance. It said safety was its top priority and that equipment was designed, operated, inspected and maintained with safety foremost. (Shell)

The coalition report identifies an even more specific contemporary Nigeria statement.

It says Shell maintained in 2013 that SPDC operated an Environmental Management Improvement Programme designed to keep equipment and infrastructure in good condition and that the programme conformed to global Shell Group standards and ISO guidelines.

Now place beside that the disclosed internal record.

An SPDC-specific engineering practice had already altered normal repair requirements in 2009.

An application for an exception from a group HSSE requirement was made in November 2012.

According to the report, it was approved in March 2013.

And it was later extended through 2016.

The report publishers argue that this undermines Shell’s public claims about compliance with global standards.

That is their interpretation.

There is another possible interpretation that needs to be considered.

Shell could argue that exceptions are part of the system

A sophisticated control framework can contain its own formal exception process.

If so, using that process does not necessarily mean the framework ceased to apply.

Indeed, the existence of an authorised exception form can demonstrate that Shell had governance machinery for dealing with departures instead of allowing local managers simply to disregard standards informally.

Under that interpretation, Shell could say:

the group framework continued to govern SPDC;

the framework allowed properly authorised exceptions;

the Nigeria circumstances were exceptional;

the deviation was formally considered;

and senior approval was obtained.

That would materially qualify the report publishers’ assertion that Shell had simply abandoned its global standards.

But such a defence immediately produces another set of questions.

What was the technical basis for approval?

What additional controls were imposed?

Was the exception genuinely temporary?

Why did it need extending through 2016?

What evidence demonstrated that risk remained tolerable during the extension?

And how material can an exception become before a public statement that operations conform to global standards requires qualification?

Those questions cannot be answered by the existence of the application form alone.

“Considerable system downtime” is not an incidental phrase

The operational justification recorded in the report also deserves careful attention.

Removing all the illegal connections would take substantial system downtime.

Downtime in an oil pipeline has economic consequences.

Production is deferred.

Revenue is lost.

The Nigerian government, as majority joint-venture participant through the then NNPC, also had a major financial interest in keeping production flowing.

Other producers could be affected.

And extensive shutdowns could themselves create operational and security complications.

All of that belongs in a fair account.

But downtime is not a safety argument in itself.

It is an operational and economic consequence of complying with a safety requirement.

If continuing operation creates additional risk, that risk has to be justified independently of the inconvenience or revenue loss caused by shutdown.

The documents disclosed so far do not establish that money was the sole or even necessarily the decisive consideration behind the exception.

It would therefore be wrong to claim that Shell simply “bought production with safety.”

What the evidence does establish is that the burden of shutting the system down formed part of the problem presented in seeking the exception.

That is significant enough.

The duration matters

There is another feature that makes this difficult to dismiss as a short-term emergency accommodation.

According to the report, approval ran from March 2013 until the end of 2014 and was subsequently extended until the end of 2016.

An emergency exception lasting days while a repair team mobilises is one thing.

An exception regime extending across years is another.

A multi-year duration does not automatically make the decision improper.

The scale of illegal tapping was extraordinary, repair access was difficult, and criminal interference could recur soon after a connection was removed.

But longevity changes the governance question.

At what point does an exceptional condition become the operating condition?

At what point does a temporary departure require redesigning the system, changing the production strategy or revising the underlying standard transparently?

And what evidence justified renewal when the initial approval period expired?

The extension documents could be especially revealing.

This intersects with Shell’s sabotage defence — but does not invalidate it

Shell continues to maintain that large-scale oil theft, sabotage and illegal refining by organised criminal gangs caused the majority of the pollution relevant to the Bille and Ogale case.

Its current litigation page says SPDC worked with Nigerian authorities, its government-owned partner and communities; cleaned spills from joint-venture facilities regardless of cause as Nigerian law required; and invested heavily in infrastructure replacement, monitoring, surveillance, repairs, shut-ins and spill-response capability. Shell says those measures evolved as criminal interference worsened and were reasonable and lawful in the circumstances. (Shell)

Those are material points.

The exception documents do not establish that sabotage was fictitious.

They do not absolve thieves who drilled pipelines.

They do not prove that an operational failure caused every spill alleged by Bille.

But Shell’s sabotage defence and Shell’s operational decisions are not mutually exclusive questions.

A criminal can create the initial hazard.

An operator can still be responsible for deciding how a hazardous system is subsequently managed.

That distinction is fundamental.

If thieves drill an illegal connection into a pipeline, responsibility for the criminal act lies with them.

Once the operator knows about that connection, however, the question of whether to isolate the line, repair it, continue operating it under special controls or seek an exception from normal requirements is an operator decision.

Document 16 goes directly to that second question.

Shell strongly rejects the publishers’ wider portrayal

Shell was given an opportunity to respond to the organisations behind Nigeria: Lifting the Lid.

Its response, dated 15 July 2026, is reproduced in full in the report.

Shell said the characterisation presented by the publishers was not one it recognised and accused them of selectively quoting documents so as to create a misleading impression.

Shell said the analysis failed adequately to reflect the exceptionally difficult Niger Delta operating environment, including organised large-scale theft, sabotage and illegal refining.

It stressed that its former Nigerian subsidiary worked with Nigerian authorities, its government-owned partner and communities and cleaned spills from joint-venture facilities irrespective of cause where Nigerian law required it.

Shell also emphasised that the Bille and Ogale proceedings concern complex contested matters that will be tested through the court process.

Shell’s own website says the Bille factual trial is expected in early 2027, involving a selection of claimants, alleged damage and disputed causes. Shell says it strongly believes in its case and will vigorously defend the claims. (Shell)

That response belongs prominently in the record.

It does not, however, specifically explain Document 16.

What Shell could now publish

The cleanest way of resolving the issue would be disclosure of the complete exception trail.

The documents that would matter most are the original 2012 application in full; the technical risk assessment; the identity by role of the approving authorities; all conditions imposed on the approval; the list or category of assets covered; the compensating controls; monitoring reports during the exception period; the 2014 review; the justification for extending the arrangement through 2016; and the eventual closure or replacement of the exception.

The same applies to the 2009 SPDC-specific DEP.

What was the technical justification for treating temporary clamps as permanent repairs?

Under what inspection regime?

What criteria determined whether an illegal connection that was not actively leaking could safely remain?

How often did it have to be inspected?

Did the rule apply indefinitely?

And how did Shell assess the additional risk that a thief could return to a dormant connection and reopen it?

The answers may support Shell’s position.

They may show a carefully engineered response to an almost impossible criminal-security environment.

Or they may reinforce the report publishers’ allegation that continued production was prioritised despite risks that Shell’s ordinary standards would not have accepted.

The evidence should decide.

What is established, alleged and inferred

The documentary distinctions are important.

Established from the published record: HEDA’s archive contains Document 9, the 2009 SPDC pipeline-repair practice, and Document 16, the November 2012 application for an exception from a Group HSSE & SP Control Framework requirement. The coalition report identifies the content and provenance of both. (Hedang)

Reported from the documents and associated court material: the 2009 SPDC-specific practice permitted temporary clamps to serve as permanent repairs and permitted continued pipeline operation where illegal taps were not actively leaking. The 2012 application acknowledged pipeline conditions calling for immediate correction or shutdown, cited substantial downtime associated with removing the illegal connections, and sought relief from the requirement to keep HSSE Critical Equipment within operating limits. According to the report, senior approval followed in March 2013 and the exception was later extended through 2016.

The report publishers’ allegation: these arrangements show that Shell exempted Nigerian operations from important global safety requirements so production could continue through compromised infrastructure, contrary to the impression created by Shell’s public statements about group-wide standards.

Inference requiring caution: system downtime and therefore production continuity were materially relevant to the exception decision. That does not by itself establish that profit overrode safety, that continued operation was unlawful, or that the exception caused any particular oil spill.

Contested: Shell rejects the publishers’ broader portrayal, argues that selected records have been presented misleadingly without sufficient context about extraordinary criminal interference, and maintains that SPDC took extensive and evolving measures to prevent, contain and remediate spills. The underlying liability questions remain before the English courts.

The deeper governance issue

There is a larger lesson in these records.

Corporate standards are easiest to obey when obedience costs little.

The real test arrives when compliance hurts.

When the plant must stop.

When production is deferred.

When revenue is lost.

When the operating environment is chaotic.

When criminals repeatedly undo repairs.

When managers face pressure from governments, partners, communities and shareholders simultaneously.

That is precisely when a global standard acquires meaning.

An exception may sometimes be justified.

But the more serious the underlying hazard, the greater the burden on the company granting itself that exception to demonstrate why the alternative remained safe enough.

And the longer the exception lasts, the harder it becomes to describe the situation as exceptional without explaining what was being done to restore normal compliance.

The question Shell’s own paperwork now poses

The Shell Nigeria files have already shown technical warnings, maintenance deficiencies, leak-detection limitations, security weaknesses, arguments over spill attribution and senior-management debates over continuing production.

Document 16 adds something fundamentally different.

It documents the governance mechanism by which continued operation could be authorised despite a conflict with a normal group requirement.

That mechanism may ultimately prove to have been rigorous.

But if it was rigorous, Shell should be able to demonstrate it.

The application was made.

The risk was identified.

Downtime was recognised.

The exception was approved.

The exception was extended.

Those are the documentary milestones now in the public domain.

The missing part is the justification.

And after years in which Shell publicly emphasised the reach and rigour of its global safety standards, that missing explanation matters.

Because the credibility of a global safety standard is not ultimately determined by the wording printed in a sustainability report.

It is determined by what happens when following that standard becomes inconvenient.

Documentary record

The principal archive is HEDA Resource Centre’s Shell Documents Released in UK Legal Proceedings. HEDA states that the redacted records include senior-executive emails and confidential audits cited in the Bille and Ogale litigation and released after organisations sought publication in the public interest. Its index lists Document 9 — MPR-10 HB 711-749_260421_131313 and Document 16 — MPR-10 HB 800-804_260421_132649. (Hedang)

Nigeria: Lifting the Lid, published in July 2026, identifies Document 9 as the April 2009 SPDC pipeline-repair DEP and Document 16 as the 12 November 2012 application for an exception from a Group HSSE & SP Control Framework requirement. The report also cites associated witness-statement material for the approval and later extension of the exception.

Royal Dutch Shell’s Sustainability Report 2011 provides the contemporaneous company description of its global HSSE governance and safety requirements. Shell said employees, contractors and operated joint ventures were required to work within the HSSE & SP Control Framework and that its operations had standards they were required to follow. (Shell)

Shell’s detailed response of 15 July 2026 is reproduced in Annex 1 of the coalition report. Its current account of the Bille and Ogale proceedings was last updated 16 July 2026 and sets out Shell’s position on sabotage, illegal refining, investment in pipeline integrity and spill response, and the forthcoming 2027 trial.

For direct inspection of the source material: HEDA Resource Centre — Shell Documents Released in UK Legal Proceedings · Nigeria: Lifting the Lid — full July 2026 report · Royal Dutch Shell Sustainability Report 2011 · Shell’s current Bille and Ogale case position

Editorial note

This article does not assert that the existence of an authorised exception from an internal Shell requirement was itself unlawful, improper or negligent.

Formal exceptions to engineering and HSSE standards can be legitimate where risks are properly assessed, competent authority approves the departure, adequate compensating controls exist and the arrangement is appropriately monitored and reviewed.

The available public record does not contain enough detail to determine whether those conditions were satisfied in every respect for the SPDC exception discussed here.

The report publishers argue that the exceptions allowed Shell to keep oil flowing through compromised Nigerian infrastructure despite standards that otherwise called for corrective action or shutdown and that this undermined Shell’s public presentation of its global safety framework. That is the publishers’ interpretation of the evidence and has not been established as a judicial finding.

Shell disputes the publishers’ wider characterisation, says the documents have been selectively presented without sufficient recognition of the exceptional scale of oil theft, sabotage and illegal refining, and maintains that its former subsidiary invested extensively in infrastructure, monitoring, repairs, shutdowns and spill response.

The Bille and Ogale proceedings remain contested. The factual issues relevant to liability have not yet been finally determined at trial.

Site wide disclaimer also applies.

*This website and sisters royaldutchshellgroup.com, shellnazihistory.com, royaldutchshell.website, johndonovan.website, shellnews.net, and shellwikipedia.com, are owned by John Donovan - more information here. There is also a Wikipedia segment, the Shell DPA Files, "Shell and the Spies", the Shell Leaks files, the Independent Shell Archive, as well as books written and published by John Donovan - Kindle eBooks. Timeline of the Donovan Shell Feud. Toxic History of Royal Dutch Shell Group. Shell and the Donovans: The Full Media Record — 550+ Articles, 110 Books, 40 Years. *All conjured up by internet wizz, Nick Gill.

Comments are closed.