Gargi
AtlasWalkthroughChainApp
Atlas›Stage 6 · Handover›M22 · Snag · Handover
M22build

Snag · Handover

Checklist-based digital snagging with auto vendor assignment, photo recording, verification, de-snag, and handover — all one workflow.

What it is

Handover delays at construction sites are driven by snag closure cycles, not by construction completion. Today, snagging is a coordination dance between CM, HPM, and vendors with handoffs that each take days. The module collapses this into one digital workflow: HPM raises snag with photo and criticality; vendor auto-assigned based on WIR history; rectification submitted with root cause and preventive action; CM verifies; HPM approves de-snag; handover scheduled when star snags closed.

Inputs
Triggers
  • ·Tower nearing OC milestone — pre-handover walkthrough
  • ·Pre-snag inspection by inhouse team
  • ·Customer joint snag inspection
  • ·Snag closure submitted by vendor or in-house team
  • ·Handover document pack ready
  • ·Possession-date scheduling
Data reads
  • ·Drawing and spec from M07 and M09
  • ·WIR history from M19 (for known issue areas, predicted defects by vendor and trade)
  • ·Customer record from M24
  • ·OC and statutory compliance from M04
Artefacts consumed
  • ·Snag list per unit with photo and location
  • ·Vendor closure evidence
  • ·Inspection request -WIR
  • ·Joint inspection sign-offs
  • ·Handover document pack
Tools & Techniques
Methods
  • ·Predictive snag list from quality patterns and WIR history
  • ·Mobile snag capture with photo, location, severity, responsible trade
  • ·Snag closure workflow with evidence
  • ·Joint customer inspection (Unit Visit UV)with structured sign-off
  • ·Handover pack auto-assembly (warranties, manuals, certificates, keys)
  • ·Possession-date readiness check
Policies
  • ·Handover SoP with snag taxonomy and severity + Possession SoP
  • ·Critical snag SoP — what blocks handover
  • ·Handover document pack SoP
  • ·Possession-date readiness SoP (PDL + 45 days)
Decision rules
  • ·Critical snag must close before handover
  • ·Snag severity drives closure SLA (critical, major, minor)
  • ·Snag responsible trade auto-identified from drawing and WIR history
  • ·Possession scheduled only after OC / part OC plus handover-pack readiness
Outputs
Artefacts produced
  • ·Snag list per unit with status
  • ·Closure evidence record
  • ·Joint inspection sign-off
  • ·Handover document pack (warranties, manuals, certificates, keys)
  • ·Possession scheduling record
Data writes
  • ·Unit status updated through snag → closure → handover lifecycle
  • ·Customer record updated on possession
  • ·Vendor performance updated on snag closure quality
Downstream triggers
  • ·Possession triggers BelleVie provisioning in M24
  • ·Snag patterns feed Vendor 360 in M13
  • ·Snag patterns feed quality predictive intelligence in M19
  • ·Handover triggers asset register update in M23
Stakeholders
  • CMSnagging schedule, vendor assignment, verification
  • HPMUnit-by-unit snagging, de-snag approval, handover acceptance
  • VendorRectification with evidence
  • CustomerReceives unit handover
The flow
  1. 01Snagging schedule (CM → HPM)
  2. 02Unit snagging with checklist and photo evidence
  3. 03Vendor auto-assignment from WIR history
  4. 04Snag rectification with root cause and preventive action
  5. 05Verification (verified / reject)
  6. 06De-snagging schedule when threshold reached
  7. 07De-snag approval by HPM
  8. 08Handover schedule when non-star snags closed
  9. 09Unit handover to HPM
State change
Before

Snagging cycle is 6–12 weeks per tower with handoff delays at every step.

After

Snagging cycle compresses; auto-assignment and digital verification remove handoff lag.

Real-world example

BA59 Iris G U104 — HPM raises flooring snag (hollow dado tiles) 14 May 10:02 AM. Auto-assigned to Sterling (per WIR history) — also flagged in Vendor 360 from quality pattern. Rectification submitted 14 May 11:46 AM with root cause "subfloor moisture" and preventive action. CM verifies; closed at 12:08 PM. Portfolio: 1,124 ready · 593 open · 130 critical.

Artefacts
  • ·Snagging schedule
  • ·Unit snag checklist with photos
  • ·Vendor assignment log
  • ·Rectification records
  • ·Verification log
  • ·De-snag approval
  • ·Handover acceptance record
Pain today

Snagging is a coordination dance. CM raises schedule; HPM has to be available; vendor has to rectify; verification has to happen. Each handoff has its own delay. Critical snags do not bubble up.

Integrations

No external system integrations — module operates on internal records.