How to Write a Professional Snagging Report

~6 min read · For surveyors, builders & site managers

A snagging report is only as good as how clearly it’s written. A vague list gets ignored; a clear, photographed, well-structured report gets defects fixed fast — and protects you if there’s ever a dispute. Here’s what to include, a simple template you can reuse, and the habits that make a report land well with the people who have to action it.

What a good snagging report does

Whether it’s a new-build handover, a defects inspection, a site audit or a punch list, a strong report has one job: make every issue unmistakable and easy to fix. That means each snag has a location, a clear description, a photo, and a priority — so the person on the tools knows exactly what to do and where.

What to include in a snagging report

1. Header / cover details

• Property or site address and plot/unit reference
• Client and inspecting company
• Inspector’s name and the date of inspection
• A unique report reference (handy for follow-ups)

2. A short summary

Totals at a glance — how many items, and how many are open, in progress or closed. Decision-makers read the summary first.

3. The itemised snag list

The heart of the report. Group items by area (Ground Floor, Kitchen, Bathroom, External…) so it’s easy to walk. For each snag include:

• Reference — a code like KIT-02 so it can be discussed and tracked
• Location — specific: “above the hob”, not just “kitchen”
• Description — the fault and, ideally, the expected fix
• Photo(s) — the single most useful thing you can add
• Priority — so urgent defects don’t get lost among cosmetic ones
• Status — open / in progress / closed, updated as work is done

4. Floor-plan reference (optional but powerful)

A plan with numbered pins showing where each snag is removes all ambiguity — especially useful on larger sites and for trades who weren’t at the inspection.

5. Sign-off

Space to record who completed each item, when, and a signature or “after” photo — closing the loop and giving you a defensible paper trail.

A simple snagging report template

Tips that make a report land well

• Photograph everything. One clear photo per snag prevents “I can’t find it” and disputes.
• Be specific and consistent. Reference codes and precise locations save everyone time.
• Prioritise. Flag safety and watertightness issues so they’re actioned first.
• Keep it live. Update statuses as items are fixed and re-issue — a moving report is more useful than a one-off list.
• Send a PDF, keep a copy. A tidy, dated PDF looks professional and gives you a record.
• Work offline. Sites rarely have signal — capture on site, sync later.

Digital vs paper

Paper and spreadsheets still work, but they’re slow: you photograph on your phone, then re-type everything into a report that evening. A dedicated snagging app collapses that into one step — capture on site, and the report is already written. That’s hours back every week, and a more consistent, professional result.