Planning advice for contractors

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 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.

The programme schedule goes to the planner. The programme narrative goes to the decision-maker. Most contractors write one that describes the Gantt rather than argues the case. Here is why that costs them at clarification and what a strong narrative actually does.

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.

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.

Clause 15 only works when early warnings trigger decisions and programme movement. Here’s a quantified register method and weekly rhythm you can run on real jobs.

The NEC4 compensation event time bar is the most asymmetric provision in the entire contract. Almost every other NEC provision creates a spectrum of outcomes through judgement, extension mechanisms, or proportionate consequences. The eight-week time bar creates a cliff: notifications inside the period preserve entitlement, notifications outside it forfeit it entirely. The contractor who understands this asymmetry organises their administration around it.

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.

Every subcontractor delay on an NEC4 project is two delays at once. The subcontract event runs on its own clock with its own notification requirements, evidence, and commercial outcomes. The head contract event runs on a parallel clock with its own clause 61.3 window, its own assessment, and its own clause 64 vulnerability. Most contractors run one of these processes diligently and the other partially or not at all.

Under the Procurement Act 2023, the question contracting authorities are asking when they evaluate bids has changed. They are not asking "can you deliver this competitively." They are asking "can this selection be defended through the contract life under the published transparency regime." The two questions sound similar. They are not. This is the complete analysis of how UK contractors win NEC tenders in 2026: what changed on 24 February 2025.

Excel is not a planning tool. It is a calculation tool with planning-shaped output. NEC contracts are built on logic recalculation. The seven recurring pitfalls of Excel programmes on NEC projects are not seven separate problems with seven separate fixes. They are seven symptoms of one structural mismatch between the category of tool and the category of contract. This is the complete analysis: why Excel cannot perform the contractual functions.

NEC did not arrive fully formed. It evolved as a deliberate response to the failures of the contracts that preceded it, and every clause in the current NEC4 suite carries the imprint of a specific problem that JCT and ICE could not solve. The history is not background to contemporary NEC practice. It is the explanation of why the controls matter, what the contract was designed to prevent, and how contractors who understand the evolution administer the contract more effectivel

There was a time when a construction programme could survive as a polite fiction. That time is ending. In modern UK construction, the programme has quietly become the document that reveals whether a contractor is genuinely managing time or simply explaining it after the event. The dividing line is no longer between firms with newer software and firms with older software. It is between firms that maintain a believable live time position and firms that periodically reconstruct

Most construction delivery teams still rely on fragmented spreadsheets, scattered emails and static PDF reports that take hours to compile and rarely tell the full story. The Contractor Performance Dashboard consolidates everything a Project Manager, Planner, QS or Site Manager needs into one coherent view: live SPI tracking, plan-versus-actual S-curves, structured obstacle logs, work-pack variance, four-week lookahead and compensation event evidence.

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. This is the editorial

Every contractor running an NEC4 contract loses some compensation event entitlement that the contract would otherwise have delivered. The amount lost is not random. It is the predictable consequence of seven specific failure modes that recur across contractor types, contract sizes and sectors. Each is preventable through operational discipline.