On NEC nuclear and energy projects, the contract's quality, records and change procedures have to bear heavier loads than usual, because requirements can be demanding and the work can run for years. The core clauses don't change, but the Scope and quality plan become very detailed, and uncertainty often pushes parties towards cost-based Options.
This page gives general contract points under the NEC4 Engineering and Construction Contract (ECC). It doesn't describe any operator's or regulator's rules. Those rules will appear in your Scope, Z clauses and the law that applies, so read them first. For the general routine, see managing NEC contracts.
Where the contract feels the pressure
| Issue | What to check | Clause (NEC4 ECC) |
|---|---|---|
| Quality requirements | Quality management system, quality plan and how far the Scope prescribes them | 40.1, 40.2, 40.3 |
| Hold and witness points | Are they in the Scope or the quality plan? Who gives notice, and what if the witness is late? | 41.3, 41.5, 60.1(11) |
| Tests before delivery | Plant tested off site, and no delivery until it passes | 42.1 |
| Changing requirements | A changed Scope, or a change in the law | 14.3, 60.1(1), X2.1 |
| Long-lead Plant and Materials | Vesting, payment and the Scope's requirements on delivery | Clause 70 and the Scope |
| Long duration | Price movement over years | X1 |
| Site access rules | Security clearance, training, restricted working | Scope, 31.2, 60.1(1) |
| Long-term performance | Low performance damages, whole life cost | X17, X21 |
Quality and records
NEC4's clause 40 gives quality a clear home. The Contractor provides a quality policy statement and quality plan within the period in the Contract Data (40.2), and a failure to follow the plan can lead to an instruction to correct it (40.3). On a highly regulated job, the Scope will often add to this.
- Make the quality plan and programme agree. Each hold or witness point takes time. Show the time and who's needed on the programme, or planned Completion is fiction.
- Track notices for inspections. Clause 41.3 expects notice in time to attend. Build it into your plan, and read your Scope for what happens if a hold point is missed.
- Keep records of the record. Know exactly where each batch of test and traceability documents sits. The Contractor's records may need to outlast the job, and the Scope can set that period.
See quality management under NEC and tests and inspections.
Changing requirements
Requirements can move during a long project, and the source of the change decides the contract's response.
| Source | Likely route |
|---|---|
| The Client changes the specification | Instruction under 14.3 and 60.1(1) |
| A change in the law, with Option X2 in the contract | A compensation event under X2.1. Check the event's conditions, including the date |
| A change in the law, without X2 | Look at where the risk lies, including any relevant Z clause, and consider 60.1(19) |
| A regulator's or operator's new interpretation, with no change in law or Scope | Not obviously any of these. Discuss it early, and clarify whether the Client will instruct a change |
A fictional example. A cable replacement job is halfway through when the operator's new inspection procedure requires an extra witness point at each joint. The Contractor warns that its gang outputs will fall. The Project Manager needs to decide whether the procedure changes the Scope. If the Scope says the latest procedure applies, the Contractor may have priced that risk. If the Scope names a specific revision, a new revision being instructed looks like a change to the Scope, under 60.1(1). This is why Scope drafting has to say which version of a procedure applies.
Choosing the Option
Where the work can't be well defined at tender, Options C, D or E are often considered over A or B. If so, the Parties need strong records, a clear view of Disallowed Cost and well-managed targets over the long term. Early contractor involvement can also suit this sort of uncertainty. See early contractor involvement and target cost and share.
Practical points for long projects
- Plan for staff turnover. Over many years, the people who wrote the Scope and first notices may leave. A clear audit trail is your only memory.
- Keep the compensation event backlog short. Long gaps between event and implementation weaken the forecast basis of the assessment.
- Check Key Dates against outages. Power generation and grid connections often come with narrow windows that the rest of the plan has to fit.
- Consider the supply chain's capability. Requirements may need to pass down in subcontracts, including those that affect quality and access. See managing NEC subcontracts.
Related guides
- Managing NEC Contracts: A Practical Guide
- NEC on Building Projects
- NEC on Maintenance and Term Contracts
- The Most Common NEC Mistakes
- NEC on Rail Projects
- NEC on Water Projects
See how this works in practice
Click through Contract Status with sample contracts: raise the notice, reply to it, and watch both sides of one record.
Take the guided tour Book a demo
Get free NEC templates, use the free NEC tools or download free NEC templates.
This guide is general information in our own words, not legal advice. Your contract and its Contract Data always govern. NEC, NEC3 and NEC4 are trade marks of Thomas Telford Ltd; Contract Status is not affiliated with or endorsed by NEC.