Snagging and Punch Lists: How to Manage Them Without Spreadsheets or WhatsApp

Call it snagging, a snag list, or a punch list — it's the same moment, and it's the one that decides whether a project ends clean. The build is essentially done. The client, consultant, or landlord walks the site and starts listing everything that isn't right: a chipped tile, a door that binds, a paint touch-up, a missing socket cover. Then the real work begins — assigning each item, fixing it, proving it's fixed, and getting sign-off so you can release retention and get paid.

Most teams run this on a spreadsheet and a WhatsApp group full of photos. It almost works. It also quietly drags handover out by weeks.

Why snagging breaks down

A snag list looks simple — a list of small defects. The trouble is everything around the list:

Photos lose their context. Forty images land in a WhatsApp group with no location, no item number, and no description. A week later nobody can match the cracked-tile photo to which room, or whether it was ever fixed.

No clear owner per item. "Someone fix the snags in unit 3" is not an assignment. Items fall between the joiner, the painter, and the MEP subcontractor, each assuming another has it.

No status, so no visibility. Open, in progress, fixed, verified, closed — none of that lives in a spreadsheet that's emailed around. So the honest answer to "how many snags are left?" is always "let me check and get back to you."

Re-inspection is a guessing game. When the consultant returns to verify, there's no clean view of what was closed since the last walk. So they re-walk everything, and the list goes around a third time.

It's disconnected from the project. The snag list sits in a separate file, unlinked from the drawings, the client, or the handover milestone it's blocking.

This is the same pattern we described in the hidden cost of running fit-out projects on WhatsApp — the tool can't hold the structure the work needs, so the structure lives in people's heads until it doesn't.

What a proper snag list workflow looks like

A snag list is really a small, time-boxed quality-control project. Treat it like one:

Capture on site, in context. Raise a snag where you're standing — photo, location, description, and the trade responsible — from a phone, in one step. No re-typing a spreadsheet back at the office.

One owner, every item. Each snag is assigned to a specific person or subcontractor, so there's no ambiguity about who closes it.

A status everyone can see. Open → in progress → fixed → verified → closed. The whole team — and the consultant — sees the live count and what's outstanding, without asking.

Proof of fix. The person who resolves a snag attaches an "after" photo. Verification becomes a glance, not a re-walk of the entire unit.

Tied to the project and the client. Snags live inside the project they belong to, linked to the relevant drawings and visible to the client or landlord in a clean portal view — so handover approval is based on a shared, current picture, not competing spreadsheets.

A record that survives. When retention is disputed months later, you have a timestamped history of every snag raised, fixed, and signed off. That's the same logic behind good construction document management — the receipt matters as much as the work.

Why this matters more than it looks

Snagging sits directly on the critical path to payment. Every day a snag list is unclear is a day retention isn't released and the client's confidence dips. Teams that run snagging properly close handover faster, take fewer trips back to site, and walk into the retention conversation with evidence instead of arguments.

It's not about adding bureaucracy. It's about making the last 5% of the project — the part clients actually remember — as organized as the rest of it. Phase-based projects with built-in sign-off, which we covered in why flat task lists fail for construction, treat handover and snagging as a real phase, not an afterthought.

---

Ready to simplify your projects?

Biltit lets your team raise, assign, and close snags from the site — with photos, status, and a client view built in. Start free during beta or see how it works.