Very few industrial assets are engineered by the organisation that ends up owning them. A refinery, a substation, a production line or a packaged system is designed by a contractor, detailed by subcontractors and built from equipment supplied by dozens of vendors. The owner writes the requirements, approves the milestones and pays the invoices.
This model works. It lets owners draw on specialist capacity they could never hold in-house, and it is how most large industrial work gets delivered.
But it hides an uncomfortable fact. When the asset is handed over, the contractor moves on to the next project. The owner is the one who operates it, answers to regulators and customers for it, and lives with every requirement that was quietly missed along the way.
The engineering was outsourced. The accountability was not.
Why accountability doesn’t transfer with the contract
Outsourced engineering changes who performs the work. It does not change who answers for it. The contract moves scope, schedule and liability for delivery; it does not move the obligation to be satisfied that what was delivered meets what was required.
Contracts are good at moving work from one party to another. They define scope, set the schedule, allocate commercial risk and specify what the contractor must deliver. What they cannot do is change who ultimately answers for how the asset performs.
A contract can move the work. It cannot move the consequence.
Liability clauses and warranties matter, but they are remedies after the fact. They help recover cost. They do not restore the schedule, undo an operating restriction or repair a reputation. For the owner, the only real protection is knowing, before acceptance, that what was delivered meets what was required.
Why engineering governance matters in outsourced projects
Most owners govern the relationship rather than the content. Engineering documentation management tells you a deliverable arrived and was filed. Engineering requirements management tells you what was asked for. Neither establishes that the thing delivered meets the thing required, which is the gap governance has to close.
Most owners do not leave delivery unsupervised. They run stage gates, maintain document registers, require vendor document submissions and sign off deliverables at agreed milestones. Owner's engineers review critical packages and sample the rest.
All of this is valuable, and almost all of it governs process. It confirms that the right documents arrived, at the right time, and that someone reviewed them. It is much less consistent at confirming that the engineering content of each deliverable meets the owner's own standards.
That is not a lack of diligence. It is a question of scale. A single project can involve thousands of deliverables from many contractors and suppliers, while the owner's technical team is a fraction of the size of the delivery team. Sampling is the only option when every check depends on a person reading every page.
What happens when engineering accountability becomes unclear?
The gap rarely comes from one large failure. It builds up in three quieter places.
- Interpretation at every tier. The contractor reads the owner standard and writes its own specification. The supplier reads that specification, not the owner standard. Each reading is reasonable, and each one moves the requirement slightly further from where it started.
- Equivalence and substitution. "Or equal" clauses, contractor house standards and supplier alternatives all invite substitution. Some substitutions are genuinely equivalent. Others meet the contractor's standard but not the owner's, and nobody on the delivery side is asked to tell the difference.
- Evidence held by someone else. When a deliverable is accepted, the reasoning behind the acceptance often lives in the contractor's records or a reviewer's inbox. Years later, when a question arises, the owner is accountable for a decision it cannot fully show.
Illustrative example
An owner standard requires a specific protection rating for instrument enclosures in washdown areas. The contractor's specification accepts a lower rating as equivalent, based on its own house standard. The supplier provides enclosures to the contractor's specification, the contractor's quality team approves them against the same document, and the owner's sampled review does not include that package. The mismatch surfaces at commissioning, when the enclosures are already installed. Every party met the requirement it was given. The owner's requirement was not met.
How engineering assurance supports accountability
The owners who close this gap do not take the work back in-house. They change what they govern.
- They make their standard the governing referenceFor every project, the owner declares which standards, specifications and addenda apply, and in what order they take precedence. Contractor house standards can add to the owner standard, but they never quietly replace it.
- They check content, not just submissionAt each handoff, deliverables are confirmed against the governing requirement itself, not only logged as received, reviewed and signed.
- They keep the evidence on their sideEvery finding records the clause it was tested against, the source it came from and the decision taken, held where the owner can show it later.
- They keep engineers in the decisionTechnology widens coverage far beyond sampling, but rulings on deviations, substitutions and acceptance stay with named owner engineers.
Owners do not need to redo the contractor's work. They need to be able to show it meets their standard.
This is what engineering assurance looks like from the owner's side of the contract: the owner's requirements as the reference point, checked at every handoff, with evidence that stays with the party that carries the accountability.
Who owns engineering project accountability?
It would be easy to read all of this as owners tightening control. In practice, the whole delivery chain gains from it.
When the governing requirements are explicit and checked early, contractors find out about a mismatch while it is still cheap to fix, not at commissioning. Fewer deliverables are rejected late. Fewer disputes turn on whose interpretation was right. And a contractor or supplier that can show, with evidence, that its work meets the owner standard is in a stronger position for acceptance, payment and the next contract.
The accountability gap is not good for anyone. It just lands hardest on the owner.
Five questions to ask before outsourcing engineering work
There is a simple question every owner can ask of a recently accepted package: if a regulator, a customer or a court asked how you confirmed this met your standard, what would you show them?
If the honest answer is a transmittal record and a signature, the work was governed but not assured. Outsourcing the engineering was the right decision. Assuming the accountability went with it is the risk.
For the discipline behind this, read Engineering Assurance: Diving into What Has Been Missing Between Requirement and Release.
