Snag List vs Punch List: Same Thing or Not? (UK vs US Guide)

Short answer: A snag list and a punch list are essentially the same thing under two regional names. "Snag list" is the term used in the UK, Ireland, Australia and New Zealand; "punch list" is the US equivalent. Both are a list of defects and incomplete items that have to be fixed before a project, or a section of it, is handed over. The work and the intent are identical; only the vocabulary and a few habits around scope differ. Archi Check does not produce site snag lists, but the raise-assign-verify-close discipline that stops items from being lost is exactly what it applies to drawing QC.

If you have worked on projects on both sides of the Atlantic, you have probably had the same conversation more than once: someone asks for the punch list, someone else hands over a snag list, and a third person wonders whether they are looking at two different documents. They are not. The confusion is entirely a matter of language, and it is worth clearing up because the underlying task — getting a building finished to the agreed standard before anyone signs it off — is one of the most consequential phases of a project.

This guide sets out where each term is used, what the list actually contains, where it sits in the project timeline, and how the items are created and tracked. It also draws a clear line between this near-completion site activity and the earlier discipline of drawing-stage QC, because the two are often muddled and they are not the same job.

Snag list vs punch list: the same idea, two names

Start with the conclusion, because it removes most of the confusion: a snag list and a punch list describe the same document. Both are a record of outstanding items — defects, incomplete work, and things that do not match the contract or the drawings — that must be resolved before a project reaches practical completion or final handover. The reviewer walks the building, notes what is wrong or unfinished, and the resulting list becomes the to-do list that gets the project over the line.

The difference is regional. "Snagging" and "snag list" are the established terms in the United Kingdom, Ireland, Australia and New Zealand. "Punch list" is the term you will hear across the United States and much of Canada. Both terms now travel — you will find US firms that say "snag" and UK firms that say "punch list," particularly on international projects or inside global contractors — but the regional default still holds.

The names have different origins, and the etymology is a small but useful tell. "Punch list" comes from the old practice of punching a hole next to each item on a paper list as it was completed or verified, a physical way of marking progress. "Snag" comes from the everyday sense of a snag as a catch or a small obstacle — the loose thread that catches, the minor thing that trips you up. Neither origin changes what the document does, but they hint at a subtle difference in habit that is worth naming.

Where the two terms genuinely differ

If the two are essentially the same, why does anyone argue about it? Because there are real, if minor, differences in scope and usage that have grown up around each term. None of them make the lists different documents, but they do shape how people use them.

• Scope of what counts. Punch lists, by reputation, lean towards incomplete or defective work that is tied to contractual completion and final payment. Snag lists, particularly in residential work, often stretch to minor cosmetic imperfections that go beyond the strict contractual requirement — a scuff on a skirting board, a paint line that is not quite clean. In practice both lists capture cosmetic items; the difference is one of emphasis, not rule.
• Residential vs commercial flavour. "Snagging" is strongly associated with new-build housing in the UK, where buyers commission independent snagging inspections before completion. "Punch list" carries more of a commercial and infrastructure connotation in US usage. Again, both terms are used across both sectors; the association is cultural, not technical.
• Who raises it. On many UK residential jobs the homeowner or an independent snagging surveyor produces the list. On US commercial jobs the punch list is more often driven by the architect, the owner's representative, or the general contractor. The role shifts with the procurement model more than with the word.
• Formality. Punch lists are frequently a formal contractual milestone — substantial completion is declared, the punch list is agreed, and final payment is tied to clearing it. Snag lists can be just as formal, but the term is also used loosely for any informal list of defects a person spots on a walk-through.

The honest summary is that these are tendencies, not definitions. If someone hands you a snag list and you expected a punch list, you have lost nothing — you are looking at the same kind of document, and the only adjustment you might make is to check how far the list reaches into cosmetic detail.

Where the list sits in the project

Both lists belong to the same moment in the project lifecycle: near completion, when the building is substantially finished but not yet handed over. This is the point where the question shifts from "is it built?" to "is it built correctly, completely, and to the agreed standard?"

