Claims » Extensions of Time
Contractor’s Programme — Contractual Status and Obligations
The programme is the single most important management document on a construction project. Yet its legal status — what the programme actually obliges the parties to do — is misunderstood by many practitioners. The answer depends entirely on which standard form applies.
4 min read · Updated 21/04/2026
 |
By Basel Al Najjar Civil Engineering Consultant, DIAC Arbitrator, Tribunal Chairman and Accredited Expert Witness. Over two decades advising UAE contractors, developers and law firms on FIDIC, claims and arbitration. |
In this article
Key takeaway
Under JCT and FIDIC, the programme is a planning tool, not a contractual document creating binding sequence obligations. Under NEC4, the accepted programme is a central contractual mechanism — and failure to maintain it directly affects compensation event entitlement. Knowing which regime applies is fundamental to effective programme management.
1. When the programme’s status matters
The question of programme status arises in two common scenarios. In the first, the contractor deviates from the programme — works are resequenced, activities reordered, or the critical path changed — and the employer argues this constitutes a breach of contract. In the second, the employer causes delay or disruption, and the dispute turns on what the programme showed the contractor intended to do and how the employer’s actions affected that intent.
In both scenarios, the outcome depends critically on whether the programme is a contractual document — creating binding obligations about sequence and method — or simply a management tool submitted to comply with a contract requirement, without creating substantive obligations beyond that submission.
2. The two different regimes — JCT/FIDIC and NEC
| Form | Programme status |
|---|---|
| JCT SBC 2016 | Clause 2.9 requires a master programme, but the standard wording does not make it a contract document or bind the contractor to follow it. Contractor retains freedom to resequence provided the completion date is met. |
| FIDIC Red Book 2017 | Clause 8.3 requires a programme to be submitted, but it is not automatically incorporated as a contract document. The obligation is to provide information to the Engineer, not to create binding sequence. |
| NEC4 | The accepted programme is a central tool. Contractor must maintain a current accepted programme; compensation events are assessed against it. Failure to maintain has real consequences for the entitlement. |
3. Leading authority — Glenlion v Guinness Trust
Leading authority
In Glenlion Construction Ltd v The Guinness Trust [1987] 39 BLR 89, the court held that the contractor’s programme was a planning document and not a binding obligation. The contractor could not be held to the programme as a contractual commitment, nor could the contractor use the programme to oblige the employer to perform its own obligations by reference to dates shown on a contractor-prepared document.
4. Practical application
For contractors
Under JCT and FIDIC, you are generally free to resequence activities provided you meet the completion date. However, the programme is your baseline for delay analysis — significant deviations from it may complicate the demonstration of delay causation in any subsequent EOT claim. Under NEC4, maintain an updated accepted programme at all times; failures affect your compensation event entitlement directly.
For employers
Under JCT and FIDIC, you cannot insist on a particular sequence of working unless this is specified in the contract. However, the programme can be relied on as evidence of what the contractor intended, when assessing the impact of delay events — so maintaining a copy of each submitted revision has evidential value later.
5. Risks and mitigation
For contractors, a programme submitted and then not maintained creates difficulties in EOT and delay analysis — the baseline is stale, and the analysis against stale baselines is evidentially weak. For employers, relying on the programme as if it were binding under JCT or FIDIC (when it is not) may lead to incorrect contractual assertions that weaken the broader position in arbitration.
Under all standard forms, maintain a current, resource-loaded programme. Update it regularly and use it as the basis for delay-event analysis. Under NEC4, treat the accepted programme as a legal obligation — not an administrative nicety.
6. Conclusion
The programme’s legal status depends entirely on the contract. Under JCT and FIDIC, it is typically a planning tool. Under NEC4, it is a central contractual mechanism. Understanding which regime applies — and managing the programme accordingly — is fundamental to effective contract management and to the strength of any subsequent EOT claim.
Related reading
|
Claims Float in the Programme — Ownership and ConsumptionHow float shown in the contractor’s programme is consumed by delay events. |
Claims As-Built Programme in Delay AnalysisWhy the as-built programme is the foundation of any credible delay claim. |
Claims Concurrent Delay — Attribution and EntitlementHow programme analysis identifies concurrent periods and dominant causes. |
Is your programme doing what the contract needs it to?
Programme management is the hinge on which EOT claims turn. We review programme submission and update practice on UAE projects and advise on how to align administration with the applicable contractual regime.
Book a 30-Minute Case Assessment →
Offices in Dubai · Available for instructions across the UAE and GCC