Which registers to keep on an NEC contract, and what goes in them
The eight simple logs that let you prove what happened and when on an NEC job, with the fields to record and how to keep your list matching the Client's.
On this page
On an NEC job you should keep eight logs: early warnings, compensation events, instructions, programmes, submissions, Defects, tests and payments. The contract only insists on one of them, the early warning register, and that is run by the Project Manager (the person the Client appoints to run the contract day to day). The rest are not required, but without them you cannot show who knew what, and when. This guide assumes NEC4 ECC; in NEC3 the equivalent of the first log is called the Risk Register.
What to put in each log
Early warnings. Reference number, who raised it and when, what the risk is, its possible effect on cost, time and quality, options discussed, what was decided, who owns the action, the due date, status, and the number of any compensation event it turned into.
Compensation events. Number, short description, which listed category under clause 60.1, the date you became aware, the date you notified, who notified, the reply date and outcome, quotation due and sent, reply due and outcome, value, time effect, date implemented, and a link to any early warning. A compensation event is something the contract says entitles you to more money or time.
Instructions. Number, date, who gave it, the clause (14.3, 34.1 and so on), a summary, and whether a compensation event was notified with it.
Programmes. Revision, date submitted, reply due, accepted or not, reasons given, planned Completion, terminal float and any forecast against Key Dates.
Submissions. Type (design, subcontractor, quality plan, Equipment design), reference, dates, outcome, reasons, resubmissions.
Defects. Number, who found it, location, description, the correction period, due date, date put right, and the cost if you do not correct it.
Tests and inspections. What, who, notice given, date, result, whether a repeat is needed and who bears the cost.
Payments. Assessment date, what you applied for, what was certified, certificate date, final date for payment, any pay less notice, amount and date paid.
What the contract actually requires
Only the early warning register has a clause behind it (15.2 and 15.4). The others follow clauses 61 to 66, 14.3, 31 and 32, 43 to 46, and 50 and 51. Your Scope may demand more, such as a Defects log. On Options C, D and E, clause 52 lists the Defined Cost records you must keep as well.
Keep your list and theirs the same
The usual failure is two versions of one log: the Project Manager's team holds one list, you hold another, and they drift apart. Three habits stop that.
- Use one numbering series, so a compensation event has one reference from notification to implementation.
- Cross-refer. An early warning that becomes an event points to it, and the event points back. So do instructions, programmes and Defects that give rise to events.
- Reconcile monthly, line by line, while people still remember.
A short worked trail
Picture a substation fence job. EW-009 warns that the Client's gate delivery may slip. It is raised on 3 June. CE-021 is notified on 10 June, linked to EW-009, with 60.1 category and awareness date recorded. Programme revision 5 shows the new erection date and goes in with the quotation. Payment application 7 picks up the change once CE-021 is implemented. Someone new can follow this in minutes.
What people get wrong
- Recording only "closed". Say whether a warning closed because the risk passed or because it became an event.
- Leaving out the date of awareness. For you as the contractor, this is the most important field in the compensation event log.
- Letting the early warning register go stale when the Project Manager should be reissuing it within a week of each meeting.
- Adding so many columns that nobody fills them in. A short complete log beats a long empty one.
Related guides
- Early warning register template
- Keeping a clear NEC audit trail
- Tracking NEC contracts in spreadsheets
- Keeping records under NEC
This guide is general information, not legal advice. Check it against your contract.
