Your Safety Case Lives or Dies on Independence
Should you consider an independent review of your safety case?
Ask yourself these questions. If you answered ‘no’ to any of them, you have a gap between compliant and safe that is worth closing before your next cycle:
Has every study in your safety case (HS1 to 7, LOPA, SimOps, bowtie, QRA) been reviewed by someone who did not write it?
Can the person who chaired or checked your studies show they had no stake in the design or the result?
Is your MoPO based on a SimOps study that matches the plant as it is today?
Has every barrier on your bowtie been tested and challenged, or only drawn?
On 6 July 1988, 167 men died on Piper Alpha, an oil platform in the North Sea. It was run under the strict, rule-based safety system of the time.
Two years later, Lord Cullen’s public inquiry concluded that following those rules had never been the same as being safe. This led to their replacement by the safety case regime built on a principle bought at a terrible price. A company cannot be the only judge of whether its own risk is under control.
Thirty-eight years on, that lesson is slowly being lost on live sites across the country. Nobody is choosing to ignore it. It’s being worn down by stretched teams, retiring experts and smaller budgets.
It’s also never deliberate. It happens one small shortcut at a time, until a site is marking its own homework and calling the folder proof that it’s safe.
We have been here before. Yet we keep acting as if it were the first time.
Compliance is the floor you are already standing on
If you run an upper-tier COMAH site, your safety report is the onshore version of the same system.
Every five years, a new report lands on your desk. It is a folder four to six inches thick. It covers your whole risk management system, and your name is somewhere near the front.
The HSE expects it. You produce it. On paper, you are compliant.
But compliance is the floor, not the ceiling.
There are two different claims here, and only one of them protects you.
Compliant means the document exists and ticks the boxes. Safe means the document is right. Your hazards are understood and well managed. And the numbers behind your major accident hazard scenarios can be defended.
Process Safety Insight
A compliant safety case is a document that exists. A safe one is a document that has survived attempts to break it.
The gap between those two claims is where a major accident hazard gets missed.
That gap almost never opens because someone ignored a hazard. It opens because the team that owned the study had no time and no distance to spot its own blind spot. Cullen saw this in 1990. We have been saying it for over 10 years.
The evidence file
A safety case is not really one document. It is a bound set of evidence. Each study answers a different question, and each one is another chance to get the answer wrong.
These studies are judgements, not box-ticking. The whole case is only as strong as its weakest judgement.
HS 1-7
HS1 to 7 are the seven stages of hazard study. They run from the first design idea through to decommissioning.
They are the backbone of the file. The early stages matter most, because mistakes build on each other.
A wrong assumption at the concept stage is carried into every study after it. The people who made it are the least likely to go back and check it, because everything they have built since depends on it. Catch it at HS1 and it is a conversation. Catch it at commissioning and it is a rebuild.
Functional Safety/LOPA
Functional safety asks two questions. How much protection is enough? And does the protection you chose do the job?
This is where LOPA (layer of protection analysis) comes in. So do the safety requirements specification and SIL determination and verification. SIL stands for safety integrity level, the standard a safeguard has to meet.
The whole exercise protects you against wishful thinking. It is easy to count a safeguard as independent when it quietly shares a sensor with three others. It is just as easy to assume a trip will work on demand because it worked on the drawing.
LOPA is where believing a trip will work is separated from proving that it will. That is a hard line to draw about your own design.
SimOps & MoPO
SimOps means simultaneous operations. It stops a tight, busy site from becoming its own worst enemy. Picture a 50 tonne vessel being lifted into place right above a team working below. SimOps decides which of those two jobs can happen at the same time, and which cannot.
The result is the MoPO, the matrix of permitted operations. This is where a study stops being paper and starts telling people what they are allowed to do. A decision made in a meeting becomes a permission on the floor. If the decision is wrong, the work procedure built on it is wrong too, and a crew ends up standing under the consequence.
Bowtie
Bowtie analysis is the diagram the whole industry uses to see risk at a glance. The knot in the middle is the top event, the thing that must not happen. In oil and gas, there is in practice only one: loss of containment. If the product stays where it should be, it is safe. If it gets out, you have an environmental problem at best. If it meets an ignition source, you have fire and explosion.
On the left side of the bowtie are the barriers that stop the top event. On the right are the barriers that limit the damage if it happens anyway.
A bowtie is only honest if those barriers are real. It is easy to draw a barrier that exists on a P&ID and never ask if it is tested, maintained, and would hold on the day. A barrier nobody has challenged is a line on a diagram, not a defence.
PAER
The industry has a short way to describe who and what that damage hits. PAER stands for people, assets, environment and reputation. Reputation is the one people underrate, until they watch a share price fall after an incident and never fully recover.
More sites are now run remotely, so a fifth letter is earning its place. S, for security. A control system that someone can reach over a network is now a real route to the same top event.
QRA
QRA, or quantitative risk analysis, turns the safety case into numbers. And numbers are more convincing than words.
QRA makes up most of the safety case. It is also the part a regulator reads most closely, because a confident number can hide a weak assumption. Change the chance of ignition or the number of people exposed, and the answer changes with it. Whoever built the model chose those inputs.
A QRA turns judgement into evidence. That is exactly why someone has to be able to defend the judgement behind it. A number is a model, not a measurement. It is only as good as the data that goes into it. So the checking that holds up is the kind that can stand behind the data under the model, not only the model itself.
Process Safety Insight
Every study answers a different question. The case only holds up if each one survives being read by someone who did not write it.
Who is allowed to mark the homework
Most of that evidence is produced by people who are very good at engineering and who have a direct stake in a clean result.
EPCs are the engineering, procurement and construction contractors who design and build on the operator’s behalf. They have more engineering skill than anyone. They can size the vessel, design the relief system and lay out the whole rig.
What they cannot do, under the regulations, is run the safety studies that check their own design. That is the whole point of the rules. You do not let the people who built something certify that it is safe.
This is more than good practice. And offshore, it is the law.
Under the 2015 offshore safety case regulations, the operator must run a verification scheme. In it, an independent competent person confirms that the safety-critical parts of the installation are sound, and stay sound for its whole life. That person must be independent enough from whoever is responsible for the thing being checked. The law does not trust the duty holder to mark its own work, and it says so plainly.
So the studies go out to tender. An independent party comes in to chair them, review them and put their name to them. “Marking your own homework” is not our phrase. It is the phrase that stuck to the building industry after Grenfell, where the system had been left to check itself. The failure is the same. Only the hazard is different.
The weak point is how the work is awarded. The EPC is tied to a contract, so its instinct is to give the verification to the lowest bidder, the same way it would for steel or scaffolding. For most line items, that is good sense. For the one study that confirms the risk is under control, it is exactly the wrong way round.
The cheapest name on the page is often a lone contractor. There is no second reviewer behind them, no team to escalate to, and no liability insurance behind their signature.
It is your risk, not the EPC’s.
You should care who signs it off, not only what the signature costs. But going the other way is no safer. The biggest name in the room is not always the most independent. Paying more, or getting a report on grander letterhead, does not make the check any more independent from your design. What you are paying for is a reviewer who is independent enough to fail your case, and senior enough to make that failure stick.
Independence is not an optional extra added to the process. It is the load-bearing wall. This is the work we do. Not the design, not the engineering, but the verification. We look over the shoulder of what is being proposed. We ask the questions the people in the room are too close to ask.
In practice, it is change management for the whole risk picture, at every stage from concept to decommissioning.
On the work that matters, the operator does not accept the EPC’s choice. It picks the chair itself.
Not the firm, the person.
One of our consultants was vetted and approved to chair these studies for a global operator. At the time, only a handful of people in the country held that approval. The operator asked for our consultant by name, over whoever the EPC would have put forward.
When the client picks the referee instead of the contractor, the regulation is working exactly as it was meant to. That kind of approval is slow to earn and hard to copy, and that is the point.
Let us guide your Process Safety Strategy
What every disaster teaches
The pattern behind Piper Alpha, Texas City and Grenfell is older than any of them. It keeps repeating for three reasons.
It fails slowly, then all at once. The gap rarely announces itself. Take a MoPO based on a SimOps study from three or four years ago. It still sets who can work where, and when. Since then, the plant has changed. A new tie-in was added on one side. More product is being pushed through the same line. A walkway was moved to make room. Each change was small and sensible. None was big enough on its own to trigger a new study. But the matrix still allows a lift over ground that the walkway now crosses. The crew reading the permit has no reason to doubt it. The people who could spot the mismatch wrote the matrix and have not looked at it since. Someone independent, walking the floor with the matrix in hand, can spot it in an afternoon. The site team has walked past it for three years. For a long time, nothing happens. Until the day it does.
The gap is capacity, not competence. Your team is already behind. The review backlog on a live site is never zero. The people who held the basis of safety for half the units are retiring, and their knowledge is leaving with them. Asking that same team to also be the calm, independent second pair of eyes on its own case is asking for the two things it has least of. Distance and time.
Independence is the part nobody can fake. An operator can hire the same engineers as anyone else. What it cannot create in-house is a reviewer with nothing to gain from the answer. That reviewer has no stake in the design, and no software or method of their own riding on the result. That is the real value of the signature. A safety case that a regulator, an insurer or a court cannot pull apart is never one written only by the people racing the deadline.
What the folder is really for
Piper Alpha did not teach this industry that oil and gas is dangerous. Everyone already knew that. It taught us that the danger lives in the gap between compliant and safe. And the only thing that reliably closes that gap is a name on the case that has nothing to gain by looking away.
Your name is already on the front of the folder. Before the next cycle comes round, ask yourself whose independent name is behind it. And would that name hold up if someone asked them to justify it?
Compliance gets you the document. Independence is what makes it defensible. Only one of them will stand next to you when it is tested.
Table of Contents




