RERA-compliant lead management: the requirements checklist.
The actionable list. If you're judging whether a system supports RERA compliance, these are the specific things it must do — beyond storing leads — for an Indian real estate developer.
What must a RERA-compliant system do?
A RERA-compliant lead management system must tie every booking to a registered project, generate the buyer-document set from booking data, keep a durable timestamped audit trail, surface each project's periodic filing deadlines, and protect records from silent alteration. The rest of this page expands each into a checkable requirement. For the wider context, start at the RERA-compliant lead management pillar.
The point-by-point requirements
- Register-before-market control. The system should let you associate leads and bookings only with registered projects, since marketing an unregistered project is prohibited in every state.
- Booking-linked document generation. It must generate allotment letters, demand notes, receipts, and possession letters filled from the booking record, so a document never contradicts what the buyer actually booked.
- Durable audit trail. Every lead and booking needs a timestamped history that can't be quietly edited after the fact — the basis for defending against a dispute. See the audit-trail requirements.
- Quarterly-disclosure deadline tracking. The system should surface each project's periodic progress-filing deadline. MahaRERA, for instance, publishes that quarterly and annual project updates are mandatory ↗, and the form and cadence vary by state.
- Project-account discipline support. Because RERA ring-fences buyers' money in a dedicated project account, the system's collection records should reconcile cleanly against it.
- Channel-partner registration capture. Store each partner's RERA registration so you don't transact through an unregistered agent.
The filing workflow itself is covered in automated RERA filing, and common questions in the RERA compliance FAQ.
Remember: the details vary by state
RERA is one central act administered by separate state authorities, so the exact forms, deadlines, and certifications differ — MahaRERA, GujRERA and Karnataka RERA each run their own quarterly regimes, as our state RERA comparison details. A compliant system handles the national constants above and lets you configure the state-specific layer on top. This page is general information, not legal advice; verify the current rules on your state authority's portal.
RERA requirements, answered.
What are the requirements for a RERA-compliant lead management system?
It must tie every booking to a registered project, generate the buyer-document set (allotment letters, demand notes, receipts, possession letters) from booking data, keep a durable timestamped audit trail, surface each project’s periodic filing deadlines, support project-account reconciliation, and store channel partners’ RERA registration. These are the checkable requirements beyond simply storing leads.
Does a RERA-compliant system need to track quarterly filing deadlines?
Yes. RERA requires periodic project-progress disclosures — MahaRERA, for example, publishes that quarterly and annual updates are mandatory — and the form and cadence vary by state. A compliant system should surface each project’s deadline so the recurring filing is not missed across multiple projects at different construction stages.
Why must documents be generated from the booking record?
Because a buyer document that contradicts the buyer’s own booking is a liability under RERA. Generating allotment letters, demand notes, receipts and possession letters from the booking data — rather than retyping them — keeps them consistent with the registered project record and the buyer’s actual booking.
Is meeting these requirements the same as being RERA-compliant?
No. The system makes compliance routine and defensible, but the legal obligation remains the developer’s. Registration, project-account hygiene, accurate disclosure, and legal review are duties the system supports rather than replaces. Treat the checklist as what the software must enable, not as a substitute for compliance itself.
See RERA documents from the booking record.
Published pricing, a 7-day free trial, and onboarding within 24 hours.