Is the programme a contract document
Two standard forms, two opposite answers. Working under one while thinking in the other is a reliable way to lose an argument about delay.
QScope Team · 30 March 2026 · 4 min read
Under the JCT forms the contractor provides a master programme, and the contract usually says in terms that it does not impose obligations beyond those in the contract documents. It is information, not an obligation.
Under NEC the Accepted Programme is a contract document in the fullest sense, and compensation events are assessed against it. Failure to submit an acceptable programme has direct payment consequences.
What that means under JCT
The contractor is obliged to complete by the completion date. How it sequences the work is its own business. It can build in any order it likes, and an employer who objects to the sequence has no contractual footing unless the contract says otherwise.
Equally, the contractor cannot hold the employer to programme dates for information or access unless those dates are in the contract. A programme showing information required on 1 March does not create an obligation to provide it on 1 March.
Why it still matters enormously
Because delay is assessed against it. When a relevant event is claimed, the question is whether it delayed completion, and the only way to answer that is to look at what the plan was and what happened to it.
A contractor with a well-maintained, regularly updated programme has a delay analysis. One with a bar chart drawn at tender and never touched has an argument.
Updating it
The value of a programme as evidence comes entirely from it being contemporaneous. A programme updated monthly, showing actual progress against plan, is a record. A programme reconstructed at the end to demonstrate a claim is an exhibit, and it is treated as one.
Most contracts require periodic updates. That obligation is worth complying with even where nobody is chasing it, because the party that benefits most is the one submitting.
Making it contractual on purpose
Some employers amend JCT to make the programme a contract document, or to require key dates. That can work, and it cuts both ways: it gives the employer sequencing certainty and gives the contractor dates it can hold the employer to.
What it should not be is done casually. A programme elevated to contractual status without thinking through the information release dates inside it hands the contractor a set of employer obligations nobody negotiated.
The commercial version
Separate from all of that, a surveyor needs a simple programme showing the dates that carry money: possession, sectional completion dates, practical completion, the rectification period end. Those four are the ones that appear in the account, and they should live where the account does.
QScope keeps a commercial programme with milestones against the contract dates, so the dates that carry consequences are recorded where the money is.