A risk register that doesn't mirror the contract is a register that won't survive its first compensation event or variation. On UK NEC4 projects and global FIDIC contracts, the contractual mechanism through which a risk materialises is as important as the risk itself.
This guide shows you how to align a risk register to NEC4 (predominantly UK infrastructure: HS2, Thames Tideway, Sellafield) and FIDIC (GCC and global EPC: NEOM, Aramco, ADNOC) so it drives commercial decisions, not just risk reviews.
Every risk on a contract-led project needs an additional field: the contractual route through which it materialises. Without this, the register can't inform NEC4 Early Warning, FIDIC notification, or compensation event quantification.
NEC4 vs FIDIC: what changes in the register
| Dimension | NEC4 (UK) | FIDIC (Global) |
|---|---|---|
| Early-warning duty | Clause 15 — mandatory, both parties. | Yellow Book Sub-Clause 8.4 (notification of likely delay). |
| Risk-trigger event | Compensation Event (CE) under Clause 60. | Variation (Clause 13) or Claim (Clause 20). |
| Quantification basis | Shorter Schedule of Cost Components. | Costs and time evaluated by Engineer/DAB. |
| Notification clock | 8 weeks from awareness (CE). | 28 days from awareness (FIDIC Red/Yellow 2017). |
| Risk-register integration | Risk Register expected at every Risk Reduction Meeting. | Engineer-led; varies by Book and Particular Conditions. |
The contract-aligned register: extra fields
On top of the standard 12 fields, contract-led projects add:
- Contract clause reference. Which CE clause (NEC4 Clause 60.1.x) or FIDIC sub-clause potentially applies.
- Notification trigger. When the early-warning / notification clock starts.
- Allocation party. Contractor / Employer / shared — mapped to the contract risk matrix.
- Liquidated damages exposure. If the risk impacts a sectional / overall completion date.
- Insurance route. Whether transferred via PI, CAR, or Delay-in-Start-Up.
NEC4: linking the register to compensation events
On NEC4 projects, the Risk Register is referenced explicitly in Clause 11.2(14) and is reviewed at every Risk Reduction Meeting (Clause 15.3). To make this work:
- Early-warning column. Mark which risks the Project Manager or Contractor has notified.
- CE clause column. Pre-map the likely CE clause (e.g. 60.1(12) physical conditions, 60.1(13) weather).
- Schedule of Cost Components readiness. The 3-point cost impact should be calculable from SCC categories, not arbitrary contingency.
- Programme acceleration vs extension of time. Schedule impact must distinguish between EoT and acceleration premium.
FIDIC: register alignment with Red, Yellow & Silver Books
FIDIC contracts (especially the 2017 second editions) demand strict notification discipline. The risk register supports this by:
- Sub-clause mapping. Variation (13), Force Majeure (18), Unforeseeable Physical Conditions (4.12), and Employer's Risks (17).
- Notification deadlines. 28-day clock for Claims under Clause 20.1 — the register flags risks approaching the trigger.
- Particular Conditions reconciliation. GCC FIDIC contracts frequently amend the General Conditions — the register must reflect the as-signed version.
- DAB / DAAB-ready quantification. Cost and time impacts presentable in the format the Dispute Avoidance Board expects.
Worked example: weather risk on a UK rail project
WHY/WHAT/HOW: “Because piling is planned through the Q1 wet-weather window, there is a risk that productivity falls 20–40%, resulting in 2–6 weeks slip and £0.3M–£0.9M cost impact.”
NEC4 mapping: Potential CE under Clause 60.1(13) if the weather exceeds a 1-in-10-year frequency at the Working Areas. SCC categories: People, Equipment, Plant & Materials, Charges. Early-warning issued at the start of the wet window.
FIDIC equivalent (Yellow Book 2017): Potential entitlement under Sub-Clause 8.5 (Exceptionally Adverse Climatic Conditions) and Sub-Clause 20.2 Claim notification within 28 days of becoming aware.
How RDE™ sharpens the contract-aligned register
Contract-related impact ranges are notoriously hard to estimate — especially CE quantum and DAB outcome bands. IQRM's Risk Data Engine™ (RDE™) calibrates these against historical NEC4 CE settlements and FIDIC claim outcomes, so the register feeds your QCRA and contingency calculation with empirically defensible numbers.
Frequently asked questions
Do we need separate registers for technical and commercial risks?
No. One register, with the contract-clause column. Splitting them fragments ownership and obscures cause-effect chains.
How often should the register be reviewed under NEC4?
At every Risk Reduction Meeting — usually monthly. Critical-path risks weekly. Anything older than 30 days is stale.
Can the FIDIC Engineer use the register as evidence?
Yes — provided the register is structured, dated, and shows the WHY/WHAT/HOW chain plus the contract sub-clause. Both DAB / DAAB and Engineer-led determinations weight it heavily.
What if the contract is a hybrid (NEC4 Option E with FIDIC sub-contracts)?
Run a single register with two contract-clause columns — primary and tier-1 sub-contract. This is increasingly common on UK rail and energy programmes.
Make your register contract-defensible
The QRM Professional Programme covers NEC4 / FIDIC register alignment, CE quantification with the SCC, and integration with QSRA / QCRA / JCL.
Explore the Programme →Related: Risk Register Guide · Construction Risk Register · Oil & Gas Risk Register · WHY / WHAT / HOW
