Snagging Register

Definition

A snagging register is the structured, location-referenced list of defects, incomplete items and cosmetic issues identified during pre-completion inspections. Each entry records what is wrong, where it is, who owns it, when it must be fixed, and how completion is verified. Snagging is distinct from punch listing in some jurisdictions — the punch list being the client's formal defect record and snagging being the contractor's internal precursor — but the mechanics are the same.

Why It Matters

The last five per cent of a project consumes twenty per cent of the budget and half of the reputation. Buildings are judged on their finishes because that is what people see, touch and photograph. A snagging register that is unstructured, uncategorised or unmoderated produces the classic bad handover: five thousand items on a spreadsheet, no priorities, no ownership, and a client who refuses to accept the building. A disciplined register does the opposite — it converts a fog of defects into a controlled programme of works.

Anatomy of a Good Entry

• Unique ID — sequential and never re-used.
• Location — building, level, room, elevation, referenced to the drawing grid.
• Trade — the discipline responsible (plastering, painting, joinery, MEP).
• Description — objective, one sentence: "Chip 30 × 20 mm on architrave, north elevation."
• Category / severity — safety, functional, cosmetic, incomplete.
• Owner — the named subcontractor foreman.
• Target close-out date.
• Verification photograph before and after.
• Sign-off — contractor and, where required, client representative.

Real-World Example

On a 220-room hotel in Dubai, the opening was locked to a specific date because the first fifty guests had non-refundable bookings. Ten days out, the initial snag walk produced 3,400 items across the tower. The commercial manager triaged them into three tiers: safety and functional (must fix pre-opening — 480 items), guest-visible cosmetic (must fix pre-opening in the first 100 rooms only — 1,100 items), and back-of-house cosmetic (fix post-opening under agreed programme — 1,820 items). Each tier had a colour, a shift pattern and a foreman. The hotel opened on time with no safety issues; the remaining cosmetic snags closed over the following six weeks under a signed post-opening agreement. Without the triage, all 3,400 items would have delayed opening by two weeks and cost the operator seven figures in lost bookings.

How to Run It Properly

1. Start snag inspections early — three to four weeks before completion, not the day before.
2. Use a mobile app — location-pinned to the drawing, photograph attached, subcontractor notified automatically.
3. Walk with the subcontractor foreman, not against them. The register is a tool, not a weapon.
4. Categorise on capture — safety, functional, cosmetic, incomplete. Uncategorised registers become impossible to prioritise.
5. Publish daily close-out rates per subcontractor. Visibility drives behaviour.
6. Verify closure with a second inspector, not the person who raised the item.
7. Freeze the register 48 hours before handover to prevent scope drift into the punch list.

Practical Lessons Learned

• Photograph everything. A description without an image is disputed within a week.
• One item, one entry. "Various paint touch-ups Level 4" is not a snag — it is a manifesto.
• Reject vague descriptions. "Poor finish" is not actionable; "Uneven emulsion, east wall, room 412, 300 × 600 mm area" is.
• Track ageing. Items open more than fourteen days are almost always ones nobody has decided who owns.
• Beware the "new snag" trickle. Every inspection reveals more; set a defensible cut-off or the list never closes.

Expert Tips

• Print A3 room-by-room floor plans with snag dots — the subcontractor can then walk one room, fix a cluster, and move on. Efficient beats fair.
• Run a "quality champion" scheme — one nominated tradesperson per trade who joins the snag walk and takes ownership. Peer accountability is faster than commercial pressure.
• Give the client's inspector a live view of the register. Transparency defuses most disputes before they escalate.
• Retain the closed register — it is training material for the next project and evidence for defect-liability discussions.
• Segregate architectural snags from MEP snags in the register; different foremen, different close-out routes.

Common Mistakes

• Snagging started too late, with no time to close before the client walks.
• No category or severity, so every item gets equal weight — and nothing gets prioritised.
• Snags raised anonymously by inspectors who never visited the location, then disputed by the foreman.
• Register split across five spreadsheets and three WhatsApp threads; nobody knows the true open count.
• Closure verified by the same person who raised the item — the checker becomes the checked.

Key Takeaways

• Snagging is a controlled programme, not a fire drill.
• Categorisation on capture is the single highest-leverage discipline.
• Mobile capture with drawing pin and photograph beats spreadsheets by an order of magnitude.
• Second-person verification is what makes closure defensible.
• Freeze the register before handover to draw a clean line between snags and punch list.

Related Concepts

Pairs with Punch List Management, Handover Documentation Pack, Commissioning Witness Testing, and Sectional Completion.