Contract and Commercial Management in EPC: Why the Money Gets Lost Between the Contract and the Claim

There is a moment on every EPC project when the commercial team realises that the project is losing money it was entitled to recover. Not because the work was not done. Not because the contract did not provide for recovery. But because the events that entitled the contractor to more time or more money were not documented when they happened, the notices were not issued within the contractual window, and the records that would have supported the claim are scattered across email threads, site diaries, and the memory of a site engineer who left the project six months ago.

This is the most expensive failure mode in EPC contracting. It is not a technical failure or an engineering failure. It is a commercial failure — a failure to manage the contract with the same rigour that the project manages the engineering and the construction.

EPCdoc’s Contract and Commercial module, powered by an AI layer that reads contract language, tracks commercial events, and surfaces obligations before they expire, is built to close this gap. It does not replace the commercial manager’s judgement. It ensures that the commercial manager’s judgement is applied to the right events, at the right time, with the right records to support it.

The Commercial Failures That Cost EPC Contractors the Most

Before explaining how EPCdoc works, it is worth being precise about where commercial value is lost on EPC projects — because the system is designed to prevent each of these specifically.

Missed notice deadlines — FIDIC, NEC4, and most bespoke EPC contracts require the contractor to issue a formal notice within a specified period (typically 28 days under FIDIC) of becoming aware of an event that will give rise to a claim for additional time or money. Miss the window, and the entitlement is gone regardless of how strong the underlying claim is. On a large project running multiple contracts simultaneously, tracking dozens of notice windows across different contract forms is genuinely difficult without a system designed to do it.

Unrecorded contemporaneous events — A claim for delay or additional cost is only as strong as the contemporaneous records that support it. A site instruction issued verbally and not confirmed in writing. A client decision that was made in a meeting but not minuted. A weather event that stopped work for three days but was only noted in the site diary of an engineer who is no longer on the project. These events happened. They are not recoverable without the records.

Variation work done without approval — Construction teams, under schedule pressure, often proceed with work that has been verbally instructed but not formally approved as a variation. By the time the project reaches final account, the client disputes that the instruction was ever given, and the contractor has done the work at their own cost.

Liquidated damages exposure not managed — A contractor approaching a milestone date that carries LAD exposure needs to know, weeks in advance, whether the milestone is achievable, whether there are grounds for an EOT claim, and whether the notice has been issued. If the milestone is missed without an EOT claim in place, the LAD clock starts running — and often runs for much longer than it needed to because the recovery plan came too late.

Back-to-back obligations not enforced — On projects where the main contractor has back-to-back subcontracts, a subcontractor delay that gives rise to a main contract claim must also be captured as a claim against the subcontractor under the back-to-back terms. This requires the same notice discipline at the subcontract level as at the main contract level — which is doubly difficult to maintain when the project team is focused on the main contract relationship.

EPCdoc’s commercial module is designed to make each of these failures structurally impossible — not by hoping the commercial team remembers to do the right thing, but by building the system so the right thing is the default.

---

How EPCdoc COM Works — The Full Commercial Lifecycle

Contract Register and Clause Navigator

Every contract on the project — the main EPC contract, subcontracts, supply agreements, consultant appointments — is registered in EPCdoc’s contract register. The registration captures the contract form (FIDIC Silver, NEC4 ECC, CPWD GCC, MoRTH, bespoke), the parties, the contract value, the key commercial terms, and the critical dates: contract start, milestone dates, completion date, defects liability period, and final account deadline.

EPCdoc’s AI reads the contract document and extracts the key commercial obligations: notice periods for different claim types, the procedure for instructing variations, the payment application cycle, the dispute resolution mechanism, and the insurance and bonding requirements. These extracted obligations are displayed in the FIDIC Clause Navigator — a searchable, plain-language reference to the contract’s commercial requirements that gives the project team instant access to what the contract requires, without having to search through a 200-page document every time a commercial question arises.

The AI also flags where the project’s contract deviates from the standard form — where a FIDIC Silver Book clause has been amended, where a back-to-back obligation differs from the main contract term, where a special condition overrides a general condition. Deviations from standard form are where commercial risk is hidden, and EPCdoc’s AI surfaces them explicitly rather than leaving them to be discovered when a dispute arises.

Notice Management and Deadline Tracking

EPCdoc’s notice management system is the most commercially critical feature of the COM module. Every event on the project that may give rise to a contractual entitlement — a client instruction, a late client approval, a force majeure event, a differing site condition, a client-caused delay — is logged in EPCdoc as a commercial event. The system calculates the notice deadline automatically from the contract’s notice period and the date the event was first recorded. A countdown timer shows how many days remain before the notice window closes.

When a notice deadline is approaching — configurable threshold, typically five to seven days before expiry — EPCdoc alerts the commercial manager, the contract manager, and the project manager simultaneously. The alert includes the event description, the relevant contract clause, the deadline date, and a draft notice template pre-populated with the event details. The commercial manager reviews and issues the notice. EPCdoc records the issuance date, the notice reference, and the method of delivery.

