ENRO ยท All articles

How to write a construction delay-log entry with evidence

Record the event and affected work without presenting an untested delay claim as fact.

By ENRO team

A delay log should record the event, affected activity, supporting evidence and action taken. It should not turn every disruption into an unsupported claim about the final completion date.

A filled example

Illustrative event: a planned pump delivery did not arrive on 4 November. The intended activity was a concrete pour at Tower B. The procurement record shows the promised time; the site report records the actual position and the work reassigned to the crew.

The entry says pour not started as planned, with schedule impact under review. It does not declare the whole project three days late unless the schedule assessment supports that conclusion.

Keep facts and assessment separate

  • Event ID, project, location and date first known.
  • Planned activity and relevant schedule version.
  • What was observed, with dated evidence.
  • Duration of the event and actual work affected.
  • Alternative work, mitigation and decisions taken.
  • Person assessing schedule impact and current conclusion.
  • Required notices or contractual follow-up identified for professional review.

Record when the event ended as well as when it began. An event lasting two days does not necessarily move completion by two days: float, sequencing, parallel work and other constraints matter.

Review and update

Link related site reports, delivery records and correspondence. Add later findings without rewriting the original observation as if the team knew them at the time. Distinguish a supplier's promised date from a confirmed delivery.

Contractual notices, responsibility and entitlement depend on the actual agreement and circumstances. This guide is a recordkeeping example, not legal or delay-analysis advice.

The useful review question is what needs a decision now: an alternative supplier, revised sequence, missing design response or more evidence. A log that records blame but no next action will not help the site recover.

Related guides

Delay-log basics

Understanding float