Construction Guide

Published: 2026-10-30 · Reviewed: 2026-11-04

Construction Site Documentation Basics

Why this matters

Construction disputes are won and lost on paperwork. When a client claims the work is three weeks late, when a subcontractor claims they weren’t paid for extras, when someone gets hurt and the insurer asks what happened, the answer is always in the records. Or it isn’t, and then the answer is whoever shouts loudest or has the best lawyer. Site documentation feels like admin that gets in the way of building; in reality it’s the only thing standing between you and a dispute you can’t win. The builders who document properly aren’t slower, they’re the ones who get paid in full and on time.

Practical steps

1. Keep a daily site log, every working day, no exceptions

The site daily log is the single most valuable document on any project. It should record:

  • Date, weather conditions, and who was on site (your crew, subcontractors, visitors).
  • What work was done, by whom, and where on the project.
  • Deliveries received, what, how much, condition, and any shortages or damage.
  • Plant and equipment on site, and any breakdowns or downtime.
  • Delays and disruptions: late deliveries, design queries raised, client changes requested, access problems, anything that stopped or slowed work.
  • Instructions given or received, especially verbal ones from the client or architect. “The client said to move the doorway” written in the log on the day is evidence; remembered six months later, it’s an argument.

Write it at the end of every day. A log filled in on Friday for the whole week is fiction with good intentions. Ten minutes at knock-off time, by the site supervisor.

2. Record toolbox talks

Toolbox talks, short safety briefings on specific topics, are a legal and practical necessity on most sites. But a talk nobody recorded might as well not have happened:

  • Log the date, topic, who delivered it, and get every attendee to sign. The signatures are the point, they prove who was briefed on what.
  • Cover the topics that match the work: working at height before the roof goes on, manual handling before the heavy deliveries, dust and silica before the cutting starts.
  • File them by date. When an incident happens and the question is “were they briefed on this?”, you want the signed sheet in seconds, not a vague memory of a chat by the kettle.

3. Log every delivery

Delivery disputes are among the most common and most avoidable in construction:

  • Record every delivery: date, time, supplier, materials and quantities, condition on arrival, and the name of the person who accepted it.
  • Note shortages, damage, and wrong items immediately, on the delivery note and in your log. A shortage reported three weeks later is your problem; reported on the day, it’s the supplier’s.
  • Photograph damaged deliveries before unloading where practical. A photo with a date stamp ends arguments.
  • Keep delivery notes filed by date and cross-reference them to your log. When the invoice arrives claiming 200 blocks and you received 150, the log is your credit note.

4. Run snag lists properly

Snagging, the list of defects and unfinished items, is where projects stall and relationships sour. A proper snag list process:

  • One list, one owner, numbered items. Not three different lists in three people’s notebooks.
  • Each snag: location, description, who’s responsible for fixing it, and a deadline. Photograph each item, “paint defect, bedroom 2, north wall” plus a photo leaves no room for “which mark?”
  • Sign off each item when rectified, with a date. The snag list isn’t done when someone says it’s done, it’s done when every item is signed off.
  • Keep the final signed-off list. It’s your proof the work was accepted, and it matters when the client “discovers” defects six months later that were never on the list.

5. Document variations and extras in writing

Nothing causes more payment disputes than extra work done on a verbal instruction:

  • Every variation, extra work, changed specification, additional days, gets written down with what was asked, by whom, when, and the agreed cost or rate, before the work is done if at all possible.
  • Get the client or their agent to sign. An unsigned variation is a favour; a signed one is an invoice.
  • File variations with the daily log entries for the days the work was carried out. The paper trail should tell the whole story without you in the room.

Common mistakes

  1. The daily log that stops when the site gets busy. The log gets skipped exactly when it’s most needed, during the chaotic periods that later become disputes. Busy is when you most need the ten minutes at the end of the day.
  2. Verbal instructions with no written record. “The architect said to just go ahead” is the most expensive sentence in construction. Confirm every verbal instruction in writing the same day, an email or a log entry the other party can see.
  3. Unsigned toolbox talks. Doing the talk but not collecting signatures means you did the work and kept none of the proof. The sign-in sheet takes two minutes to pass around.
  4. Snag lists without photos or sign-off. A snag list that’s just descriptions becomes a debate about whether item 14 was “that crack or the other crack.” Photos, numbered items, signed completion, or it’s not a snag list, it’s a wish list.

Templates that help

Bottom line

Site documentation is your insurance policy and your invoice backup in one: a daily log written every day, toolbox talks with signatures, deliveries logged with shortages noted on the spot, snag lists with photos and sign-off, and every variation in writing before the work starts. The builders who do this don’t just win disputes, they mostly avoid them, because the paperwork makes everyone’s position clear from day one.