THE SHELL NIGERIA FILES

Shell’s Privilege Problem: A Technical Warning, an Audit Nobody Wanted — and the Fear of What the Record Might Show

Disclosed emails show a Shell technical executive objecting to continued operation of a pipeline outside integrity standards — and being told future disagreements of that seriousness should be put “under legal privilege”

Some corporate documents are damaging because they reveal what went wrong.

Others are more troubling because they reveal what executives feared might one day be discoverable about what went wrong.

Two sets of internal Shell emails now public through the HEDA Resource Centre deserve particularly close attention.

The first concerns a 2008 decision to continue operating the old Nembe Creek Trunk Line, despite a senior technical executive’s objections.

The second concerns a proposed 2013 audit of Shell’s management of crude-oil theft between 2009 and 2012.

Taken together, the documents raise a serious governance question:

When senior Shell personnel confronted uncomfortable evidence about the company’s Nigerian operations, was the priority always to establish the full facts — or was there also a powerful concern about what those facts could expose Shell to if they entered the corporate record?

The documents do not prove unlawful concealment.

They do not establish that legal professional privilege was improperly asserted.

And the disclosed material does not establish whether the controversial 2013 audit was ultimately abandoned, delayed or completed.

Those qualifications matter.

But what the emails actually say is stark enough without embellishment.

A Technical VP objects

The first documentary trail dates from October 2008.

HEDA’s public archive identifies the underlying material as Document 10 — MPR-10 HB 708-710_Redacted_260421_131342. The report’s footnotes identify an email chain involving Markus Droll and Ann Pickard concerning approval for continued operation of the old Nembe Creek Trunk Line outside technical-integrity standards.

This was no trivial disagreement about paperwork.

According to the disclosed correspondence, Droll objected to the decision to continue pumping crude through the pipeline.

His concern, as summarised in the report, was that SPDC and those taking the decision remained exposed, and that the argument that supplying wells could not effectively be shut down was weak. He finished by saying the approach made him, as Technical VP, “pretty uncomfortable.”

That is significant.

Technical executives exist precisely to identify risks that commercial or operational pressures may make inconvenient.

A technical objection is not proof that a decision is wrong.

But when the senior technical voice says an operating course leaves the company exposed and expressly records discomfort, that warning becomes part of the governance trail.

The response is therefore crucial.

“Put any disagreements … under legal privilege”

Ann Pickard replied that the operating decision had not been easy and defended it as, in her assessment, the lower-risk option for people and the environment.

That part of the response is important and should not be omitted.

The documents do not show an executive saying environmental consequences did not matter. Pickard’s stated position was that alternative courses also carried risks and that she had selected what she judged to be the lower-risk option.

But she also told the technical executive that future disagreements at that level should be placed “under legal privilege”, saying his official disagreement had significantly exposed the company.

Those words deserve careful examination.

Legal professional privilege is a legitimate and fundamental part of the legal system. It protects qualifying confidential communications made for the purpose of obtaining or giving legal advice. The mere fact that a company seeks privileged legal advice does not imply misconduct, nor does marking something privileged automatically prove an attempt at concealment.

But context matters.

This was not an abstract reminder to consult lawyers.

It followed immediately after a senior technical executive had formally put on record his disagreement over continuing to operate infrastructure outside technical-integrity standards.

That is why the email matters.

The question is not whether Shell was entitled to obtain legal advice.

Of course it was.

The question is why the fact that the technical disagreement had been recorded without privilege was described internally as significant exposure.

Safety record or litigation record?

There are two very different ways a responsible corporation can react when its technical leadership records a serious objection.

One is:

Make sure the warning is fully documented so future decision-makers, auditors and investigators can understand exactly what happened.

Another is:

Make sure future disagreements of this kind are communicated in circumstances less likely to become disclosable.

The disclosed email does not allow us to state conclusively that Shell chose the second approach.

But it unquestionably raises that concern.

And the distinction is not academic.

Corporate safety systems depend upon uncomfortable information travelling upwards without being sanitised.

Engineers and technical managers must be able to tell commercial leadership that a decision is dangerous, non-compliant or unacceptable.

If executives begin thinking about technical objections primarily in terms of evidential exposure, the culture of record-keeping itself can become distorted.

That is precisely why this email merits scrutiny.

Five years later: another uncomfortable document

Now move forward to February 2013.

HEDA’s archive identifies a second underlying record as Document 26 — MPR-11 HB 1619-1621_Redacted_260421_134338.

The report identifies it as an email concerning draft terms of reference for an SPDC crude-oil-bunkering business-impact and mitigation-effectiveness audit.

The planned audit was potentially important.

Crude-oil theft had become central to Shell’s explanation of production losses, pipeline interference and environmental damage in the Niger Delta.