This is not administrative tidiness. It is commercial protection. A notice issued on day 27 of a 28-day window preserves an entitlement that a notice issued on day 29 loses permanently. EPCdoc ensures the notice is never issued on day 29 because it is flagging the deadline on day 21.

The notice register gives the commercial team a complete, chronological record of every notice issued and received on the project — with the supporting event documentation attached to each notice. When a dispute arises at the end of the project and both parties are arguing about what was notified when, EPCdoc’s notice register is the contemporaneous record that settles the question.

Variation Order Management

Every variation on the project — whether initiated by the client, instructed under the engineer’s authority, or identified by the contractor as a departure from the original scope — is managed in EPCdoc’s Variation Order register from identification through assessment, negotiation, and approval.

The VO workflow enforces the contractual variation procedure: identification and notification, preliminary cost and schedule assessment, formal submission, client review and negotiation, approval, and incorporation into the contract price and programme. No work proceeds under a variation instruction without a VO record in EPCdoc — which means the contractor’s exposure to doing variation work without approval is eliminated by the system itself, not by hoping the site team remembers to ask for a VO before they start.

EPCdoc’s AI supports the variation assessment process in two ways. First, it extracts the relevant contract clauses for valuing the variation — the day-work rates, the schedule of rates, the overhead and profit percentages, the escalation provisions — and presents them alongside the VO assessment form, so the commercial engineer is working from the contract terms rather than from memory. Second, it analyses the proposed variation against the project’s existing cost data — the actual manhour rates being achieved by the engineering team, the current material costs from the procurement module, the current labour productivity rates from the construction progress data — and identifies where the variation assessment differs significantly from actual project data. An assessment that is 30 percent below the actual cost being incurred is a problem that EPCdoc flags before the VO is submitted, not after it is approved at the wrong value.

EPCdoc also tracks back-to-back VO issuance: when a main contract VO is approved, the system prompts the commercial team to raise the corresponding subcontract VO against the affected subcontractor. The back-to-back obligation is enforced by the workflow, not by memory.

Extension of Time Claims

EOT claim management in EPCdoc follows the same discipline as notice management: every delay event is logged, every notice is tracked, and every EOT submission is built from the contemporaneous records in the system rather than reconstructed after the fact.

The EOT register captures each delay event — its nature (employer risk, force majeure, neutral), its start and end date, the days claimed, the FIDIC or NEC clause under which the claim is made, and the notice status. EPCdoc’s AI analyses the delay events against the CPM schedule to identify which delays are on the critical path and therefore give rise to an entitlement to time, and which are concurrent delays that may affect the quantum of entitlement. The critical path analysis is done automatically from the CPM data already in EPCdoc — not by the planning expert who charges by the day to produce a delay analysis report at the end of the project.

For compensable delays — delays that are not just the client’s risk but carry a right to additional payment under the contract — EPCdoc connects the delay event to the prolongation cost calculation: the cost of maintaining the project team and site facilities for the extended period, calculated from the actual costs in the project controls module. The prolongation cost is not estimated — it is calculated from the actual time-related costs being incurred, which is the most defensible basis for a compensation claim.

The EOT submission document is generated from EPCdoc’s records: the delay event log, the notice history, the CPM analysis, and the prolongation cost calculation. The commercial team edits and finalises the narrative. The data is already there.

Interim Payment Certificates and Cash Flow

EPCdoc’s IPC module manages the payment application cycle from preparation through submission, certification, and payment. The payment application is compiled automatically from the project’s earned value data — the engineering progress from the EPM module, the procurement milestones completed, the construction quantities certified — rather than from a separate manual assessment. The application reflects what has actually been done, not what the commercial team thinks they can justify in this period’s application.

The IPC workflow tracks the client’s certification obligation: the contract specifies how many days the client has to certify and pay after receiving the application. EPCdoc tracks both clocks — certification and payment — and alerts the commercial team when either deadline is approaching without action. A client who is chronically late in certifying or paying is building up a commercial entitlement for the contractor. EPCdoc records the pattern.

Retention deductions, advance payment recovery, liquidated damages deductions, and set-off claims are all tracked in the IPC register against their contractual basis. When the client makes a deduction that is not supported by the contract, EPCdoc flags it — not as an automated dispute, but as an alert to the commercial manager that a deduction has been made that requires a written challenge within the contractual response period.

Liquidated Damages Management

LAD exposure is the commercial risk that EPC contractors manage with the most anxiety and the least rigour. EPCdoc changes this by making the LAD position visible at all times — not just when the milestone date is approaching, but throughout the project as the schedule evolves.

