Contemporaneous records and NEC4 event assessment

What you need to know

Contemporaneous means written at or around the time. A Friday write-up of Monday is not, and should be dated for what it is rather than backdated.
A timestamp shows when an entry was made. It does not prove every statement inside it.
NEC4 ECC early warnings sit at clause 15.1, not clause 16.1. A compensation-event notification under clause 61.3 is a separate communication, and a diary entry or meeting minute does not substitute for either.
Records help establish facts. They do not establish entitlement, decide the valuation or guarantee payment.
Hours, output, weather, instructions and delays belong in the site diary that day.
Rosie drafts from the record rather than from memory. Check the suggested clauses and dates against the contract, and keep the decision to notify with the authorised people.

Contemporaneous records are created at or around the time of the events they describe. They can help explain what happened, when and with what effect. Their value depends on their accuracy, relevance and context; a timestamp alone does not prove every statement.

Build a connected account

Record the activity, location, timing, people involved, resources and relevant communications. Link photographs, instructions, delivery records and programme information where useful. Preserve originals and identify corrections.

Separate observation from inference. “Excavation stopped at 10:15 after encountering an unidentified obstruction” records a fact. Whether the obstruction meets a contractual physical-conditions test is a separate assessment.

Keep the NEC4 procedures distinct

NEC4 ECC early warnings are addressed in clause 15.1, not clause 16.1. Give the required early warning as soon as awareness of the relevant matter arises; do not wait for a monthly report or an internal financial threshold.

Compensation-event notification is a separate process. Standard clause 61.3 includes an eight-week time bar from becoming aware that an event has happened, with an exception for events the Project Manager should have notified. Check the form, amendments, notification duty and facts before deciding that a notice is late.

An early warning, meeting minute or diary entry does not automatically substitute for a separate notification. Use the contractual recipient and communication method.

Apply the event test

A change in conditions, additional cost or delayed activity is not automatically a compensation event. For physical conditions, apply clause 60.1(12); for weather, use the specified calendar-month measurement and historical test under clause 60.1(13). A photograph of standing water can support the factual account without establishing a qualifying weather event by itself.

Support actuals and forecasts

A compensation-event assessment uses the relevant actual and forecast Defined Cost at the dividing date, with the applicable Fee and time-assessment rules. Later invoices do not automatically replace the required forecast assessment.

Show how the event affects the relevant Accepted Programme. A disruption to one activity need not delay planned Completion, and a simple statement that the critical path was affected needs supporting analysis.

Handle gaps honestly

If an entry is made later, date it accurately and identify the sources and limits of recollection. Do not backdate it or describe it as contemporaneous. Other evidence may still assist; lack of a particular diary entry does not automatically mean the event cannot be proved.

Likewise, extensive documentation does not make a claim indisputable or guarantee payment within a week. Records, contractual entitlement and valuation all need consideration.

Use technology as review support

Search, structured categories and AI can help locate related material and flag possible issues. Check suggested clauses, dates and conclusions against the contract and original evidence. Keep the decision to issue a notice or accept an assessment with the authorised people.