The last 5% of a construction project takes 20% of the calendar. Almost always, that's because the punch list is managed in a text thread instead of a document.
What a punch list should include
- Item — one thing per row. Not "kitchen touch-ups" — "cabinet door 12, hinge adjustment."
- Location — room and (if relevant) wall or elevation.
- Photo — the number one accelerator. A picture cuts a five-message thread into a single row.
- Owner — you, a sub, or the client (client-supplied items are punch list too).
- Status — Open / In progress / Done / Client-verified.
- Due date — if it's not dated, it slips.
How to run the walk-through
- Walk the whole job first without writing anything down. Get the room in your head.
- Second pass, tag every item — photo, one-line note, location.
- Read the list back to the client on the spot. Anything they add gets a row.
- Set a target-done date before you leave. Even if it's "next Wednesday."
- Send the list to the client the same day — not tomorrow.
The rule that closes projects
Nothing gets scheduled for a punch item until the item is on the list. This is where most contractors leak time — crews go back to the job because the client sent a text, fix one thing, and don't log the visit. Two weeks later, the list feels like it hasn't moved.
List first, then work. That single rule is the difference between a two-week punch and a two-month one.
Client-supplied items
Some punch items belong to the client (a rug order, a paint touch-up they wanted to do themselves). Put those on the list anyway, tagged as client-owned. It's the only way the schedule reflects reality.
Closing the job
Once every row shows "Done" or "Client-verified," send a short "punch complete" email that references the list. Then issue the final invoice. Progress billing in SiteView handles this cleanly — the final draw is unlocked once punch is closed.
Free tools
Want a signable document for a scope change that came out of the walk-through? Use the free change order generator.