On many EPCM projects, schedule control and delay analysis are treated as though they were the same activity.
They may sit with the same team. They may use the same Primavera file. They may rely on the same progress updates.
But they answer fundamentally different questions.
Schedule control asks: where does the programme stand today, where is it moving, and is the current completion strategy still achievable?
Delay analysis asks: what caused a particular movement in the programme, what impact did it have on completion, and how should that impact be treated under the relevant contract?
Schedule control is continuous and primarily focused on managing delivery. Delay analysis may be prospective or retrospective, depending on when it is performed and what needs to be demonstrated. Its focus is causation, critical-path impact, entitlement and contractual responsibility.
On an EPCM structure, keeping those two disciplines aligned becomes particularly important.
WHY EPCM MAKES THIS HARDER, NOT EASIER
Under a single EPC lump-sum contract, delay attribution is usually more contained. There is one principal contractor, one primary contractual programme and fewer contractual interfaces through which delay causation must be traced.
An EPCM programme is structurally different. The Owner typically holds multiple direct contracts covering engineering, procurement and several construction packages. Each package may have its own contractual programme, its own baseline and milestones, different notice requirements, different risk allocation, different extension-of-time mechanisms, and different definitions of excusable or compensable delay.
The EPCM manager coordinates the overall programme but generally does not carry the same execution risk as an EPC contractor. That creates an important structural challenge: the party with the clearest visibility of the overall programme is not necessarily the party that must demonstrate contractual causation under an individual package.
A delay originating in one package may affect several others before reaching the overall completion date. The programme shows the ripple effect. The contract determines what that ripple effect means commercially.
THE INTEGRATION PROBLEM
Credible delay analysis depends on more than having an updated master schedule. The integrated programme must genuinely reflect the logic and interdependencies between individual packages — understanding not only where each package stands, but how one package constrains another.
Engineering release dates may drive procurement. Procurement may drive site access to equipment. Civil works may constrain mechanical installation. Mechanical completion may control commissioning. A delay at one interface may therefore migrate through several contractual boundaries before affecting programme completion.
Where package schedules are maintained independently and reconciled mainly for monthly reporting, the resulting master schedule may still be perfectly adequate for progress reporting. It may be far less reliable for establishing contractual causation.
For delay analysis to remain defensible, the project needs traceability between contractual baselines, approved programme revisions, actual progress, logic changes, critical and near-critical paths, interface milestones, retained logic, float consumption, delay events, and mitigation and recovery actions — both at package level and at integrated programme level. Under delivery pressure, this is often one of the first disciplines to weaken.
SCHEDULE UPDATES ARE NOT DELAY ANALYSIS
A schedule update records what changed. It does not necessarily explain why it changed.
If completion moves by four weeks between two reporting periods, the programme may clearly show the movement. But several questions remain: what event caused it, when did it begin affecting the critical path, was that path already being affected by another event, was the delay caused by the contractor, the Owner, another package or an external event, was mitigation available, did another delay absorb some or all of the apparent impact, was the affected activity actually critical at the time?
Those questions cannot be answered simply by comparing planned and actual dates. They require causation analysis — established against the contractual position, not only against the latest programme.
OVERLAPPING DELAY EVENTS ARE THE NORM, NOT THE EXCEPTION
Large EPCM programmes naturally generate overlapping events. Several packages may be progressing simultaneously, each with its own critical or near-critical path feeding into the integrated completion date. Engineering delay may overlap with procurement delay. Late access may overlap with contractor underperformance. Equipment delivery may overlap with incomplete enabling works.
Two contractors may each experience events that justify an extension of time under their respective contracts, while only one of those events actually affects the overall programme completion date. Whether overlapping events amount to true concurrent delay is a separate question, requiring analysis of causation and of the critical path at the relevant point in time.
This is why a global comparison between the original baseline and the final as-built programme may be insufficient. A credible analysis will normally examine how the critical path evolved during the project and what was driving completion when each material event occurred — depending on the contract, the available records and the purpose of the analysis, through time-impact analysis, windows analysis, as-planned versus as-built analysis, collapsed as-built analysis, or another methodology appropriate to the circumstances.
The methodology matters. But the quality of the underlying schedule and contemporaneous records matters even more. No analytical methodology can fully compensate for a programme that was never maintained in a way that allows cause and effect to be reconstructed.
FLOAT IS ALSO A CONTRACTUAL ISSUE
Float is often treated as a purely scheduling concept. On multi-contract programmes, it can quickly become a commercial issue. If Package A consumes available programme float, does that reduce the time available to Package B? Who is entitled to use that float — the project, the Owner, the contractor that generated it, or whoever uses it first?
The programme may show how float was consumed. It does not, by itself, determine the contractual consequences.
The same applies to mitigation. A contractor may accelerate activities to protect an interface milestone and prevent a delay from reaching the overall completion date. From a schedule-control perspective, the intervention has worked. From a contractual perspective, there may still be questions around responsibility for the underlying event, entitlement to additional cost, entitlement to extension of time, acceleration instructions, mitigation obligations, and disruption or loss of productivity.
The schedule position and the contractual position are related. They are not identical.
WHY THIS MATTERS BEYOND THE PROGRAMME
For project owners, investors, lenders and PMO functions, delay is rarely only a planning issue. Movement against contractual completion dates may affect liquidated damages, extension-of-time entitlement, milestone payments, financing drawdowns, guarantees, contingency requirements, commissioning dates, revenue commencement, covenant tests, and completion support arrangements.
Those decisions require more than an aggregate statement that the programme is “six weeks behind.” They require an understanding of what is actually driving the delay. A project may be six weeks behind its original programme while the contractual position across the individual packages is considerably more complex — one contractor entitled to additional time, another responsible for delay, a third having suffered delay without affecting programme completion, an Owner-caused event overlapping with contractor delay.
The master schedule can show the programme outcome. A defensible delay analysis is needed to establish the contractual consequences.
GOOD SCHEDULE CONTROL CAN STILL PRODUCE POOR DELAY EVIDENCE
This is one of the more important governance distinctions. A programme can have excellent schedule control — regular updates, accurate progress measurement, clear dashboards, reliable forecasts, well-managed recovery plans — and still be unable to support a credible delay analysis when one is needed.
Why? Because schedule control is primarily designed to manage the future. Delay analysis requires the project to preserve enough information to reconstruct causation. If logic changes are not documented, baselines are overwritten, interface assumptions are changed without traceability, or delay events are not contemporaneously connected to programme impacts, the reporting system may continue to function while the contractual evidence gradually deteriorates.
By the time a major claim or dispute emerges, the project may know exactly where it stands today but struggle to demonstrate how it got there.
THE GOVERNANCE GAP
The real issue is therefore not whether Planning or Project Controls is performing well. It is whether the project governance structure connects four different disciplines:
SCHEDULE CONTROL — what is happening to the programme?
↓
DELAY ANALYSIS — what caused the movement and what did it affect?
↓
CONTRACT MANAGEMENT — what contractual rights and obligations arise from that event?
↓
COMMERCIAL MANAGEMENT — what is the resulting financial exposure?
On EPCM programmes, these functions may sit in different teams, organisations and contracts. That makes integration a governance requirement rather than simply a planning responsibility. A better dashboard will not close that gap. A stronger reporting cycle will not close it either. The gap is closed when programme data, contractual events, notices, cost records and commercial positions can be traced back to the same underlying events.
THE PRINCIPLE
Schedule control tells you where the programme stands and where it is heading. Delay analysis explains why it moved, what actually affected completion and how those effects should be treated under the relevant contract.
The two disciplines depend on much of the same information. But they do different jobs. On EPCM programmes, confusing them can be particularly expensive because schedule impacts routinely cross package boundaries while contractual entitlement does not.
The objective should therefore not be simply to maintain an accurate master programme. It should be to maintain a programme and project record capable of supporting both effective delivery today, and defensible contractual analysis tomorrow.
HOW ACC TRUST CAN SUPPORT
ACC TRUST supports project owners, investors, lenders and EPCM teams in connecting schedule control with contractual causation, entitlement and commercial exposure, including through:
independent review of master schedule integration across EPCM packages;
assessment of contractual baselines, retained logic, float treatment and programme change control;
review of interfaces between package schedules and the integrated master programme;
delay analysis using methodologies appropriate to the contract, available records and purpose of the assessment;
assessment of overlapping and concurrent delay events;
critical-path validation at the relevant time of individual delay events;
correlation of programme movements with notices, contractual entitlement and commercial exposure;
integration of schedule position with claims, variations, cost forecasting and management reporting.
The objective is not simply a more current schedule. It is a project governance structure where, when delay attribution matters, the programme and contemporaneous records can support the decisions that follow.
For independent support on project controls, contract governance and delay analysis:
Discover ACC TRUST’s services:
→ https://acctrust.ro/services
Discuss a specific project with us:
→ office@acctrust.ro
About ACC Trust Insights
ACC Trust Insights is ACC TRUST’s knowledge centre dedicated to contract administration, contract governance, project controls and commercial risk management on complex construction, infrastructure and energy projects.
Explore all articles:
→ https://insights.acctrust.ro
ACC TRUST
Commercial & Contract Governance Advisory
Property · Infrastructure · Energy
office@acctrust.ro