Possession handover and snag management for builders
Possession handover software runs the final step of a sale: inspecting the unit with the buyer, recording and fixing snags, checking dues are clear and issuing the possession letter. MapBhoomi uses a checklist per project, turns failed items into snags with photos, priority and an assignee, refuses possession while high-priority snags or dues are open unless a manager overrides with a reason, and generates the possession letter with keys, meter readings and the defect-liability end date.
Handover is the last impression a buyer has of the developer, and often the messiest: snags noted on paper, keys handed over with dues still open, complaints after possession lost on a phone. A recorded handover closes every loose end.
Where the usual way breaks
- Snags are noted on a printed sheet and never closed.
- Possession is given while dues are still outstanding.
- Keys and meter readings handed over are not recorded.
- Buyer complaints after possession have no owner.
How a handover runs
- Start the handover from a registered booking and schedule it; the buyer is told.
- Walk the checklist (doors, flooring, electrical, plumbing, meters and more), each item OK, issue or not applicable.
- Issues become snags with photos, priority, assignee and due date; closing one needs a resolution.
- Readiness checks required items, open high-priority snags and dues.
- Hand over: the booking moves to possession, revenue is recognised in the ledger and the possession letter is generated.
After possession
Buyers see their snags in the portal, confirm fixes or reopen them, and can report new issues with photos until the defect-liability period ends.
Who it is for
- Apartment and villa developers handing over units
- CRM teams running possession
- Site and quality teams closing snags
- Developers with a defect-liability period to honour
One handover, checklist to keys
- Handover scheduled. Sales team: Handover · Sat 11:00 (From the registered booking). Buyer: Handover date set (Sat 11:00 · Tower B).
- Checklist walked with buyer. Site team: 14 items checked (2 issues found). Buyer: Walked the flat (Doors, floors, meters).
- Snags assigned and closed. Site team: Snag · bathroom tile cracked (High · closed with resolution). Buyer: Confirmed the fix (In the buyer portal).
- Dues checked. Accounts: Dues ₹ 0 (Readiness check passed).
- Keys handed over. Buyer: Possession letter (Keys and meter readings). Accounts: Revenue recognised (At possession).
- Issue after moving in. Buyer: Reported a leak, with photo (Within defect liability). Site team: New snag · kitchen sink (Assigned, with a due date).
Modules it uses
What is a snag list?
A list of defects found when inspecting a finished unit before handover, each to be fixed and confirmed.
Can possession be given with dues open?
Only if a member with handover rights records an override with a reason; the amount is logged.
Can buyers report defects after moving in?
Yes, from the buyer portal, until the defect-liability period ends.
Can each project have its own checklist?
Yes. A company default is created on first use, and each project can override it.