RERA Registration Check: Step-by-Step Guide for Land Teams

RERA registration checks are framed almost entirely as a homebuyer protection tool — verify before you book, download Form C, confirm the promoter is on record. For land acquisition teams at real estate developers, the verification logic runs differently. You need to know whether a competing developer’s project in your target micro-market is actively progressing (absorbing land supply), or stalled (potentially releasing land back into the market). You need to plan your own project’s RERA registration timeline before committing to land acquisition costs. And you need to understand how much land registered promoters in a corridor have already absorbed before pricing your bid.

This guide covers the six-step process for a complete RERA registration check, the data each step surfaces, and how to build the check into a repeatable team workflow — from initial site assessment through to legal due diligence.

Why Land Acquisition Teams Run RERA Checks

For land acquisition professionals, a RERA check answers three distinct questions that do not appear in any due diligence framework written for homebuyers. First: which developers are actively competing for land in your target corridor, and how far along are their projects? Second: has a competitor’s project stalled, signalling pressure on their land position that might create a distressed sale or joint-venture opportunity? Third: if your team acquires a specific parcel and plans a project above the RERA threshold, what compliance timeline does that create?

The frame matters because the source data is the same but the interpretation is different from a buyer’s. A homebuyer wants to see strong construction progress and a project nearing completion. A land acquisition team wants to see either early-stage projects that confirm micro-market demand before you bid, or stalled projects that suggest a competitor is under financial pressure.

Team use case	What you look for in RERA data	Signal meaning
Competitor micro-market mapping	All project registrations within 2 km of target parcel	Confirms developer density and land already absorbed
Stalled developer identification	Projects with no QPR update and expired completion date	Developer under financial or approval pressure
New acquisition compliance planning	Registration threshold for intended product type	Sets RERA filing timeline and obligations
Pricing intelligence	QPR sales data: units sold vs total units	Demand proxy for that product in the micro-market
Land bank estimation	Sum of registered project land areas by promoter	Total land a competitor has absorbed in the corridor

Which Projects Must Register Under RERA

The Real Estate (Regulation and Development) Act, 2016 mandates that any real-estate project on land exceeding 500 square metres or with more than eight residential or commercial units must register with the state RERA authority before any advertisement, booking, or offer to sell. This threshold applies to new projects launched after each state’s RERA rules came into force, and to ongoing projects that were not completed at that time — those needed to register within three months of the rules taking effect.

Project type	Mandatory registration threshold	Who commonly misses this
Apartment project	More than 8 units OR more than 500 sq.m of land	Small builders launching boutique projects
Plotted layout	More than 8 plots OR more than 500 sq.m of total area	Peri-urban layout developers
Villa or row-house project	More than 8 units OR more than 500 sq.m	Villa developers building in batches of 8-10
Commercial project	More than 500 sq.m of land or more than 8 units	Small office and retail complexes
Mixed-use project	Either residential or commercial threshold triggered	Developers splitting projects to avoid threshold
Ongoing project (pre-RERA)	Not completed before state rules came into force	Older stalled projects launched before RERA

Renovations, roads, and fully self-occupied projects are exempt. Some states also exempt projects by government entities. The critical implication for land acquisition teams: a competing developer with a project on a 2-acre parcel and 40 apartments cannot legally market or accept bookings without RERA registration. If a competitor project in your target area is not registered, that developer is in violation of the Act — which has legal consequences for both their project and their land position.

The Four Categories of Data a RERA Check Returns

A complete RERA registration check returns four categories of data relevant to land acquisition analysis. Registration status confirms whether the project is currently active, expired, under renewal, cancelled, or revoked. Project details cover land area, survey numbers, number of units, sanctioned FSI, and project start and completion dates. Promoter details confirm the legal entity name and the promoter’s compliance record across their other projects. Quarterly Progress Reports track construction stage completion and units sold, filed every quarter by the developer — and visible on the state portal.

Data category	Where it appears	What a land acquisition team does with it
Registration status	Form C, portal search result	Confirms project is legally active; cancelled signals pressure
Land area and survey numbers	Form C, project detail page	Estimates how much land the competitor absorbed and where
Project timeline	Form C, portal page	Infer land deal close date (project start minus 6–12 months)
Promoter details	Form C, promoter tab	Cross-reference against TNREGINET deed search for registered transactions
QPR units sold	Quarterly report	Demand proxy: high sales = healthy micro-market
QPR construction stage	Quarterly report	Stalled construction + overdue completion date = financial pressure

Step 1 — Identify the Right State RERA Portal

RERA is a central Act administered by each state’s own regulatory authority. A project in Tamil Nadu is not visible on MahaRERA; you must search the relevant state portal. Data completeness and search functionality vary significantly across states. Tamil Nadu, Maharashtra, Karnataka, and Gujarat have the most structured data for land acquisition analysis.

