← All articles

Site capture · 7 min read

How to do a snagging inspection (and turn photos into a register someone can act on)

The hard part of snagging is rarely taking the photographs. It is everything afterwards: matching photos to notes, typing the register, splitting actions by trade, chasing completion, and proving the work is done.

The key point

A useful snagging inspection is a disciplined walk-around plus a controlled handoff. Capture each item with a photograph and a short note while you are still on site, structure those items into a register your project already understands, issue only the relevant items to each contractor, then close each item against completion evidence — not against a memory of an email thread.

This guide is for project managers, site managers, inspectors, client teams and contractors who snag repeatedly on live projects — housing, fit-out, estates, rail and infrastructure alike.

What “good” snagging looks like

A strong snagging process does four jobs:

  1. Capture — evidence and observation stay linked
  2. Structure — each item has location, description, owner and status
  3. Issue — the right party sees only their work
  4. Close — completion photos and responses sit against the same item

If any of those steps still live in camera rolls, copied spreadsheet tabs or long email chains, the workflow is doing more admin than it should.

Homeowner-facing guidance, such as the NHQB Homeowner Guide to Snagging (V2, May 2026), explains how buyers can check a new home for snags and what the New Homes Quality Code expects from developers. Commercial project snagging uses the same discipline of systematic inspection — but the register must also serve contractors, programme and handover evidence under the project’s own documents.

Before you walk: set the register up to succeed

Agree the columns you will keep

If the client already has spreadsheet headings, keep them. Remapping every project into a new corporate format creates resistance and duplicate reporting. A workable register typically needs at least:

  • Unique item reference
  • Location (building / level / room / asset)
  • Description of the defect or outstanding work
  • Responsible party / trade
  • Priority or category (as your project defines it)
  • Status (open / in progress / ready for inspection / closed / rejected)
  • Photo / evidence reference
  • Target or programme date (where used)

Decide what “closed” means

Closed should mean: authorised review of completion evidence against the original item — not “someone said it was done in a WhatsApp group”.

Bring the project documents you are allowed to use

Drawings, specifications and contract extracts help you describe the required finish and locate the issue. They are optional for many tools; if confidentiality rules prevent upload, keep inspecting and record against what you can see on site. Never upload material your company does not permit you to share with a software provider.

On the walk: capture at walking speed

Work in the order of the inspection

Stay systematic — floor by floor, room by room, elevation by elevation — so nothing relies on memory later.

Photo first, then the shortest useful note

For each item:

  • Take a clear photograph of the defect in context
  • Mark or note the exact location
  • Dictate or type a rough description, including site jargon if that is fastest
  • Tag a trade or party when you know it; leave it unassigned when you do not

Polished prose is not required on site. Clear evidence is.

For a shorter practical guide on pairing context and detail photographs, see Take photos that explain the snag.

Separate defects, queries and additional work

Not every observation is a defect. Queries and potential additional work should be identifiable so contractors are not forced to treat everything as a normal snag.

Do not stop the walk to build the final report

Report assembly belongs after capture. The goal on site is a complete, ordered set of evidence-backed observations.

After the walk: structure the register

Turn rough notes into clear records against your project columns:

  • Correct locations and references
  • Descriptions a contractor can act on
  • Owners or trades
  • Priorities
  • Links between photos and rows

This is where many teams lose an evening: retyping, matching images and formatting. Software can draft structured snag records from photos and notes for human review; people still decide what is accurate, contractual and fair.

For a shorter guide on writing a location, an observation and a next action, see Write a snag someone can act on.

Illustrative only (from SnagSort’s public homepage, 12 October 2026 comparison): under stated assumptions for 60 snags after initial capture, traditional report preparation was shown as 120 minutes versus 20 minutes with SnagSort’s workflow — an 83% reduction in that narrow preparation slice. The site states this is not a timed customer study, and setup, uploads, contractor responses and close-out sit outside the example. Treat it as a worked illustration of where admin time usually goes, not as a promised saving.

Issue work without sharing the whole world

Handing every contractor the full client register creates noise, commercial leakage and missed items.

Better practice:

  • Scope access by party and item type
  • Include the description, location and client photographs against each item
  • Ask for a programme where outstanding work needs dates
  • Allow responses for additional work or queries without forcing them into the same bucket as defects

Contractors should be able to answer the right items — not filter a master spreadsheet to find themselves.

Close-out: evidence against the item

Ready for inspection

When a contractor marks work complete, they should return completion photographs and notes against the same snag reference.

Review, reject or accept

Authorised project members decide whether evidence is accepted. Rejection returns the item with history retained. Acceptance closes it with the trail intact.

For a shorter guide on keeping contractor submission and authorised acceptance separate, see “Done” is the start of the review.

Export what the organisation already expects

PDF reports, Excel-ready rows and evidence packs support handover and project records. Keeping exports aligned with the client register avoids a second reporting format.

A practical snagging checklist (template fields)

Use this as a field checklist / register starter — adapt headings to the project:

  1. Project / package name
  2. Inspection date and inspector
  3. Item ID
  4. Location (and drawing reference if known)
  5. Description
  6. Photo(s) before
  7. Trade / responsible party
  8. Category (defect / query / additional work)
  9. Priority
  10. Issued date / portal or email reference
  11. Contractor programme date
  12. Photo(s) after / completion notes
  13. Review decision (accept / reject / remain open)
  14. Closed date and closer

That structure is enough to run capture → structure → issue → close without inventing a new methodology for every site.

Where SnagSort fits

SnagSort is a web application built around that loop: photos and rough notes become a structured register; each contractor gets a scoped portal; completion evidence comes back against the item. Project Intelligence can hold drawings and specifications so you can ask where a detail sits and pin issues on plans. The live product runs in the browser and is available now as a PWA (an installable web app); iOS and Android apps are planned and not live yet.

Pricing on the public site (checked 11 November 2026) starts at £12/month for Pro (1 active project), with Team £39/month (5 projects) and Business £99/month (20 projects). Every paid plan lists a 14-day free trial, unlimited users and contractors, and full project-aware AI features on the matrix. Enterprise capacity is by discussion.

AI assists descriptions and document questions; it does not certify compliance or decide entitlement. Manual entry remains available.

Try or enquire: Pricing & trials · Enquire · How it works for clients · Contractor portal

Related practical guides on SnagSort

These shorter live guides cover parts of the same workflow in more detail:

FAQ

What should be on a snagging list template?

At minimum: a unique ID, location, description, responsible party, status, photo evidence and a clear close-out decision. Add programme dates, priorities and categories to match how your project already works.

How do you run a snagging inspection on a live project?

Inspect systematically, capture photo-linked observations as you go, structure them into the project register, issue scoped lists to contractors, then accept or reject completion evidence against each item.

Should snagging replace our Excel register?

Not necessarily. Many teams keep existing column headings and export Excel-ready rows so the site workflow improves without forcing a new corporate format.

Can contractors see every snag on the project?

They should not need to. Scoped access by party reduces noise and keeps unrelated items out of their queue. On SnagSort, contractors do not become normal project members.

Do you need drawings uploaded before you can snag?

No. You can inspect and record without project documents, then add drawings or specifications later if your organisation permits it.

Bring the record together

Explore how SnagSort connects site capture, contractor responses and inspection.

See how it works

Keep reading

All articles ↗