“Project Management for Oil and Gas: A Practical Guide”

What is project management for oil and gas?

Project management for oil and gas is the planning and control of capital projects and operational shutdowns across upstream, midstream, and downstream assets, from concept selection through first production and handover to operations. It combines classic scope, cost, and schedule control with process safety, regulatory approval, and production economics.

The output is not a building or a product line. It is a producing asset with a production profile, an operating cost, an abandonment obligation, and a safety case. Delivering on budget but missing nameplate throughput is still failure.

Why is oil and gas project management different from other capital projects?

Four structural differences separate it from general construction or infrastructure work.

Capital is committed before the design is complete. Final investment decision (FID) is taken at a point where engineering is typically 60–80% complete at best. The owner is therefore buying a large amount of uncertainty and must price it into contingency rather than pretend it away.

Process safety is a design constraint. Flare radiation, blast overpressure, escape routes, fire protection, and hazardous area classification shape the layout before cost optimization begins. Retrofitting a safety requirement after detailed design is one of the most expensive changes a project can make.

Contractors deliver most of the work. Engineering, procurement, fabrication, installation, and commissioning are usually split across multiple contracts in different countries. Interface management becomes the dominant risk, and the owner’s team is small relative to the total workforce.

The asset must keep running. Brownfield work happens inside a live plant, with simultaneous operations, permit-to-work systems, and production targets. A tie-in that takes six hours longer than planned can cost more than the engineering that designed it.

What are the stage gates in an oil and gas project?

Stage gates convert a long capital cycle into a sequence of decisions with defined deliverables. The exact names differ between operators, but the logic is consistent: assess the opportunity, select the concept, define it, execute it, then operate it.

Two disciplines keep the gates meaningful. The first is that each gate has a defined owner who can say no. A gate that only ratifies the previous decision is a reporting milestone, not a control. The second is that the estimate class must match the gate. Approving FID on a Class 4 estimate is a decision to fund optimism.

How accurate should an estimate be at each stage?

Estimate accuracy improves as engineering matures, and the ranges below follow AACE International’s classification. They are ranges, not guarantees — a well-run Class 3 estimate is still wrong by design.

The practical consequence is contingency sizing. On a project with a Class 3 estimate of $800 million mid-point, a P90 outcome can sit $160–240 million above the mid-point. If the funding request is built on the mid-point, the project is underfunded from the day it is approved.

A worked example. An $800 million mid-point estimate carries a 15% contingency ($120 million) for a Class 3 range of −15% / +25%. At the P90 end, the exposure is $800M × 0.25 = $200 million, leaving an $80 million gap. Either the contingency rises to 25%, or the scope is descoped by $80 million before FID. Both are legitimate; approving the project and hoping is not.

How is HSE managed as part of project delivery?

HSE is managed through design, contract, and leading indicators, with lagging data used to verify rather than to manage. The industry’s own benchmark shows why lagging data alone is insufficient: IOGP’s 2024 safety performance indicators record 32 fatalities in 21 separate incidents among member companies, a fatal accident rate of 0.77, a total recordable injury rate of 0.81, and a lost time injury rate of 0.24.

Those numbers matter in three ways:

• They set the contract bar. Contractor selection must include HSE performance history, supervision ratios, and a bridging document that reconciles the contractor’s management system with the owner’s.
• They drive design reviews. HAZID at concept, HAZOP at detailed design, and a safety integrity level assessment for instrumented functions. Each review needs a close-out log with owners and dates, not a signed attendance sheet.
• They shape construction planning. Simultaneous operations, confined space entry, lifting operations, and hot work in live plants need permits, isolation certificates, and gas testing that are scheduled as activities, not as paperwork around activities.

Leading indicators worth tracking weekly include permit audit completion, safety observation frequency and closure, isolation errors caught, overdue corrective actions, and subcontractor induction coverage. A project with a falling TRIR and a rising backlog of overdue safety-critical actions is not a safe project; it is a lucky one.

How do FEED and FID gates protect the project?

FEED defines the scope tightly enough to price and execute it, and FID is the point where the owner commits capital against that definition. Skipping or compressing FEED feels like schedule savings and almost always becomes a change-order program.

A credible FEED package includes the design basis, process flow diagrams, P&IDs at the required maturity, equipment lists and datasheets, plot plan, utilities and offsites, execution strategy, schedule, cost estimate, risk register, and the HSE studies that demonstrate the design is safe. FID then tests readiness: is the estimate Class 3 or better, are long-lead items quoted, is financing closed, are permits on track, and has operations signed up to the production profile?

Design changes cost far less during detailed engineering than during construction, when they trigger rework, rescheduling, and site disruption. A piping layout change that costs $40,000 in engineering can cost $400,000 once spools are fabricated and shipped.

A worked example. A project spends $32 million on FEED and then discovers at FID that the export pipeline route requires an additional 12 kilometres of line and two crossings, adding $45 million. Because the discovery happens before detailed design, the estimate is revised, the schedule absorbs four months, and contingency covers the cost. The same discovery during construction would add rework, delay first production, and consume contingency already allocated to construction risk.

How do you manage long-lead equipment?

Identify long-lead items during concept selection, obtain budgetary quotes during FEED, and place orders as early as the design allows — often before full FID through limited notices to proceed. The schedule is then built around the equipment delivery dates rather than adjusted after they slip.