For Tamil Nadu, the TN RERA search tool on Proquiro provides a pre-indexed, searchable version of the rera.tn.gov.in data — covering registered buildings, plotted layouts, and agents, with direct Form C links and faster navigation than the state portal’s own interface.

State	RERA Authority	Official portal	Data quality for land teams
Tamil Nadu	TNRERA	rera.tn.gov.in	Good — buildings, layouts, agents indexed
Maharashtra	MahaRERA	maharera.maharashtra.gov.in	Excellent — most complete dataset in India
Karnataka	K-RERA	rera.karnataka.gov.in	Good — updated QPR data available
Telangana	TS-RERA	rera.telangana.gov.in	Moderate — search limited to project name or number
Andhra Pradesh	AP-RERA	rera.ap.gov.in	Moderate
Uttar Pradesh	UP-RERA	up-rera.in	Moderate — large dataset, search can be slow
Gujarat	GujRERA	gujrera.gujarat.gov.in	Good
Rajasthan	RRERA	rera.rajasthan.gov.in	Limited — requires registration number for search

For multi-state land acquisition programs, searches must be run on each state portal separately. The competitor intelligence module aggregates TNRERA data so Tamil Nadu teams can run micro-market RERA sweeps without navigating the state portal for each search.

Step 2 — Choose the Right Search Method

Each state portal offers two to four search methods. The right one depends on whether you know the specific project you are verifying, or you are running a broad sweep of all developer activity in a micro-market. Promoter-name searches are the highest-signal method for land acquisition competitive intelligence — they return all projects registered by a competitor developer in one result set.

Search method	Best use case	Input required	Result type
Search by project name	Verify a specific project a broker mentioned	Project name (exact or partial)	Single project registration record
Search by promoter or builder name	Map all projects by a competitor developer	Company or individual name	All registered projects under that promoter
Search by RERA registration number	Verify a registration number the promoter disclosed	10–16 digit state-format number	Single project registration record
Search by area, taluka, or district	Map all registered projects in a geographic corridor	District or taluka name	All projects in that administrative boundary
Filter by project type	Understand product mix in a corridor	Filter selection (apartments, layouts, commercial)	Filtered list by project type

For Tamil Nadu micro-market mapping, the most effective workflow is: search by district or taluka, note all registration numbers in the target area, then filter by completion date to separate active-build from stalled or expired projects. The Proquiro TN RERA tool returns the full TNRERA dataset in one indexed interface, removing the need for repeated portal searches per sub-area.

Step 3 — Read the Registration Certificate (Form C)

Form C is the official certificate issued by the state RERA authority upon project approval. It carries the registration number, project and promoter details, and the registrar’s signature. Every RERA-registered project in Tamil Nadu has a Form C linked on rera.tn.gov.in. For land acquisition teams, Form C is the starting point — not the end point — of a RERA check. The fields most relevant to acquisition analysis are the land area, survey numbers, project timeline, and promoter identity.

Field in Form C	What to verify	What it signals for land acquisition
Registration number	Format matches state convention	Confirms registration is genuine
Project name and site address	Matches what the promoter has stated	Confirms you have found the right project
Total land area (sq.m)	Cross-reference against broker area claims	Actual parcel size the developer acquired
Survey numbers	Compare against patta and TNREGINET records	Confirms which survey numbers are part of the project
Sanctioned FSI	Matches applicable planning authority norms	Density the developer is targeting — benchmark for your feasibility
Project start date	Typically 6–12 months after land deal close	Infer approximate land acquisition date
Scheduled completion date	Should match QPR timeline	If overdue, the project may be stalled
Promoter name and legal entity	Cross-check against TNREGINET deed search	Verify the actual promoter entity holds the title
Registration validity period	Must be currently active	Expired means project not renewed — compliance issue

When survey numbers appear in Form C, cross-reference them against the Encumbrance Certificate at the relevant Sub-Registrar Office via tnreginet.gov.in to verify the land parcel matches the promoter’s disclosures and to check who held the land before the developer registered the project.

Step 4 — Audit the Quarterly Progress Reports

Quarterly Progress Reports (QPRs) are filed by the developer every quarter and published on the state RERA portal. They disclose units sold to date, the percentage of construction completed for each floor or phase, the amount drawn from the designated escrow account, and the current completion estimate. For land acquisition teams, QPRs are more informative than Form C — they show whether the project is actually progressing or sitting registered without activity.

