Chapter IV: Managing the EPC contract

Signing the EPC contract feels like the finish line. The contractor is selected, the price is fixed, the risk is transferred. What remains, it seems, is execution.

That instinct is understandable and nearly always wrong. The contract creates the framework. What happens inside that framework, how it is managed, documented, and enforced from day one, determines whether the risk transfer you negotiated actually holds. This chapter is about what that management requires in practice.

The Turnkey Illusion

The EPC model is sometimes described as turnkey: the owner hands over the keys at the beginning and receives a finished facility at the end. The description is not entirely wrong, but the conclusion owners sometimes draw from it, that they can staff lightly and check in at milestones, is one of the more expensive mistakes in this business.

Consider what is happening simultaneously during a major EPC project. Engineering is producing hundreds of drawings and specifications, many of which require owner review and approval. Procurement is placing orders for long-lead equipment, each with its own technical requirements and delivery schedule. Construction is beginning in the field while design is still being finalized. Commissioning planning is underway. Permits are being managed. Subcontracts are being executed. All of this is happening at the same time, on parallel tracks, with dependencies running in every direction.

The owner’s team needs to be present not to direct the work, but to know what is happening, confirm it is consistent with the contract, and raise issues before they become problems that are too late or too costly to correct. An owner who discovers a design error at construction completion has a very different problem than one who catches it at the 30% design review.

Staffing to the Contract

The skills your team needs depend on the contract structure. In a multi-contract or construction management delivery, the owner effectively acts as the general contractor, coordinating between separate engineering, procurement, and construction firms. That requires technical depth, construction field experience, and contract administration capabilities all in one team.

In a true EPC, much of that coordination responsibility transfers to the contractor. But the owner’s team still needs contract administration skills: the ability to read and enforce the contract, manage correspondence, evaluate change order claims, and conduct meaningful design reviews. What changes is the character of the owner’s role, not its importance.

A team that is technically strong but has no contract experience will get outmaneuvered in disputes. A team with contract experience but no technical depth cannot evaluate what the contractor is actually building. Both gaps are common, and both are expensive.

Structure and Documentation Discipline

The value of a methodical, structured, and disciplined project management process cannot be overstated, and it is consistently underestimated by people who have not been through a major dispute.

Industrial construction projects are not business as usual. They run for years. They involve hundreds of people on both sides. Key personnel routinely turn over: sometimes the people who made critical decisions are gone before those decisions have consequences. When that happens, the only thing that survives is the documentation.

This means formal meeting minutes for every project meeting, distributed and acknowledged within 48 hours. Numbered correspondence logs on both sides, so nothing falls through the cracks and every letter has a response. Decision registers that capture not just what was decided but who decided it and when. Submittals logged, tracked, and closed. RFI (request for information) logs maintained in real time.

This is not bureaucracy for its own sake. When a dispute arises two years into a project — and on a large EPC, something will arise — the party with the cleaner record has a significant advantage. The party whose project manager took personal notes in a spiral notebook and resolved issues over the phone without follow-up is at the mercy of whatever the other side wrote down.

The Formality Spectrum

There is a narrow and important space between the informal handshake and the formal project letter written by legal counsel full of positioning language and careful hedging that signals both sides have stopped trying to solve the problem and started building a record for arbitration.

Your instinct at the start of a project is to work collaboratively. You want to resolve issues with your counterpart over a phone call, keep things moving, avoid the friction of formal correspondence on every minor disagreement. And for a while, that works. Issues get resolved. The relationship feels functional. The informal approach carries on.

The problem is that it carries on while the issues get larger. At some point, the disagreement reaches a scale where your counterpart can no longer make a handshake deal.  The cost is too large, or it requires approval from someone above them. Or your counterpart moves on to another project. Their replacement arrives, reviews the situation, and cannot believe what concessions their predecessor agreed to. Formal letters begin to arrive. The tone shifts. And now you are sitting on a set of informal understandings that you cannot document and a series of concessions that you made in good faith, and you feel exposed.

The opposite failure is just as real. Some project teams start formal and stay formal. Every issue becomes a dispute. Every dispute generates letters, meetings, legal reviews, and delay. The overhead of managing the correspondence becomes its own project.

Neither extreme serves you. What works, in my experience, is resolving issues at the lowest level you can, over a call, over a meeting, but documenting the resolution promptly, through a follow-up email or meeting minutes that both sides can confirm. The handshake is fine. The undocumented handshake is not.

Change Order Management