An audit examining how Shell had managed the problem between 2009 and 2012 therefore had the potential to answer difficult questions.

Were controls adequate?

Were mitigation measures effective?

Had known problems been addressed?

Had management systems failed?

Were claimed oil losses defensible?

And what consequences might those findings have for claims by government or affected communities?

An internal Shell manager apparently had a grim expectation of the answer.

“This cannot have a good outcome”

According to the disclosed 2013 email, the senior manager sought to have the proposed audit rescheduled.

The manager predicted that its findings would be “UNACCEPTABLE” and warned that Shell could be “very exposed”when disputing government oil-loss claims or community compensation demands.

Then came perhaps the most revealing concern.

Although the manager acknowledged that an audit could help improve operations, the email questioned whether the exercise might “do more harm than good.”

Pause on what that means.

Audits are supposed to uncover weaknesses.

An audit that discovers serious deficiencies is not malfunctioning.

It is doing its job.

If the anticipated problem is that the findings will be bad, embarrassing or financially damaging, postponing scrutiny does not correct the underlying problem.

It simply postpones the moment at which the problem is formally recorded.

The report goes further than the evidence allows

The publishers of Nigeria: Lifting the Lid describe this material under the heading “Safety concerns overridden or suppressed” and say the 2013 correspondence suggests executives sought to suppress evidence of mismanagement.

That is their interpretation.

It should not automatically be converted into an established fact.

The report itself acknowledges an important evidential gap: the disclosed documents do not say whether the audit ultimately took place or, if it did, what conclusions it reached.

That limitation matters.

It would therefore be wrong to state categorically that Shell cancelled an audit to hide damaging findings.

The currently public evidence does not establish that.

What is established by the disclosed email, as presented in the report, is that a senior manager wanted the exercise rescheduled while explicitly worrying that an adverse audit result could weaken Shell’s position against government and community claims.

That alone warrants an answer.

Shell should say what happened to the audit

There is an exceptionally simple way to resolve this.

Shell should publish the complete audit trail.

Was the audit scheduled?

Was it rescheduled?

Who approved the change?

What reason was formally recorded?

Did the audit ultimately proceed?

Who conducted it?

What did it find?

What corrective actions followed?

Were the findings presented to senior Shell management?

Were they communicated to Nigerian regulators or joint-venture partners?

And were they considered when Shell disputed community compensation claims or government claims concerning oil losses?

If the audit ultimately proceeded in full and the disclosed email merely records a temporary scheduling dispute, publication would materially change the picture.

If it did not proceed, the reason deserves explanation.

Corporate transparency is particularly important here because the manager’s own email connected the anticipated audit result with Shell’s potential exposure to claims.

The old NCTL makes the privilege email harder to dismiss

The 2008 correspondence cannot be viewed in isolation from the wider documentary record concerning the old Nembe Creek Trunk Line.

Other material in the newly released archive describes serious concerns over pipeline integrity, maintenance and continued operation.

The subsequent record shows that Shell eventually replaced the old NCTL in 2010, yet another internal communication from 2014 described an approximately 80-kilometre section of the retired line as still containing stagnant crude and associated it with repeated operational spills while decommissioning was delayed by budget pressures.

That later history does not prove that Droll’s 2008 objection was correct in every respect.

It does demonstrate that his concern was not about an imaginary risk.

He was objecting within a system whose infrastructure would continue generating serious internal concern for years.

That makes the instruction about handling future disagreements through privilege all the more worthy of examination.

What an accountability culture should look like

Large industrial organisations routinely face choices where every option carries risk.

Shutdowns themselves can create technical, economic and sometimes safety consequences.

Executives are entitled — indeed required — to weigh competing risks.

That is the strongest argument in Shell’s favour regarding the 2008 decision.

Pickard’s email explicitly said she believed continuing operation in the chosen mode represented the lower risk to people and the environment.

But responsible risk management requires something else as well:

a reliable record of dissent.

When the technical leadership disagrees with an operating decision, that dissent should be preserved accurately.

Not because the technical executive must always win.

But because boards, regulators, investigators and courts may later need to establish who knew what, which options were considered and why a particular course was chosen.

A culture in which bad news is recorded clearly is safer than one in which people first ask how discoverable the bad news might become.

Then there is the community

It is easy to read these emails solely as corporate-governance documents.

That would miss the most important constituency.

Outside Shell offices were Niger Delta communities living beside pipelines, wells, waterways and polluted land.

For those communities, the quality of Shell’s internal decision-making was not theoretical.

If a pipeline failed, crude could enter fishing waters.

If an audit identified deficiencies, correcting them could prevent pollution.

If an audit was delayed, any underlying weakness remained.