QPR field	Signal for land acquisition analysis	What inaction in this field signals
Units sold vs total units	Demand in the micro-market	Zero sales with ongoing construction suggests bulk or JV deal
Construction completion percentage	Physical pace of the project	Low completion on an overdue project means stalled
Last QPR filed date	Active compliance by the developer	No QPR for two or more quarters indicates non-compliance
Fund utilisation vs amount raised	Financial management	Large unexplained gap signals possible diversion
Revised completion date	Whether extensions have already been taken	Two or more extensions means prolonged project, likely stressed

A project with no QPR updates for two or more consecutive quarters and an original completion date already passed is the strongest RERA-based indicator of a distressed developer land position. This is the segment most likely to generate joint-venture enquiries or distressed land purchases. The RERA project data guide covers how to convert this QPR analysis into a structured site assessment framework.

Step 5 — Verify the Promoter Registration

RERA requires that each promoter be registered on the state portal, and that registration is separate from the individual project registration. A promoter can appear across multiple projects — searching by promoter name or PAN returns every project filed under that entity. For competitive intelligence, the promoter-level check is more useful than any single project check when you want to map a competitor’s total land exposure in a geography.

Promoter check step	Purpose	How to run it
Search by company name or PAN	Find all registered projects by this developer	Use the promoter search tab on the state RERA portal
Sum land areas across active projects	Estimate total land absorbed by this promoter	Add land areas from Form C for each active project
Check promoter compliance status	Any complaints, proceedings, or revocations?	Review the promoter’s case history tab on the portal
Cross-reference with TNREGINET	Verify registered deeds match disclosed projects	Search the promoter name in the SRO document deed index

Tamil Nadu’s patta and chitta records available via eservices.tn.gov.in are a useful cross-check: if a promoter has RERA-registered a project citing specific survey numbers, those survey numbers should show patta mutation into the promoter’s entity name in the revenue records. A mismatch — RERA registration in one entity’s name, patta in another — is a structural red flag requiring legal investigation.

Step 6 — Check the Land Conversion Status for the Project Parcel

RERA registration does not verify that the underlying land has received a Land Use Conversion (LUC) order for the intended development. The RERA authority accepts the developer’s declaration that approvals are in place but does not independently verify conversion status before issuing registration. Projects on agricultural land without a valid LUC order are registered on the strength of developer declarations — and some are later discovered to lack proper conversion.

For land acquisition teams acquiring parcels adjacent to or within RERA-registered project areas, the land conversion status of the broader corridor matters because it establishes the regulatory precedent for your own project. Tamil Nadu’s land conversion records and FMB records — cross-referenced with TNREGINET — establish the actual conversion status independently of what a RERA Form C shows.

Document	What it confirms	Source in Tamil Nadu
RERA Form C	Developer’s declared approval status	rera.tn.gov.in
LUC order (Collector)	Actual change-of-land-use approval	Collector’s office, cross-checked via revenue records
Patta and chitta	Land classification in revenue records	eservices.tn.gov.in
FMB sketch	Survey boundary and land extent	District Survey Department
DTCP or CMDA layout approval	Planning permission for the project	DTCP or CMDA office — separate from LUC

A clean RERA registration in a corridor does not mean every adjacent parcel is legally convertible. Your own acquisition needs an independent conversion check through the revenue and planning channels, not just a cross-reference against a neighbouring project’s Form C.

RERA Red Flags That Signal Land-Side Risk

Certain RERA registration patterns are operational red flags for land acquisition teams. Not because they make a project dangerous to buy from — that is a homebuyer concern — but because they signal conditions that affect land supply, competitor positioning, and your own project’s regulatory risk.

Red flag	What it signals	Recommended land team action
Registration cancelled or revoked	Developer faces regulatory action; project at risk	Monitor for distressed land sale; do not count as active demand signal
No QPR filed for two or more quarters	Developer non-compliant; project likely stalled	Strong distressed signal; initiate indirect outreach via broker
Completion date extended two or more times	Project significantly delayed; likely under financial pressure	Evaluate joint-venture potential; check if land is encumbered
Form C land area mismatches broker claim	Developer may have sub-divided land or registered a partial project	Re-verify land area with patta and FMB; request full survey chain
Survey numbers absent or mismatched in TNREGINET	Project land may have unresolved title issues	Do not treat as demand signal; verify title independently
Multiple projects by same promoter, all stalled	Developer facing systemic financial stress	High distressed-sale probability; broker introductions warranted
Project registered after construction began	Developer violated RERA by starting before registration	Legal risk to the project; uncertain regulatory outcome
Sanctioned FSI exceeds normal corridor norms	Developer may have contested approvals or excess FSI	Verify with CMDA or DTCP; do not use as comparable for demand analysis

Using RERA as Competitor Land Intelligence

RERA registrations are the most structured, government-verified dataset showing who is developing what, where, and with how much land. For land acquisition teams, the competitive intelligence value exceeds the compliance value on most site assessments. The workflow: map all RERA-registered projects within a defined radius of your target parcel, aggregate land areas by promoter, and cross-reference QPR data to separate active-build from stalled inventory.

