How to Record Construction Delays on Site

A delay should record more than "work was held up"

Construction sites rarely run exactly to plan.

Weather changes. Access gets blocked. Materials arrive late. Information is missing. Another trade hasn't completed its work. Plant breaks down.

The problem isn't simply that delays happen.

The problem is trying to reconstruct what happened weeks or months later from a note that says: Poor record: Delayed due to access.

A useful construction delay record should make it possible for someone who wasn't there to understand:

• what happened

• when it happened

• why it happened

• what work was affected

• who and what was impacted

• what happened next

• what evidence exists

Your daily site diary is one of the best places to start building that record.

What is a construction delay record?

A construction delay record documents an event that prevents work from progressing as planned or reduces the rate at which work can be completed.

It might relate to:

• weather

• restricted site access

• incomplete preceding works

• delayed materials

• unavailable plant

• design information

• instructions or changes

• inspections or approvals

• subcontractor coordination

• safety issues

• unexpected site conditions

The purpose is not to make a legal argument from the site.

It's to record the facts while they're fresh.

Your project manager, contract administrator or commercial team can determine what those facts mean later.

What should you record when a delay happens?

1. Date and time

Record when the issue started.

Where possible, also record:

• start time

• finish time

• whether the issue is ongoing

• when work resumed

Poor record: Concrete delayed this morning.

Better record: Concrete pour scheduled for 7:00am commenced at 10:15am.

Specific records are much easier to interpret later.

2. What caused the delay?

Describe the event rather than simply labelling it a delay.

Poor record: Access delay.

Better record: Northern loading-zone access was unavailable while mobile crane operations were underway.

The second record explains what actually happened without requiring someone to guess.

3. What work was affected?

A delay does not necessarily affect the entire site.

Record the specific:

• work area

• trade

• activity

• level

• zone

• subcontractor

• scheduled task

Example: Ceiling framing to the Level 3 eastern corridor was unable to commence because preceding mechanical rough-in remained incomplete.

This connects the delay to actual site activity.

4. Labour affected

If workers are unable to continue their planned work, record it.

Useful information can include:

• subcontractor or trade

• number of workers

• period affected

• whether they remained idle

• whether they were moved to another activity

Example: Four carpenters were affected from 8:00am to 10:30am. The crew was moved to Level 2 defect works at approximately 8:45am.

That gives considerably more context than simply recording that carpentry was delayed.

5. Plant and equipment affected

The same principle applies to plant and equipment.

Record relevant items such as:

• excavators

• cranes

• concrete pumps

• EWPs

• trucks

• lifting equipment

• hired machinery

Include whether the equipment was idle, redeployed or unavailable.

6. Weather and site conditions

If weather affects work, record what happened on the site, not simply that the weather was bad.

Useful details might include:

• rain

• high winds

• extreme heat

• standing water

• muddy access

• unsafe surface conditions

• work areas affected

• activities stopped

Example site diary entry: Heavy rainfall between approximately 11:20am and 12:10pm caused water accumulation around the western excavation. Excavation work stopped and recommenced after the area was inspected and made accessible.

This creates a much more useful record than a generic note.

Poor record: Rain delay.

7. Photos

Photos can add important context to a written site record.

Capture images showing things such as:

• blocked access

• site conditions

• incomplete work

• damaged materials

• standing water

• unavailable work areas

• equipment issues

• progress at the time of the event

Where possible, keep photos attached to the same daily record rather than buried in someone's camera roll.

8. Instructions and communications

If the event relates to an instruction or communication, record what was received and from whom.

This might include:

• site instructions

• superintendent directions

• RFIs

• emails

• subcontractor notifications

• design information

• meeting decisions

You don't need to rewrite an entire email into the site diary.

Record enough information to connect the diary entry to the source.

Example: The site manager instructed the ceiling contractor at approximately 9:10am not to commence works in the eastern corridor pending completion of mechanical services.

9. What the team did about it

A useful diary records the response as well as the problem.

For example:

• workers were reassigned

• works were resequenced

• another workfront was opened

• temporary access was established

• damaged equipment was replaced

• an inspection was requested

• additional resources were organised

This gives the later reader a clearer picture of how the day actually unfolded.

Construction delay record example

Consider this entry: Poor record: Excavation delayed due to access.

It tells you almost nothing.

A stronger entry could read:

Better record: 8:20am — Northern trench excavation was unable to commence because access was obstructed by materials stored in the excavation access route. The excavator and three-person civil crew were affected. The crew relocated to drainage preparation while access was cleared. Photos were taken at 8:25am. Access was restored at approximately 10:05am and excavation commenced shortly afterwards.

Now someone reviewing the project months later can understand the event without relying on memory.

Site diary vs delay record

Your site diary records the overall story of the day.

That can include:

• labour

• subcontractors

• weather

• work completed

• deliveries

• inspections

• incidents

• photos

• delays

A delay record goes deeper into a particular disruption.

The two should work together.

For many projects, the practical approach is to record the event properly in the daily diary and link it to any additional project documentation required by the team.

A simple construction delay checklist

When something disrupts work, ask:

• What happened?

• When did it start?

• When did it finish?

• Where did it happen?

• What activity was affected?

• Which workers or subcontractors were affected?

• Was plant affected?

• What caused it?

• What did the team do in response?

• Were photos taken?

• Is there an instruction, email or other record connected to it?

If your record answers those questions, you've captured considerably more useful information than a generic note saying the project was delayed.

Record delays while they're happening

The worst time to reconstruct a construction delay is months after it occurred.

Names get forgotten. Times become estimates. Photos become difficult to find. People remember events differently.

Recording site activity as it happens creates a much clearer project history.

WorkSiteDiary keeps daily site records, workforce information, weather, notes and photos together so site teams can capture what happened while the information is still fresh.