On a typical job the sequence runs roughly like this. The contractor declares that the works, or a defined section of them, are substantially complete. A walk-through or inspection follows, often involving the architect or contract administrator, the contractor, and sometimes the client or their representative. The defects and incomplete items found during that inspection become the snag or punch list. The contractor then works through the list, and a verifying party confirms each item is resolved before the certificate of practical completion — or its local equivalent — is issued.

There is usually a second wave too. After handover, a defects liability period (the "rectification period" or "snagging period" in some contracts) gives the client a window to report faults that emerge once the building is in use. Items raised in that period are tracked in the same way. So the list is not a single event but a discipline that runs from substantial completion through to the end of the defects period.

How snags and punch items are created and tracked

The mechanics are the same regardless of which word you use, and they are simple to describe and surprisingly easy to get wrong. Each item needs four things to be useful: a clear description of the defect, a location, an owner who is responsible for fixing it, and a status that moves from open to closed once the fix is verified.

A well-run list captures more than "fix the door." It records where the door is, what is wrong with it, who is responsible, when it was raised, a photo if relevant, and — crucially — confirmation by someone other than the person who fixed it that the fix is actually done. That last step is the one most often skipped, and it is the one that determines whether the list is a genuine record or just a wish list.

A worked example of a few items

To make it concrete, a handful of typical entries on a near-completion list might read:

• Apartment 04, ensuite: tile grouting incomplete along the shower tray edge — assigned to tiling subcontractor, raised 02 June, photo attached, status open.
• Ground floor lobby: ironmongery missing on the riser cupboard door — assigned to the joinery contractor, raised 02 June, status open.
• Level 2 corridor: emulsion finish scuffed near the lift lobby, requires touch-up — assigned to the decorator, raised 03 June, status open.
• Plant room: two pipe brackets loose, do not match the coordinated services drawing — assigned to the M&E contractor, raised 03 June, status open.
• External, north elevation: sealant to window perimeter incomplete at first floor — assigned to the facade subcontractor, raised 04 June, status open.

Each of those has an owner and a status, which is what separates a tracked list from a loose collection of notes. When the tiling is finished, someone other than the tiler confirms it on site, and only then does the item close, with the date and the verifier recorded. Multiply that discipline across a few hundred items and you have a defensible record of how the building reached completion. Skip it, and you have a list nobody trusts.

UK vs US: a side-by-side comparison

The table below pins down the regional differences without overstating them. Read the right-hand columns as tendencies and defaults, not as hard rules — the central point is that the rows describe the same document.

If you take one thing from the table, let it be the second row. The defining purpose is identical on both sides. Everything else is dialect.

How this differs from drawing-stage QC

Here is the distinction that matters most for anyone trying to run quality properly: a snag list or punch list is a site activity, and it sits at the end of the project. It is about the physical building — what was actually constructed and whether it matches the design. Drawing-stage QC is a different job that happens much earlier, on the documents themselves, before anyone breaks ground.

The two are connected, because a defect on a snag list often traces back to a problem that was already present in the drawings. A clash between services and structure that nobody caught during drawing review becomes a loose-bracket snag on site. A dimension that was never coordinated between disciplines becomes a punch item when the cladding does not fit. The earlier you catch the issue, the cheaper it is to fix — a redline on a drawing costs a comment; the same error on site costs labour, materials, and programme.

So the snag list is, in part, the bill for QC that did not happen earlier. That is not an argument against snag lists — site inspection will always be necessary, because some things genuinely cannot be known until the building exists. It is an argument for taking the drawing-review stage as seriously as the site walk, and for using the same tracking discipline in both. For the full picture of what drawing QC involves, see What is drawing QA/QC?, and for the stages it moves through, the drawing QA/QC process in 4 stages.

The discipline that stops items from being lost

Whether you call it a snag or a punch item, the failure mode is always the same: an item is raised, someone is supposed to fix it, and then it falls through a gap. Nobody confirms the fix, the list is out of date within a week, and at handover there is an argument about what was actually resolved. The cause is almost never a lack of effort. It is a lack of a closed loop.