Intelligence question	How RERA answers it	Data quality
Who are the active developers in this corridor?	Promoter names on all registrations in the district or taluka	Complete for registered projects
How much land has each developer absorbed?	Sum of registered land areas per promoter	Indicative — does not capture unregistered parcels or pre-RERA projects
Is demand real or speculative?	QPR units-sold data across active projects	Direct from mandatory government disclosures
Which developer is most likely under pressure?	QPR non-compliance combined with expired completion date	Highest-signal filter for distressed land
What product type is selling in this corridor?	Unit-type distribution in Form C and QPR sales data	Direct demand signal for your product planning
What land-to-FSI ratios are competitors using?	Land area from Form C combined with sanctioned FSI	Reveals density benchmarks in the specific zoning

This analysis is manageable manually for corridors with 10–15 registered projects, but labour-intensive for areas with 50 or more registrations. The competitor intelligence module in Proquiro aggregates TNRERA data with SRO transaction records and guideline values so teams can run this as a standard part of site assessment — not a separate portal research task.

What RERA Cannot Tell You About a Land Parcel

RERA registration is a project-level disclosure record, not a title verification record. It confirms what a developer has filed with the regulatory authority and what the authority has accepted. It does not verify that the developer’s title is clean, that the survey numbers are correctly bounded in ground reality, that encumbrances have been released, or that the land has been legally converted for the intended use.

Information gap	Why RERA does not cover it	Where to find it instead
Ownership chain going back 30 years	RERA records submitted documents but does not audit title	TNREGINET registered deed index and SRO document chain
Live mortgages or bank charges	EC is not part of RERA registration	Encumbrance Certificate from TNREGINET
Patta mutation status	Revenue records are separate from RERA	Tamil Nadu eservices patta download
Land use conversion order	RERA accepts developer declarations; does not verify	Collector’s office LUC order; land conversion records
FMB boundary accuracy	RERA records land area in sq.m but not boundary accuracy	FMB and TSLR sketch from the Survey Department
Court attachments not registered at SRO	Lis pendens not reported to RERA	District Civil Court search
Government acquisition notifications	Not visible on RERA	District Collector, Gazette notifications, NHAI alignment maps

A clean RERA registration in a micro-market is a positive demand signal, but it does not replace title due diligence on any specific parcel your team intends to acquire. The document verification workflow covers the additional checks — EC, patta, FMB, LUC — that complete the picture RERA leaves partially open.

Building a RERA Check Workflow for Acquisition Teams

RERA checks are most useful when built into two specific points in the land acquisition pipeline: at initial site assessment for micro-market mapping, and at legal due diligence for competitor verification and your own project’s RERA compliance planning. Running RERA checks ad-hoc, as one-off searches triggered by individual broker introductions, misses the competitive intelligence value of tracking registration patterns over time.

A workflow that acquisition teams can implement without dedicated compliance staff:

1. Initial site assessment. When a parcel enters the pipeline, run a RERA sweep of all registered projects within a 2-km radius. Note each promoter, project size, and QPR status. Assign one of three labels: active-build, stalled, or completed. This gives the competitive land-absorption picture before committing to field visits.

2. Legal due diligence initiation. Update the sweep to catch new registrations since the initial check. Cross-reference Form C survey numbers against TNREGINET EC for competing projects’ parcels. Note any cancellations — these change the competitive supply dynamic and may signal a distressed parcel entering the market.

3. Offer stage compliance planning. Pull your planned project’s RERA registration requirements based on the acquired parcel size and intended unit count. Confirm the registration timeline — RERA requires registration before any marketing or booking, not just before construction. Teams that skip this step routinely discover a 60–90 day registration process sits between land close and first pre-sales.

Workflow stage	RERA check type	Time required	Output
Initial site assessment	Micro-market sweep by district or taluka	30–60 minutes per area	Competitor density map with stalled-project flags
Field visit preparation	Promoter-level check for top active competitors	15–30 minutes per promoter	Field team briefing note
Legal due diligence	Form C and QPR audit for all projects within 500 m	60–90 minutes per check	Deal memo competitive section
Offer preparation	Compliance check: project RERA registration requirements	30 minutes	Registration timeline in deal feasibility model
Ongoing monitoring	Monthly portal sweep for new registrations and cancellations	20–30 minutes per area	Pipeline intelligence update

The task management module in Proquiro allows teams to assign RERA checks as structured tasks with the portal results attached to the parcel record — timestamped and visible to the full team rather than held in one person’s notes or email. When a RERA status changes on a competitor project, the update enters the deal record tied to that parcel, not a WhatsApp message that scrolls off the screen.