Closure forecasting.
Current closure velocity measured against the handover date: “at this rate, Zone 4 closes eleven days late” — while there is still time to add resources.
The register of minor defects that decides when the taking-over certificate is issued, when retention is released, and whether the opening date holds.
Last updated
Zepth Core module
93.7%
of UK new-build buyers reported snags in their new home
HBF National New Homes Survey 2025
140–150
snags found per new-build home by professional UK snagging inspections
New Build Inspections / UK snagging data
Untrained buyers spot only 10–30 of them. The gap between what an inspector finds and what an owner notices is the point — the ones nobody sees still come back in the defects period.
5–10%
of contract value typically held as retention — half released at taking-over, half after the defects period closes
Standard retention convention
10 years
decennial liability for structural defects in the UAE, running from completion
UAE Civil Code, Arts. 880–883
Joint contractor–engineer liability, and it cannot be contracted away. Handover records therefore need to outlive the defects liability period by a decade.
A snag list — called a punch list in the US — is the register of minor defects and incomplete items identified as a project approaches handover: the chipped tile, the misaligned door, the unpainted reveal. Individually trivial, collectively they decide when the taking-over certificate is issued, when retention money is released, and whether an opening date holds.
Zepth captures snags in the field with photos and locations, assigns them to the responsible subcontractor, and tracks each one through rectification and verification — with the closure evidence attached to the item. At handover, the register and its photographic proof of closure is the record that gets certificates signed and retention released.
Snags are where the project’s cash and calendar converge. Under FIDIC-style contracts the taking-over certificate — issued once the works are complete except for minor outstanding items — starts the defects liability period, transfers care of the works and insurance risk to the employer, and releases the first half of retention. The second half waits until the defects period closes cleanly.
Open snags sit directly on top of that money: some contracts provide for the employer to withhold up to 150% of the estimated value of open items. A contractor with a bloated, slow-closing snag list is financing the employer’s risk with its own cash, months after the work was “done”.
The volumes are real. UK professional snagging inspections average around 140–150 snags per new-build home, where untrained buyers spot 10–30. Dubai handover inspections report ranges from roughly 30–80 defects per apartment to well over 150 in poorly finished stock, and 300+ in villas — the attributed ranges vary considerably by inspector and by the standard applied, so treat them as directional rather than as a benchmark. The pattern, though, is universal: there are always more snags than anyone expects, and the closing weeks decide whether they are a list or a crisis.
Snag ≠ defect ≠ NCR. A snag is a minor cosmetic or incomplete item caught pre-handover. A defect is a failure against contract or specification, managed post-taking-over under the DLP regime. An NCR is a formal quality record raised during execution, with root cause and disposition. The terms get blurred daily on site; contractually they behave completely differently — and a “snag” that turns out to be systemic, such as cracking traced to missing reinforcement, escalates into NCR territory with different consequences.
Pre-snagging is the contractor’s leverage. The formal list belongs to the certifying authority — the engineer, architect or employer’s agent. But disciplined contractors run their own pre-snagging, and push it down to subcontractors, before ever inviting the consultant. A consultant walking into a pre-snagged building writes a short list; walking into an un-snagged one, they write an encyclopedia — and every item then needs a de-snagging re-inspection cycle to close.
Hotels add a second gate. On hospitality projects the operator’s technical services team inspects against brand standards on top of the consultant’s snagging — room by room, FF&E included. Open snags at that gate don’t just delay a certificate; they slip a soft-opening date while pre-opening payroll burns.
The DLP is a right, not just a liability. During the defects period the contractor has the right to return and remedy at its own cost — almost always cheaper than the employer engaging others and back-charging. And in the UAE the contractual 12 months sits underneath Civil Code decennial liability: contractor and supervising engineer remain jointly liable for ten years for structural defects, a liability that cannot be contracted away. Handover records need to live at least that long.
Weak pre-snagging produces a bloated consultant list, which produces multiple de-snag rounds with an increasingly frustrated consultant. The taking-over certificate is delayed, liquidated-damages exposure continues, the first retention half stays locked, and the start of the defects period is pushed out.
The opposite failure is just as expensive: pressure to occupy forces a certificate with a long “minor items” annex. Occupied units make access for de-snagging miserable, closure velocity collapses, and the second retention half sits hostage a year later.
Every version of the failure is a records problem as much as a work problem — paper lists that cannot say which items are open, who owns them, or what proof of closure exists.
The certificate lands on time — a pre-snagged building gets a short consultant list instead of an encyclopedia, and every avoided item is an avoided re-inspection cycle.
Retention comes back sooner — closure evidence is attached to each item, so the register itself is the argument for releasing the money.
Systemic problems surface as systemic — the same snag repeating across forty units is one root cause, not forty line items.
The record outlives the project — which it has to, where decennial liability runs for ten years.
Raise a snag on mobile with photo, location and trade, assigned to the responsible subcontractor there and then.
Every item has an owner and a date; open, overdue and ageing snags are visible by zone, trade and subcontractor.
Items close only with closure evidence attached — photo, date and verifier — so the register can carry a certificate.
The register and its photographic proof of closure, exportable as the record that gets certificates signed and retention released.
Notified defects, access, remedy and verification tracked through to the performance certificate — the record does not stop at taking-over.
Zone by zone, pushed down to subcontractors with completion dates — weeks before the consultant walks. This is the step that decides how long everything after it takes.
By the certifying authority. Each item logged with location, trade, photo, and responsible party.
Assigned and tracked by subcontractor, with an owner and a date on every item.
The verification re-inspection. Items close only with evidence attached — photo, date, verifier — because at handover the evidence IS the argument.
Issued with de-minimis items carried by agreement into the defects period, money attached to each.
Notified defects logged, access arranged, remedied and verified — through to the performance certificate and the final retention release.
Current closure velocity measured against the handover date: “at this rate, Zone 4 closes eleven days late” — while there is still time to add resources.
The same snag type recurring across units flags a systemic cause — and a candidate NCR — instead of two hundred individual line items.
Open-item ageing by trade, drafted into the weekly report before the meeting starts.
“What stands between us and the taking-over certificate?” — answered from the live register, with the money attached to each open item visible.
The engineer’s judgment stays in charge; the AI removes the latency and the blind spots.
Open, overdue and ageing snags by zone, trade and subcontractor; closure velocity against the handover date; and the handover pack itself — the register with photographic proof of closure on every item, exportable for the certificate and the retention release.
Nothing — it is regional terminology. UK, GCC and Commonwealth markets say snag list; the US says punch list. The workflow is identical.
Formally, the certifying authority: the engineer, architect or employer’s agent. In practice contractors pre-snag internally first, and buyers or developers increasingly commission independent snagging inspectors — especially in residential handovers.
UK professional inspections average roughly 140–150 per new-build home. Dubai inspection firms report anywhere from around 30 to 150+ per apartment depending on finish quality, and more in villas — but these ranges vary considerably by inspector and by the standard applied, so treat them as directional. The operative number is not how many you find; it is how fast they close.
Yes — for minor items that don’t prevent safe use, carried into the defects period by agreement, typically with money withheld against them. Material defects — structural, fire, waterproofing — normally block the certificate.
Read the full answerCommonly half at taking-over and half after the defects period closes. Open snags delay the first half by delaying the certificate, and unresolved defects hold the second half — and the performance certificate — hostage.
Read the full answerLatent defects — those not reasonably discoverable at handover — survive the DLP under general limitation law. In the UAE, decennial liability adds ten years of joint contractor–engineer liability for structural failure, which no contract clause can exclude.
Read the full answerRelated answers
In the guides
Terms defined here
Zepth is the construction project delivery platform — it runs construction, procurement and asset management on one record, and does the work: reading the drawings, reviewing the submittals, matching the invoices and flagging the risks, with a human sign-off on anything consequential.
A short, tailored walkthrough on your real workflow — no generic demo.