Punch List Template and How to Close One Out

A punch list is the list of things that are not done, not right, or not accepted, written so that someone can fix each one and someone else can confirm it was fixed. Every project has one. Most of them fail the same way: the list gets written, the items get argued about, and closeout drags on for weeks because nobody can say for certain what was open, who owned it, and what "done" was supposed to look like.

This guide covers what belongs on a punch item, how to write one that can be closed, how to run the walk, and the closeout process that keeps the list from becoming a negotiation. The template at the end follows the same structure.

What a punch list is for

A punch list has one job: to get from "the work is mostly done" to "the work is accepted" with a record of every step. That makes it three things at once:

1. A work list for the contractor. Each item tells a trade what to fix and where.
2. An acceptance record for the owner. Each closed item is a small sign-off; the closed list is the acceptance.
3. The evidence when the two disagree. Retainage, final payment, and warranty start dates often hang on whether the punch list was closed and when.

It is not a wish list, a change order, or a place for scope that was never in the contract. If an item is new scope, it goes into a change request, not the punch list. Mixing the two is the fastest way to lose the contractor's cooperation on the items that are legitimately theirs.

What belongs on every punch item

The template carries these columns. The first four are the ones a reader needs to act; the rest are the ones a reader needs to close.

• Location / area — the room, grid line, elevation, equipment tag, or panel. Specific enough that a person who was not on the walk can find it.
• Item (deficiency) — what is wrong or incomplete, stated as an observation, not an instruction. "Sealant missing at window head, west elevation, Grid B-3" beats "fix the sealant."
• Responsible trade / party — who owns the fix. Name a trade or a company. If you do not know, write "Unassigned" and resolve it at the punch meeting; do not guess, because a guessed assignment is one the contractor will reject.
• Photo ref — the photo that shows the condition, identified by its time or number. A punch item with a photo gets closed; a punch item without one gets debated.
• Status — Open or Done. Two states are enough. "In progress" is how items sit untouched for a month.
• Date found — the walk date, or the time the item was captured.
• Date closed and Verified by — filled in by the person who confirmed the fix, not the person who did it.

Leave priority off unless the contract requires it. On a real closeout nearly everything is "must fix before acceptance," and a priority column becomes a way to argue about sequence instead of doing the work. If a handful of items block occupancy or startup, mark those and leave the rest unranked.

How to write an item that can be closed

The test of a punch item is whether two people who were not on the walk — the trade fixing it and the person verifying it — would agree on what closes it.

One deficiency per item. "Door 104: closer not adjusted, kickplate missing, frame scratched" is three items. Written as one, it stays open until the last of the three is fixed and gets closed on the strength of the first two.

Location first, then the condition. Trades work by location. A list sorted by room or by grid gets walked in an hour; a list in the order the items were noticed gets walked in a day.

Say what "done" looks like when it is not obvious. "Grout missing at floor tile, Room 112 entry" is obvious. "Paint touch-up, Corridor 2" is not — touch-up to what standard, over what area? If the acceptance criterion is a spec section, cite it.

Observation, not opinion. "Ductwork hanger spacing exceeds 10 ft between Grid C-4 and C-6" can be checked with a tape. "Ductwork looks unsupported" cannot.

Weak: "Electrical room — cleanup and labeling."

Better: "Electrical Room E-1: panel LP-2 directory not filled in; two spare breakers unlabeled; conduit knockouts open at top of panel (photo 14:22)."

Running the punch walk

Walk it with the contractor, not after them. A list built alone gets contested item by item. A list built together gets accepted item by item, because the responsible party heard the observation at the same moment you made it.

Photograph everything you write. Not selectively — everything. The item you skip the photo on is the one that gets disputed.

Capture as you go, not at the end. Notes reconstructed in the truck lose the location detail that makes an item closeable. If you are dictating, say the location first every time.

Do not stop to argue on the walk. If the contractor disagrees that an item is theirs, mark it "Unassigned" and move on. Ownership gets settled at the punch meeting with the drawings open, not standing in a corridor.

Issue the list within 24 hours. A punch list that arrives a week after the walk is already stale; conditions change, and so do memories.

Closing one out

Closeout is where the money is, and it is where most punch lists fall apart. The process that holds up:

1. Assign. Every Unassigned item gets an owner at the punch meeting. An item nobody accepts is either not a deficiency or is a change — decide which and move it off the list.
2. Fix. The contractor works the list and reports items complete. "Complete" from the contractor is a claim, not a closure.
3. Verify. Someone on the owner's side looks at each reported item, in the field, against the original photo. This is the step people skip, and it is the step that gives the closed list its weight.
4. Sign off. The verifier records the date and their name. If the fix is not acceptable, the item stays open and the reason goes on the list.

Three rules make this work:

• The person who verifies is not the person who fixed it. Self-certified closeout is not closeout.
• A closeout photo for every item that had a condition photo. Same location, same angle. Two photos side by side end most disputes before they start.
• Reissue the list after each round, not a marked-up copy. Everyone works from the same current version. The old versions stay in the project file as the record.

When the list reaches zero open items, the closed list — with dates, verifiers, and photos — is the acceptance document. Attach it to the final pay application and the warranty start letter.

Common mistakes

• Writing instructions instead of observations. "Fix the leak" cannot be verified. "Water staining on ceiling tile below AHU-2 condensate line" can.
• Guessing who is responsible. A wrong assignment costs a week of back-and-forth. "Unassigned" costs one conversation.
• Letting the contractor close items. They report; you close.
• Combining items to keep the list short. A short list of vague items takes longer to close than a long list of specific ones.
• Punching scope that was never in the contract. It poisons the whole list. Route new scope through a change request.
• No closeout photos. Six months later, when a warranty item comes up, the closeout photo is the only proof of the condition at acceptance.

How FieldBinder AI produces a punch list

In the field, a punch item is one capture: the location and what needs to be fixed, typed or dictated, with a tag. Each item carries an open/done state you toggle as the work is verified. Photos taken in the same project sit alongside the items in the project feed.

When you generate a Punch List, the app drafts a numbered list from the project's captures with, for each item, the location if one was stated, the description, the responsible party only if a capture named one — otherwise "Unassigned", never guessed — and a reference to a related photo by its capture time. The report exports as a branded PDF with the project's site photos, each with its caption, tag, and time, or as plain text you can paste into an email. The open/done state is tracked in the app; the date-closed and verified-by columns on the template are yours to fill at verification.

The draft is a starting point, not a signed document. Every generated report is marked as AI-assisted, and you are responsible for reviewing it before it goes to a contractor or an owner. What the app removes is the transcription and the sorting, not the walk and not the verification.

AI report generation is part of the Pro plan; capture and organization by project are included on every plan. See pricing · How it works for contractors

Related

• Daily reports and punch lists for contractors
• Field documentation for project managers
• Site visit reports for owner's representatives