Snagging Report Example: What a Good One Looks Like

What every snagging report needs

1. A cover — project name, client, site address, inspection date, who inspected.
2. A summary count — snags raised, closed and still open. One line that tells the client where the job stands.
3. One entry per snag, each with:
   • Snag number and precise location (plot, room, area — GPS on external works)
   • A specific description of the fault
   • The trade or person assigned
   • Date raised, date closed
   • Photos of the fault — and after the fix, photos of the completed work alongside
4. Timestamps and locations on the photos. This is what makes the report evidence rather than a tidy to-do list. When a client queries whether the fix was done, or when damage appeared, the dated photo answers it.

Who the report is for

• Clients — proof the work is finished properly, or an honest statement of what's outstanding
• Main contractors — closing out subcontractor packages at stage completion
• Your own records — the defects liability period runs for months after handover; the report is what protects you when something is queried later

The fastest way to produce one

You can build a snagging report by hand — walk the job with a snag list template, photograph everything, then paste photos into a document against each entry. It works, but an hour of walking turns into an evening of formatting.

The alternative: raise each snag with photos as you walk, and let the app do the assembly. SiteSnap Pro turns a day's snagging into a branded PDF — your logo, one, two or four photos a page, before/after side by side, dates and locations printed on or left off — in a few taps. Start a 14-day free trial, or see how the snagging workflow works.