Snagging Inspections: Getting to a Clean Handover

Almost every contested handover comes down to the same problem: the two sides never agreed on a single, shared list. The client walks the building and writes notes on their phone. The contractor has their own list from an earlier inspection. The architect or inspector adds comments by email. By the time anyone tries to reconcile them, there are three versions of the truth, and each item is open to interpretation. Was that scuff there at the last inspection or is it new? Is the paint finish a defect or just the agreed standard? Without a common record, every one of these becomes a negotiation.

The second cause is timing. A snagging inspection run too early catches work that was always going to be finished anyway, padding the list with items that resolve themselves and making the real defects harder to see. Run too late, and the client is already chasing keys while trades have demobilized, so fixing anything means calling people back to site. The inspection has to land in the narrow window where the work is genuinely complete but the team is still mobilized to act on what's found.

The third cause is that nobody owns closure. Items get raised, but no single person is responsible for confirming each one is fixed and signing it off. The list grows, work happens in the background, and at handover nobody can say with confidence which items are genuinely closed and which are still open. A clean handover depends on closing that loop item by item, with evidence, not on a verbal assurance that "it's all been sorted."

The snagging inspection should happen when the work is substantially complete — all trades finished, the space cleaned, services commissioned and tested — but before the client takes occupation. That sequence matters. Snagging a space that's still being worked in means you're recording dust and offcuts as defects, and you'll have to re-walk it anyway. Wait until the site is in the condition the client will actually receive it.

It often helps to run a pre-snag or contractor's own inspection a week or two before the formal one. The contractor walks their own work first, clears the obvious items, and presents the building for the client's inspection in good order. This isn't about hiding problems — it's about not wasting the formal inspection on things the contractor would have caught themselves. The client's inspection then focuses on genuine disputes and standards, not on a wall of self-evident snags that should never have been there.

Book the inspection as a fixed appointment, not an open-ended visit, and make sure the people who can make decisions are present or reachable. The client or their representative, the contractor's site lead, and ideally whoever signs off payment all need to be in the loop. An inspection where findings can't be discussed and agreed on the spot just defers the disputes to later, which is exactly what you're trying to avoid.

The single biggest defence against a disputed handover is the quality of each entry. A snag that reads "paintwork" invites argument; a snag that reads "scuff and roller marks on the east wall of bedroom two, left of the window, approx 1m from floor" does not. The entry should describe one specific problem, in one specific place, clearly enough that the person fixing it never has to come back and ask what you meant. Vague items are the ones that get challenged, deferred, and forgotten.

Every item needs a photo and a precise location. The photo settles the question of condition — what was wrong, and what it looked like at the time of inspection — so there's no later debate about whether the damage was pre-existing or whether the fix was adequate. The location means the right trade finds the item in minutes rather than wandering the floor. Together they turn a subjective complaint into an objective record that both sides can look at and agree on, which is the whole point of the exercise.

Be explicit about the standard, too. A snagging list isn't a wish list for improvements beyond the contract — it's a record of where the work falls short of what was agreed. Where a finish is to a defined tolerance or specification, note it, so the conversation is about whether the work meets the standard rather than whether the standard was reasonable. Keeping the list tied to the agreed scope is what keeps it credible, and a credible list is one the contractor accepts rather than fights.

Not every snag carries the same weight, and treating them all identically slows handover down. A useful list separates items that block handover — anything affecting safety, function, or compliance — from cosmetic items that can be cleared shortly after occupation under an agreed timeframe. Sorting the list this way lets both sides agree handover can proceed once the blocking items are closed, rather than holding the whole thing hostage to a chipped skirting board. Be clear up front about which category each item falls in, because that classification is itself something the two sides need to agree.

Route each item to the trade or party responsible for it, not to a general pile. Plumbing snags go to the plumber, joinery to the joiner, and so on. When items are assigned by responsibility, work happens in parallel and nobody waits on a single coordinator to redistribute the list. It also makes accountability clear: each item has a name against it, so when something stalls you know exactly who to chase rather than discovering at the next inspection that it fell through a gap.

Give each item a target date as well as an owner. "Fix the door" with no date is an item that drifts; "adjust and re-hang the door to unit 3 by Friday" is a commitment. Dates let you see at a glance what's overdue, and they give the client confidence that the outstanding list is shrinking on a schedule rather than sitting untouched. The combination of category, owner, and date is what turns a list of complaints into a plan that closes.

An item isn't closed because someone says they fixed it — it's closed when there's evidence it was fixed and the client has accepted it. The cleanest way to do this is a fix photo against every snag: the same location, showing the corrected work, paired with the original. Before-and-after pairs remove the back-and-forth of re-inspecting in person for every small item, and they build a record that stands up if anyone questions the work months later.

Hold a re-inspection (or a rolling series of sign-offs) where the client confirms each fixed item is acceptable. This is the step that prevents the slow-trickle handover, because it forces closure to happen item by item rather than in a vague final wave. As items are signed off, the open list shrinks visibly, and both sides can see exactly how many items stand between the current state and a clean handover. When the blocking list reaches zero, handover can proceed, with any agreed cosmetic items carried forward on a documented and dated tail.

Keep a timestamped trail of the whole sequence — when each item was raised, who it went to, when it was marked fixed, and when it was signed off. This record is what protects both parties. For the contractor, it proves the work was completed to standard within the agreed window, which matters when final payment or retention is on the line. For the client, it proves what was outstanding at handover and what was promised afterward. An audit trail isn't bureaucracy here — it's the thing that makes the handover final instead of permanently re-openable.

SnagGrid is built for exactly this walk. During the inspection you snap a photo and drop a map pin — the address auto-fills, so the location is precise without typing — then add your rough notes, and AI drafts a clear, factual report from what you wrote. It never invents facts, and you approve every word before anything goes out, so each entry says what you actually saw and nothing more. That gives you the kind of specific, photo-backed item that doesn't get argued with, captured in a single pass while you're still standing in front of it.

From there, per-category routing sends each snag to the right trade or recipient automatically, one-tap follow-up reminders keep overdue items moving, and case tracking lets you carry an item from raised to fixed to signed off. Every action is logged to an audit trail with timestamps, so when handover comes you can show exactly what was outstanding, who was responsible, and when each item closed — backed by before-and-after photos rather than verbal assurances. A team dashboard with roles shows the whole open list at a glance, CSV export gives you a clean record for the handover file, and a scoped REST API with webhooks ties it into your own project systems.

Pricing is $29 per month per organization for one seat, plus $15 per month for each extra seat — so the snagging inspection stops being three competing lists on three phones and becomes one shared, evidenced record both sides can sign off on. That single source of truth is what turns a contested handover into a clean one.