What Is a Snag List? A Practical Guide for Construction Teams

Before a project closes, someone has to walk the site and write down everything that isn't right. The door that doesn't close flush. The paint scuff on the hallway wall. The missing silicon bead around the bath. That list — the snag list — is the record standing between you and a clean handover.

For some teams it's a spreadsheet. For others it's a clipboard and a camera roll. The problem isn't writing the list — it's everything that happens next. Tracking who's responsible for each item. Chasing resolution. Proving it was fixed. Getting sign-off. This guide covers what a snag list actually is, what goes on one, and how construction teams manage the process without losing control of it.

The definition

A snag list is a formal record of defects, incomplete work, or items that don't meet the agreed specification at the point of practical completion. It's produced as part of the handover process — after construction is substantially done but before the client formally accepts the project.

In the UK and UAE construction markets, "snagging" is the standard term for this process. In the US you'll often hear "punch list." They mean the same thing: a list of outstanding items that must be resolved before — or sometimes shortly after — handover.

What goes on a snag list

Anything that doesn't meet spec, isn't complete, or is visibly defective. In practice, snags fall into a handful of categories:

• Finishing defects — paint scuffs, tile cracks, scratched glass, damaged fixtures
• Incomplete work — missing ironmongery, unfinished skirting, unsealed joints
• Installation issues — doors that don't hang correctly, windows that don't seal, plumbing that drips
• Specification mismatches — wrong materials used, wrong finish applied, wrong dimensions
• Commissioning items — systems that haven't been tested or signed off (HVAC, fire alarm, lifts)

A snag is not a change order. If the client decides they want a different floor tile after the work is complete, that's a variation — not a snag. A snag is specifically something that doesn't meet what was originally agreed.

Who creates a snag list

On most projects, the snag list is created by one of three parties — or sometimes all three simultaneously:

• The main contractor's QA team, during a pre-handover inspection
• The client or their representative, during a walkthrough before formal acceptance
• An independent snagging surveyor, hired by the client (common on residential developments)

Professional teams don't wait for the client to find snags — they walk the project first, log everything, and resolve as much as possible before the formal handover walkthrough. Showing up to handover with your own snag list already half-resolved is the mark of a competent contractor.

The problem with spreadsheets

Every experienced PM has managed a snag list on a spreadsheet. And every one of them has experienced the same failures: the file emailed around and edited in parallel, creating three versions nobody can reconcile. The photo in a WhatsApp message with no connection to the item it refers to. The sub who says they fixed it but the status column hasn't been updated in two weeks. The client who disputes whether a snag was actually resolved because there's no evidence.

Spreadsheets are fine for creating the list. They break down at every step after that.

What a managed snag list looks like

A well-managed snag list isn't just a record — it's an active workflow. Each item needs:

• A unique reference number for traceability
• A description specific enough that a subcontractor can act on it without asking questions
• At least one photo showing the defect
• A location — ideally pinned to a floorplan, not just 'Unit 4B kitchen'
• An assigned responsible party
• A due date
• A status that updates as work progresses
• Evidence of resolution — photo or comment confirming the fix
• Sign-off confirming acceptance

When every snag has all of that attached to it, the handover documentation writes itself. When items are missing any of those fields, you're left chasing information the night before handover.

The handover document

The snag list doesn't disappear at handover — it becomes the handover documentation. A completed snag list with photo evidence, resolution records, and sign-offs is a legal and contractual document. It's what the client can point to if defects reappear. It's what you can point to if a client disputes whether something was fixed.

This is why managing a snag list on WhatsApp screenshots is a problem. It's not just inefficient — it leaves both parties without the evidence they need if things go wrong after handover.