Use the checklist to make each snag understandable and reviewable. The worked example is synthetic and must be adapted to the inspection scope for your project.
Give the issue an identifier and a precise project location. Describe the observed defect or unfinished work, add dated photographs and reference the relevant drawing or specification when applicable. Separate the observed condition from an unverified cause. Record the author and date so the team knows who made the observation.
Identify the responsible role or contractor, the requested action and the agreed follow-up process. Keep a requested completion date distinct from an accepted commitment. Review issue status at a frequency appropriate to the project, and record changes with enough context for a person joining the team later.
Retain the original issue, add evidence of completed work and identify the person reviewing closure. Follow the inspection and acceptance process required by your project. This general checklist does not define technical tolerances, certify compliance or replace a qualified inspection. UK snagging and US punch list workflows can use the same record structure with locally appropriate terminology.
| Field | Synthetic example |
|---|---|
| Issue / location | SN-003 / Level 1, room 1.04 |
| Observed condition | Damage visible to door leaf finish |
| Evidence | Photo PH-051; observed 9 October 2026 |
| Responsible role | Assigned trade contractor |
| Closure requirement | Repair evidence followed by reviewer inspection |
| Status | Open; no acceptance recorded |
14-day trial · No card needed · 30-day money-back guarantee