De-snagging: how to run a re-inspection and report what was fixed

After the developer says the snags are fixed, a de-snag (re-inspection) checks each one. The buyer wants a clear answer: what is done, what is not, and what is still a safety risk.

Start from the first report

Re-inspect against the original snag list, not from scratch. Every snag keeps its reference number and original photo, so nobody argues about which defect is meant.

Three outcomes per snag

• Fixed: the defect is gone and the repair is acceptable.
• Partly fixed: work was done but the result is not acceptable yet (for example only some hollow tiles re-laid).
• Not fixed: no change. Add a new photo to show it.

Record any new defects caused by the repairs as new snags.

The de-snag report

• A summary: how many snags were re-checked and the percentage fixed.
• Open items first, safety items at the top.
• For each open item: original photo, new photo, and what is still wrong.
• A short list of what remains for the developer, again grouped by trade.

State your re-inspection policy up front

Buyers compare firms on whether a de-snag is included, how many visits, and the price of extra visits. Put it in your agreement and on your booking page.

In HandoverCheck, you start a re-inspection from the published report: the open snags come across with their photos, you mark each one in the app, and the report shows the counts and the percentage fixed.

See a sample de-snag report.