Most standard forms treat the programme as information: useful, required to be provided, and not a contractual obligation as to sequence. Some forms and many amendments go further, and where they do the consequences run in both directions, which is why the status of the programme is checked early in extension of time claim preparation.
Contractors sometimes resist submitting a programme for this reason and employers sometimes press for one. Both are reacting to the same point from opposite sides.
The default position
Under most traditional forms the contractor is required to provide a programme and is not bound to work in accordance with it.
The obligation is to complete by the completion date, by whatever sequence the contractor chooses.
That flexibility is valuable and it is also why the programme alone proves very little about what the parties agreed.
What changes when it becomes contractual
The sequence becomes an obligation, so departing from it may be a breach rather than a management decision.
Equally, interference with the agreed sequence by the employer becomes easier to characterise as a matter carrying relief.
So the change cuts both ways, which is why it is worth understanding rather than simply resisting.
How it usually happens
An amendment stating that the programme forms part of the contract documents, sometimes in a single line among many.
A requirement that the contractor work in accordance with the accepted programme, which has a similar effect.
Or an acceptance procedure under which the accepted programme becomes the reference point for assessment, which is the NEC approach and is deliberate rather than accidental.
The acceptance question
Where the contract provides for acceptance, an unaccepted programme sits in an awkward position and the parties frequently proceed as though it were accepted.
That is a weak place to be when a delay claim arrives, because the reference point for assessment is in dispute before the facts are reached.
Chasing acceptance is unglamorous and it is worth more to both parties than almost anything else in programme administration.
Float and the contractual programme
Where the programme shows completion earlier than the contract date, the gap is terminal float, and who may use it is a familiar argument.
A programme that becomes contractual sharpens that argument, because the sequence and the dates in it carry more weight.
It is worth knowing which position the contract takes before relying on the float for either purpose.
Updates and revisions
Where the programme is contractual, revisions matter: the current reference point may be the latest accepted revision rather than the original.
Contracts differ on whether revision changes the obligation or merely records progress, and the wording is worth reading.
Keeping revisions dated, submitted and acknowledged removes most of the scope for argument on this point at almost no cost.
What it means for a delay claim
A contractual programme gives the claim a firmer baseline, which is usually to the contractor’s advantage when employer risk events are relied on.
It also gives the employer a firmer basis for saying the contractor departed from the agreed sequence.
Which of those dominates depends on the facts, and on how well the programme was maintained while the work was running.
What it means at tender
The amendment is worth pricing, in the sense of understanding what it commits the contractor to before the tender is submitted.
Where the programme submitted with a tender becomes contractual, the sequence in it needs to be one the contractor can actually work to.
A tender programme produced to show a deliverable date, rather than a workable sequence, becomes a liability the moment it is incorporated.
Where no programme was ever provided
The contractual requirement was breached, which matters less in practice than the evidential hole it leaves.
Without a baseline there is no reference point for assessing the effect of any event, which weakens claims and defences alike.
Reconstructing one is possible and should be identified as a reconstruction, because presenting it otherwise is the kind of thing that undermines an otherwise sound claim.
Practical administration
Submit it, chase acceptance, revise it when the work changes, and keep the record of each step.
Mark on it the information required and when, because that is what turns a programme into a management document rather than a compliance exercise.
None of this is claims work, and all of it is what makes claims short when they become necessary.
Reading the clause
The relevant words are usually in the contract particulars or in a schedule of amendments rather than in the body of the form.
They are short, and the difference between information and obligation is usually a single phrase.
An hour spent on this at the start of a project is worth more than any amount of argument about it afterwards.
Where the parties disagree about status
It happens, usually once a claim has arrived, and it is a question of construction rather than of fact.
Establishing what was submitted, when, and what was said in response frequently resolves it without reaching the legal question.
That factual work is needed for the claim in any event, so it is rarely wasted.
Where it fits
The status of the programme is established before any analysis, because it governs what the analysis can rely on.
Whether an amendment has changed the position is initial dispute review work and takes very little time.
Maintaining the programme during the works belongs with commercial management, and it is the cheapest protection either party has on time risk.
It is also the part most often dropped when the project gets busy, which is precisely when the programme is doing the most work and is worth the most to whichever party kept it up to date.
Running late with nobody agreeing why?
Extension of time claim preparation sets out the events relied on, their effect on the programme and the contractual route to relief, in a form that can be assessed rather than argued over.