If compensation liability turned upon what Shell knew or how it had responded, the completeness of the documentary record could matter enormously.

That is why wording about corporate exposure cannot simply be dismissed as lawyers doing what lawyers do.

The people exposed to the physical risk have a legitimate interest in understanding how the corporation discussed its legal risk.

Shell rejects the report’s portrayal

Shell disputes the campaign organisations’ interpretation of the disclosed record.

In its July 2026 response to Amnesty International, Shell said the documents had been selectively quoted in a way that created a misleading impression and did not adequately reflect the difficult operating environment in the Niger Delta, including large-scale theft, sabotage and illegal refining. Shell also said its former Nigerian subsidiary worked with Nigerian authorities, its government-owned partner and communities and cleaned spills from joint-venture facilities regardless of cause as required by Nigerian law.

Shell further emphasised that the Bille and Ogale claims concern complex and contested issues that will be tested through the English court process.

Its current public case page similarly maintains that the majority of pollution at issue resulted from organised oil theft, sabotage and illegal refining and says Shell will vigorously defend the claims at the factual trial scheduled for 2027.

That position must be included.

But it does not answer the specific documentary questions raised here.

Why was a technical executive told that recording his disagreement without privilege had significantly exposed Shell?

What happened to the audit whose expected findings worried a senior manager?

Those questions stand independently of whether criminal gangs also damaged pipelines.

Privilege cannot become the story instead of safety

Nobody should argue that corporations lose the right to confidential legal advice when they operate dangerous infrastructure.

They do not.

But there is an equally important principle of corporate accountability.

Legal risk management must not substitute for operational risk management.

If an engineer believes infrastructure should not continue operating, the central question should be whether the engineer is right.

If an audit is expected to expose serious deficiencies, the central question should be whether those deficiencies exist.

If community compensation claims may be strengthened by truthful internal findings, the central question should not be how inconvenient that truth becomes for the company.

It should be whether compensation is owed.

The disclosed emails do not prove Shell crossed those lines.

They show enough to justify asking whether it came dangerously close.

Publish the complete record

Shell says context is missing.

There is an obvious answer to that complaint:

provide the context.

Publish the full decision record surrounding continued operation of the old NCTL in October 2008.

Publish the technical risk assessment.

Publish the competing options.

Publish the legal and engineering advice that can lawfully be disclosed.

Publish the subsequent integrity findings.

And publish the complete administrative history of the proposed 2009-2012 crude-oil-theft audit, including whether it was ultimately conducted and what it concluded.

If the documents vindicate Shell, Shell should want them public.

If they do not, communities are entitled to know that too.

Because what is already public presents an extraordinary picture:

A senior technical executive formally objected to a pipeline decision.

He was overruled.

He was told that future disagreements of that seriousness should be handled through legal privilege.

Years later, another senior manager contemplated postponing an audit because its anticipated findings could expose Shell when fighting claims from government and communities.

Those facts do not require exaggeration.

They require answers.

Documentary record

The first principal source is Document 10 — MPR-10 HB 708-710_Redacted_260421_131342, publicly listed by HEDA. The report identifies the 10 October 2008 email as being from Markus Droll to Ann Pickard and the following response from Pickard; the exchange concerned continued operation of the old NCTL outside technical-integrity standards.

The second principal source is Document 26 — MPR-11 HB 1619-1621_Redacted_260421_134338, also publicly listed by HEDA. The report identifies it as correspondence concerning draft terms of reference for the UIO-G/2013.002 Nigeria-SPDC Crude Oil Bunkering Business Impact & Mitigation Effectiveness Audit, dated February 2013.

Section 4.6 of Nigeria: Lifting the Lid — Internal Documents Expose Shell’s Negligent Oil Operations reproduces and analyses both documentary episodes. The report expressly states that the currently disclosed record does not establish whether the proposed audit subsequently proceeded or what its findings were.

Shell’s formal July 2026 response rejects the report’s overall characterisation, argues that selected quotations create a misleading impression, stresses the exceptional scale of criminal interference in the Niger Delta and says the disputed issues will be tested in ongoing litigation.

Editorial note

This article does not allege that Shell unlawfully asserted legal professional privilege, destroyed records, concealed evidence or cancelled the 2013 audit. The disclosed material does not establish those propositions.

It reports what the internal correspondence says and examines the legitimate governance questions arising from it.

Legal professional privilege is a recognised protection for qualifying confidential legal communications and its use is not itself evidence of misconduct. The significance here lies in the documented context in which privilege and potential litigation exposure were discussed.

The Bille and Ogale claims remain contested and have not yet resulted in a factual determination of the issues discussed above. Shell says it will vigorously defend the claims 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.