Planning advice for contractors

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.

Evaluators have seen thousands of Social Value statements. The difference between a low score and a high one is rarely intent. It is evidence, deliverability, and a clear audit trail. This article explains what PPN 002 and the Social Value Model actually require, why most tender answers still fall short, and what a contract-linked jobs-and-skills commitment needs to stand up to post-award scrutiny.

There is a four-to-twelve-week window between contract award and site mobilisation that the contractor's commercial outturn depends on more than any other stage of delivery. It is unremarkable in most calendars and rarely discussed at board level. Yet what gets set up during this window will determine, more than any subsequent decision, whether the project's commercial position is defensible at month eighteen. Pre-construction is not preparation.

An NEC tender bid is scored question by question, and the courts have read what evaluators wrote. This guide follows four real cases, from a road interchange tendered on NEC3 to an NEC4 programme question, shows how close the scores run, explains the assessment summary each assessed bidder now receives, and sets out what to check in a tender programme before it goes in.

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

Water, power networks, carbon capture and nuclear have well over £100 billion of approved spending ahead of them, most of it on assets that have to keep running. Those tenders are not won on the same things as a school or an office. They turn on outage windows the client booked long ago and on equipment that can take two years to make. What evaluators check in an industrial tender programme, and how it becomes the contract baseline under NEC4.