Planning advice for contractors

Most JCT and NEC comparisons stop at philosophy: one allocates risk, the other encourages collaboration. Both true, and useless when the project manager has just rejected your programme. This is what actually changes when a team fluent in JCT runs an NEC job: the programme becomes a contractual instrument, extensions of time become compensation events on an eight-week clock, change is valued from Defined Cost rather than your rates, and early warnings acquire a price.

The notice says not accepted, and what happens next decides more than the fate of one submission. This playbook covers the moment in full: the four reasons Clause 31.3 permits and why they are the only four, the detail a notice must give you under Clause 13.4, the triage that sorts right from wrong from unclear, when withholding acceptance becomes a compensation event under 60.1(9), and the cost of drifting while the Accepted Programme goes stale.

In June 2026 the High Court refused to enforce a £1.65m NEC adjudication award in Premier Modular v Maidstone and Tunbridge Wells NHS Trust. The legal headline is natural justice. The lesson for contractors is a project controls one. The whole dispute turned on which programme was the Accepted Programme, and the date the claim relied on was never in it. Under NEC, a compensation event is only as good as the Accepted Programme it stands on, and acceptance is a status you earn,

Most contractors prepare NEC programmes for submission. The strongest contractors prepare them for review. The difference is whether the planning team knows what the project manager actually checks, in what order, and what triggers rejection at each step. This article walks through the review sequence as the project manager experiences it: the first thirty seconds, the structural integrity pass, the clause 31.2 information check, the realism test, and the scope compliance che

Most NEC4 time impact assessments fail at the project manager's desk, not in the planning team. The analysis is usually sound. The structure is what fails. This article explains the five elements every accepted assessment contains: the dividing date with justification, the accepted programme with version, the compensation event fragnet built in isolation, the impacted programme with the calculation, and the narrative that walks the project manager through the cause and effect

A programme that has lost integrity does not announce itself. It looks exactly like one that works. The problems only surface when a compensation event tests it and the programme cannot answer the one question the NEC contract keeps asking. This article describes five signs any project director can check in ten minutes, without specialist planning knowledge, to know whether the programme is protecting their commercial position or quietly giving it away.

Most contractors submit programme revisions that update progress, move the data date forward, and miss everything else clause 32 requires. The project manager receives a schedule that shows where the job is but not what the contractor is doing about it. That is not a revision. It is a progress snapshot. This article explains what a clause 32 programme revision actually needs to contain, why most revisions are rejected, and what to do when the project manager is deliberately a

Most contractors treat clause 31 as a procedural hurdle to clear at the start of the job. Submit the programme, wait for acceptance, move on. That approach quietly hands commercial control to the project manager. This article explains what the accepted programme actually protects, how the deemed acceptance mechanism works, and why a programme that was accepted at mobilisation provides almost no commercial protection by month six.

On NEC Options C and D, real cost can still become vulnerable when the accepted programme and the cost record stop telling the same story. This article looks at the hidden commercial fracture between planning and QS records, and why that is where Defined Cost recovery often starts to fail.

For mechanical, electrical, civil, groundworks and fit-out contractors, the accepted programme often only becomes important when change or delay lands on a programme that no longer reflects the live job. This article explains why that drift matters under NEC and how programme protection is often lost by degrees, not all at once.

Many specialist subcontractors run NEC packages without a full planning team. The issue is not team size. It is whether the programme stays live, current and commercially usable while the job is moving.

Where multiple compensation events arise under NEC4, separate assessment is usually the safer route. This guide explains the accepted programme, the dividing date, and why one blended impact programme can weaken traceability.

Time Risk Allowance and terminal float both create breathing space in an NEC programme. That is why contractors often confuse them. But they sit in different places, serve different purposes, and blurring the line between them weakens programme acceptance, distorts the update cycle, and makes compensation event assessments harder to defend. This article explains what each one actually is, how they connect without being the same, and why keeping the distinction clean matters c

A practical NEC3 vs NEC4 comparison focused on programme acceptance, treated acceptance, early warning discipline and CE integration, based on NEC’s “Next Generation” white paper.

Clause 64 is not a procedural fallback. It is the contract's switching mechanism for commercial control of valuation. When the contractor submits compliant quotations on time with current programme information, the contractor controls valuation. When the contractor fails to meet any of the four conditions, the contract switches that control to the project manager, with consequences that typically reduce entitlement by thirty to sixty percent.

An accepted programme is not a procedural document. It is the shared reference frame against which every compensation event is assessed, every delay analysed, every progress conversation grounded. When it is missing, the reference frame itself becomes contested, and that contest favours the project manager. This is what the absence of an accepted programme actually means commercially, why it shifts control, and how contractors recover the position before the damage compounds.

Most contractors ask how to get NEC4 compensation event quotations agreed. The question is the wrong one. The strongest contractors ask what makes a quotation acceptable to a project manager who wants to accept it and what makes a quotation rejectable by a project manager looking for reasons to reject. The first optimises for completeness. The second optimises for acceptability. The two are not the same.

A UK Tier 2 contractor with a strong NEC track record won its first major FIDIC contract and was in dispute eighteen months later. A UK contractor with extensive FIDIC experience won an NEC4 contract and had the project manager invoking clause 64 within six months. Both failures had the same underlying cause: contractors who switch between NEC and FIDIC without recognising that the two contracts reward fundamentally different organisational capabilities.

NEC contract administration today still works the way it worked in 1993. A programme gets submitted as a document. The project manager reviews it as a document. Acceptance is recorded as a document. The contractual machinery is electronic in form and paper in function. This is changing faster than most contractors have absorbed, and not in the way the industry talks about.

UK adjudication data records 2,264 referrals between May 2023 and April 2024, with inadequate contract administration identified as the leading cause of disputes at 50 per cent of cases. Behind that figure sits a pattern most experienced commercial directors recognise. Contractors with weak NEC4 programme compliance lose disproportionately on change assessment, on delay narratives, on cashflow timing, and on tender evaluation. The losses are not random.