An Occupancy Certificate isn’t the finish line.
A handover ceremony makes a project look finished. The keys change hands, the OC is framed on a wall, and everyone assumes the builder’s job is done. But “occupied” and “complete” are not the same thing in the eyes of the law — and a recent Karnataka RERA order spells out, in plain directions, exactly what a developer still owes buyers — including forming an Association of Apartment Owners — after the Occupancy Certificate is issued. At the heart of it sits one idea: before the common areas can be lawfully handed over, they must be inspected, audited and rectified.
The case in brief
An apartment project in Bengaluru had its Occupancy Certificate issued in August 2021, and flats were sold and occupied. A buyer approached RERA because, despite completion and occupation:
- no Association of Apartment Owners had been formed,
- no Deed of Declaration had been executed,
- the common areas had not been handed over, and
- the khata and electricity connection had not been transferred into his name, though his sale deed required it.
The two sides then turned on each other. The developer said it was willing to form the association and had begun the process, but blamed the landowner for obstructing a meeting and refusing to cooperate — and argued that several issues were already pending before an Arbitral Tribunal. The landowner countered that the project was never genuinely finished, relying on chartered engineer reports flagging pending and defective works, and asked that the defects be fixed first.
The deficiencies cited were not cosmetic. They spanned fire safety, solar lighting and heating, the gas line, CCTV, rainwater harvesting, terrace waterproofing, screed cracks and seepage affecting the flats below, borewell and water storage, BWSSB and individual water-meter provisioning, grill safety, and khata bifurcation — with rectification estimated at ₹54 lakh or more, and a warning that further latent defects could surface on detailed inspection. The landowner also sought a penalty against the developer under Section 61, citing alleged breaches of Sections 14(1), 11(4)(a), 11(4)(b), 11(4)(d), 11(4)(e) and 17.
Why the Authority ruled this way
The order isn’t just a list of instructions — it rests on a few principles worth understanding:
- An OC doesn’t end the developer’s duties. Merely because an Occupancy Certificate has been issued, a promoter cannot be absolved of continuing statutory and contractual obligations — especially where stakeholders raise genuine concerns about common-area deficiencies, infrastructure and safety.
- But the association can’t wait forever. Equally, forming the association cannot be postponed indefinitely just because quality and rectification disputes are pending between the developer and landowner (including in arbitration). Hence the balanced approach: form the association on a clock, while inspecting and fixing essential defects.
- These duties are statutory, not optional. Section 11(4)(e) casts a duty on the promoter to enable formation of the owners’ association, and Section 17 requires the promoter to hand over the necessary documents and the common areas to that association. Both are mandatory.
- Defect liability survives the OC. Under Section 14(3), the promoter’s liability for structural defects and defects in workmanship, quality or services continues for the prescribed period — regardless of the Occupancy Certificate.
- The point of RERA. The Act exists not only to see construction finished, but to secure transparency, accountability and protection for buyers. A delayed association directly hurts owners on maintenance, utilities, khata transfer and the management of common areas.
The Order — what the parties must now do
This is the part that matters. Acting under Section 31 of the RERA Act, the Full Bench — Chairman Rakesh Singh and Member Gurijala Ravindranadha Reddy — partly allowed the complaint and issued the following binding directions.
1. Form the Association of Apartment Owners — within 90 days
The developer and landowner are jointly directed to initiate and complete the lawful formation and registration of the Association of Apartment Owners under the Karnataka Apartment Ownership Act, 1972 and Rules — within 90 days of the order.
2. Execute the Deed of Declaration and hand over records
The developer must execute the necessary Deed of Declaration and hand over all relevant project records to the Association — sanctioned plans, approvals, specifications, drawings, working drawings and common-area documents — in accordance with law.
3. Sort out khata and utilities
The developer shall take responsibility, and the landowner shall cooperate, for bifurcation/transfer of khata and the necessary BESCOM, BWSSB and other utility formalities in favour of eligible buyers (including the complainant), per law and the sale deed.
4. Inspect the common areas before handover — within 60 days
Before final and effective handover, both must ensure a professional inspection, verification and inspection report on essential common-area deficiencies and statutory compliances. The inspection must commence within 60 days of the order. (The full scope is set out in the audit checklist below.)
5. Use mutually agreed experts
The inspection must be carried out by qualified technical experts/engineers mutually agreed by the parties (failing which, as directed by the competent Authority), with the developer fully cooperating and furnishing all records, approvals, drawings and specifications required.
6. Rectify defects at the developer’s own cost
Once pending and defective works are identified, the developer must rectify and complete them at its own cost — within the period set by the inspection report / competent authority or within 90 days of the inspection report — and bear the cost of inspection and re-inspection.
7. Defect liability runs from real handover
The Section 14(3) defect-liability obligations continue in law and are reckoned from the date of lawful and effective handover, after the essential rectification works are completed.
8. Everyone must cooperate
The complainant, the landowner, the other apartment purchasers and all concerned parties must cooperate in the formation of the association, inspection, rectification and handover.
9. Arbitration stays separate
The disputes pending before the Arbitral Tribunal (A.C. No. 152/2024) are to be adjudicated independently on their own merits; this order does not prejudice the parties’ rights and contentions there.
10. Penalties left open
On penal consequences under Section 61 and other provisions, liberty is reserved to consider them separately upon determination of any non-compliance in future proceedings.
11. No hiding behind the OC
The developer shall not evade or dilute its statutory obligations on common areas, infrastructure, safety and project compliances by relying solely on the Occupancy Certificate or completion documents.
Order passed by the K-RERA Full Bench — Rakesh Singh, Chairman, and Gurijala Ravindranadha Reddy, Member.
The inspection the order requires
The order’s central safeguard is that handover cannot be an empty formality. Before the common areas pass to the association, a structured inspection has to take place — on a clock, by qualified people, at the developer’s cost. (An independent RWA handover audit is built to document exactly this.) In practical terms:
- Timing — the inspection must begin within 60 days of the order, before any final and effective handover.
- Who carries it out — qualified technical experts/engineers, mutually agreed by the parties; if they can’t agree, as directed by the competent Authority.
- Cooperation — the developer must furnish all records, approvals, drawings, working drawings and specifications needed for the inspection.
- The output — a verification and inspection report documenting essential common-area deficiencies and statutory compliances, expressly including latent and patent defects.
- Rectification — defects are fixed at the developer’s own cost, within the report’s timeline or within 90 days of it; the developer also bears the cost of inspection and re-inspection.
- The defect-liability clock — the Section 14(3) period starts only from the lawful and effective handover after rectification, not from the OC.
The common-area audit checklist
The order names the systems an inspection must cover. Read together, they amount to a full common-area audit — and the same system-by-system review is what a committee should run periodically, not just once at handover:
- Fire safety systems — detection, suppression, signage and access
- Water supply, borewell, water storage and rainwater harvesting — sources, tanks, pumps and RWH provisioning
- Terrace, seepage and waterproofing — including seepage affecting the flats below
- Plumbing and electrical systems — distribution, metering and safety
- Structural and civil defects, if any — cracks, screed failures, structural concerns
- Utility and infrastructure compliances — BESCOM, BWSSB, water meters, gas line, CCTV
- Other deficiencies affecting safety, habitability and lawful enjoyment — including latent and patent defects
Ticking through these at handover is the legal minimum. Running the same audit on a regular cycle is how a community catches problems while they’re still cheap to fix.
What this means for you
Homebuyers: Possession and an OC do not end the builder’s duties. You have an enforceable right to a registered association, handover of common areas and documents, and rectification of genuine defects — on firm, RERA-set deadlines.
Developers: Completion on paper isn’t completion in law. Section 14(3) liability outlives the OC, and the cost of fixing real deficiencies — plus the inspection — can land on you.
Landowners in joint-development arrangements: Cooperation on association formation, khata and utilities is expected from you too, and a separate arbitration won’t stall buyers’ statutory rights.
A step-by-step guide for committees
For an RWA management committee, the hard part is knowing exactly what to demand, document and verify at each stage of a handover — the legal records, the infrastructure and fire-safety audits, the maintenance schedules and everything in between. Nemmadi’s RWA HOTO Handbook walks committees through the full handover-takeover process, so nothing critical slips through when a project is signed over.
