Why NEC4 is a Formula One car, not a Mini

Teams that treat NEC4 like a traditional contract find out early, and expensively, that it does not forgive the same mistakes.

Two kinds of vehicle

At Sypro’s October webinar, Dr Stuart Kings, one of the nine drafters of NEC4, offered a comparison that will be familiar to anyone who has moved between contract suites. Traditional forms, he said, “in terms of the procedures and deadlines and remedies, they’re quite forgiving and, if I dare say, a little bit ambiguous. And it’s a little bit like getting into a Mini, and you can just stick it into gear and drive off.”

NEC4, by contrast, is a Formula One car. It is highly engineered, and it performs brilliantly when driven properly. But it demands preparation, it punishes mistakes quickly, and it is very obvious when a team does not know what it is doing.

What makes NEC4 different

The difference is prescription. NEC4 sets out what must happen at the start of a project, how change is managed, how the programme is submitted and accepted, and how the project is closed out. Each step has a named actor, a timescale and, in many cases, a remedy for failure.

The programme is a good example. The contractor submits a revised programme at the interval set in the Contract Data, often monthly, and the Project Manager has two weeks to accept it or not accept it for one of four stated reasons. Compensation events follow a similar pattern, with eight weeks to notify, three weeks to quote and two weeks to reply, and default outcomes if a party misses its deadline.

In a traditional form, a missed response might simply leave a matter open. Under NEC4, it can mean a quotation is treated as accepted, a claim is time barred, or a Project Manager makes an assessment the contractor never had the chance to influence.

Risk management works the same way. The Project Manager must prepare the first Early Warning Register within one week of the starting date and hold the first early warning meeting within two weeks. A contractor that fails to give an early warning it could have given may see a compensation event assessed as if the warning had been given. Even communication is prescribed: where the Scope names a communication system, a notice sent any other way has no effect.

None of this is hidden. It is all in the contract. The problem is that teams used to more forgiving forms do not expect the contract to mean exactly what it says.

The cost of driving it like a Mini

The industry data shows what happens when teams are not prepared. The 2024 Construction Adjudication in the United Kingdom report from King’s College London and The Adjudication Society found that half of respondents cited inadequate contract management as a notable cause of disputes, and 42% cited a lack of competence among project participants, down from 48% the year before. Arcadis’s Global Construction Disputes Report has repeatedly named failure to properly administer the contract as the most common cause of disputes.

Those are not failures of the contract. They are failures of preparation and administration. A team that signs an NEC4 contract and then runs it the way it would run a traditional form will miss the timebars, the reply periods and the separate notice requirements, and will discover them only when the other party relies on them.

Prescription is a feature, not a flaw

It would be easy to conclude that NEC4 is simply harder. That misses the point. Stuart was clear that it is prescriptive “for good reason”. The deadlines force decisions while the facts are fresh. The remedies stop matters being left at large until the final account. Assessing time and money together under one compensation event avoids the global extension of time arguments that plague other forms.

The prescription is what makes NEC4 a management tool rather than just a legal framework. When the procedures are followed, both parties know where they stand throughout the project, and disputes are confined to genuine questions of interpretation rather than arguments about what was notified, when.

Preparing the team

If NEC4 is a Formula One car, the team needs the equivalent of a pit crew and a pre race checklist.

Train the people who administer the contract. Accreditation programmes for NEC4 Project Managers and supervisors exist for good reason. Competence is the first defence against dispute.

Use a commencement checklist. Work through every clause at the start, confirm who owns each action and tick it off jointly.

Hold a launch event. Bring client, Project Manager, contractor and finance together to agree how the contract will be run, including working arrangements between the formal deadlines.

Use the right instruments. A specified communication system and a live view of every deadline turn the contract’s prescription from a risk into a discipline.

The right car for the job

Nobody would hand the keys of a Formula One car to someone who has only driven a Mini and expect them to win. NEC4 rewards teams who respect what it is: precise, demanding and, when driven well, very effective at delivering projects on time and within budget.

Meet the author Dr Stuart Kings

NEC4 Drafter & Co-author

PhD, MRICS, MCIPS, BSc (Hons)

View Profile

Share