NEC4 is gaining ground where JCT has dominated. Here's what's actually different, when each contract framework makes sense, and what your software must handle.
For most of my career, the contract question for commercial fit-out and refurbishment was simple: JCT Minor Works or Intermediate. Maybe the full Standard Building Contract for something larger. JCT was the default for private sector work in the UK, and nobody questioned it.
That's been changing. Over the past few years, I've seen NEC4 turning up on projects where five years ago it would have been JCT without question. Private developers, commercial landlords, even some local authority framework projects that used to specify JCT are now asking for NEC4 terms. For small contractors who've spent their entire careers under JCT, this creates a problem: they're being asked to tender under a contract framework they don't fully understand.
So let's cut through it. What's actually different? When does each framework make sense? And what should you watch out for?
JCT and NEC come from fundamentally different philosophies.
JCT is adversarial by nature. It doesn't pretend otherwise. It allocates risk, defines obligations, and provides mechanisms for resolving disputes when things go wrong. The assumption is that the parties will look after their own interests, and the contract exists to define the boundaries.
NEC is collaborative by design. It requires the parties to act "in a spirit of mutual trust and cooperation." That's not just a nice sentiment — it's a contractual obligation. The whole framework is built around early warning, shared risk management, and collaborative problem-solving. The assumption is that problems are better resolved together than through adversarial claim processes.
In practice, the difference is less dramatic than the theory suggests. NEC projects can be just as adversarial as JCT ones when the relationship breaks down. And JCT projects can be perfectly collaborative when the parties want them to be. But the contract terms do shape behaviour, and the NEC structure pushes towards early engagement in a way that JCT doesn't.
Risk allocation. NEC uses a "Risk Register" approach where risks are identified, allocated, and managed collaboratively throughout the project. JCT allocates risk at the outset through the contract terms and leaves the parties to manage their own.
Compensation events vs variations. This is the biggest practical difference. Under JCT, you have variations (changes to the works) and loss and expense (financial compensation for employer-caused problems). Under NEC, these are combined into "compensation events" — a single mechanism that covers both time and cost effects of qualifying events.
The NEC compensation event process has strict timelines. The contractor must notify a compensation event within eight weeks of becoming aware of it. The project manager has one week to respond. If the contractor is asked to submit a quotation, it must be submitted within three weeks. If the project manager doesn't respond to the quotation within two weeks, it's deemed accepted.
These timelines are tighter than JCT, and they're enforced. Miss the eight-week notification window under NEC and you lose the entitlement. Under JCT, late notification weakens your position but rarely extinguishes the claim entirely.
Programme. NEC puts the programme at the centre of contract administration. The contractor must submit a programme for acceptance, update it regularly, and the programme is used to assess compensation events. JCT mentions the programme but doesn't give it the same contractual weight.
For small contractors, this means the programme under NEC isn't just a management tool — it's a contractual document. It needs to be realistic, regularly updated, and properly maintained. The loose approach to programming that many small contractors get away with under JCT won't work under NEC.
Payment. NEC uses a defined cost-based approach for some payment options (particularly Options C and D), which requires open-book accounting. JCT typically uses activity schedules or bills of quantities, with payment based on the value of work done. Under NEC Option A (priced contract with activity schedule), the mechanism is more similar to JCT — payment for completed activities.
Early warnings. NEC requires either party to give early warning of any matter that could increase cost, delay completion, or impair performance. This is a proactive obligation — you're required to flag potential problems as soon as you become aware of them, even before they've materialised. JCT has no equivalent requirement.
JCT remains the better choice for:
Straightforward private sector projects. Commercial fit-outs, refurbishments, and alterations where the scope is well-defined, the procurement is traditional, and the parties are experienced in JCT administration. The contract is familiar, the case law is extensive, and everyone knows how it works.
Projects with clear risk allocation. When the employer wants to fix the risk allocation at the outset and let the contractor manage delivery, JCT's approach is efficient. The contractor prices the risk, takes responsibility for delivery, and claims only for qualifying events.
Small projects. JCT Minor Works remains the simplest and most proportionate contract for genuinely small, simple works. NEC doesn't have an equivalent lightweight form — even the NEC4 Short Contract has more administrative requirements than JCT MW.
When the design team is experienced with JCT. Contract administration under JCT and NEC is different. If the architect and QS have administered 200 JCT projects and zero NEC projects, putting them on an NEC contract creates risk. The administrative procedures, notice requirements, and programme management obligations under NEC require specific experience.
NEC is worth considering for:
Projects with significant uncertainty. When the scope isn't fully defined at tender, when design is developing during construction, or when site conditions are unpredictable. NEC's compensation event mechanism handles change more fluidly than JCT's variation process.
Collaborative procurement. When the employer wants an integrated team approach — early contractor involvement, shared risk management, target cost arrangements. NEC Options C and D (target cost contracts) enable gainshare/painshare arrangements that JCT doesn't support natively.
Public sector and framework work. Many public sector frameworks now specify NEC, particularly for infrastructure and larger building projects. If you're tendering for framework work, NEC competence is increasingly a requirement.
Complex programmes. When programme management is critical and the contract needs to reflect programme performance, NEC's approach gives the programme contractual status that JCT doesn't.
If you're working under NEC for the first time:
Understand the notification timelines. Eight weeks to notify a compensation event. Three weeks to submit a quotation. These are hard deadlines under NEC, not soft targets. Miss them and you lose entitlement. Set up a tracking system from day one.
Take the programme seriously. Your programme under NEC isn't a nice-to-have — it's a contractual document used to assess time impacts. Keep it realistic, submit it for acceptance, and update it regularly. An unaccepted programme weakens your position on every compensation event.
Get familiar with the defined cost calculations. If you're on an NEC Option C or D contract, you'll need to demonstrate your actual costs transparently. This means proper cost recording, time allocation, and open-book accounting. The commercial approach is different from JCT lump-sum contracting.
Early warning everything. Under NEC, early warning is not a sign of weakness — it's a contractual requirement. If you can see a potential problem developing, notify it. The early warning register is your risk management tool and your evidence trail.
Don't assume JCT knowledge transfers directly. The language is different, the procedures are different, and the administrative requirements are different. If you're going to work under NEC regularly, invest in training. A two-day NEC4 course is worth the money.
For most small contractors doing commercial fit-out and refurbishment, JCT will remain the default for the foreseeable future. But NEC is becoming more common, and the ability to work competently under both frameworks is increasingly a competitive advantage.
At Construction AI, the financial module works as both JCT contract management software and NEC4 contract management software — tracking variations or compensation events, managing payment applications against either framework, and monitoring the notification timelines that NEC requires. Combined with the project management tools for programme management and correspondence, the system adapts to whichever contract framework the project is running under.
Whatever framework you're working under, the fundamentals don't change: know the contract, meet the deadlines, and keep records. The contract framework is the rulebook. Read it before the game starts.
Stephen Mckenna MCIOB
30+ years in UK commercial construction, from site management to director level. Now building the project management tools he wished he'd had.
Tier-one contractor processes shouldn't only be available to tier-one contractors. Drawing registers, document control, RFIs, programmes, financial tracking — built for how you actually run projects, priced so any construction business can access them. Get started today.
By subscribing, you agree to our Privacy Policy.
A delay that isn't notified is a delay you'll pay for. Here's how to identify delay events, notify properly, and build EOT claims that actually succeed.
Practical completion triggers half your contract obligations. Here's what it actually means, the common arguments, and how to manage the process properly.
Choosing the wrong JCT contract costs thousands. A practical guide to when Minor Works is right, when you need Intermediate, and the grey area in between.
Tier-one processes, priced for any size business. Get started today.