RERA is often spoken of as a single national requirement. In practice it's one central act administered by separate authorities in each state, and those authorities are digitising their filing processes at very different speeds. For a developer operating in one state that's manageable; for one expanding across state lines, it's a moving target worth tracking deliberately.
What RERA actually requires
At its core, RERA requires a developer to register every qualifying project with the state authority before marketing or selling it, and then to keep that registration current. Registration means disclosing the project details, the approvals, the land title, the timeline, and the promoter information, and committing to deliver on what's disclosed.
Beyond the initial registration, the ongoing obligations are what catch small developers out: periodic project-progress updates, maintenance of the separate project bank account RERA mandates, and the documentation that has to be generated correctly for buyers at each stage — allotment letters, demand notes, receipts, and possession letters. None of it is individually hard. The volume and the recurrence are what create the burden.
Which states have moved digital
The larger, more active real-estate states run their RERA processes through online portals. Maharashtra's MahaRERA, Gujarat's GUJRERA, and Karnataka's RERA each handle project registration and ongoing filing through their official state portals rather than across a counter. Gujarat's portal, for instance, takes quarterly progress reports through Form-8 online and, from 2025, levies daily fines for delayed quarterly reporting — a sign of how central the digital process has become to compliance.
The practical effect of a digital authority is that registration, updates, and document submission happen through a portal — faster and more trackable, but also less forgiving of incomplete or inconsistent data, because the portal validates as you go. The flip side: a small mismatch between what you file and what you disclosed gets caught by the system, not waved through.
Which still require paper, or a hybrid
Not every state authority is at the same level of digital maturity. Some run hybrid processes — online registration but physical submission of certain documents, or portals incomplete enough that builders fall back to in-person filing for parts of the process. For a developer entering a new state, the only safe assumption is that the process there differs from the one they know, and that "RERA is fully online now" is true in some states and optimistic in others. The practical step is to check the specific authority for the state you're operating in, rather than assuming it matches a neighbour's.
What stays the same across states
For all the variation in how states run their portals, the spine of RERA is national, and a developer who understands the constants can walk into any state already knowing most of what matters.
Registration before marketing is universal. Every qualifying project — broadly, above the size and unit thresholds the law sets — must be registered with the state authority before it's advertised or sold. The threshold details and the portal differ; the principle does not. Marketing an unregistered project is a problem in every state.
The separate project bank account is universal. RERA requires that a defined portion of the money collected from buyers for a project be kept in a dedicated account and used for that project's construction and land cost. The mechanics of certification vary, but the ring-fencing of buyers' money is a national feature, not a state quirk.
Periodic progress disclosure is universal. Every authority requires promoters to keep the project's status updated — construction progress, approvals, timelines — so buyers can see where their project actually stands. The form and frequency differ by state; the obligation to keep the record current does not.
Disclosure-and-deliver is universal. The core bargain of RERA is that you disclose the project honestly at registration — title, approvals, plans, timeline, promoter details — and then deliver on what you disclosed. Deviating from the registered particulars, or carrying false information, exposes a developer everywhere.
The buyer-document trail is universal. Allotment letters, demand notes, receipts, and possession letters tied accurately to each booking are expected across states, and they have to agree with the project record. A document that contradicts a buyer's own booking is a liability in any jurisdiction. The lesson for a developer operating in more than one state is to build the process around these constants and treat the portal differences as the variable layer on top. If your registration discipline, project-account hygiene, progress-update habit, and document generation are solid, adapting to a new state is mostly a matter of learning that state's portal — not relearning RERA.
Quarterly compliance, the recurring burden
The part that quietly consumes time is not registration — it's the ongoing reporting. RERA authorities require periodic updates on project progress, and keeping those filings current across multiple projects, each at a different construction stage, is a recurring administrative load. Miss them and you risk penalties; the obligation doesn't pause because you're busy selling.
This is where the documentation engine matters. The developers who handle RERA well don't treat each filing and each buyer document as a fresh manual task — they generate them from the same project and booking data that already lives in their system, so a demand note or a possession letter is filled correctly from the record rather than retyped. The CRM's job isn't to replace legal review; it's to make sure the document a buyer receives never contradicts their own booking record, and that the recurring filings aren't forgotten.
The cost of getting it wrong
RERA is not a regime where non-compliance is a quiet risk you can carry. The authorities can impose penalties for late or missing filings, for marketing an unregistered project, or for deviating from what was disclosed at registration — and in serious cases, registration itself can be affected. For a small developer, the financial penalty is bad enough; the reputational and timeline damage of a RERA problem surfacing mid-project is worse, because it can stall sales and rattle the buyers who've already booked.
The asymmetry is what makes compliance worth getting right. The cost of staying compliant is mostly administrative discipline — filing on time, generating documents correctly, keeping the project account clean. The cost of failing is open-ended and arrives at the worst moment. That's an easy trade to get on the right side of, and it's almost entirely a matter of process rather than expense. A builder who treats RERA as a recurring operational task, with the data and reminders in one place, rarely faces the downside; one who treats it as something to deal with when a notice arrives eventually deals with a notice.
What a small developer should do
If you can't afford full-time compliance staff — and most builders running a few projects can't — the realistic approach is threefold. First, know the digital status of every state you operate in, and don't assume it matches the one next door. Second, generate buyer documents and filings from your system of record, not from scratch, so they're consistent and fast. Third, put the recurring deadlines somewhere that reminds you, because the penalty for a missed quarterly update is entirely avoidable and entirely your own to bear. It helps to think of RERA compliance as three recurring rhythms rather than one big event. There's the project-start rhythm — register, open the project account, disclose — which happens once per project and is mostly about getting the paperwork right the first time. There's the quarterly rhythm — update progress, keep the filings current — which is where most slippage happens and where a simple reminder system earns its keep. And there's the per-booking rhythm — generate the allotment letter, the demand note, and the receipt correctly from the booking record — which scales with sales and is best handled by generating documents from data rather than retyping them. The builders who get into trouble are rarely the ones who don't understand RERA; they're the ones who treat it reactively, when a deadline or a notice forces it. The fix is unglamorous and entirely within reach: one system that holds the project data, generates the documents, and surfaces the deadlines, so compliance becomes a byproduct of running the business rather than a separate job nobody has time for.
RERA rewards the organised and punishes the improvised — and for a small developer, being organised is mostly a matter of having the data in one place and the reminders switched on. Do that, and RERA becomes a quiet, recurring task in the background of the business rather than the thing that derails a launch.