What you need to know
- Check Scope and amendments before rejecting a review requirement.
- Routine record review is distinct from formal acceptance.
- Preserve originals and identify factual corrections.
- NEC4 ECC mutual trust and co-operation is clause 10.2.
When someone asks to approve a site record, clarify what the review is intended to achieve. Checking an entry for factual accuracy, coordinating a report and accepting a contractual submission are different actions.
Start with the project requirements
NEC4 ECC does not create a universal Client approval procedure for every routine diary entry. That does not mean that record review can never be required. The Scope, an incorporated procedure or a contract amendment may require particular records, circulation, checks or sign-offs. Read those requirements before saying that approval is unnecessary.
The parties may also agree a practical review workflow. State who reviews the record, by when, what the review means and how disagreements are recorded. Do not assume that an informal arrangement changes contractual notice requirements.
Keep acceptance specific
NEC4 ECC uses acceptance for specified submissions, including programmes and certain design, subcontracting and compensation-event submissions. Each procedure has its own requirements. Acceptance of a programme is not the same as agreement to a compensation-event quotation, and acknowledgement of a diary is not automatically either of those things.
Do not apply one generic deadline or deemed-acceptance rule to every submission. Check the provision governing that communication. The fact that some procedures contain a remedy for non-response does not create a universal rule that silence means acceptance.
Project Manager or Supervisor acceptance does not generally transfer the Contractor’s responsibility for providing the works or its design responsibility. Clause 14.1 addresses that distinction.
Review facts without losing the original evidence
A useful record-review process lets people query dates, locations, resource numbers and descriptions promptly. Preserve the original entry, identify corrections and record unresolved differences. An unqualified approval stamp can obscure whether the reviewer checked facts, agreed a valuation or merely received the document.
For example, a team might circulate a weekly report a day before wider issue for factual comments. The agreed workflow should explain whether the report is issued if no comments arrive, and whether disputed statements remain identified as the author’s account. This is an illustrative arrangement, not a standard NEC requirement.
Issue contractual communications separately
A report may contain information relevant to an early warning or compensation event, but inclusion in the report does not necessarily satisfy a separate notification obligation. Use the contract’s communication method, address the correct recipient and make the required notification separately where the contract requires it.
NEC4 ECC’s obligation to act in a spirit of mutual trust and co-operation is at clause 10.2. It complements the obligation to act as the contract states; it does not remove procedures or deadlines.
A practical review checklist
- Identify the contractual requirement, if any, for review or acceptance.
- State what the reviewer is checking and what a sign-off means.
- Keep original records and make corrections traceable.
- Record disagreement without rewriting the original account as agreed fact.
- Track formal notices and submissions independently of routine reporting.
Further reading
- GMH: communications under NEC ECC
- GMH: Project Manager and Supervisor roles
- GMH webinar: communicating effectively under NEC4
Check the NEC form, edition, incorporated amendments, selected options, Contract Data, Scope and Z clauses used on your project.
Gather helps teams organise site evidence for commercial review. Explore Gather’s site records.





.webp)




