Owner's engineer or project management consultant: what is the difference?

You have a project heading toward FID, a contracting strategy half written, and two proposals that both promise to protect the owner. One firm calls itself a project management consultant (PMC), the other an owner's engineer, and the contractor's documents keep naming a third party, the engineer of record. When these roles blur, you get either a decision nobody owns or two firms reviewing the same documents and billing you for both.

The project management consultant runs the project for you. The owner's engineer tells you whether what is being designed, drilled or installed is right. The engineer of record designs it, signs for it, and usually works for the contractor.

For the basics of the role, see what an owner's engineer does. This note is about buying it.

Owner's engineer vs PMC: what is the difference?

Both sit on your side of the table, which is why they get mixed up. The difference is accountability. A PMC owns the management of delivery: schedule, cost, contract administration, interfaces between contractors, and reporting to you, partners and lenders. An owner's engineer owns technical judgment: whether the design basis is sound, whether the contractor's engineering meets your specification and standards, whether a deviation is acceptable, and whether field work matches the design.

A quick test: what would each be blamed for? Costs drifting for months before anyone says so is a project management failure. A project that finishes on time with a weak well design or subsea tie-in quietly accepted is a failure of technical assurance. The labels are used loosely, so buy by responsibility, not by title.

Both have a view on change orders. That works if each knows which question it answers: the PMC, what a change does to cost and schedule; the owner's engineer, whether it is technically sound and actually needed. A PMC measured on dates may lean toward accepting a deviation to hold the schedule, so the owner's engineer needs a direct line to you, not only the PMC's reporting line.

Where does the engineer of record fit?

The engineer of record produces the design and puts its name to it. It usually sits inside the EPC contractor or a design contractor, and its responsibility reaches beyond you, to the regulator and whoever will operate the facility. The owner's engineer checks that work for you without taking over responsibility for it.

Two things follow. First, write the owner's engineer's role as review and comment, and state that its comments do not relieve the engineer of record of design responsibility. Once your owner's engineer starts approving drawings, nobody is sure who owns the design. Second, keep the roles in separate hands: an owner's engineer that is also the engineer of record on the same scope is reviewing its own work. The same logic applies to contractors: see owner's engineer vs EPC.

When is one enough, and when do you need both?

• An owner's engineer alone fits when there is one main contract, you have your own project manager and cost control, and you lack depth in wells, subsea or geosciences. A geothermal developer drilling its first deep wells is typical: it can run the programme but needs someone who has delivered wells to check the design and put experienced people at the rig site through onshore and offshore operations supervision.
• A PMC alone fits when you have strong engineers in-house but not the people to run several contracts, interfaces and partner reporting at once.
• Both make sense when the work is split across several contracts, when it is your first project of this kind, or when partners or lenders want technical assurance independent of the team managing cost and schedule.
• Not both yet, if you are still before FEED. At that stage you need technical judgment on the concept and the contracting strategy more than someone to run delivery. The split between the two roles follows from that strategy and from the owner's review points, which are best settled in the front end. Well-run front-end engineering (FEED) should tell you which of these roles you will need in execution.

We work as owner's engineer and also offer owner-side project management consulting. If one firm holds both roles, ask how it keeps them apart: different named leads, a written line between managing and reviewing, and a technical lead who can reach you directly. If you are considering us for both roles, put the same questions to us and write our answers into the responsibility matrix, so they bind us through execution.

What to write into the scope and RFP

A scope that covers these points prevents most of the confusion and is easier to compare across bidders:

• Responsibility matrix. For each key decision (design acceptance, deviations, change orders, contractor payments, go or no-go at each gate): who recommends, who reviews, who decides. You decide.
• Review, not approval. Owner's engineer comments do not move design responsibility away from the engineer of record.
• Reference standards. Name your specifications and standards, such as NORSOK, ISO or API, so comments are not a matter of taste.
• Independence. Each bidder discloses any current work for your contractors, their designers or key suppliers on this project, and commits to tell you before taking any such work during the engagement.
• Named people. Who does the work, how much of their time you get, and how substitutions are agreed.
• Deliverables. For the PMC: schedule, cost reports, change log. For the owner's engineer: review records, a technical risk register, site reports, and records of the tests and inspections it attended for you.
• Turnaround and escalation. Agreed review times, so assurance is not the bottleneck, and a direct line from the owner's engineer to you on technical concerns.

On cost, the same factors drive both roles: the number of contracts and interfaces, the disciplines covered, the site or offshore presence you want, and the length of execution. Buying both need not mean paying twice if the matrix stops them reviewing the same documents.

To compare bids fairly, have every bidder price the same contracts, review packages, site or offshore days and execution period, and show the named people's time behind the total and how scope changes are priced. A low price that assumes fewer reviews or less site presence is buying you a smaller scope.

Comparing bidders: questions to ask and red flags

Ask each bidder, at clarification or interview:

• Which decisions in the responsibility matrix would it recommend, which would it review, and which does it think you should keep?
• Who, by name, reviews a well or subsea deviation, and who reports on cost and schedule? Can you meet both before award?
• What current or recent work does it have with your contractors, their designers or key suppliers, and will it take any during the project?
• How does it word a review comment so it does not become an approval?
• If its technical lead disagrees with the project manager on a deviation, how does that reach you, and how fast?

Treat these as warning signs:

• An owner's engineer bid from a firm that, directly or through an affiliate, also designs or builds part of the same project.
• A scope that says "manage" where you meant "review", or "approve" where you meant "comment".
• A PMC proposal strong on reporting with nobody able to judge a technical deviation, when you lack that person in-house too.

Two of our anonymised engagements show owner-side work in practice: "Deep geothermal wells, delivered to standard" and "Subsea decommissioning, contracted without surprises".

If you are drawing the line between these roles on a live project, send us your draft scope. The senior partner who scopes the split with you stays on the project through execution, holding the responsibility matrix you agreed at the start.