Topic hub
NEC4 programme controls — schedule, risk and early warnings
How NEC4 actually changes the day-to-day controls function. The Accepted Programme under Clauses 31 and 32, Compensation Events, Early Warnings as a working mechanism, and earned value reporting under Options C, D and E.
About this topic
NEC4 is the dominant contract suite on UK public-sector capital programmes — most of Network Rail’s enhancement portfolio (CP6 and CP7), large parts of National Highways’ Road Investment Strategy works, AMP7 and AMP8 water programmes, Environment Agency capital schemes, and a wide range of HM Treasury-funded major projects. The NEC4 Engineering and Construction Contract (ECC) replaced NEC3 in 2017 and is published by the Institution of Civil Engineers. Its main pricing options run from Option A (priced contract with activity schedule — broadly a lump sum) through Option B (priced contract with bill of quantities), Options C and D (target contracts with activity schedule or bill of quantities, sharing pain and gain against the target cost), Option E (cost reimbursable), to Option F (management contract). The choice of option is not a procurement detail — it determines what the controls function has to measure, what evidence the Project Manager needs to assess, and how aggressively the Contractor will work to capture every line of Defined Cost. NEC4 is preferred over FIDIC and JCT on UK public works because of its plain-English drafting, its bias toward collaborative working, and its formal Early Warning and Compensation Event machinery — but those same features create controls obligations that teams arriving from other contract heritages routinely underestimate.
Clauses 31 and 32 sit at the centre of NEC4 for the planner. Clause 31 sets out what the first Programme submitted for Acceptance must contain — the starting date, access dates, key dates, completion dates, planned dates for each operation, order and timing of work, float, time risk allowances, health and safety requirements, the resources required, and a statement of how the Contractor plans to do the work. Clause 32 then requires the Contractor to submit a revised programme at the intervals set in the Contract Data, when instructed by the Project Manager, and within each Compensation Event quotation. The Project Manager has two weeks to accept or to give one of the four contractual reasons for non-acceptance — the programme is not practicable, does not show the information required, does not represent the Contractor’s plans realistically, or does not comply with the Works Information. A programme that is not Accepted is a much weaker contractual document; in dispute, the last Accepted Programme is what the adjudicator will work from. Compensation Events under Clause 60 (a defined list of nineteen circumstances ranging from Project Manager instructions to weather measured against the Contract Weather Data) must be notified within eight weeks of the Contractor becoming aware, must be quoted with a change in Prices and Completion Date, and crucially must show their effect on the Accepted Programme. A controls function that cannot demonstrate, activity by activity, how a CE moves the planned dates is a controls function that loses CE valuations at assessment.
NEC4 does not mandate earned value reporting by name — there is no clause that says "the Contractor shall report against ANSI/EIA-748" — but the Options C, D and E target-cost and cost-reimbursable regimes produce data that maps directly onto an earned value system, and many public-sector Employers add a Z-clause requiring EVM-grade reporting. Under Option C, the Contractor is paid Defined Cost plus a Fee, with a target cost set at contract award; pain and gain are shared against that target according to the share ranges in the Contract Data. The controls implication is that Defined Cost (Schedule of Cost Components, with disallowed items stripped out) has to be tracked at activity level against the Accepted Programme, and the Contractor’s forecast Final Defined Cost has to be maintained and submitted at the cycle set in the Contract Data. That is, in practice, an EVM system: BCWS comes from the Accepted Programme, BCWP comes from progress against the activities, ACWP is Defined Cost less Disallowed Cost, and CPI/SPI fall out of the arithmetic. The mistake teams make is treating the NEC4 cost report and the EVM report as separate documents — they should be the same dataset cut two ways. On Option A and B fixed-price work, EVM is not contractually required and the Contractor has no incentive to expose cost data; what the Employer can ask for is progress against the activity schedule, which still gives SPI but not CPI. Where EVM is genuinely required (DEF STAN contracts, GMPP programmes), the Z-clause should reference ANSI/EIA-748 explicitly and the Integrated Baseline Review should sit alongside Programme Acceptance.
Clause 15 — the Early Warning mechanism — is the part of NEC4 that practitioners talk about most and use worst. The clause requires either party to notify the other as soon as they become aware of any matter that could increase the total of the Prices, delay Completion, delay a Key Date, or impair the performance of the works in use. The Project Manager then enters the matter on the Early Warning Register and the parties hold an Early Warning Meeting to consider how to avoid or mitigate the impact. Done properly, this is a live, weekly conversation between the controls leads on both sides, and the register becomes the working interface between the project risk register and the contract. Done badly — which is most of the time — Early Warnings become defensive contractual records issued only when a Contractor wants to preserve a Compensation Event entitlement, or a tickbox that the Project Manager populates from monthly reports rather than from real conversations. The asymmetric incentive is real: a Contractor who fails to give Early Warning of a matter they could reasonably have been aware of is at risk of having a later Compensation Event assessed as if they had given it (Clause 63.7), so there is a strong defensive impulse to notify everything. The fix is to integrate the Early Warning Register and the project risk register in a single workflow, to treat the EW Meeting as the recurring risk-management forum rather than a separate exception process, and to use the register’s mitigation actions as visible inputs into the next monthly schedule update. None of this is exotic; it just requires the controls function to actually own the mechanism rather than leave it to the commercial team.
Guides on this topic
5 guides in this cluster
Guide
NEC4 and Schedule Risk — What the Contract Actually Expects
A plain-English guide to Clauses 31 and 32, the Accepted Programme, float allocation, compensation events, and the most common mistakes contractors and project managers make.
11 min read
Guide
NEC4 Clause 15: What Schedule Risk Looks Like in Practice
Why the compensation event mechanism makes schedule assurance non-optional — and what good looks like.
9 min read
Guide
NEC4 Clause 32: Programme Revisions and the Acceptance Loop
NEC4 Clause 32 governs how the Accepted Programme is kept current. The Contractor revises at intervals, after each compensation event, and on PM instruction. Here is what every revision must contain, why PM silence is not acceptance, and the common failures that hurt at Clause 63 quantum.
9 min read
Guide
NEC4 Early Warnings — Clause 15, Risk Reduction Meetings, Early Warning Register
Clause 15 and 16 under NEC4 — what triggers an early warning, how the Early Warning Register sits alongside the Accepted Programme, risk reduction meeting mechanics, and why early warnings are a protection tool rather than an admission of failure.
10 min read
Guide
Earned Value Management Under NEC4 — What the Contract Actually Requires
How EVM and NEC4 interact, what the contract demands, and how to build a system that satisfies both the commercial team and the programme director.
9 min read
Frequently asked
NEC4 programme controls — questions we get asked
- What does NEC4 actually require of the project controls function?
- A maintained, formally Accepted Programme (Clause 31/32); a live Early Warning mechanism (Clause 15) that operates between formal Compensation Event notifications; auditable schedule and cost records sufficient to support Compensation Event valuation; and reporting that aligns with the contract’s assumptions about how delay and cost are tracked.
- What are the headline differences between NEC4 and NEC3?
- NEC4 (2017) keeps the structural shape of NEC3 but tightens several mechanisms. The Early Warning Register replaces the NEC3 Risk Register and is owned by the Project Manager; the role names changed (Employer became Client); a new Option X22 introduced two-stage Design Build Operate; the Dispute Resolution Service Contract was added; and the Scope replaces Works Information in some publications. For the controls function, the practical changes are limited — Clauses 31, 32, 60 and 63 are recognisably the same machinery as NEC3 — but the language and roles need updating in templates and procedures, and the Early Warning Register’s formal ownership shifted in a way that affects who has the pen at the weekly EW meeting.
- What is an Accepted Programme under NEC4?
- An Accepted Programme is the Contractor’s programme that has been formally accepted by the Project Manager under Clause 31.3. It must contain the starting date, access dates, key dates, completion dates, planned dates for each operation, order and timing of work, float, time risk allowances, health and safety requirements, resources and a statement of method. Once Accepted, it becomes the contractual baseline against which Compensation Event impact is assessed and delay is tested. A programme that has been submitted but not Accepted (commonly because the Project Manager has not given a contractual reason within two weeks) is in a weaker position at adjudication — the parties will argue about what the working programme actually is.
- What is a Compensation Event and how does it affect the programme?
- A Compensation Event is one of the nineteen circumstances listed in Clause 60.1 (and any added in Contract Data Part One) that entitle the Contractor to a change in the Prices, the Completion Date or a Key Date. They must be notified within eight weeks of the Contractor becoming aware, and the quotation must include the effect on the Accepted Programme. The controls implication is that every CE quotation needs an impacted programme showing the activity-level effect of the event — not just a global delay claim. Where the controls team cannot produce that impacted programme, the Project Manager is entitled to make their own assessment, which routinely undervalues the entitlement.
- How is the Early Warning mechanism supposed to work?
- Either party gives written notice as soon as they become aware of a matter that could increase the total of the Prices, delay Completion or a Key Date, or impair performance in use. The Project Manager enters it on the Early Warning Register. An Early Warning Meeting is held to agree mitigation actions and who will take them. The register and the meeting actions feed back into the next programme revision and the project risk register. The mechanism is designed to be a working forum, not a paper trail — the test of whether it is functioning is whether the EW Meeting actions visibly change the schedule and the cost forecast, or whether they just get filed.
- When does Option C target cost beat a fixed-price Option A contract?
- Option C makes sense where scope is partially defined, where there is genuine value in collaborative cost management between Client and Contractor, and where both parties are willing to expose their cost data. Option A makes sense where scope is well-defined, the design risk sits with the Client (or has been transferred via a separate design contract), and the Client wants cost certainty at the expense of behavioural alignment. The mistake is choosing Option C as a way to start construction with an immature design and then trying to retrofit cost discipline — that produces an Option C contract where the target is meaningless, the pain/gain mechanism does not bite, and the Client carries all the cost risk. Option C requires real Schedule of Cost Components capability, real Defined Cost transparency, and an Employer-side team that can challenge Disallowed Cost; without those, it is Option E in disguise.
- What is Defined Cost under NEC4?
- Defined Cost is the cost of the components listed in the Schedule of Cost Components (long or short form, depending on the option), less Disallowed Cost. It is what the Contractor is paid under Options C, D and E (plus Fee), and what is netted against the target under Options C and D. Disallowed Cost (Clause 11.2(25)) is cost that the Project Manager decides is not justified by the Contractor’s accounts and records, was incurred only because the Contractor did not follow an acceptance or procurement procedure stated in the Scope, results from a Subcontractor’s plant or equipment being used unproductively, or was incurred due to the Contractor’s fault. The controls function has to track Defined Cost at WBS/activity level, maintain the audit trail, and operate the Disallowed Cost mechanism actively — passive cost reporting under Option C is how target cost contracts get into trouble.
- How does NEC4 dispute resolution work — W1, W2, and Adjudication?
- NEC4 offers three dispute resolution options. Option W1 applies where the Housing Grants Construction and Regeneration Act 1996 (HGCRA) does not apply (typically overseas contracts, some PFI/PPP arrangements, or contracts with a residential occupier); it provides for adjudication within set timescales and a Dispute Resolution Service. Option W2 applies where the HGCRA does apply (most UK construction contracts); it follows the Act’s requirements and allows a party to refer a dispute to adjudication at any time. Option W3 is the new NEC4 option using a standing Dispute Avoidance Board that visits the project periodically to head off disputes before they crystallise. In practice, most UK NEC4 contracts use W2. For the controls function, the key point is that the audit trail you maintain through delivery — the Accepted Programmes, the CE notifications and quotations, the Early Warning Register, the Defined Cost records — is exactly what the adjudicator will be working from. Controls discipline during delivery is dispute insurance.
Got a programme where this matters?
Most engagements start with a short call. We work out whether we’re the right fit, then come back with a short scoping note — scope, duration, team, indicative cost.