Why group a snag list by trade?

Developers hand snags to the teams that fix them, so a list grouped by trade lets each team see its own items and the count per trade.

What columns should a developer snag list have?

Reference, trade, room and location, defect, description, action required, severity, photo link, and columns for the developer's response and fixed-on date.

How do I track the developer's answers?

Record for each snag whether the developer accepted it, disputed it (with a reason) or reports it fixed (with a date), next to the snag itself.

How to send a snag list to the developer, grouped by trade

Updated 25 October 2026

A buyer's report is written for the buyer. The developer's handover team needs something different: a list they can split between subcontractors and track to completion.

Group by trade

Handover teams pass work to tiling, painting, joinery, MEP, glazing and civil teams. A list grouped by trade lets each team see only its own items, with the count per trade at the top.

Columns that help

Reference (the same number as the buyer's report)
Trade, room and exact location (or a floor-plan pin)
Defect, description and action required
Severity
Photo link
Developer response and fixed-on date, for the developer to fill in

Send it as a spreadsheet as well as a printout: handover teams usually track snags in Excel.

Track the developer's answers

For each snag the developer usually does one of three things: accepts it, disputes it (with a reason), or reports it fixed (with a date). Keeping those answers next to the snag makes the de-snag faster and gives the buyer a clear record.

In HandoverCheck you can share a no-login link with the developer. Their team marks each snag accepted, disputed or fixed, you see the counts on the inspection, and you get an email when every snag is marked fixed so you can book the de-snag. You can turn a link off at any time.

See a sample developer list by trade.

Questions

Why group a snag list by trade?: Developers hand snags to the teams that fix them, so a list grouped by trade lets each team see its own items and the count per trade.
What columns should a developer snag list have?: Reference, trade, room and location, defect, description, action required, severity, photo link, and columns for the developer's response and fixed-on date.
How do I track the developer's answers?: Record for each snag whether the developer accepted it, disputed it (with a reason) or reports it fixed (with a date), next to the snag itself.