The Shell Leaks Files

SLF-2007-017

The Sakhalin Papers VII: The Whistleblower Warnings — Claims That Shell’s Management Could No Longer Control the Project

Archive Reference: SLF-2007-017
Collection: The Sakhalin Papers
Evidence Standard: Authenticated Shell communications, contemporaneously preserved whistleblower material, official project records, contemporaneous journalism, parliamentary evidence and relevant court-record context.

Introduction

On 2 June 2007, royaldutchshellplc.com published allegations attributed to a confidential source inside the Sakhalin-2 project.

The source made two distinct categories of claim.

The first concerned the project timetable. The insider alleged that senior management was promoting an unachievable December 2007 target for making the onshore pipeline ready to receive hydrocarbons, while specialist personnel believed that completion would extend into 2008.

The second category was considerably more serious. It included allegations that professional advice was being disregarded, personnel were being pressured to endorse the preferred timetable, and questionable relationships existed between project management and certain contractors.

The eventual project chronology supports an important part of the source’s warning: the pipeline was not completed in December 2007.

It does not, however, prove every allegation the source made.

This archive file therefore asks three separate questions:

1. What did the whistleblower allege?
2. Which predictions were borne out by subsequent events?
3. Which accusations remain unproven?

That distinction is essential to responsible documentary history.

The Nature of the Evidence

1. An anonymous source is not an authenticated Shell document

The whistleblower statement was preserved and published contemporaneously. It contained detailed references to Sakhalin Energy’s onshore pipeline organisation, its programme, named managers, internal disciplines and contractors.

Its specificity gives it evidential interest.

It does not, by itself, establish the source’s identity, employment status or personal knowledge.

Unlike the David Greer “Pipeliners All!” email examined in the previous archive file, the whistleblower statement was not subsequently authenticated by Shell or Sakhalin Energy.

It must therefore be classified as a contemporaneously recorded insider allegation, not as an authenticated corporate record.

That does not make it worthless.

It determines how cautiously it must be used.

The Whistleblower’s Central Warning

2. The disputed December 2007 target

The source alleged that Sakhalin Energy management was presenting December 2007 as the date by which the onshore pipeline would be ready for hydrocarbons.

According to the statement, several internal engineering and construction disciplines had concluded that completion would instead occur during 2008. The source alleged that operational, procedural and construction constraints had been excluded from the preferred programme and that information inconsistent with the December target was being rejected.

The allegation was not merely that a deadline might be missed.

The source claimed that management was committed to a date that internal specialists considered technically unattainable.

The statement concluded with the stark assessment:

“The current SEIC management can no longer effectively manage Sakhalin II.”

That was an opinion expressed by an anonymous source. It was not a judicial finding, an official audit conclusion or a statement accepted by Shell.

3. Alleged pressure on project personnel

The source further alleged that members of specialist disciplines were being pressed to endorse the December programme despite their professional reservations.

It was claimed that staff risked having responsibility shifted onto them if the target was subsequently missed: management could point to an apparently agreed programme, while the individuals concerned would carry the professional consequences.

The source described project information as being accepted only when it supported the chosen date and alleged that personnel were being placed under considerable pressure.

Evidential position

No authenticated record examined for this instalment independently proves that staff were coerced into approving a false programme.

The allegation must remain identified as an allegation.

There is, however, authenticated evidence that senior project management was confronting visible anxiety and a lack of confidence among personnel at approximately the same time.

The Greer Email as Corroborative Context

4. “Pipeliners All!”

David Greer’s authenticated email of 18 April 2007 was addressed to a large group of personnel connected with the onshore pipeline operation.

Greer wrote that comments and body language observed at a project meeting suggested the department risked becoming a team that did not want to fight and lacked confidence in its ability.

He attempted to rally the recipients with militaristic language and ended with the instruction:

“Lead me, follow me or get out of my way.”

Shell and Sakhalin Energy confirmed the email’s authenticity after it was supplied to the Financial Times. Greer left the company several weeks later, although Sakhalin Energy rejected as speculation the suggestion that the leaked email had caused his departure.

What the email corroborates

The Greer document confirms that:

• senior management perceived faltering confidence among pipeline personnel;
• the remaining programme was regarded as an exceptional challenge;
• management considered a forceful intervention necessary;
• substantial organisational pressure existed within the project.

What it does not corroborate

The email does not prove that project schedules were falsified.

It does not establish that staff were coerced into signing an unachievable programme.

It does not prove improper relationships with contractors.

It supports the whistleblower’s description of a project under intense managerial and schedule pressure, but it does not authenticate every allegation.

Earlier Internal Warnings About Schedule Pressure

5. The Bouman–Van Spronsen correspondence

The Sakhalin archive contains authenticated internal communications predating the 2007 whistleblower statement.

In 2002, Shell manager Hans Bouman raised concerns with Sakhalin Energy technical director Engel van Spronsen about well design, seismic faults, shallow gas and the danger of allowing schedule considerations to override technical caution.

