A project change can look clean on paper. The estimate is updated.

A project can look controlled on paper while drifting in the field. The Level 3 schedule is approved.

A project can look complete on paper and still be dangerously incomplete in practice. The dossiers are submitted.

Large capital projects rarely fail because boards lacked reports. They fail because leaders did not see risk early enough, did not believe the signals they saw, or did not have a reliable way to compare today’s project with the hundreds of projects that came before it.

A major project rarely finishes as the project that was first modelled. The plot plan changes.

On a long-running capital project, one of the most expensive questions is also one of the simplest: why did we decide that? The team can usually find the answer to what was decided.

A risk register can look healthy while the project is quietly losing control. The column is filled.

Carbon on an EPC project does not sit neatly in one department, one contract, or one emissions scope. It moves through design decisions, purchase orders, temporary power plans, fabrication yards, chartered vessels, commissioning fuel, and supplier data systems.

A project rarely loses control of scope in one dramatic moment. More often, it happens through small acts of accommodation.

Major project trouble rarely arrives without warning. It usually appears first as a collection of small, explainable, easy-to-dismiss changes: a technical query that takes longer than normal, another nonconformance report on a familiar detail, a supplier that stops giving firm delivery dates, a construction supervisor who quietly adds weekend shifts to hold the plan together.

A project can fail even when every major contractor claims to be on plan. Engineering can hit its deliverable dates.

Major projects rarely fail their environmental obligations because nobody made any promises. They fail because the promises were made early, recorded in many places, and then treated as background information while the project moved on.

A project can survive a bad meeting minute. It may not survive a lost decision.

A project can carry biodiversity risk long before the first excavator arrives. The risk often sits in a folder labeled “ecology,” backed by surveys that were sound when completed but no longer describe the site.

AI can now draft a contract clause, flag a procurement anomaly, summarize a HAZOP action log, forecast cost at completion, and propose schedule recovery options in seconds. That does not mean it should be allowed to approve a variation, release a purchase order, accept a safety risk, or instruct a contractor.

On a major project, waiting rarely looks dramatic. A crew stands by for a permit.

A project can look healthy right up to the point where it cannot be integrated. Engineering is on track.

Project teams rarely compress schedules because they want to. They do it because a milestone is under threat, a shutdown window cannot move, revenue is tied to first production, or a regulator, owner, lender, or joint venture partner expects the date to hold.

A capital project can be on schedule, within its approved contingency, and still be quietly moving away from the outcome it was approved to deliver. That is the uncomfortable nature of project drift .

Claims management plays a critical role in the success of oil and gas projects. These projects often face complex challenges, including tight schedules, high costs, and unpredictable conditions.