The Independent Lens
Independent review that turns unresolved findings into decisions — settled on design ground, at the point where they still cost least.
A project can pass every review it is required to pass and still carry its hardest questions into commissioning.
Major projects undergo HAZOPs, design reviews, technical authority checks, peer reviews, regulatory inspections, vendor audits, pre-commissioning reviews and numerous discipline-specific assessments. Yet significant questions still reach late project stages unresolved.
What is often missing is a sufficiently independent view across the boundaries between engineering, compliance, project execution and future operation. A review works well inside the scope it was given. Far fewer are set up to read across those scopes and say what the combined result means for the decision now in front of the project.
A finding that surfaces late is never only a technical question. By then it comes with:
- a design already substantially developed;
- equipment that may already have been procured;
- interfaces divided across Owner, EPC, licensor and vendors;
- incomplete or conflicting requirements;
- schedule pressure;
- uncertainty over contractual responsibility; and
- a decision whose technical and commercial consequences are now connected.
At that point, identifying the deficiency is only the beginning. The real assurance question becomes:
What actually needs to change, why, how far, by when, and who carries the obligation?
Independence is not simply distance from the project or its parties.
Robust assurance requires enough technical depth to understand why decisions were made, while retaining enough distance to challenge whether those decisions remain defensible. Our role is neither to reproduce the EPC’s engineering nor to replace the Owner’s technical authority. It is to bring clarity where the two disagree, and to give a gate the independent reading it needs before the project moves past it.
That requires multidisciplinary experience across design and operations, Owner and Contractor organisations, project execution and process safety. Five cases also have to be kept apart. Findings routinely treat them as one.
An independent reviewer creates value not by generating more findings, but by reducing uncertainty around the decisions that matter.
Every material finding is examined through three distinct lenses.
They inform one another, but they are deliberately not allowed to answer one another’s questions. A commercial pressure is not allowed to settle a technical question. The relationship is not symmetrical, though: a technical conclusion will often create a contractual consequence, and it should be allowed to.
See how each lens is applied
01 Engineering Safety
What the design was meant to achieve, and whether it still does. That means the Owner’s specifications and constraints, the project safety philosophy, and the licensed or procured technologies the design was built around — because a package bought in early sets limits everything downstream has to live with.
Safeguards are read the same way. A relief device, an interlock, a procedure and a passive barrier carry different integrity requirements through life, and each drifts from the design basis by a different route: one through modification, one through an assumption that was never tested, one through obsolescence in the technology it was built on.
02 Regulatory Compliance
Conformity in the first sense is direct: what the applicable regulations, codes, standards and permit conditions require of this asset, and whether the design and its documentation actually meet them.
Then the harder dimension. Where a requirement rests on recognised and generally accepted good engineering practice, how far a finding has to be taken becomes a judgement, and an alternative that delivers the same protection may be defensible. Compliance therefore becomes a reasoned technical position, not simply a reference to a clause.
03 Contract Management
Clarifying the contract is not our role, and neither is deciding whose action an item becomes. Contracts rarely set out safety obligations in any detail. Much of designing for safety carries uncertainty, and performance-based standards leave the demonstration to the parties, so matters are left open.
What an independent reviewer can do is narrower. We identify accurately what sits clearly within one party’s remit and needs no independent judgement at all. Where it is wanted, we give feedback on which reviews the contract should place at which critical stages of the project. Before an audit that is already long overdue begins, we say what it is likely to surface, so nobody is deciding under surprise.
And where a safety-related matter is already in dispute, we establish the technical findings and stop there, so the argument can continue on a technical basis. The rest belongs to the parties.
Timing determines the value of independent review.
The same technical concern can have fundamentally different consequences depending on when it is identified.
FEED
Challenge the design basis, major safety decisions, technology assumptions and project specifications while alternatives remain open.
EPC
Test whether requirements have been correctly translated into systems, packages, calculations, specifications and safety-critical functions. Control technical deviations, vendor interfaces and departures from the approved design basis before they become embedded in equipment and construction.
Pre-Commissioning
Verify that what was designed has actually been built, tested and made ready for safe operation — and that outstanding assumptions have been replaced by evidence.
Active Operation
Establish the baseline between original design intent and actual plant condition, then identify degradation, modification, obsolescence and emerging gaps against current risk and operating requirements.
Independent assurance therefore should not be a single event. It should be positioned at the points where new evidence becomes available and decisions become progressively harder to reverse.
We have designed these systems, not only reviewed them.
We have designed safeguards at the stages where they are actually shaped, so we know what integrity each one has to hold across its life and where it falls short of the design basis. We do not audit a single safeguarding philosophy, or the design documents attached to it. We look at the safety of the plant as a whole.
01 What can still change, and when?
Which modification the design can still absorb at this phase, and which one has already passed the point where it is worth making.
02 If it cannot, what replaces it?
Where the original change is no longer practical, the alternative that delivers the same protection — and the technical argument that makes it defensible.
03 Who acts, and when does it cost least?
How the work divides across Owner, EPC, licensor and vendors, and the point in the schedule at which each action is cheapest to take.
We give a project a strategic route through its gaps, so that debate is settled on design ground and a rational, cost-effective decision can be made.