A reliable list runs on a simple cycle: raise the item with a clear description and location, assign it to an owner, have the fix made, verify the fix independently, and close it with a record. The same logic underpins good drawing QC, where the loop is Check, Correct, Verify, Close. The shape is identical because the problem is identical — a defect is only truly resolved when someone other than the person who fixed it has confirmed it, and there is a record that says so.

That record is what makes the list defensible. When a dispute arises months later about whether a defect was cleared, the answer should be a tracked entry with a date, an owner, and a verifier — not someone's memory of a walk-through.

Where Archi Check fits

It is worth being precise about scope here, because honesty about what a tool does is more useful than a stretch. Archi Check is QC software for architectural drawing sets — it works on the drawings, before site. It does not produce site snag lists or punch lists, and it is not a site-inspection app. What it does is apply the exact tracking discipline described above to the drawing-review stage, which is where many of the issues that later become snags can be caught and closed for the price of a comment.

In Archi Check, every markup is a tracked comment, not a loose annotation. When a checker clouds a clash or flags a missing dimension, that comment carries an owner, a status, and the sheet and revision it sits on. It moves through Check, Correct, Verify, Close — raised, assigned, verified, closed — so an issue cannot quietly disappear the way an unverified snag does. A correction is not finished until someone other than the author verifies it, and the whole chain leaves an audit trail you can point to later.

Two further things matter for record-keeping. Archi Check stores QC data in your own project folders rather than a vendor cloud, so the audit trail belongs to you and lives with the rest of the project. And the two-screen workflow lets you mark up the full-size drawing on one monitor while the register tracks every open item beside it. Archi Check runs on Windows today, with macOS coming soon, and there is a 14-day free trial. It will not clear your punch list — but it will help you keep the drawing defects off it in the first place. For the on-drawing version of the same job, see defect tracking on drawings.

FAQ

Is a snag list the same as a punch list?

Yes, in substance they are the same document. Both are a list of defects and incomplete items that must be fixed before a project, or a section of it, is handed over. "Snag list" is the term used in the UK, Ireland, Australia and New Zealand, while "punch list" is the US and Canadian equivalent. The work and the intent are identical; only the regional vocabulary and some habits around scope differ.

What is a snag list in construction?

A snag list is a record of defects, faults, and incomplete items identified on a building near completion, which the contractor must resolve before handover. It typically captures the location of each item, a description of the defect, who is responsible for fixing it, and a status that closes once the fix is verified. In new-build housing it often extends to minor cosmetic imperfections as well as functional defects.

Why are they called different names in the UK and US?

The names have separate origins. "Punch list" comes from the old US practice of punching a hole beside each item on a paper list as it was completed or checked. "Snag" comes from the everyday British sense of a snag as a small catch or obstacle. Both evolved regionally to describe the same near-completion defect list, which is why the terms are used interchangeably on international projects.

When in a project is a snag or punch list created?

It is created near completion, once the building or a defined section is substantially finished but not yet handed over. An inspection or walk-through produces the list, the contractor works through it, and a verifying party confirms each item before the completion certificate is issued. A second wave of items is often raised during the defects liability or warranty period after handover.

How is a snag or punch list different from drawing QC?

A snag or punch list is a site activity at the end of the project, concerned with the physical building and whether it matches the design. Drawing QC happens much earlier, on the documents themselves, before construction starts. Many snags trace back to issues that were already present in the drawings, so catching them during drawing review is far cheaper than fixing them on site. The two share the same raise-assign-verify-close discipline.

Catch the drawing defects before they become snags

A snag list is partly the bill for QC that did not happen earlier. If you want to catch drawing-stage defects before they reach site — with every issue tracked, assigned, verified, and recorded — see how Archi Check applies the same discipline to your drawing set: Try Archi Check free for 14 days.

Related guides

Keep building out your drawing QC process with Archi Check and these related guides:

• Defect tracking on drawings
• The drawing QA/QC process in 4 stages
• How to create as-built drawings
• What is drawing QA/QC?

Archi Check is an independent product by Archi for architectural drawing QA/QC. Product names and trademarks referenced belong to their respective owners and are used for identification only.