If you work in construction, you have heard the term snag list on almost every project. Yet many teams still manage snags with notebooks, spreadsheets, or long WhatsApp threads, and that is where problems start. This guide explains what a snag list is, what belongs on it, and how to run one properly from first inspection to final sign-off.
What is a snag list?
A snag list is a record of defects, omissions, and unfinished items found on a construction project. Each entry, often called a snag or defect, describes something that needs to be fixed, completed, or corrected before the work can be considered done. In the UK and Ireland the term snagging is standard, while teams in the US usually call the same document a punch list.
A good snag list is more than a to-do list. It is a quality record that shows what was found, who is responsible for fixing it, when it was fixed, and who confirmed the fix.
What goes on a snag list?
Most snags fall into four groups:
- Cosmetic defects: paint drips, scratched worktops, chipped tiles, poor silicone lines, damaged plaster.
- Functional issues: doors that stick, windows that do not lock, taps that drip, sockets without power.
- Omissions: missing sealant, ungrouted tiles, absent door stops, incomplete trims.
- Compliance and safety items: missing signage, incorrect fire stopping, unlabeled distribution boards.
Every entry should include a clear description, an exact location, a photo, a priority, and an assignee. Vague entries like "fix wall in hallway" waste time because nobody knows what, where, or whose job it is.
Who uses snag lists?
Almost everyone on a project touches the snag list at some point. Site managers and project managers create and triage snags. Subcontractors receive and resolve them. Developers and clients review progress before handover. Independent snagging inspectors may compile the list on behalf of a buyer or funder.
Because so many people are involved, the format matters. A list that lives in one person's notebook cannot be shared, tracked, or audited.
When in the project do you snag?
Snagging is not only an end-of-project activity. Strong teams snag continuously:
- During the build, at the end of each stage or trade package.
- At pre-handover, as a formal inspection before practical completion.
- After handover, during the defects liability period, when latent issues appear.
Catching defects early is always cheaper. A paint touch-up found at first fix costs minutes. The same issue found after furniture arrives can cost a return visit.
Paper, spreadsheet, or software?
Paper lists are fast to start but impossible to track. Spreadsheets add structure but break down with photos, versioning, and multiple users. Dedicated snag software keeps every defect, photo, comment, and sign-off in one place, with a full history of who did what and when.
Tips for a better snag list
- Write descriptions a stranger could act on without calling you.
- Always attach a photo taken at the time of inspection.
- Assign every snag to a named person, not a company.
- Set a due date and a priority on every item.
- Review the list weekly and close items only after re-inspection.
SnagCore was built around exactly this workflow: capture on-site with photos, assign to contractors, track completion, and export a clean report at handover. You can start a free trial and run your next inspection with it.
A well-run snag list protects your reputation, your programme, and your margins. Treat it as a core project document, not an afterthought.