Construction Project Evidence Checklist: What to Capture Before You Need It

The record you need later is usually created today

Most construction evidence does not feel like evidence when it is created.

1. It looks like a photo.

2. A worker signing in.

3. A note about a delivery.

4. A weather record.

5. A permit approval.

6. A diary entry saying one trade could not start.

7. An incident photo.

8. A revised drawing.

None of those records necessarily feels important at the time.

Then three months later somebody asks:

• Why did this activity finish late?

• Who was actually on site that day?

• When did the revised information arrive?

• Was this work approved before it started?

• What did the area look like before the damage occurred?

• Was the subcontractor inducted?

• When was this issue first identified?

At that point, the question is no longer whether the project created information.

It almost certainly did.

The question is whether anyone can find enough of that information to reconstruct what actually happened.

That is the difference between collecting documents and building a project record.

Think in evidence chains, not individual forms

A useful construction record rarely depends on a single document.

Imagine a subcontractor says their work was delayed because an area was unavailable.

One diary entry saying:

"Area unavailable. Subcontractor delayed." does not tell you much.

But now connect it with:

• the planned activity

• the date and time

• the subcontractor on site

• worker attendance

• photographs of the inaccessible area

• the reason access was unavailable

• the instruction given to the crew

• the work they completed instead

• the date access became available

• the resulting work completed afterwards

You now have something much more useful.

You have an evidence chain.

A good evidence chain answers six questions:

1. What was supposed to happen?

What work was planned, expected or authorised?

2. What actually happened?

What did the team encounter or complete?

3. Who was involved?

Which workers, subcontractors, supervisors or other parties were present?

4. What changed?

Was there a delay, instruction, safety issue, revised design, access problem or other event?

5. What supports the record?

Are there photographs, drawings, attendance records, documents, permits or other evidence?

6. What happened next?

Was the issue resolved? Did work restart? Was an action assigned? Was additional information received?

If your project records can answer those questions, someone who was not standing on site at the time has a reasonable chance of understanding the event later.

1. Capture the baseline before recording the exception

One of the easiest things to miss is what should have happened.

A record that says work changed is much more useful when you can establish what the team was working from beforehand.

Depending on the event, that might include:

• drawing number and revision

• specification

• programme activity

• scope of works

• approved SWMS

• permit

• work instruction

• scheduled delivery

• approved work area

• planned labour

• agreed sequence

This creates a baseline.

Without it, someone reviewing the project later can see what happened but may not understand what was different about it.

You do not need to duplicate every project document inside a diary entry.

The important thing is being able to identify the information relevant to the work.

2. Know who was actually on site

Attendance is more useful than it first appears.

A worker register answers a basic question:

Who was there?

But when connected to other project records it can provide much more context.

For example, you may later need to understand:

• whether a particular subcontractor had workers available

• who could have witnessed an event

• how many workers were affected by a delay

• whether someone was present during a pre-start

• who was working in an area when an incident occurred

• when a worker or visitor entered and left the project

Useful attendance records can include:

• worker name

• company or subcontractor

• site

• date

• sign-in time

• sign-out time

• relevant worker status or induction information

Attendance should not live as an isolated spreadsheet if the information is going to be useful operationally.

Its value increases when it can be connected with the rest of the day's activity.

3. Record what work actually happened

This is where the daily site diary earns its place.

The diary should create a simple chronological record of the project.

Useful information may include:

• work completed

• areas worked in

• subcontractors present

• labour levels

• plant and equipment

• deliveries

• inspections

• visitors

• notable conversations

• delays

• site conditions

• photographs

• incidents

• outstanding issues

The goal is not to write an essay about every working day.

It is to capture enough information that the day still makes sense when somebody reads it months later.

Contemporaneous records such as site diaries, photographs, emails, timesheets and meeting minutes can become important when construction events later need to be reconstructed. An often-cited example is the NSW Supreme Court's White Constructions decision, where contemporaneous project records were central to assessing alleged delay.

4. Capture the conditions around the work

Sometimes what happened is only understandable when you know what the site looked like at the time.

Useful conditions can include:

• weather

• rainfall

• temperature where relevant

• access conditions

• work area availability

• preceding trade completion

• site congestion

• temporary works

• material availability

• equipment availability

