The MEP Snag List at Handover: How to Run It So Defects Actually Close

A handover snag list works when it is a controlled register, not a walk-round with a notebook. Every defect gets a number, a location, a category, an owner and a closing proof; only the person who raised it can close it; and money is held against what is open. Run that way, defects close in weeks. Run loosely, they become disputes in the defect liability period.

What is a snag list, and when does it start?

A snag list records every item that is incomplete, defective or different from the drawings at the point a building or system is offered for handover. It is not the same as commissioning. Commissioning proves that systems work; snagging records where the installation, finish or documentation falls short of the contract.

The common mistake is to start at the end. The Government of India's Manual for Procurement of Works says the owner may carry out a detailed inspection of the commissioned project to ensure no deficiencies remain before taking over, and expects as-built drawings, maintenance manuals and statutory clearances to be handed over with the work. The practical reading for a private project is to snag in stages: concealed work before it is closed up, each floor or plant room as it is completed, and the whole building at final handover. A defect found at ceiling-closure stage costs a few hours; the same defect found after tenant fit-out costs a shutdown.

How should defects be categorised?

Categories decide what blocks handover and what only blocks a payment. Without them, a missing label carries the same weight as a fire pump that does not start. Agree the categories in the contract, not at the walk-round.

The percentages and sums held per category are commercial terms, not code. Whatever you agree, write the rule down: for example, that any category A item stops the taking-over certificate, however small the rest of the list.

How do you run the snagging walk so the list is usable?

1. Walk by discipline and by zone, with drawings. Electrical, HVAC, plumbing and fire fighting each need their own checker, because a plumber rarely notices a missing fire damper.
2. Log on the spot. One line per defect: unique number, drawing reference, room or grid location, discipline, category, a photograph and the clause or drawing it fails. "Fix leakage" is not a defect description; "chilled-water flange, riser 2, level 3, weeping" is.
3. Issue the register within a day. The contractor assigns each item to a named supervisor and commits to a date for it.
4. Close by evidence, not by assertion. The contractor marks an item "ready for re-inspection"; the finder checks it and signs it off. A contractor may not close its own item.
5. Re-inspect on a fixed cycle. A weekly re-inspection, with the register re-issued showing only open items, makes progress visible and prevents items being re-opened later on a different argument.
6. Freeze the list at a cut-off. New items after the cut-off are treated as latent defects under the defect liability period, not as part of the handover list. This protects both sides.

How does the snag list connect to retention and the defect liability period?

The Manual for Procurement of Works describes the usual structure in public works: a performance security, plus a percentage of each running bill held back as retention until final acceptance. According to the Manual, half of the retention is released when the taking-over certificate is issued, and the other half 365 days after the defect liability period ends, or on final payment if that comes first. A defects liability certificate is issued only when the contractor has completed all obligations, and the Manual advises checking that nothing is outstanding before the bank guarantee is released.

That structure is a public-sector convention, and a private contract can set different percentages and periods. The principle carries over: a snag list only has force if payment depends on it. Link the taking-over certificate to category A closure, hold a sum against category B items, and make the final bill conditional on category C documents. Our guides on retention money and final-bill disputes and the defect liability period cover how these disputes arise, and the handover documents article lists what the category C file should contain.

What makes snag lists fail?

• No testing before the walk. Items found by testing are different from items found by eye. Keep the testing and commissioning records alongside the register, so a failed test becomes a category A or B item automatically.
• Disputed scope. If the contractor says an item is "as per drawing" and the owner says otherwise, the contract drawings and approved variations decide. Keep the approved set under document control.
• Tenant or user fit-out mixed with base-build defects. Separate the registers. Damage by a later trade is not the MEP contractor's defect.
• Everything on one day. Snagging a whole building in a day produces a list nobody can close. Stage it.
• No owner-side engineer. Someone with authority has to accept or reject closure. If the owner's representative is absent, the contractor will close its own items.

How Secured Engineers helps

Secured Engineers delivers MEPF under one contract, so the electrical, HVAC, plumbing and fire fighting snag items sit in one register with one responsible team. Design is in-house, and Fire NOC, CEIG and DISCOM net-metering filings are handled in-house, which means category A items tied to approvals are tracked by the same people who file them. We work from offices in Noida (Delhi NCR) and Ludhiana, and have delivered 535+ projects across 18+ states, with 89.77% repeat clients.

If you have a snag list already, we can look at it against the contract drawings and BOQ and say which items belong to which category. Start with the turnkey MEPF contracting page, use the MEPF cost calculator for budgeting a rectification scope, then send the register and drawings on WhatsApp, call +91 70099 85817 or ask for a free proposal.