What a punch list is, and how it differs from a snag list

A punch list is the itemised set of work that still has to be finished or corrected before a contractor collects the rest of the money. Not a wish list, not a to-do list, and not a place to record things you would have designed differently. Every line on it is contracted work that is missing, incomplete or wrong.

That is the whole definition, and the money is the part that makes it work. A list nobody has to close is a list nobody closes.

The punch list is what releases the final payment

Most construction contracts hold back part of the contract sum until the work is accepted, with the retainage percentage written into the agreement itself. The punch list is what stands between the contractor and that balance. Items get walked, listed, corrected, re-walked and signed off, and the retainage is released against a closed list.

Two consequences fall out of that. The first is that scope matters more than anything else on the list: an item that is not contracted work does not belong on it, because you cannot withhold payment for work nobody agreed to do. The second is that ambiguity costs the owner as much as the contractor. An item that cannot be objectively closed will get argued about instead of fixed.

A snag list is the same document under a different name

Snag list and snagging are the words used in the UK and Ireland. Punch list is North American. Canadian contracts often say deficiency list. Australian jobs may call it a defects list against practical completion. The document is identical: what is still owed before the work is accepted.

If you work across those markets, pick one term per project and put it in the contract, then use it everywhere. Mixed vocabulary in the same email chain is how two lists end up in circulation.

Substantial completion is what starts the clock

The punch list walk normally happens at substantial completion, usually defined in the contract as the point where the owner can occupy and use the work for its intended purpose even though items remain. A tenant can move into Suite 203 with four missing outlet cover plates. They cannot move in without power.

Getting the timing right matters because the date often triggers other things: the start of warranty periods, the transfer of insurance and utilities, and the end of liquidated damages. A walk held too early produces a list padded with work that was always going to be finished that week, which buries the real items.

An item you cannot close is not an item

A usable punch item answers four questions: where, which trade, what is wrong, and what "done" looks like. Add a photo and the row stops needing a phone call.

Compare that against what most lists actually contain: "touch up paint 2nd floor", "clean windows", "fix door". Each of those takes a phone call to interpret, and the phone call happens three weeks later when the person who wrote it has moved to another job.

The punch list template has these columns already laid out, with a filled example to copy.

Three things belong on a different list

Change orders are not punch items. If the owner wants a different fixture from the one specified, that is new scope with a price attached, and putting it on the punch list disguises a cost as a correction.

Warranty work is not punch work. A punch item is contracted work that was never done right. A warranty claim is work that was accepted and then failed. The distinction decides who pays and under which clause.

Damage caused after acceptance is its own category, and it usually turns into an insurance or tenant-improvement conversation rather than a construction one. Photographs with dates settle these fast, which is the practical reason to photograph the finished condition at the walk and not just the defects.

Zero items is not the goal, a closed list is

Nobody finishes a building with an empty list. A 40,000 square foot fit-out that produces twelve items has a superintendent who self-punched carefully, and one that produces three hundred has a walk that was held far too early. Neither number tells you much on its own.

What tells you something is the close rate. Items should leave the list steadily, each with a date and a person's name against the closure, and the ones that sit open for a month are the ones that need a different conversation. Track two dates per item, raised and closed, and the pattern shows up without any effort.

The write-up at home is where the detail is lost

The common workflow is still a clipboard and a phone camera, then an evening at a laptop matching photos to scribbled lines. That evening is where items lose their location, where two similar defects merge into one line, and where "east wall" becomes "east wall?".

Capturing on the walk removes the pass entirely. Photograph the defect, say what is wrong out loud while you are looking at it, mark the photo where the problem is, and move on. Sitewise transcribes the voice note on the iPhone, stamps each capture with time and a GPS pin, and exports the whole walk as a PDF or DOCX you can send from the site. It works with no signal, which is normal in a stairwell, and syncs later.

It has limits worth knowing before you try it: no scheduling, no budgeting, no e-signature routing, no assignment workflow for subs, iPhone and iPad only. For a walk that ends in a document somebody emails, it fits. For a punch process where fifteen subs each need their own logged, assigned and tracked queue, you want dedicated punch software.

The list stops being useful the moment it stops being specific

Every problem with punch lists comes back to the same thing: a line item that means one thing to the person who wrote it and something else to the person who has to fix it. Location, trade, defect, acceptance criteria, photo. Five fields, and close-out goes from a negotiation back to a task list.