• power or service interruptions

• unexpected site conditions

Consider the difference between:

and:

The second record gives somebody something to investigate.

If there are attendance records, photographs and relevant diary entries attached to the same date, the picture becomes clearer again.

5. Photograph the condition, not just the finished work

Construction projects generate huge numbers of photos.

The problem is that a photograph without context can become nearly useless.

Six months later, a phone gallery containing IMG_8437.jpg does not tell you:

• which project it relates to

• where on the project it was taken

• why it was taken

• what you are supposed to notice

• what happened afterwards

A useful construction photo should ideally be connected with:

Project - Which site?

Date - When was it taken?

Location - Where on the project?

Context - Why does this photo matter?

Related event

Does it relate to a diary entry, delay, incident, inspection, delivery or corrective action?

Think about taking photos that show conditions before, during and after an important event.

That sequence often explains far more than a single image.

6. Record changes while everybody still remembers them

Construction projects change constantly.

The dangerous records are not always major formal changes.

They are often ordinary events such as:

• revised information arriving

• work being resequenced

• an area becoming unavailable

• a verbal direction

• a requested change

• an unexpected site condition

• additional work being performed

• completed work being removed or modified

• a different material being used

• an inspection changing how work proceeds

When something changes, capture the facts available at the time.

That usually means:

• date and time

• location

• people involved

• what changed

• previous information being followed

• new information or direction

• work affected

• immediate response

• supporting photos or documents

You do not need the site team to determine the contractual consequences.

The first priority is creating an accurate record of the event.

7. Treat delays as events, not just a number of lost hours

A useful delay record should allow someone to follow the sequence.

For example:

7:00 am

Electrical subcontractor signs into site with six workers.

7:20 am

Crew attempts to begin rough-in works in Apartment Zone B.

7:35 am

Area found unavailable due to incomplete wall framing.

7:45 am

Supervisor records the issue and photographs the affected area.

8:00 am

Electrical crew redirected to Zone D.

2:15 pm

Framing works in Zone B completed.

Following morning

Electrical work begins in Zone B.

That tells you significantly more than:

The useful evidence is the sequence.

Where possible, capture:

• planned activity

• cause of the delay

• affected work

• people and resources affected

• start time

• end time

• photographs

• action taken

• alternative work performed

• date normal work resumed

8. Keep safety records connected to the work

Safety documentation is one area where record keeping can also have specific regulatory requirements.

SafeWork SA identifies records including notifiable incidents, hazardous substance information, plant records and inspection reports, while also recommending records of risk assessments, controls, induction and training. These records may help demonstrate how safety has been managed if an incident is investigated.

Useful project safety records may include:

• site inductions

• SWMS

• pre-starts and toolbox meetings

• permits

• hazards

• incidents

• safety observations

• corrective actions

• worker acknowledgements

• evidence of completed actions

The important part is not simply creating the form.

You need to be able to answer questions such as:

• Which version applied?

• Who received it?

• Who acknowledged it?

• When was it approved?

• What action resulted?

• Was the issue actually closed?

For high-risk construction work, SWMS have specific requirements around preparation, availability, compliance, review and retention. SafeWork SA also notes that a SWMS should be reviewed when the work changes or controls may no longer be adequate.

9. Capture decisions and approvals

A surprising amount of project knowledge lives inside conversations.

A supervisor talks to a subcontractor.

A project manager approves something verbally.

Someone sends a text.

An inspector asks for a change.

An email disappears into somebody's inbox.

When a decision matters, capture:

• what was decided

• date

• person making the decision

• parties involved

• work affected

• supporting information

• required action

• approval status where relevant

The record does not need to duplicate the entire conversation.

It needs to make the decision traceable.

10. Do not lose the follow-up

Many project records document the beginning of a problem but not the end.

An incident gets reported.

A defect is identified.

A permit condition needs to be addressed.

A safety observation creates an action.

A missing document is requested.

Then everyone moves on.

A complete record should show:

Issue identified → owner assigned → action taken → evidence provided → reviewed → closed

That makes the project record useful for management, not just storage.

It also makes outstanding work much easier to see before it disappears into email, notebooks or somebody's memory.

The five tests for a useful construction record

Before considering an important record complete, ask these five questions.

Could somebody who was not there understand it?

