Reality Check
Stop Pretending Risk Disappears
Oil & gas projects don’t fail because risk exists. They fail because owners pretend it doesn’t—by pushing it onto contractors, confusing insurance with mitigation, and protecting dates instead of flow.
“You can outsource execution; you cannot outsource uncertainty.”
For decades, the industry has tried to make risk disappear through contracts. Lump-sum wrappers, indemnities, warranties, caps, and exclusions get stacked like talismans to ward off reality. Then the surprises arrive: an uncharted utility, a permit that drifts, a weather window that closes, a tie-in that won’t align with operations. Suddenly the model breaks, relationships sour, claims swell, and the schedule bleeds.
This is not a morality tale. It’s a management failure. Risk belongs where the levers are—where someone can actually reduce its likelihood or consequence at the lowest total cost. That means getting allocation right, financing it intelligently, and building systems that preserve flow across interfaces.
Put risk where levers exist.
Use insurance wisely.
Protect interfaces, not dates.
Myth #1
“Push the risk down.”
You can transfer liability. You cannot transfer uncertainty. When owners try to dump uncontrollable risk on vendors, the market responds rationally: higher prices, thicker exclusions, more claims, and less competition. What you’ve done is swap manageable variability for a certainty of adversarial behavior.
“A lump-sum without mature scope is just a pre-paid claim.”
Principle
Control = Ownership
Risk ownership belongs to the party with the information and levers: who sets the data, governs access, holds the interfaces, and can actually change outcomes. That ownership must be explicit in both the risk register and the contract.
- Weld rejection rates → contractor: their procedures, supervision, and NDT.
- Late Permit to Work due to operator rules → owner/PMC: your governance, your clock.
- Differing site conditions relative to the baseline survey → shared, with a clear DSCDSC: Differing Site Conditions clause specifying relief when actual site conditions materially differ from baseline data.clause: owner warrants the baseline; contractor gets defined relief for truly differing conditions.
When accountability is misallocated, you pay for the risk twice: once in the tender premium and again in claims.
Financing vs Reduction
Insurance Isn’t Mitigation—It’s an Invoice
Insurance changes who pays when things go wrong; it doesn’t make those things less likely to happen. It’s risk financing, not risk reduction.
Mitigation reduces probability or impact. In oil & gas, that’s HAZID/HAZOP, LOPA and QRA, disciplined vendor qualification, FAT, SAT, design margins and redundancy, constructability reviews, realistic weather windows, and genuine schedule buffers. Use insurance CAR/EAR, third-party liability, professional liability, marine cargo) alongside—aligned with your indemnities and caps—so you don’t create gaps or double-pay.
“Insurance lowers pain, not probability.”
Contracting
The Lump-Sum Lie
Lump-sum EPCC works only when scope is mature, site risks are bounded, and interfaces are under control. Otherwise, it incentivizes optimism, paperwork, and legal creativity. The antidote is boring but powerful: FEED quality, data warranties, DSC clauses, relief events, and priced options for scope growth. If uncertainty is substantial, target-cost with gainshare/painshare is frequently cheaper in total and much faster to correct when reality shifts.
Warrant & verify data.
Define, trigger, trace.
Buy truth early.
Offshore Reality Check
Knock-for-Knock Needs Brains
Knock-for-knock regimes apportion liabilities cleanly, but they don’t magic away hazards. Pair them with bow-tie thinking and barrier health KPIs. Know which threats you are preventing, which barriers degrade under pressure, and how you’ll detect and recover. If a barrier is critical and fragile, fund it—don’t litigate it later.
Levers that Reduce Risk
Contracting Levers That Actually Reduce Risk
Relief events provide a mechanism for time and cost relief for events beyond a party's control, such as unforeseen ground conditions or extreme weather. A Differing Site Conditions (DSC) clause specifically outlines the process for handling physical conditions at the site that are different from what was represented in the contract documents. Together, they create a clear, pre-agreed process that prevents costly disputes and litigation, protecting project health over contractual finger-pointing.
Liquidated Damages (LDs) should be a genuine, pre-agreed estimate of the damage caused by a breach, not a punitive weapon. LDs that are set unrealistically high incentivize contractors to submit excessive claims to avoid the penalty, leading to an adversarial relationship. Properly calibrated LDs, tied to a realistic delay-cost model, serve as a predictable and fair way to manage schedule risk while maintaining a cooperative project environment.
A Force Majeure (FM) clause should clearly define the events that constitute an FM, such as specific weather conditions, civil unrest, or natural disasters, and provide objective data sources for verification. It should also include a clear duty to mitigate, requiring the affected party to take reasonable steps to minimize the impact of the event. A well-defined FM clause prevents ambiguity and ensures both parties know their obligations when unpredictable, macro-scale events occur.
Using price adjustment indices for long-lead materials or commodities (e.g., steel, copper, concrete) protects both the owner and the contractor from unexpected market volatility. This mechanism avoids the need for constant renegotiation and prevents the contractor from building in a large risk premium to account for future price swings. It provides a transparent, data-driven way to handle inflation or deflation, stabilizing the project's financial model.
A "fitness-for-purpose" obligation requires the contractor to ensure the final product is suitable for its intended use, regardless of the quality of the owner's supplied data. A "skill & care" obligation, on the other hand, only requires the contractor to perform their work with professional competence. Applying a fitness-for-purpose clause in a contract with immature scope or poor data quality forces the contractor to take on the owner's design risk, which they will price accordingly. A better approach is to balance the two with clear data warranties from the owner.
PCGs (Parent Company Guarantees) and performance bonds are financial instruments that provide security to the owner against contractor default. They are a form of risk financing, ensuring that if a contractor fails, there are funds available to complete the work. They do not, however, mitigate the risk of failure itself. It's crucial to understand their role: they are a backstop for financial recovery, not a substitute for robust project management and risk mitigation strategies.
An owner's data—including FEED packages, site surveys, and subsurface information—is a critical risk item. Warranting this data means the owner guarantees its accuracy, and the contractor can rely on it to develop their bid and execution plan. If the data is later proven to be inaccurate, the contractor is entitled to relief. This forces the owner to invest in high-quality data upfront, which is far cheaper than paying for change orders and claims during execution.
Governance
Make Risk Visible—or Pay for It in Arbitration
Most “surprise” claims are just invisible risks that lacked a named owner, a clause, or a buffer. Fix that with ruthless traceability:
- Top 20 risk list signed by both parties at contract award.
- For each: named Risk Owner, Action Owner, treatment plan, trigger, and a pre/post score.
- Trace each to a contract lever: clause, relief event, buffer, or index.
- If you cannot trace it, it’s an orphan risk—your future dispute.
- Escalation thresholds: define $$ and days that mandate a decision at the right level.
And keep it alive. A monthly risk forum that kills dead items and funds living ones is cheaper than a claims team.
Information Risk
Owner Data Is a Risk Item
FEED quality, survey accuracy, P&IDs, vendor datasheets, metocean statistics, and tie-in windows are not neutral. They are risk-bearing information assets. Treat them like equipment: verify, maintain, and version-control. If your data is poor, your mitigation is theatre.
“Risk lives where the levers are.”
Pin This
Oil & Gas Allocation Cheat Card
Contractor-leaning
Means & methods, supervision, welding/NDT, shop testing, subcontractor performance, logistics they plan and control.
Owner-leaning
Permits & access, third-party operators, ROW and land, data quality (FEED, surveys, tie-in windows), subsurface/product specification uncertainty, owner-driven scope change, political risk.
Shared/Mechanized
Extreme metocean (relief events + buffers), geotech beyond baseline (DSC), commodity shocks (price indices), global supply chain disruptions (force majeure with duties to mitigate).
Implementation
Implementation in the Real World: A 10-Point Plan
- Risk Breakdown Structure tuned for oil & gas (HSE, technical, schedule/constructability, supply chain, interface, regulatory, ESG/political).
- Joint risk register from FEED through EPC: Owner (A), Action Owner (R), PMC Oversight (C), Stakeholders (I). Don’t conflate accountability with who executes the task.
- Constructability and interface reviews early and often; publish an interface map with owners and due dates.
- Buffers at interfaces using Last Planner + CCPM: protect throughput, not just milestones.
- Contract-risk traceability: Every high-risk item maps to a clause or buffer before award.
- Insurance aligned with indemnities and caps; eliminate overlaps and gaps; understand what’s retained vs. financed.
- Vendor readiness: pre-award qualification, surveillance plans, FAT/SAT gates tied to risk treatments.
- Transparent change control: small, fast decisions beat “perfect” slow ones. Pair with target-cost mechanics when uncertainty is high.
- Barrier management for Major Accident Hazards: bow-ties with leading KPIs; fund weak barriers proactively.
- Leadership cadence: monthly risk forum, quarterly portfolio risk review; approve spend where it actually drops probability or consequence.
The Close
Make It Boring—or Make It Expensive
Projects don’t need more courage, heroics, or lawyers. They need boring clarity: who actually controls each risk, how the contract reflects that truth, and how the schedule protects flow rather than fantasies.
Before your next contract goes out the door, ask for three exhibits:
- Top-20 risks with named owners, treatments, triggers, and pre/post scores.
- A traceability map from those risks to clauses, relief events, or buffers.
- An interface buffer plan that shows how you’ll keep throughput under pressure.
If it’s not on paper, it’s not managed. And if it’s not managed, you will pay for it—in margin, schedule, and reputation.
Partner
Work with Ekton: Put Risk Where the Levers are
Ekton Project Analytics helps oil & gas owners and PMCs allocate risk to the party that can actually control it, protect flow at interfaces, and separate mitigation from insurance. We turn the article’s principles into implementation:
Risk Allocation Sprint (2–3 weeks)
Top-20 risks mapped to owner/action owner, contract lever (DSC, relief event, LDs, indices), and interface buffers.
→ Our Integrated Cost, Schedule & Risk Analysis program embeds Monte Carlo with CCPM/Last Planner to protect throughput—not just dates.
Contract & Data Readiness
FEED/data warranties, knock-for-knock alignment, and traceability from risks to clauses—so uncertainty isn’t “pushed down” and reborn as claims.
Capability Building
PMI-RMP Exam Prep for Oil & Gas—practical casework on allocation, barrier health, and interface risk, so teams model reality, not fantasy.