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.

NEC contracts have become the backbone of UK infrastructure, utility and engineering projects. Whether you are bidding for work in energy, rail, highways, water, industrial facilities or major civils packages, your NEC tender submission is now a core differentiator and the Procurement Act 2023 has raised the bar even higher. Procurement expectations now reward stronger planning evidence and measurable Social Value. Bidders must now demonstrate: robust planning & controls cap

Excel is great for registers and dashboards, but risky as the master NEC programme. Here are 7 pitfalls that undermine cause and effect, plus fixes using a lean logic linked schedule.

NEC Whitepaper: “The History of NEC – Evolving to be the world’s favourite procurement suite” The NEC story is not just “contract history”; it explains why NEC projects succeed or fail in practice. The NEC whitepaper traces the suite from its origins in the late 1980s to the current NEC4 era, highlighting the consistent theme: NEC is designed to stimulate good project management, not merely allocate legal risk after the event. First, NEC is explicit that collaboration is “har

The programme used to sit alongside the job. Now it often reveals whether the job is really under control. This article explains why construction planning has become a more serious commercial function, and why the firms that maintain a believable live time position are starting to separate themselves from those that reconstruct one later.

A contractor performance dashboard that turns progress meetings into decision sessions: clear KPIs, plan vs actual trends, obstacles, and mitigation—built to satisfy NEC and FIDIC reporting expectations.

Contractors lose entitlement on NEC4 Compensation Events when the process is loose: missed 8-week time bar, wrong Accepted Programme at the dividing date, weak notices and quotations with no programme story. Here are 7 pitfalls and the controls that fix them.

Time Risk Allowances are not padding. Under NEC, they are part of realistic planning. Clause 31.2 requires the contractor’s programme to show float and time risk allowances, and the NEC guidance is clear that where reasonable TRA is missing, unclear or not shown properly, the Project Manager has grounds not to accept the programme because it does not represent the contractor’s plans realistically or does not show the information the contract requires. That sounds technical, b