Van Spronsen acknowledged that he sometimes shared Bouman’s concern about the schedule. Bouman subsequently confirmed the authenticity of his emails to Dow Jones Newswires. Sakhalin Energy said the well design was revised in 2005, while Van Spronsen denied that the issues identified had caused the project’s cost escalation.

One observation from the contemporaneous reporting was particularly relevant:

“I would never ever want to be schedule-driven” on a project of that scale.

These earlier emails concerned well design rather than the 2007 pipeline completion programme. They do not prove the later whistleblower allegations.

They do establish that concern about schedule pressure within Sakhalin-2 was not invented retrospectively.

Testing the Prediction Against the Project Record

6. Was the pipeline ready in December 2007?

The strongest test of the anonymous warning is the subsequent project chronology.

In January 2008, an official Gazprom account of a Sakhalin-2 project visit described the onshore oil and gas pipelines as still under construction.

Contemporaneous reports in November 2008 stated that construction of the approximately 800-kilometre pipeline system had been completed and that filling it with oil and gas had begun.

Sakhalin Energy’s present project history records that gas production from the Lunskoye-A platform began in 2008, when gas first entered the project’s pipeline system. It similarly dates commercial development of the Piltun-Astokhskoye-B area to late 2008.

The available record therefore supports the whistleblower’s central scheduling prediction:

The onshore pipeline system was not completed by December 2007. Substantial construction and commissioning activity continued into 2008.

7. The wider commissioning delay

The whistleblower statement concentrated on pipeline readiness rather than the date of the first commercial LNG cargo.

The wider project timetable nevertheless provides relevant context.

In December 2007, Sakhalin Energy announced that completion of the LNG plant and the first exports would be delayed. Reuters reported Gazprom’s intention to attempt first LNG exports by the end of 2008, while the Sakhalin regional governor said supplies were more likely to begin in spring 2009.

Gazprom’s official project history records that the LNG plant entered service in February 2009.

These developments do not prove that the anonymous source possessed perfect information.

They do demonstrate that the warning of slippage beyond the publicly promoted timetable was substantially correct.

The Contractor Allegations

8. Starstroi and SU4

The source also raised questions about the relationship between Sakhalin Energy management, prime contractor Starstroi and subcontractor SU4.

The allegations included possible conflicts of interest and inappropriate relationships. No evidence examined for this instalment establishes those accusations as fact.

In June 2008, WWF referred to the claims in written evidence submitted to the House of Commons Environmental Audit Committee. The parliamentary record stated:

“Allegations have been made by a whistleblower of inappropriate relationships between SEIC management and its contractors.”

It specifically identified Starstroi and SU4 and cited the January 2008 royaldutchshellplc.com article as its source.

What parliamentary inclusion means

The inclusion of the allegations in published parliamentary evidence is historically significant.

It demonstrates that WWF considered them relevant enough to place before a select committee and that they entered the permanent parliamentary record.

It does not mean that Parliament investigated, adopted or proved them.

The wording carefully preserved their status as allegations.

The same discipline should be maintained here.

Court-Record Position

9. What the courts did—and did not—decide

WWF and The Corner House prepared a judicial-review challenge concerning the UK Export Credits Guarantee Department’s proposed support for Sakhalin-2. The challenge was discontinued after Sakhalin Energy withdrew its application for ECGD support in February 2008.

Separate proceedings concerning disclosure resulted in government information about Sakhalin-2 being released. Parliamentary evidence records that two hearings confirmed that departmental responses expressing serious environmental concerns should be disclosed in the public interest.

Those proceedings concerned government transparency and the handling of potential export-credit support.

They did not determine:

• whether Sakhalin Energy manipulated its construction programme;
• whether personnel were coerced;
• whether contractor relationships were improper;
• whether any individual had engaged in corruption.

No judicial finding establishing those allegations has been identified.

Reassessing the Archive’s 2008 Headline

10. Were the warnings “100% correct”?

The archive article published on 6 January 2008 carried the headline:

“The Sakhalin-2 whistleblower warnings which proved 100% correct.”

Under the present evidential methodology of The Shell Leaks Files, that description requires qualification.

What was vindicated

The source predicted that the December 2007 pipeline target was not achievable and that completion would extend into 2008.

The official chronology supports that prediction.

The source also portrayed the project as suffering from schedule pressure, weak confidence and management strain. Greer’s authenticated email provides meaningful contemporaneous support for that general description.

What was not proven

The surviving evidence examined here does not prove:

• deliberate fabrication of project information;
• systematic coercion of specialists;
• an organised attempt to transfer blame;
• improper financial or personal relationships with contractors;
• corruption involving Starstroi or SU4.

The accurate archival conclusion is therefore:

The whistleblower’s central scheduling warning was materially vindicated. The accompanying allegations of misconduct remain unproven.

Correcting that distinction does not weaken the archive.

It strengthens it.

Historical Analysis

The importance of the 2007 warning lies partly in its timing.

It was published before the December deadline had passed, before the pipeline’s completion slipped into 2008 and before the LNG plant entered service in 2009.

It was therefore predictive rather than retrospective.

