Snagging List Template: What to Include

A snagging list is only as good as the information on it. A vague list — "fix paint, check doors" — creates arguments, missed items, and repeat visits. A well-structured snagging list template turns a chaotic walkthrough into a clear, trackable action list that any trade can pick up and act on.

This article sets out exactly what a snagging list template should include, and how to structure it so snags actually get closed.

What a snagging list template should capture

Every snag entry should answer the same set of questions. At minimum, your template needs these columns or fields:

• Snag number — a unique reference for each item, so it can be tracked and discussed.
• Location — room, floor, and area. "Bedroom 2, window reveal" not just "upstairs".
• Element — what the snag relates to: wall, floor, door, M&E, external.
• Description — a clear statement of the defect and the required standard.
• Photo — at least one image showing the defect and its context.
• Responsible trade or contractor — who needs to fix it.
• Priority — critical, major, or minor.
• Status — open, in progress, fixed, verified, closed.
• Date raised and date closed — for tracking turnaround.

If your template captures all of that, almost nothing can fall through the cracks.

Structure it room by room

The most usable snagging lists are grouped by location, not by trade. When a decorator arrives, they want to see every paint snag in the order they'll walk the building — not hunt through a list sorted by date. Group by floor, then room, then element. A digital tool can re-sort the same data by trade when you need to issue work to a subcontractor.

Write descriptions anyone can act on

The single biggest cause of repeat snag visits is a description the operative can't interpret. Compare:

• Poor: "Door issue."
• Good: "Bedroom 3 door binds on frame at top hinge side, does not latch — adjust hinges and check alignment."

The good version tells the joiner the location, the symptom, and the likely fix. Always state the defect and the standard it fails to meet.

Use priority to drive sequencing

Not every snag is equal. A non-functioning fire door is critical; a minor scuff on a skirting board is not. Tagging priority lets you push the items that block handover to the front of the queue and avoid wasting a trade visit on cosmetics while a safety item sits open.

Track status to closure

A snag isn't done when it's reported, or even when it's fixed — it's done when someone has verified the fix. Your template should distinguish "contractor says fixed" from "inspector confirmed closed". That verification step is what stops the same snag reappearing at final handover.

Paper template vs digital

A spreadsheet or printed template works, but it has limits: photos live separately on a phone, re-sorting by trade means manual work, and there's no audit trail of who changed what and when. A snagging app uses the same fields but captures the photo against the item automatically, lets you reassign and re-sort instantly, and timestamps every status change — so the list and the evidence never drift apart.

Key takeaways

A strong snagging list template captures location, element, a clear description, a photo, the responsible trade, priority, and status. Group it by location, write descriptions that name the defect and the standard, and don't close an item until the fix is verified. Get the template right and the de-snag becomes a formality instead of a fight.