If the entry only makes sense to the person who wrote it, it needs more context.

Was it recorded close to when the event happened?

The longer you wait, the more detail disappears.

Can you identify the people and location involved?

Avoid records that only say things like “subbie”, “client” or “upstairs”.

Is there evidence attached or easy to find?

Photos, files, attendance, approvals and related records should not require a detective hunt.

Can you see what happened next?

Important project events usually have a consequence, action or resolution.

If you can answer all five, you probably have a useful record.

A practical example

Imagine the following event.

A ceiling contractor arrives Monday morning expecting to begin work.

The mechanical subcontractor has not finished services above the ceiling.

The ceiling crew moves to another part of the project.

Mechanical work finishes Wednesday afternoon.

Ceiling installation begins Thursday.

Weak project record

Monday diary:

That statement may be completely accurate.

But there is very little behind it.

Stronger evidence chain

Baseline

Programme shows ceiling installation planned to begin Monday in Level 4 Zone A.

Attendance

Ceiling subcontractor signs six workers onto site Monday morning.

Site diary

Supervisor records that ceiling work cannot begin in Zone A because overhead mechanical work remains incomplete.

Photos

Dated photographs show outstanding mechanical installation within the affected area.

Response

Ceiling crew is relocated to Zone C.

Follow-up

Wednesday diary records completion of the outstanding mechanical work.

Resolution

Thursday attendance and diary records show the ceiling contractor commencing work in Zone A.

Now someone looking at the project later can follow the event from beginning to end.

That is the difference between having a note and having evidence.

What should you capture on every project?

Not every project needs exactly the same records.

But a useful construction evidence system will usually cover these areas:

People

• workers

• subcontractors

• visitors

• site attendance

• inductions

Daily operations

• work completed

• labour

• plant

• deliveries

• site conditions

• weather

• photographs

Changes and interruptions

• delays

• instructions

• revised information

• access restrictions

• unexpected conditions

• work resequencing

Safety

• SWMS

• pre-starts

• permits

• incidents

• hazards

• observations

• corrective actions

• acknowledgements

Documents

• drawings

• specifications

• supporting files

• approvals

• inspection records

• relevant correspondence

Follow-up

• outstanding actions

• responsible person

• due date

• evidence

• approval

• closure

Different contracts, jurisdictions and types of work can impose specific documentation and retention requirements, so this checklist should sit alongside the requirements applying to your particular project rather than replacing them.

The real problem is usually not missing information

Most construction sites already generate enormous amounts of information.

The problem is fragmentation.

The diary is somewhere else.

Photos are on phones.

Attendance is in a spreadsheet.

Permits are PDFs.

Inductions are in another folder.

Safety actions are in email.

Someone has the latest document revision.

Someone else remembers why the work changed.

The project technically has the information.

But when someone asks a difficult question, somebody still has to reconstruct the story.

That is what a connected project record is designed to avoid.

Build the record before you know which part will matter

You cannot predict every dispute, incident, audit, client question or project review.

You also should not document every minute of the working day.

The goal is to consistently capture the pieces that explain the project:

• What was planned.

• Who was there.

• What happened.

• What changed.

• What evidence supports it.

• What happened next.

Do that consistently and the project gradually builds its own history.

When somebody eventually asks what happened, you are no longer starting with people's memories.

You are starting with the record.

Keeping the evidence connected with WorkSiteDiary

WorkSiteDiary is a connected construction-site management platform for recording daily work, managing people and access, coordinating safety workflows, organising documents, and producing reliable project evidence.

Instead of treating daily diaries, worker attendance, permits, inductions, incidents, photos and actions as unrelated forms, WorkSiteDiary keeps them connected to the relevant project.

Site teams can capture information through mobile-friendly and QR-based workflows while project teams retain dated records, approvals, acknowledgements, actions and supporting evidence.

Records can then be reviewed and exported for clients, reporting, audits, claims and project close-out.

The value is not simply having more forms.

It is being able to understand what happened without rebuilding the project from scratch.

Related guides

Explore the related WorkSiteDiary guides:

• What should be included in a construction site diary? — use the daily record checklist

• Construction site attendance register — record who was on site and when

• How to record construction delays on site — document work interruptions

• Construction site diary template — copy a daily report structure