EPCdoc calculates the current LAD exposure daily: the milestone date, the current forecast completion date from the CPM schedule, the gap between them, and the daily LAD rate from the contract. When the forecast completion date slips beyond the milestone date, EPCdoc calculates the LAD liability that would accrue if no EOT is approved, and flags it alongside the EOT claims currently in submission. The commercial team can see at a glance whether their current EOT submissions, if approved in full, would eliminate the LAD exposure — or whether there is a residual exposure that requires additional claims, recovery of the schedule, or a commercial negotiation.

EPCdoc also tracks the interaction between LAD and back-to-back subcontract LADs. When the main contractor is exposed to LAD for a delay caused by a subcontractor, the system ensures that the corresponding LAD claim against the subcontractor is also in process.

---

The AI Layer — Commercial Intelligence That Works While You Sleep

Contract Obligation Monitoring

EPCdoc’s AI reads the registered contracts continuously and monitors the project’s commercial activities against the contract’s obligations. When a pattern of events in the project data matches a known risk pattern — a series of client-instructed changes that have not been formally notified, a payment application that is approaching the period where the client’s failure to certify would constitute a deemed approval under the contract, a subcontractor who is approaching their LAD threshold — the AI flags it to the commercial manager.

This is commercial intelligence that no spreadsheet can replicate: the ability to read across all of the project’s commercial data simultaneously and identify situations that the contract says are significant, before the commercial team has specifically looked for them.

Cashflow Forecasting

EPCdoc’s AI generates a 13-week rolling cash flow forecast from the project’s commercial data: payment applications due and their expected certification and payment dates, purchase order payment milestones due, subcontractor payments due, and any retentions due for release. The forecast reflects the actual payment behaviour of this client and these subcontractors — their historical certification and payment lead times — rather than assuming that everyone will pay on the contractual due date.

When the cash flow forecast shows a liquidity trough — a period when outflows will exceed inflows by a material amount — EPCdoc alerts the commercial and finance teams far enough in advance to arrange bridging facilities, accelerate a payment application, or defer a subcontractor payment that the subcontract terms permit to be deferred. Cash flow management on a large EPC project is a full-time commercial function. EPCdoc automates the forecasting so the commercial team can focus on the management.

Claim Assessment and Strength Analysis

When the commercial team is preparing a formal claim — whether for additional payment, for EOT, or for compensation of prolongation costs — EPCdoc’s AI analyses the strength of the claim against the contract’s requirements: is the notice history complete, is the delay analysis on the critical path, is the cost calculation supported by actual project data, does the claim follow the contractual submission procedure?

The AI does not decide whether the claim will succeed — that requires the judgement of an experienced commercial professional and ultimately depends on how the adjudicator or arbitrator reads the facts. But it identifies the gaps in the claim that would give the client grounds to dispute it, before the claim is submitted, when those gaps can still be filled. A claim submitted with complete notice history, a contemporaneous delay record, and an actual-cost-based prolongation calculation is in a fundamentally stronger position than a claim assembled retrospectively. EPCdoc makes the former the standard rather than the exception.

LD Exposure and Risk Quantification

EPCdoc’s AI runs a continuous risk quantification on the project’s commercial exposure: the probability-weighted LAD liability based on the current schedule forecast and its confidence interval, the value of pending VOs that the client may dispute, the value of claims in submission that may not be approved in full, and the cost of uncommitted scope that remains to be contracted. The commercial risk register presents this exposure in a format that the project manager and senior management can act on — not a list of risks, but a quantified picture of the project’s commercial position under different scenarios.

---

Reporting That the Boardroom Can Read and the Adjudicator Can Use

EPCdoc generates two levels of commercial reporting from the same underlying data.

The monthly commercial report for senior management presents the project’s commercial position: contract value versus projected final account, approved VOs and their cumulative impact, pending claims and their probability-weighted value, LAD exposure, cash flow forecast, and subcontract commercial position. Every number is traceable to a transaction in EPCdoc — no number in the commercial report is an estimate or an opinion if the underlying data exists in the system.

The claim dossier for dispute resolution is assembled from EPCdoc’s records: the notice history, the event log, the contemporaneous cost records, the CPM delay analysis, the correspondence register. This is not a document that needs to be prepared specially for a dispute. It is the natural output of EPCdoc having been used correctly throughout the project — every commercial action recorded, every notice filed, every decision documented. The adjudicator or arbitrator who receives a claim supported by EPCdoc’s records is receiving a claim that was documented while the events were happening, not reconstructed afterwards. That is the difference between a strong claim and a winning one.

---

Commercial Management Is Project Management

The separation between “commercial” and “project” management is a false one on EPC contracts. Every engineering decision has a commercial consequence. Every construction delay has a notice obligation. Every procurement decision affects the cash flow. Every client instruction is either a variation or a scope clarification, and the difference between them is worth money.

EPCdoc’s Contract and Commercial module integrates commercial management into the project management system — not as a separate function that produces reports for the boardroom, but as a live, connected layer of the project that sees every commercial event when it happens and ensures the right response at the right time.

The contract was written to protect the contractor’s position. EPCdoc ensures that protection is actually used.