RERA Project Data for Land Deal Site Analysis

This guide is for land teams and buyers who want to use public RERA records to understand registered projects near a candidate parcel. RERA records should not be presented as a complete property database, a live land-price feed, or proof of title, absorption, financial health, planning capacity or future demand.

In short

• RERA records are dated project evidence. Save the authority, registration number, promoter, project name, declared location, documents, last visible update, URL and retrieval date.
• There are four defensible uses: confirm a named project exists, compare declared project fields, find questions for planning and title review, and track dated changes.
• A RERA record does not show what a promoter paid for land, their full land bank, sales, permitted FSI for another parcel, or whether anyone wants to sell.
• RERA is project-level evidence. Title, survey, possession, planning and litigation checks on the parcel stay separate.

The legal baseline is the Real Estate (Regulation and Development) Act, 2016. Section 4 sets application disclosures; section 11 addresses promoter functions, including updates on the authority website. State rules, forms, portal design and record completeness affect what a user can actually retrieve.

Build a reproducible project table

For each record, keep only what the source actually exposes, then test every conclusion against another appropriate source.

Field	How to treat it
Registration number and status	Quote the authority’s current label and retrieval date
Promoter identity	Preserve legal name and project-specific entity; do not merge similar names without evidence
Project location and land identifiers	Record as declared; reconcile independently with parcel records
Declared area, buildings or plots	Retain the unit and document context; do not infer buildable area
Approvals and uploaded documents	Record issuer, reference, survey numbers, validity and conditions where visible
Completion date or extension	Distinguish original declaration, revised date, order and current portal field
Periodic update	Record the reporting period and upload date; absence is not automatically proof of non-compliance

For Tamil Nadu, begin with the official TNRERA portal. Other states have separate authorities and search systems. Do not transfer a field definition or availability claim from one portal to another.

Use RERA records in four defensible ways

Confirm that a named project record exists

Search using the project, promoter and registration number. Retain the result and linked certificate or order. Name matching alone can produce false positives; compare the location and legal entity.

Compare declared project characteristics

For a defined date and geography, compare fields that exist consistently across the selected records. Publish the number of usable records, missing fields, retrieval date and inclusion rule. Do not call the result a market census if the portal search or sample is incomplete.

Find questions for planning and title review

Survey numbers, approvals and declared area can identify documents to verify with their issuing authorities. A RERA upload is a lead to the underlying evidence, not a substitute for a current certified record or parcel survey.

Monitor dated changes

Repeat the same search and record what changed. Preserve both observations. A changed completion date, status or uploaded order should be explained using the authority’s record; avoid inventing a cause.

Do not read these claims into a RERA record

Land-acquisition price

Project selling prices, carpet area or projected revenue do not disclose what the promoter paid for land. Residual valuation can be useful internally, but it is sensitive to assumptions about approvals, construction, finance, taxes, sales costs, obligations, timing and required return.

If you publish a residual scenario, state every input, source date, geography and limitation. Do not label it a registered land comparable.

A promoter’s complete land bank

A registration is linked to a declared project. It does not reveal every land interest held by the promoter or group. Aggregation also requires careful entity resolution; similar brands and group companies are not automatically one legal owner.

Absorption or demand

A periodic field or promoter update may provide project-specific information. It does not by itself establish independently verified sales, cancellations, inventory, demand for another product, or future absorption.

Permitted FSI for another parcel

An approval for one site reflects its rules, road width, plot shape, reservations, transfers, premiums, conditions and date. Nearby project FSI is a question prompt, not a guaranteed entitlement for a target parcel.

Distress or availability

Delay, extension or an old update does not prove insolvency, distress, willingness to sell land or recoverability. Use orders, insolvency records, litigation and direct evidence before making such a claim.

Follow eight steps for a safe site analysis

1. Define the decision, geography and observation date.
2. Save the search method and every included registration number.
3. Extract only fields supported by the record.
4. Record missing or conflicting fields instead of estimating them silently.
5. Verify approvals with the issuing planning authority.
6. Verify land identifiers, title, survey, possession and encumbrances separately.
7. Treat valuation, demand and competitor conclusions as hypotheses requiring their own evidence.
8. Recheck records before an investment decision because portal status can change.

The RERA glossary and land due diligence checklist can help structure those separate checks. If evaluating software, confirm its live data sources, permitted use, refresh method, provenance and export before relying on a dashboard.

What this means for you

If you run land acquisition for a developer: save every RERA record with its URL and retrieval date, and label any residual valuation as a scenario, not a comparable. Use nearby projects to raise questions, then answer them with parcel records.

If you are buying a single plot: a registered project nearby shows a declared project, not that land is for sale or what land cost. Do your own title, survey and possession checks on your plot.

If you are selling land: a neighbouring RERA record is project-level evidence, not proof about your land. Title and survey checks on your parcel stay separate.

What this guide does not prove

It provides no national ranking of RERA portals, standard search radius, minimum comparable count, price band, FSI expectation, supply-gap threshold, promoter strategy, or prediction. Those conclusions require a defined dataset and method beyond the public project records cited here.