Snagging Process
The systematic identification, logging, and closure of minor defects on a construction project before handover — the industry's most under-appreciated cost centre.
Definition
The snagging process is the systematic walk-through of a completed or near-completed construction project to identify minor defects ("snags") — a paint drip, a scratched door frame, a squeaking hinge, a misaligned floor tile — and record them in a controlled log so that each item is fixed and verified before final handover. It sits between substantial completion and final acceptance, and it is where more late-project time and margin is lost than most owners or contractors admit. A tightly run snagging process saves weeks; a loose one adds months.
How It Works
- Pre-snag walk — the contractor self-inspects and closes obvious defects before inviting the owner in. Skipping this step wastes everyone's time.
- Owner (or independent) snag inspection — a room-by-room, element-by-element inspection producing a numbered snag list, ideally on tablet-based software with photographs and locations pinned to a floor plan.
- Log — every snag has a unique ID, location, description, photograph, responsible trade, target close date, and status (open / in progress / closed / rejected).
- Rectification — trades work through their assigned items, updating status.
- De-snagging inspection — the owner or supervising consultant verifies each item is genuinely closed.
- Sign-off — no residual open snags of any consequence.
Real-World Construction Example
A 240-unit residential tower reached substantial completion on schedule. The contractor's pre-snag walk closed roughly 4,800 items across the tower. The independent snag inspection identified a further 6,200. The initial rectification programme was two weeks. Reality: eight weeks, because 1,900 items were "closed" but the de-snagging inspection re-opened them (paint touched but not blended, silicone patched but not tidied). The developer learned three lessons: (1) always budget for at least two de-snag cycles; (2) require photographic evidence of closure before the trade leaves site; (3) pay for snagging closure inspection as part of the trade contract, not as an owner cost.
Real-World IT / Agile Example
Snagging maps directly to defect triage before release in software delivery. A retail e-commerce migration used a "release snag list" for the final two weeks before go-live: 1,400 defects at start, prioritised into P1/P2/P3, cleared to zero P1 and zero P2 before launch, with 130 P3 items scheduled for the first two post-launch sprints. Same discipline as construction: unique IDs, screenshots, assigned owner, close-out verification by an independent tester. The teams that treat this as an engineering exercise (with SLAs, a shared board, and daily standups) close much faster than teams that treat it as end-of-project heroics.
Categories of Snags
- Aesthetic — paint, sealant, alignment.
- Functional — a door that does not close properly, a socket that reads inverted polarity.
- Compliance — smoke detector coverage, fire-door gaps, accessibility items.
- Latent — defects that appear later (usually treated separately under warranty, not snagging).
Expert Tips
- Snag on tablets, not paper. Cloud snagging apps with GPS/floor-plan pinning cut administrative time by 70% and eliminate lost lists.
- Photograph every open and every close. Photos end most "was it closed properly?" disputes.
- Pay trades for closure, not for identification. Never let the trade that caused the snag also decide it is closed.
- Cluster snags by trade daily. Sending a painter a list of 40 items in one wing is far more efficient than 40 separate call-outs.
- Do not accept "closed pending photograph". If it is not verified, it is not closed.
Common Mistakes
- No pre-snag; the owner sees rough work and loses confidence in the whole project.
- Paper lists; illegible, lost, or "the office has the master copy" excuses.
- One giant list dumped on the site manager with no trade allocation.
- Handing over with hundreds of open snags "to be fixed later" — closure rates plummet the moment the site is demobilised.
- Treating snagging as an administrative exercise instead of a technical quality exercise.
Practical Lessons Learned
- The best predictor of a smooth handover is the ratio of snags identified by the contractor's own pre-snag to those identified by the owner. High ratios (say 3:1 contractor-found:owner-found) predict rapid closure; low ratios predict months of pain.
- Retention held against snag closure is far more powerful than any contractual threat — trades close snags fast when payment depends on it.
- Investing in one senior "snagging coordinator" pays back several-fold. The coordinator's job is not to identify snags — it is to close them.
Key Takeaways
- Snagging is a controlled process, not an end-of-project scramble.
- Tablet-based logging with photographs is now the industry norm; paper lists are obsolete.
- Always hold retention against snag closure.
- Zero open items at final handover — everything else is a warranty issue.
Related Encyclopedia Entries
Related Research Articles, Case Studies & Tools
Frequently Asked Questions
How many snags is 'normal' at handover?
In residential construction, 20–40 items per apartment is typical for a good contractor at first inspection. Commercial fit-outs often see 5–15 per 100 m². Zero is unrealistic; more than 80 per apartment suggests systemic quality problems that need investigation, not just more snagging cycles.Who pays for snagging rectification?
The contractor, always. Snags are pre-completion defects — they are not variations, not additional work, and not chargeable. Trying to charge for snag closure is a red flag.Is a snag the same as a defect?
Snags are the subset of defects identified before final handover. After handover, the same problems become 'defects' under the defect liability period. The terminology matters because the contractual mechanism differs — retention vs warranty call-back.How do I stop the snag list from growing indefinitely?
Freeze the list on a named date, invite one final owner walk to add any missed items, then close the list. Anything found after that date is a defect under the warranty period, not a new snag.Can we hand over with open snags?
Only trivial cosmetic ones, and only with a written agreement listing them and the closure date. Handing over with functional or compliance snags open is a mistake — the owner loses leverage and closure rates collapse.Which snagging software should I use?
The choice matters less than consistent use. Whatever tool syncs offline (poor site Wi-Fi), pins to a floor plan, and produces trade-sorted lists will work. Standardise across your projects rather than picking a new tool each time.How does this apply on a software release?
Same discipline: unique bug IDs, screenshots, assigned engineer, verified closure by an independent tester, SLAs by severity, and a public burn-down chart. The construction snagging process is genuinely a mature template for release-defect management.Which calculators on PMMilestone.org apply to Snagging Process?
For Snagging Process, the most relevant tools on the flagship platform are the Schedule Health Checker and DCMA 14-point quality assessment. They reproduce the formulas referenced in this entry against your own project data.What is a common misconception about Snagging Process?
That quality cost only includes inspection. The cost-of-quality model includes prevention, appraisal, internal failure and external failure — and on capital projects external failure (rework, claims, defect liability) usually dwarfs the others.Which related encyclopedia entries should I read alongside Snagging Process?
Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.How does Dr. Hassan Eliwa's research treat Snagging Process?
Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Snagging Process is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.How is Snagging Process defined on PMMilestone Research & Insights?
The systematic identification, logging, and closure of minor defects on a construction project before handover — the industry's most under-appreciated cost centre. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.
People also ask
Follow-up questions practitioners search for next — each one points to the calculator, template or reference entry that answers it.
Which learning track covers this end-to-end?
Structured tracks from beginner planner to programme controls director. Project Controls Academy ↗
Which book goes deeper than this entry?
Practitioner field handbooks with worked numerical examples. Books & Publications ↗
Which calculator on PMMilestone.org applies here?
The integrated EVM workbook covers most cost-schedule diagnostics. EVM Calculator ↗
Where is this in the glossary?
Quick-lookup definitions across 1,200+ PM terms. PM Glossary on PMMilestone.org ↗
Related Entries
More in Quality
- Letter BBIM Coordination
The disciplined process of combining the 3D models produced by design and trade contractors, detecting conflicts, and resolving them in a virtual environment before steel, ductwork, or pipe is fabricated and installed.
- Letter CConcrete Cube Testing
The sampling, curing and crushing regime that proves a concrete pour actually reached its design strength — and the auditable chain of custody that makes those results defensible.
- Letter JJidoka
The lean principle of 'autonomation' — building quality into the process by empowering people and machines to stop the line the moment a defect is detected, rather than passing the problem downstream.
- Letter NNon-Conformance Report (NCR)
A formal record of work that does not meet the specification, the drawings, or an approved procedure — logged, dispositioned, closed out and trended to expose systemic quality problems.
- Letter NNon-Functional Requirements
The quality attributes a system must exhibit — performance, reliability, security, scalability, accessibility — that often determine success or failure more decisively than functional features.
- Letter QQuality Gate
A formal checkpoint at which work is evaluated against pre-defined criteria and either passed forward, paused for rework, or stopped — preventing defects from flowing into later, more expensive stages.
Further reading on PMMilestone.org
Curated companion resources hosted on the flagship platform, PMMilestone.org.
- For practitioners who want to go deeper, the Learning Tracks.
- Engineers researching this topic typically continue with the Books & Publications.
- A practical companion to this entry is the EVM Calculator.
- Closely related on the flagship platform is the Schedule Health Checker.
- Useful alongside this article is the PMMilestone.org knowledge hub.