Commercial & Contract · Mandatory · Pre-Construction

Programme of Works

A programme showing the planned sequence and duration of construction activities.

Last reviewed: 29 March 2026 — This guide reflects UK law as of this date. Contract / JCT remains current with no amendments enacted as of 29 March 2026. Next scheduled review: 29 March 2027.

Legal basis	Contract Law / JCT Suite of Contracts / NEC4 Suite of Contracts
JCT status	Under JCT contracts, the contractor's programme is NOT a contract document — it is provided for information only and has no contractual status unless expressly incorporated
NEC4 status	Under NEC4, the programme IS a contract document — it is identified in the contract data, accepted by the project manager, and used to assess compensation events and extensions of time
Critical path	The longest sequence of logically linked activities through the programme, which determines the minimum project duration. Any delay to a critical path activity delays the project completion date.
Delay analysis	The comparison between the baseline programme and the as-built programme is the foundation of delay analysis in construction disputes

1. The Master Programme

The master programme is both the timetable for the construction project and the primary evidence base in any delay dispute. It sets out the sequence, duration, and logic of every activity required to deliver the project from commencement to practical completion. A properly prepared and maintained programme is the single most important management tool on any construction project.

The programme serves two distinct purposes. First, it is a planning tool — it communicates to every member of the project team what work needs to be done, when, and in what sequence. It drives procurement, resource allocation, and coordination between trades. Second, it is a dispute document — when delays occur and the parties disagree about responsibility, the programme (and its history of updates) becomes the primary evidence for delay analysis. The baseline programme records what was planned; the as-built programme records what actually happened; and the comparison between the two is the foundation of every delay claim.

The contractual status of the programme differs significantly between JCT and NEC4. Under JCT contracts, the contractor's programme is provided for information only and has no contractual status unless expressly incorporated as a contract document. Under NEC4, the programme is a contract document — it is identified in the contract data part 2, accepted by the project manager, and used to assess compensation events, extensions of time, and the contractor's planned completion. This fundamental difference has significant practical implications for how the programme is prepared, maintained, and relied upon.

Keep the baseline programme intact

The baseline programme — the programme as it stood at the commencement of the works — must be preserved and never overwritten. It is the reference point against which all delay analysis is carried out. If the baseline is lost or modified, the ability to demonstrate the planned sequence and timing of the works is severely compromised. Updated programmes should be saved as separate revisions, with the baseline always retained as a distinct and unaltered record. Every delay analyst, adjudicator, and judge will look for the baseline first.

2. Key Elements

The following elements are the core components of a properly prepared master programme. Each element must be present for the programme to function as both a management tool and an evidence document.

Element	Detail
Programme type	Typically a Gantt chart (bar chart) produced in scheduling software such as Primavera P6 or Microsoft Project. The programme must be logic-linked (a linked bar chart), not a simple bar chart without logic, in order to demonstrate the critical path and the effect of delays.
Activities	Every significant task required to deliver the project, broken down to a level of detail that is sufficient for planning and progress monitoring. Activities should be trade-specific and location-specific (e.g. "Block A — Level 3 — M&E first fix") rather than generic.
Durations	The planned duration for each activity, based on the scope of work, the resources available, and the productivity assumptions. Durations must be realistic and achievable — an unrealistic programme is worse than no programme at all.
Logic links	The dependency relationships between activities (finish-to-start, start-to-start, finish-to-finish, or start-to-finish). Logic links define the sequence of work and are essential for identifying the critical path. A programme without logic links cannot demonstrate causation in a delay analysis.
Critical path	The longest sequence of logically linked activities through the programme, which determines the minimum project duration. Any delay to a critical path activity will delay the project completion date by the same amount, unless the delay is mitigated. Identifying and monitoring the critical path is the most important function of the programme.
Contract completion date	The date for completion stated in the contract (or as adjusted by extensions of time). This is the date by which the contractor must achieve practical completion. The programme must show how the planned sequence of activities leads to completion by this date.
Milestones	Key dates within the programme, including sectional completion dates, design freeze dates, procurement deadlines, and employer obligations (e.g. access dates, information release dates). Milestones provide reference points for monitoring progress and identifying delay.
Float	The amount of time an activity can be delayed without delaying the project completion date. Total float is measured against the project completion date; free float is measured against the start of the next activity. The ownership and use of float is a common source of dispute — under most standard forms, float belongs to the project, not to any individual party.
Resources	Where required (particularly under NEC4), the programme should show the resources (labour, plant, and materials) allocated to each activity. Resource loading allows the project team to identify resource clashes, plan procurement, and verify that the planned durations are achievable with the resources available.
Issue history	A record of every version of the programme issued during the project, including the date of issue, the reason for the update, and a summary of the changes made. The issue history is essential for delay analysis, as it shows how the programme evolved in response to events on site.

3. Common Mistakes

No genuine critical path

A programme without a genuine, logic-linked critical path is not a programme — it is a bar chart. Many contractor programmes are produced as simple bar charts with activities shown in approximate sequence but without the logic links that define the dependencies between them. Without logic links, it is impossible to identify the critical path, and without the critical path, it is impossible to demonstrate the effect of any delay event on the project completion date. In any delay dispute, the first question will be whether the programme has a genuine critical path. If it does not, the programme will carry little or no evidential weight.

Not updating the programme

A programme that is not regularly updated is a historical document, not a management tool. The programme must be updated at regular intervals (typically monthly, or more frequently on fast-moving projects) to reflect actual progress, changes to the sequence of work, the effect of delay events, and any re-planning by the contractor. Each update should be saved as a separate revision, with the baseline always preserved. A programme that has not been updated for months provides no useful information about the current status of the project and cannot support a delay analysis.

4. Frequently Asked Questions

Is the contractor's programme a contract document under JCT?▾

No. Under JCT contracts, the contractor's programme is not a contract document. It is provided for information only and has no contractual status unless it has been expressly incorporated into the contract by amendment. This means that the programme does not define the contractor's obligations — the contract documents (the contract conditions, the employer's requirements, the contractor's proposals, and the contract sum analysis) do. However, the programme is still critically important as a management tool and as evidence in delay disputes. The fact that it is not a contract document does not mean it can be ignored. Under NEC4, the position is fundamentally different — the programme is identified in the contract data part 2, must be accepted by the project manager, and is used as the basis for assessing compensation events and extensions of time. Under NEC4, the programme is a contract document and carries full contractual weight.

Generate your Programme of Works on Construction Suite

Construction Suite walks you through every required section with a guided Q&A — built to Contract / JCT — and generates a professionally formatted document in minutes.

Get started free