How to run a snagging list that gets you signed off and paid

Snagging is the most emotionally charged stage of any build. The hard work is done, the client is excited to move in or move on, and suddenly the conversation is entirely about what is wrong — the paint nib by the architrave, the door that catches, the silicone line that is not quite straight. Handled well, snagging is the moment a good job becomes a referral. Handled badly, it is where final payment stalls and goodwill evaporates.

What snagging actually is

A "snag" is a minor defect or unfinished item identified at or near completion — the small stuff that falls short of the agreed standard. Snagging is the process of listing those items, agreeing them, fixing them, and getting the client to confirm they are done. It is normal. Every project has snags. A project with zero snags usually means nobody looked properly.

The mistake builders make is treating snagging as an informal "let me know if you spot anything" — which leaves the list open-ended, undocumented, and entirely in the client's control. That is how a job stays "nearly finished" for two months while the final payment sits unpaid.

Run the snag list as a structured handover, not a complaints box

The shift that changes everything is to own the snagging process rather than wait to be told. Walk the project with the client, room by room, and build the list together. This does three things: it surfaces issues while you are there to assess them, it stops new snags appearing indefinitely, and it signals professionalism — you are inviting scrutiny, not avoiding it.

• Do a self-snag first. Walk it yourself before the client does and fix the obvious. Half the items the client would have flagged disappear, and the ones that remain look like genuine fine-tuning rather than sloppiness.
• Capture each snag specifically. Location, description, a photo. "Mark on landing wall, 1m from window" beats "wall needs touching up".
• Agree what is in and out of scope. Some "snags" are actually new requests — a variation in disguise. Separate genuine defects from changes of mind, kindly but clearly, at the point they are raised.
• Put a date against resolution. An open list with no timeline never closes. "These eleven items, done by Friday week" does.

Get the sign-off — it is what closes the job

The single most important step is the one most builders skip: getting the client to confirm, in writing, that the snags are resolved and the work is accepted. Without it, the job is never formally finished, and "not finished" is the client's justification for holding payment.

Sign-off does not need to be a solicitor's letter. It needs to be a clear record: here was the agreed list, here is each item marked resolved, and here is the client confirming they are satisfied. The moment that exists, the final payment has no hiding place — and you have a clean, documented end to the project.

Why this protects you long after handover

A documented snag list is also your defence months later. If a client returns in six months claiming the work was never finished, an agreed and signed-off snag list is the difference between a quick resolution and an open-ended liability. It marks the line between defects you are responsible for and ordinary wear, settlement and use.

This is the logic behind tying snagging into the project record rather than running it on a scrap of paper. In Builders Ready, the work, the decisions and the variations already live in one place and roll into the handover document — and a structured snag list belongs in exactly the same record, signed off by the client and closed cleanly. Whatever tool you use, the rule is the same: own the list, agree it, fix it, and get it signed off. That is how a job ends with a referral instead of a row.