Snag lists that hold up: a site-handover checklist for SA builders

A snag list is only useful if it can be trusted later — by the client, by a body corporate, or by you if something's disputed months down the line. Here's how to run a handover process that actually holds up, not just one that ticks a box on the day.

Every builder runs some version of a snag list at handover. The problem isn't the list itself — it's what happens when a client disputes something three months later and the only record is a signed piece of paper that's gone missing, or a WhatsApp photo with no date attached to it. A snag list that can't be reconstructed isn't evidence, it's a memory.

What makes a snag list defensible

A snag record that holds up in a dispute has four things: it's dated, it's tied to a specific unit or site, it has photo evidence for each item, and it has a clear sign-off trail showing who agreed what was resolved and when. Miss any one of these and you're relying on people's memory of a walkthrough that happened months ago.

Practical checklist for a handover that holds up

• Walk the site with the client or their representative present, not alone — a snag list without the client's sign-off is your opinion, not an agreed record
• Photograph every snag item individually, not just a general sweep — vague photos are hard to defend later
• Date and timestamp every item as it's logged, not batched and entered later from memory
• Reference each snag to a specific room, unit, or location — "kitchen tap" isn't enough on a multi-unit sectional title project
• Get sign-off from the client on the snag list itself, not just a general handover certificate
• Log the resolution of each item separately, with its own date and photo — "fixed" isn't evidence, a photo of the fix is
• Get a final sign-off once all items are closed, distinct from the original snag list
• Keep the full record — original snags, resolution evidence, and both sign-offs — somewhere it can't be edited after the fact

Sectional title and body corporate handovers

Multi-unit projects add complexity: snags can belong to a specific unit, to common property, or to the body corporate as a whole, and disputes often surface long after individual owners move in. Keeping snag records structured by unit and by common-area category from the start avoids the scramble to work out, months later, whether a defect was ever raised and whether it was the contractor's or the body corporate's responsibility to fix.

When to call a professional

A snag list covers workmanship and finishing defects. If a walkthrough uncovers something structural, or touches electrical, roofing, waterproofing, or plumbing systems that go beyond cosmetic snagging, that item needs a qualified professional to assess and sign off — not just a note on the snag list. Treat those items separately and get them properly closed out before final handover sign-off, particularly where they could affect an insurance position later.

Why paper and WhatsApp snag lists fall apart

• Photos aren't reliably dated or tied to the right unit once they're mixed into a phone's camera roll
• A paper list can be lost, and there's no record of who actually signed it
• There's no clear separation between the original snag and the evidence it was fixed
• Multiple people (site supervisor, project manager, client) end up with different versions of "the list"
• Reconstructing the timeline for a dispute six months later relies entirely on memory

How SiteCheck fits

SiteCheck keeps snag items tied to a project record with dated photo evidence and sign-off tracked against each item — from the original snag through to resolution and final handover. Rather than reconstructing a timeline from scattered photos and paper after a dispute arises, the record exists as it happened, which helps if a client, body corporate, or insurer later questions what was agreed and when.

FAQ

Is a snag list legally binding?

A signed snag list is evidence of what was agreed at handover, but it's not a substitute for your contract terms. Get advice from a professional if a dispute moves beyond a normal snagging disagreement.

How long should we keep snag records after handover?

Long enough to cover any defects liability period in your contract, and any applicable legal claim period — this varies by contract and project, so check your specific terms.

Can subcontractors see the snag list, or only the main contractor?

That depends on how you set up access — SiteCheck supports role-based access so subcontractors can be shown only the items relevant to their trade, without seeing the full project record.

What if the client won't sign off on a snag list?

Record the walkthrough date, the items raised, and the client's response (even if it's a refusal to sign) — an unsigned but dated and photographed record is still far stronger evidence than nothing.

See how snag tracking works in SiteCheck end to end. Book a demo.