That gives the schedule warning genuine historical weight.

At the same time, accurate prediction does not automatically validate every accompanying allegation. A source may be correct about engineering progress and mistaken—or insufficiently informed—about motive, misconduct or contractual relationships.

Documentary analysis must resist the temptation to treat a partly vindicated source as infallible.

The proper method is claim-by-claim assessment.

Commentary

The whistleblower’s most dramatic assertion was that Sakhalin Energy’s management could no longer control the project.

That statement cannot be established as an objective fact.

But the record does show a project whose internal timetable had become deeply contested, whose pipeline personnel required an extraordinary motivational intervention, whose completion moved beyond the disputed December target and whose senior project director departed during the resulting public controversy.

In ordinary corporate communications, those elements would have appeared separately:

• a revised completion date;
• a management departure;
• a construction update;
• a reassuring statement about eventual delivery.

The leaked material connects them.

It reveals that the delay was not merely an external surprise announced after the event. Someone claiming detailed knowledge of the project had warned in advance that the programme was not achievable.

That is precisely why contemporaneously preserved whistleblower material matters—even when it must be handled with caution.

Evidence Assessment

Existence and date of the whistleblower statement: Confirmed by contemporaneous website publication and archive preservation.

Identity and employment status of the source: Not publicly established.

Prediction that pipeline completion would extend into 2008: Supported by official and contemporaneous project records.

Description of management pressure and low confidence: Partially supported by the authenticated Greer email.

Claim that project information was fabricated: Not proven.

Claim that personnel were coerced into approving the programme: Not proven.

Allegations concerning Starstroi and SU4: Recorded by WWF in parliamentary evidence, but not judicially or independently established.

Court findings on the whistleblower accusations: None identified.

Document Integrity Statement

This archive file deliberately separates:

• authenticated corporate documents;
• anonymous insider allegations;
• official project milestones;
• contemporaneous reporting;
• parliamentary evidence;
• court-record context;
• historical inference;
• editorial commentary.

The fact that one prediction was vindicated has not been used to authenticate unrelated allegations.

The archive’s earlier “100% correct” characterisation has been reassessed in accordance with the more rigorous evidential standards now applied by The Shell Leaks Files.

Sources and Documentary References

Primary and archival material

• Confidential whistleblower statement published on 2 June 2007 and republished on 6 January 2008.
• Authenticated David Greer “Pipeliners All!” email, 18 April 2007.
• Hans Bouman–Engel van Spronsen internal correspondence concerning Sakhalin design and schedule risks.

Official project records

• Gazprom project review recording that onshore pipelines remained under construction in January 2008.
• Sakhalin Energy records concerning first gas and late-2008 commercial development.
• Gazprom record of the LNG plant entering service in February 2009.

Contemporaneous reporting

• Reports of pipeline completion and commissioning in November 2008.
• Reuters, Itar-Tass and The Moscow Times reports concerning delays to LNG completion and exports.

Parliamentary and court-record context

• WWF memorandum to the House of Commons Environmental Audit Committee, 20 June 2008.
• Parliamentary account of the proposed judicial review and disclosure proceedings concerning ECGD’s handling of Sakhalin-2.

Related Archive Files

• SLF-2007-011 — The Sakhalin Papers I: How Internal Documents Became Geopolitical History
• SLF-2007-012 — The Sakhalin Papers II: The Cost Escalation That Changed Everything
• SLF-2007-013 — The Sakhalin Papers III: Environmental Inspections, Regulatory Pressure and the Battle for Control
• SLF-2007-014 — The Sakhalin Papers IV: Behind Closed Doors — Internal Communications During the Crisis
• SLF-2007-015 — The Sakhalin Papers V: The Gazprom Agreement — How Control of Sakhalin-2 Changed Hands
• SLF-2007-016 — The Sakhalin Papers VI: After the Deal — “Pipeliners All!” and the Internal Record of Shell’s Response

Archivist’s Note

An archive should not merely preserve old conclusions. It should test them.

The whistleblower’s prediction about the project timetable proved substantially accurate. That deserves to be recorded.

The more serious allegations were never established to the same evidential standard. That must also be recorded.

The credibility of The Shell Leaks Files depends upon preserving both parts of that conclusion.

About The Shell Leaks Files

The Shell Leaks Files is an independent documentary archive preserving authenticated historical material relating to Royal Dutch Shell plc, Shell plc and associated companies.

The archive applies a consistent methodology based upon provenance, contemporaneous corroboration, official records and the explicit separation of documentary fact from allegation, inference and commentary.

Next Archive File

SLF-2007-018 — The Sakhalin Papers VIII: The Story Shell Wanted “Killed” — Internal Emails, The Sunday Times and the Battle to Contain the Sakhalin Narrative

The next instalment will examine authenticated Shell correspondence concerning a proposed Sunday Times investigation into the Donovan archive’s role in the Sakhalin-2 crisis.

It will reconstruct what the newspaper intended to publish, Shell’s internal discussion of applying pressure to stop the article, what subsequently happened—and the limits of what the surviving documents allow us to conclude.