Snag list template

A snag list people can act on.

Download the editable defect register for your snag list. Record each unfinished item or defect with a location, description, evidence reference, responsible trade and current status. Use the illustrative sample PDF to inspect SiteWarden’s app-generated output.

For builders and site teams setting up a snagging list for practical completion, a client walkthrough, or a handover inspection.

SiteWardenSample report
A page from the SiteWarden sample defect report, with photos, locations and item details.
The real output. Photos, locations and status in one shareable PDF.

Start with an editable worksheet.

Use the same editable register for snags, unfinished work and defects.

Download snag register CSV

Read the snag register guide

Adapt the fields to your project. The sample PDF shows app-generated report output; these standalone CSVs are not SiteWarden import files or approved technical inspection specifications.

01

Every field a snag list needs: ID, location, element, issue, trade, priority, status, and owner.

02

A format that survives contact with fifty snags and six contractors.

03

A free completed example report showing the finished output.

What a snag list template should include

A snag list is only useful if someone can act on each line without asking questions. Every snag needs enough context to be assigned, fixed, and verified.

  • Snag ID and date raised, so items can be referenced in conversations and reports.
  • Location and element: level, room or area, and the thing that is wrong.
  • Issue description and photo evidence captured at the point of inspection.
  • Trade, responsible contractor, priority, status, and verification sign-off.

Keep the spreadsheet and evidence organised

A spreadsheet can work when the team agrees who maintains it, where evidence is stored and how status is reviewed. As the list grows, check that each evidence reference still opens and each update stays connected to the correct item.

  • Use an item reference to match photos or evidence to the correct row.
  • Define who can update progress and who checks the entry before its status changes.
  • Record the review evidence and authorised acceptance before marking an item closed.
  • Check which version is current before preparing a report for the client.

Start from the finished report, not the blank sheet

The fastest way to design a snag list is to look at what the client should receive at the end. Download the free sample defect report to see the finished format, then work backwards.

  • The sample shows real-world structure: IDs, locations, photos, trades, priorities, statuses, and closeout notes.
  • Use the editable register for tracking work and the report worksheet for preparing output. Both are standalone files; neither is an app import format.
  • SiteWarden produces the report from the same records captured on the walk — no rebuild.
A few more details

Common questions.

Still weighing it up? Talk to our team.

What should a snag list template include?

At minimum: a snag ID, date raised, location, element, issue description, photo evidence, responsible trade or contractor, priority, status, and a verification column so closure is confirmed rather than assumed.

Is there a free snag list example I can look at?

Yes. The SiteWarden sample report is a free completed example showing snag IDs, photos, locations, trades, priorities, statuses, and closeout notes in a client-ready format.

Snag list or defect list — which term should I use?

Use the term your team and contract use. Snag lists and punch lists can include unfinished work as well as defects. A defect list focuses on work that needs correcting; the location, evidence, responsibility and status fields are useful for all three.

See it on your next site walk

Bring your list.
We’ll walk you through it.

Unfinished work, defects and the details in between. See how the current app captures, organises and reports on them.

Book a Demo