Search for defect tracking advice online and you will see two terms used constantly: snag list and punch list. Are they the same thing? In practice, yes. The difference is mostly geography and a few conventions worth understanding if you work with international teams.
The short answer
A snag list is the standard term in the UK, Ireland, Australia, and New Zealand. A punch list is the standard term in the United States and Canada. Both refer to the list of defects, incomplete items, and corrections that must be resolved before a project, or a phase of it, is accepted as complete.
If your snag list process is solid, it will satisfy anyone who asks for a punch list, and vice versa.
Where each term comes from
Snagging comes from the idea of catching the small snags, the rough edges left behind when trades finish up. Punch list has a more mechanical origin: contractors would literally punch a hole next to completed items on a paper list, hence the name.
Both traditions produced the same artefact: a documented list of outstanding work attached to a stage of completion.
Small conventions that differ
While the documents are equivalent, a few habits differ between regions:
- Timing: US contracts often tie the punch list formally to substantial completion, a defined contractual milestone. UK and Irish projects more often treat snagging as a rolling activity that peaks before handover.
- Ownership: on US commercial jobs the architect or engineer of record frequently issues the punch list. In the UK and Ireland it is more commonly the contractor, the employer's agent, or a snagging inspector acting for the buyer.
- Terminology on the list itself: punch lists often reference specification sections, while snag lists more often reference rooms, plots, or drawings.
None of these differences change the fundamentals: find the defect, record it clearly, assign it, verify the fix.
Why the workflow matters more than the name
Teams lose far more time to a badly managed list than to any terminology confusion. The failure modes are identical everywhere: vague descriptions, no photos, no named owner, no due date, and no record of who signed off the fix.
Whether you call it snagging or punching, the same rules apply:
- Record every item with a photo and an exact location.
- Assign each item to a named person with a deadline.
- Keep one master list, not five versions in five inboxes.
- Verify every fix before marking an item complete.
One list, any name
If you work across regions, pick one master format and stick to it. SnagCore uses the term snag list, but the workflow it supports, capture, assign, track, report, is exactly what a punch list process needs. If your team is still running either list through chat threads, read about the true cost of WhatsApp snag tracking before your next project.
The name on the document will not delay your handover. A chaotic process will.