Start Before the Building Is Finished
Snagging is often treated as a single event near the end of a project, which guarantees a long list and a difficult final month. The better approach is progressive: inspect and close work zone by zone as it completes, so that a finished room stays finished rather than accumulating damage from following trades.
Progressive snagging has a second benefit. Patterns emerge early, so a recurring detailing or workmanship problem can be corrected in the remaining areas rather than repeated across the whole building and then rectified everywhere.
The Contractor's List Comes First
A contractor should inspect its own work and close its own defects before inviting the client to inspect. Presenting an unprepared building to a client produces a list dominated by items the contractor already knew about, which wastes everyone's time and erodes confidence.
When the client's inspection then finds relatively few items, the conversation is about quality rather than about competence, and the remaining programme is short and predictable.
Record Items So They Can Actually Be Closed
A defect record that says "paint damage in bedroom" cannot be closed reliably. A useful record identifies the room by its drawing reference, the specific location within it, the nature of the defect, a photograph, the responsible trade, and the date raised.
Whether this is managed on a spreadsheet or in dedicated software matters less than the discipline of one list, one owner per item, and a clear status. Multiple parallel lists held by different parties is the most common reason snagging drags on.
Distinguish genuine defects from incomplete work and from client-requested changes. Conflating the three turns a technical process into a commercial argument.
- Location by drawing reference, not by description
- Photograph attached to every item
- Responsible party and date raised
- Status, date closed, and verification of the closure
Commissioning Is Not Snagging
Mechanical, electrical, and plumbing systems need testing, balancing, and commissioning with documented results, and this is separate from cosmetic snagging. Air balancing, water flow rates, control sequences, fire alarm and life safety verification, and lift commissioning all produce records that form part of handover.
These activities need the building substantially complete and permanent power available. Squeezing them into the final days is how projects hand over with systems that work approximately rather than correctly.
What a Complete Handover Package Contains
Handover is more than access to the building. The client should receive documentation that lets them operate, maintain, and repair what they now own, and it should be organised well enough to be usable years later.
The most commonly missing items are as-built drawings that reflect what was actually installed, warranty documents registered in the client's name, and a schedule of the actual products and finishes used. Without that schedule, a simple repair years later becomes a matching exercise.
- As-built drawings for architecture, structure, and services
- Operation and maintenance manuals with equipment schedules
- Commissioning and test records, including waterproofing tests
- Warranties and guarantees registered to the client
- Schedule of finishes, paint references, and attic stock
- Keys, access credentials, and system passwords handed over formally
Train the People Who Will Operate It
A building full of controls that nobody understands will be operated badly. Handover should include practical training for the household staff, facilities team, or operator covering the cooling system, controls, irrigation, pool plant, generator, and anything else with a mode of operation.
Recording that training, and leaving simple written instructions alongside the formal manuals, prevents a great deal of avoidable service calls in the first year.
The Defects Period Is Not a Second Snagging Round
After handover, an agreed period covers defects that emerge in normal use. It exists for latent issues, not as an extension of unfinished work, and treating it as the latter is unfair to both parties.
The process should be defined in the contract: how the client reports an item, the response time expected, and how the retention is released once items are closed. A clear procedure here is what turns the end of a project into a relationship rather than a dispute.
Key takeaways
- Snag progressively by zone rather than in one event at the end.
- The contractor should close its own list before the client inspects.
- One list, one owner per item, photographs on everything.
- Commissioning records are part of handover and need real programme time.
- Train whoever will operate the building, and record that training.