What records to keep on an NEC contract: a practical checklist

A practical checklist of the records to keep on an NEC project and when to capture them, so programme, payment and compensation event claims hold up.

Communications and records3 min read

On this page
  1. Why it matters under NEC
  2. Records to keep, and when
  3. How to keep them well
  4. Common failures
  5. Related guides

NEC contracts run on notices, programmes and assessments. When something goes wrong, the side with clear, dated records usually has the stronger case. Good records are not about building a claim from day one. They are about being able to show what happened when someone asks.

This checklist is for a Contractor; a Subcontractor needs most of the same records plus those the subcontract requires. Check your contract, Contract Data and any Z clauses for specific record or reporting duties.

Why it matters under NEC

  • Compensation event entitlement depends on notifying within eight weeks of becoming aware of the event (clause 61.3; seven weeks in the NEC4 subcontract), which depends on knowing when you became aware. Events arising from a Project Manager or Supervisor instruction, notification, certificate or changed decision are not caught by that bar.
  • On Options C, D and E, cost that is not justified by your accounts and records is Disallowed Cost, and Defined Cost needs proof of payment (clause 52.2).
  • Quotations need details of the assessment and programme effect (clause 62.2).
  • Payment depends on assessment and certification (clauses 50 and 51).
  • The parties act in a spirit of mutual trust and co-operation (clause 10.2), and shared, accurate records support that.

Records to keep, and when

From day one

  • The signed contract, Contract Data, Scope (Works Information in NEC3), and every amendment and Z clause.
  • Tender information and the ground or site information you relied on.
  • The first programme, the Accepted Programme and each revision, with the date submitted and the date accepted or not. See clause 31 programme checklist.
  • A contacts list showing who holds which role under the contract.

Every day

  • Site diary: weather, labour, plant, activities, visitors, instructions, delays, hold points.
  • Photographs with date, location and subject.
  • Delivery notes and plant records.
  • Daily labour and plant allocation, with extra or changed work kept separate.

Every week

  • Progress against the Accepted Programme, with actual start and finish dates.
  • Quantities installed, where measured.
  • Notes of any instruction or conversation with the Project Manager or Supervisor.
  • An update of the early warning and compensation event registers. See early warning register template.

Every time something happens

Event Record
Instruction received Copy, date, sender, how received, who was present
Early warning Notice, response, meeting notes, actions
Compensation event Notification, date of awareness, evidence, quotation, replies
Programme submission The file, the date, the reply, reasons if not accepted
Defect notified Notice, cause, correction, dates
Access problem Dates access was due and given, effect
Payment application and certificate Dates, amounts, differences, interest

Monthly or at assessment dates

  • Defined Cost records for target or cost reimbursable options, with supporting evidence.
  • Payment assessments and certificates, and any difference with your own.
  • Updated programme and a summary of changes to the Completion Date and Key Dates.

At the end

  • Completion and Defects dates, certificates and correction records.
  • Final account papers.
  • A full set of notices and communications.

How to keep them well

  1. Use the contract's communication system for anything that must be communicated, and keep the sent record (clause 13).
  2. Date everything at the time. Do not reconstruct entries later.
  3. Keep originals in a structure others can follow, and back them up.
  4. Name files consistently, with date, subject and reference.
  5. Separate extra work costs from base work from the start.
  6. Keep the programme native files, not just PDFs, for every submission.
  7. Capture oral agreements in writing the same day.

Common failures

  • Site diaries written up weeks later.
  • Programme revisions overwritten without a version trail.
  • Photos with no date or location.
  • Verbal instructions never confirmed.
  • Costs for different compensation events mixed together.

This guide is general information, not legal advice. Check it against your contract.

Was this useful?