Change orders are where EPC contracts bleed. They are also the area where the gap between the contract you signed and the project you are managing becomes most visible.

Changes originate from everywhere: owner-directed scope additions, scope errors or omissions, differing site conditions, regulatory changes, equipment substitutions, and interface issues with third parties. Some are legitimate and unavoidable. Others are the result of an underpriced bid finding its margin on the back end. Most come wearing the costume of the first one (owner-directed changes)

The discipline that matters most is this: no work proceeds on a changed scope without an executed change order, or at minimum a written authorization to proceed with pricing to follow. This sounds obvious. It is violated constantly. The field pressure to keep work moving, the sense that “we’ll sort out the pricing later,” the reluctance to slow down for paperwork, all of it conspires against this discipline, and all of it produces the same result: a backlog of unpriced, disputed changes that consumes the back half of the project.

Equally important is the change order review process itself. The contractor’s change order pricing should be reviewed against the contract’s defined pricing methodology: unit rates, allowable markups, labor rates established at contract execution. Owners who do not have this baseline and do not review change proposals against it routinely overpay.

Schedule Oversight

The project schedule is the contractor’s primary tool for managing the work. It is also one of the primary tools for managing the owner’s expectations, and, if left unscrutinized, for shifting responsibility for delays.

Owners need the ability to read and critically evaluate schedule updates. This means understanding the critical path, not just the milestone dates. It means recognizing when the contractor has changed logic ties or added float without explanation. It means knowing the difference between a schedule that reflects how the work is actually proceeding and one that has been revised to make the current status look acceptable.

An owner who cannot evaluate the schedule independently is entirely dependent on the contractor’s narrative. When delays emerge, that dependency becomes a serious liability. By the time the owner understands the scope of the problem, the contractor has often already built a record attributing the delay to owner actions.

In my experience, the cost of keeping a scheduler in the owner’s team, or at a minimum, outsourcing this service to an owner’s consultant, is returned many times over.

Payment Applications and Financial Controls

Monthly payment applications are the financial heartbeat of the project. They are also where the schedule of values, which you negotiated carefully at contract execution (see Chapter III) either holds or doesn’t.

The risk is front-loading: a schedule of values that assigns disproportionate value to early line items, allowing the contractor to overbill in the early months and leave the owner holding underpaid retainage against work that is largely complete. By the time the imbalance becomes visible, the leverage to correct it is limited.

Review each pay application against actual work in place in addition to the schedule of values. Challenge line items where billing appears to outpace physical progress. Verify that stored materials claimed in a pay application are actually on site and secured. Maintain a running picture of the project’s financial status relative to physical completion. If those two curves diverge significantly, something is wrong.

Retainage should be managed with the same discipline. Its purpose is to retain owner leverage through project completion and punch list closeout. Releasing it early, under contractor pressure, before the facility is performing as specified, is one of the more common ways owners lose their final source of contractual protection.

RFIs and Submittals: The Paper Trail That Bites

The RFI and submittal process is among the least glamorous parts of EPC contract management and among the most consequential.

Contractors use unanswered or slow-turned RFIs and submittals as the foundation of delay and impact claims. To be fair, contractors do need the owner to answer the RFIs on time.  The logic is straightforward: if the contractor submitted a question or a drawing for approval, and the owner did not respond within the contractually required window, the contractor has a documented basis to claim that the owner’s failure affected their work. Whether or not the claim is ultimately valid, the record is there.

The owner’s team needs a live RFI log and a live submittal register, tracked daily, with response due dates flagged before they expire. Review turnaround commitments in the contract should be taken seriously. If the contract says ten business days, that is a contractual obligation running in both directions, and that does not mean the owner should wait until the end of that period.  The sooner an answer is provided, the better progress in design or in the field. Owner representatives who treat submittals as administrative paperwork rather than contractual deliverables will find that paperwork cited against them when disputes arise.

The flipside is also true: a contractor who submits incomplete or non-conforming submittals and then claims the clock was running is using process as a weapon. While the owner’s rejection of a non-conforming submittal, clearly documented, with the specific deficiency identified, resets the clock and protects the record, it doesn’t necessarily remove risk from the owner.  If the RFI’s are not properly prepared by the contractor, the project will get delayed, and that is not good for anybody.  In these scenarios, it would behoove the owner to help/bolster the contractor, even though that is not the owner’s responsibility.

What Comes Next

Disputes are not a sign of a failed project. They are a feature of complex ones. What matters is how prepared you are when they arrive. Chapter V will cover that preparation, and what to do when it is tested.