Lead times vary by backlog and specification, and have stretched in recent years. Don’t memorize the table; keep a vendor enquiry log with quoted lead times, order status, inspection milestones, and float per package.

A worked example. A compressor package slips four months on a project designed for 20,000 barrels of oil equivalent per day. At a netback of $65 per barrel, deferred revenue is 20,000 × 65 × 120 days = $156 million. The compressor’s price might be $28 million. The commercial argument for spending $2 million on expediting, a second fabrication slot, or an early preservation and storage program is easy to make — and it has to be made before the slip, not after.

How do you plan a shutdown turnaround?

A turnaround is a project with a fixed window, a frozen scope, and an economic penalty per day. Start with lost throughput, not the labor budget. A 120,000 barrel per day refinery running a 45-day turnaround at a $70 margin per barrel gives up 120,000 × 45 × 70 = $378 million of margin. Each day of overrun costs $8.4 million. That figure determines how much engineering, planning, and contractor supervision is justified, and it explains why turnarounds are managed with the same gate discipline as capital projects.

The sequence that works:

1. Scope challenge, 12–18 months out. Every work order is challenged on condition, risk, and cost. Scope that is not frozen at the agreed gate will be discovered on the critical path.
2. Integrated schedule, 9–12 months out. Merge operations, maintenance, inspection, and capital work into one schedule with a single logic. Most turnaround overruns are integration failures, not execution failures.
3. Contractor strategy, 6–9 months out. Award against a defined scope with productivity assumptions stated. A low rate with an undefined scope is not a saving.
4. Readiness review, 60 days out. Materials on site, scaffolding plan, permits, isolation lists, and a tested cost and schedule baseline.
5. Daily control during execution. One plan, one progress curve, one decision log, and a daily cost of delay stated at the morning meeting.

What do schedule and cost performance look like in numbers?

Consider a $1.2 billion greenfield gas processing project with a 30-month execution schedule. Engineering is $96 million (8%), procurement $720 million (60%), construction $300 million (25%), and commissioning and contingency $84 million (7%).

If procurement is the largest line, it is also the largest schedule lever: a 10% slip in the delivery of the two largest packages adds roughly three months to mechanical completion. At a deferral cost of $40 million per month, that slip costs $120 million — 10% of the total project cost, from a delivery variance that never appears in the cost report as an overrun.

Now test the cost side. A 5% overrun on construction ($15 million) is visible, escalates through change orders, and attracts management attention. The same $120 million of deferred production is invisible in the capital cost report, which is exactly why project managers must report schedule and production impact in the same dashboard as cost.

What trade-offs are unavoidable in oil and gas projects?

Standardization versus optimization. Reusing a proven design shortens engineering and reduces risk; optimizing for this reservoir or this site can add value but consumes schedule and engineering capacity. Standard design is usually right when the schedule is tight; optimization is right when the margin per unit is high and time is available.

Local content versus delivery certainty. Local fabrication and employment can be contractual or regulatory requirements, but capability and capacity vary. The trade-off should be priced: a local fabrication package that adds four months may still be the right choice, but the cost must be in the estimate rather than discovered later.

Brownfield tie-in versus new build. Brownfield avoids new permits and leverages existing infrastructure but carries simultaneous-operations risk and unpredictable existing conditions. New build is cleaner to execute but slower to permit and more capital-intensive.

Compression versus contingency. Compressing FEED or skipping a design review saves months now and usually costs more later. The honest way to take that trade-off is to reduce scope, not to reduce definition.

What mistakes derail oil and gas projects most often?

1. Approving FID on a Class 4 estimate. The project is funded below its own uncertainty range from day one.
2. Treating HAZOP as a formality. Actions are logged but not costed, and the design proceeds with open safety findings.
3. Discovering long-lead items after the schedule is baselined. The schedule then becomes a record of the slip rather than a plan.
4. Splitting work across too many contracts without an interface owner. Every interface between contractors is a place where responsibility evaporates.
5. Planning turnarounds on labor hours instead of throughput loss. The wrong number drives the wrong decisions.
6. Handing over to operations without a performance test. Nameplate capacity becomes an assumption rather than a verified fact.

How does Doitify support oil and gas project delivery?

Oil and gas projects generate an unusual amount of structured coordination: gate deliverables, vendor inspection milestones, interface registers, HSE action close-out, and turnaround work packs. Doitify is an all-in-one platform for project management, team management, and goal achievement that lets an owner’s team hold those in one workspace — multi-level tasks and sub-tasks for work packs, WBS dependencies for the integrated schedule, Gantt and Kanban views for planning and execution, checklists for gate readiness and permit compliance, risk and constraint logs, document control, and workload views across a contractor-heavy team.

The realistic use case is not replacing the EPC’s scheduling system. It is giving the owner’s project team a single view of gate readiness, vendor deliverables, and action close-out so that decisions are made from current data rather than from the last consolidated report.

*Disclosure: Doitify is our product. It supports planning, tracking, and reporting; it does not replace engineering, process safety, or contract expertise.*

Conclusion

Project management for oil and gas is the discipline of committing capital in the right order and defending the assumptions behind it. Gate the estimates, fund the uncertainty, order the long-lead items early, treat HSE as design work, and price turnaround days in lost production rather than labor hours. The projects that succeed are not the ones with the fewest problems; they are the ones where the problems were visible early enough to be affordable.

If this post on project management for oil and gas was helpful, you might also enjoy WBS vs Project Plan: What’s the Difference? and Project Integration Management Explained.