All articles

Field guide

Snag List vs Punch List: What's the Difference?

June 24, 2026 · 6 min read

If you work across construction, fit-out, or property turnover, you'll hear two names for the same idea — snag list and punch list. They describe the running list of small defects and unfinished work that has to be fixed before a job is signed off. The words differ by region, not by meaning. What matters far more than the label is how you capture each item, who you send it to, and whether anyone can prove it was fixed. Here's the difference between the two terms, and how to actually run the list well.

What a punch list is

Punch list is the common term in the United States and North America. It's the list of items left over near the end of a project — the things that are wrong, missing, or not finished to the standard agreed in the contract. A chipped countertop, a door that won't close, a missing outlet cover, paint that needs a second coat. Each item is something specific that has to be corrected before the work is accepted and final payment is released.

The name comes from the old practice of literally punching a hole next to each item on a paper list as it was completed. The method has changed, but the job hasn't — walk the space, find what's not right, write it down, get it fixed, confirm it's done. The punch list is the gap between "nearly finished" and "actually finished."

What a snag list is

Snag list is the term used in the UK, Ireland, Australia, and across much of the construction world. A snag is a small defect or unfinished detail — the same kind of item that lands on a punch list. Snagging is the act of inspecting the work and recording every snag you find, usually room by room, before handover.

So a snag list and a punch list are the same thing under two names. If a US property manager and a UK contractor compared their lists, they'd find the same content — defects to fix, items to finish, things to check again. The difference is vocabulary, shaped by where you happen to be working.

What actually goes on the list

Whatever you call it, a good entry describes one problem clearly enough that the person fixing it doesn't have to come back and ask. That means a short factual note — what's wrong and what "done" looks like — plus a photo and the exact location. "Cracked tile" is weak. "Cracked floor tile, second from the wall, by the window in unit 4B" is something a contractor can act on without a phone call.

Typical items span trades and finishes: damaged or missing hardware, gaps in caulk or grout, doors and windows that bind, touch-up paint, fixtures that don't work, cleanup that wasn't done. Some are cosmetic, some affect function or safety. The list doesn't judge size — it just records each thing that stands between the work and sign-off, so nothing gets quietly skipped.

Where these lists are used

The classic case is construction handover — the builder finishes, the client or their inspector walks the building, and the snag or punch list is the agreed record of what's outstanding before keys change hands. Final payment often depends on clearing it, which is why an accurate, photo-backed list protects both sides.

But the same workflow runs well beyond new construction. Commercial fit-out teams snag a space before a tenant moves in. Property managers run a punch list at turnover between residents, logging what needs repair before the next lease. Facilities teams use the same approach for routine inspections and ongoing maintenance. The format scales from a single apartment to a whole site without changing.

How to manage one well

Four things make a list trustworthy: a photo, a location, an assignment, and a record. The photo removes argument about what was wrong. The location means the right person finds the item fast. The assignment puts a name against each fix so it doesn't drift. And the record — a timestamped log of when it was raised, sent, and closed — is what lets you prove the work was done if anyone questions it later.

This is exactly where spreadsheets, group chats, paper forms, and email start to fail. Photos sit on one phone, addresses get typed wrong, items get raised and then forgotten, and there's no single trail showing what happened. A report that's sent and forgotten is a problem that stays broken. The fix isn't more effort — it's a workflow that captures all four things in one pass and keeps them together.

How SnagGrid handles the list

SnagGrid is built for exactly this work, whichever word you use for it. You snap a photo and drop a map pin — the address auto-fills, so the location is right without typing. You add your rough notes, and AI drafts a clear, professional report from what you wrote. It never invents facts, and you approve every word before anything goes out, so the report says what you saw and nothing more.

From there SnagGrid emails the right recipient, logs the item to an audit trail, and gives you one-tap follow-up reminders so nothing stalls. A team dashboard with roles shows the whole list at a glance, you can export to CSV for records or reporting, and a scoped REST API with webhooks lets you wire it into your own systems. Pricing is $29 per month per organization for one seat, plus $15 per month for each extra seat — so a snag or punch list stops being a scattered set of photos and turns into a record you can stand behind.

FAQ

Frequently asked questions

Is a snag list the same as a punch list?
Yes. They describe the same thing — a list of small defects and unfinished items to fix before a job is signed off. Punch list is the common US and North American term, while snag list is used in the UK, Ireland, Australia, and across construction. The content is identical; only the name changes by region.
Why is it called a punch list?
The name comes from the old practice of punching a hole next to each item on a paper list as it was completed. The tools have changed, but the idea is the same — track each outstanding item and mark it off once it's fixed and confirmed.
What should each item on the list include?
At minimum, a clear note of what's wrong and what "done" looks like, a photo, and the exact location. That combination lets the person fixing it act without coming back to ask questions, and it removes any later argument about the condition of the work.
Where are snag and punch lists used?
Most often at construction handover, before final payment. The same workflow also fits commercial fit-out, property turnover between residents, and routine facilities inspections. The format scales from a single unit to a full site without changing.
How does SnagGrid help manage a snag or punch list?
You snap a photo and drop a map pin so the address auto-fills, then AI drafts a factual report from your notes that you approve before it sends. SnagGrid emails the right recipient, logs every item to an audit trail, and gives one-tap follow-up reminders. A team dashboard, roles, CSV export, and a REST API with webhooks keep the whole list in one place.

Report it properly — and prove you did.

Capture the problem once, approve the wording, and SnagGrid sends a structured, evidence-backed report to the right inbox — then reminds you to follow up.

You approve every word before it sends. SnagGrid never invents facts.