Contractor’s Programme 

Contractual Status and Obligations

The programme is the single most important management document on a construction project. It defines the intended sequence and timing of works, establishes the critical path, and provides the baseline against which delay is measured. Yet its legal status — what the programme actually obliges the parties to do, and what consequences follow from deviations — is misunderstood by many practitioners.

The Problem

The problem of programme status arises in two common scenarios. 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. 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 additional substantive obligations.

The Legal Principle

Under JCT SBC 2016, Clause 2.9 requires the contractor to submit a master programme, but the standard wording does not make the programme a contract document or bind the contractor to follow it. The contractor retains freedom to resequence, accelerate, or otherwise adjust its planned sequence, provided the contract completion date is met. This was confirmed in Glenlion Construction Ltd v The Guinness Trust [1987] 39 BLR 89, where the court held that the contractor’s programme was a planning document and not a binding obligation.

Under NEC4, the position is fundamentally different. The accepted programme is a central tool for contract management. The contractor is required to maintain a current accepted programme, and compensation events are assessed against it. A failure to maintain the accepted programme has real consequences — compensation event assessments default to the contractor’s assessment if the programme is not current.

Under FIDIC Red Book 2017, Clause 8.3 requires a programme to be submitted, but — like JCT — it is not automatically incorporated as a contract document. The FIDIC programme obligation focuses on the provision of information to the engineer rather than creating binding sequence obligations.

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. Under NEC4, maintain an updated accepted programme at all times — failures to do so 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 employer can rely on the programme as evidence of what the contractor intended, in assessing the impact of delay events.

Risks

For contractors: a programme that is submitted and then not maintained creates difficulties in EOT and delay analysis. For employers: relying on the programme as if it were binding (when it is not) may lead to incorrect contractual assertions.

Mitigation

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.

Conclusion

The programme’s legal status depends entirely on the contract. Under JCT and FIDIC, it is typically a planning tool, not a binding obligation. Under NEC4, it is a central contractual mechanism. Understanding which regime applies — and managing the programme accordingly — is fundamental to effective contract management.