Builder to Society Handover: A Practical Guide for New RWA Committees

Why the builder handover is a governance decision, not a formality

A newly registered society usually treats the handover from the builder as the last step of moving in — collect the keys to the common areas, get a set of documents, and start running the place. In practice it is closer to a first governance decision than a formality: whatever is verified, recorded, or left unchecked at handover becomes the baseline every future committee, auditor, and resident dispute will be measured against. A defect that goes unrecorded at handover, or a document the builder never handed over, does not go away — it just becomes the incoming committee's problem to prove years later, usually with far less leverage than it had on day one.

This is general guidance on how builder-to-society handover typically works in India. The applicable law — RERA obligations, state cooperative or apartment ownership rules, and the specific remedy of "deemed conveyance" where a builder does not act — varies by state, and the exact process a society should follow needs to be confirmed with a lawyer familiar with the local framework, not assumed from a generic checklist.

What handover legally involves

• Under the Real Estate (Regulation and Development) Act, 2016 (RERA), a developer is generally required to execute a conveyance deed transferring title in the common areas to the association of allottees, and to hand over physical possession of those common areas, within a defined period once the building has an Occupancy Certificate — the exact timeline and process depend on the state's RERA rules
• Where a builder does not initiate or complete this transfer, several states provide a separate legal remedy — commonly referred to as **deemed conveyance** — that lets the society apply through the competent authority to have the conveyance executed without the builder's active cooperation; the availability, procedure, and authority differ by state, and Maharashtra's framework under MOFA is the most established example, not necessarily the model that applies elsewhere
• Handover is not only about title to the land and building — it also covers physical assets (lifts, DG sets, pumps, fire-fighting equipment, STP/WTP plants), statutory approvals, and any deposits or corpus the builder was holding on the society's behalf
• Property tax and utility dues on the building up to the handover date, and on any unsold units the builder continues to hold afterward, are matters the society should get in writing rather than assume are settled

Documents to collect before accepting handover

• Occupancy Certificate (OC) and Completion Certificate for the building
• Sanctioned building plans and any approved deviations, along with the fire NOC and lift/elevator certification
• A schedule of common-area assets being handed over — lifts, pumps, generators, STP/WTP, fire systems — ideally with make, model, and installation date, not just a verbal list
• Defect Liability Period (DLP) terms in writing, so the society knows what construction or equipment defects the builder is still obligated to fix and until when
• Confirmation of the maintenance corpus, sinking fund, or any deposits the builder collected from allottees and is required to transfer to the society
• Written confirmation of the property tax and utility payment status on the building, including any units still unsold and held by the builder
• Warranty documents and AMC contracts already in place for lifts, fire systems, and other common equipment, so the society knows what it is inheriting versus what it needs to arrange itself

Common mistakes new committees make

• Accepting physical possession of common areas informally, without a signed handover document listing what was actually transferred and its condition at the time
• Treating a verbal or email assurance about pending defects as equivalent to a written, dated commitment with a resolution timeline
• Not confirming whether the conveyance deed has actually been executed and registered, and assuming that occupying the building is the same as holding legal title to it
• Letting the builder's original warranty and AMC paperwork for lifts, pumps, and fire equipment get lost in the transition, leaving the society unable to claim under warranties it is still entitled to
• No single committee member or sub-committee owning the handover process end to end, so documents get collected piecemeal and gaps only surface months later when something breaks or a dispute arises

What a defensible handover record should include

• A signed, dated handover document listing every common-area asset transferred, its condition, and any known defects at the time
• The full set of legal and statutory documents — OC, sanctioned plans, fire NOC, conveyance status — stored somewhere the next committee can find without depending on whoever handled the original handover
• A written record of the Defect Liability Period terms and a log of what has been raised with the builder against it, with dates
• Confirmation, in writing, of the corpus, sinking fund, and deposit amounts transferred, reconciled against what allottees were told they had paid
• A clear answer — confirmed with a lawyer, not assumed — on whether the conveyance deed is executed and registered, and what the society's options are if it is not

How MySocietyEntry helps

The handover itself — legal due diligence, conveyance or deemed conveyance proceedings, and negotiating outstanding defects with a builder — needs a lawyer and, where relevant, a structural or MEP consultant, and sits outside what a society operations platform does. Where MySocietyEntry helps is afterward: handover documents, asset schedules, and warranty or AMC paperwork can be stored in one place instead of a founding member's personal drive, corpus and deposit amounts received from the builder can be logged against the accounting module's opening balances so they are traceable from day one, and any AMC contracts already in place for lifts, pumps, or fire systems can sit alongside every AMC the society signs afterward — so the committee is working from one continuous record instead of two separate ones split at the handover date.

Final takeaway

A builder handover that is accepted informally, on the strength of a walkthrough and a verbal assurance, tends to resurface as a dispute years later — over a missing asset, an unresolved defect, or a conveyance that was never actually completed. A committee that insists on a written, itemized handover, confirms the legal status of the conveyance, and keeps the resulting documents somewhere the next committee can find them is protecting every resident who moves in after it, not just the founding group signing off on day one.