RERA Project Data for Land Deal Site Analysis
A source-led workflow for using public RERA project records as contextual evidence—without treating them as land-price, title, absorption, or planning proof.

On this page
Public RERA records can help a land team understand registered projects near a candidate parcel. They 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.
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.
Direct answer
Use RERA records as dated project evidence. Capture the exact authority, registration number, promoter name, project name, declared location, retrieved documents, last update visible, URL and retrieval date. Then test each analytical conclusion against another appropriate source.
Build a reproducible project table
For each record, retain only what the source actually exposes:
| 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.
Four defensible uses
1. 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.
2. 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.
3. Identify 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.
4. 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.
Claims RERA data does not establish
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.
A safe site-analysis workflow
- Define the decision, geography and observation date.
- Save the search method and every included registration number.
- Extract only fields supported by the record.
- Record missing or conflicting fields instead of estimating them silently.
- Verify approvals with the issuing planning authority.
- Verify land identifiers, title, survey, possession and encumbrances separately.
- Treat valuation, demand and competitor conclusions as hypotheses requiring their own evidence.
- 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 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.
Sources and editorial notes
Methodology
This guide reads RERA fields only as dated project disclosures under the Act, requires a source URL and retrieval date for each record, and removes rankings, inferred land banks, price estimates, absorption claims, standard radii, sample thresholds, and product automation claims that lacked reproducible data.
Sources
- The Real Estate (Regulation and Development) Act, 2016 — India CodePrimary source · Checked
- Tamil Nadu Real Estate Regulatory Authority — Tamil Nadu Real Estate Regulatory Authority (TNRERA)Primary source · Checked
Updates and corrections
- Removed unsupported portal rankings, disclosure generalisations, project-to-land-deal timing, competitor land-bank inferences, residual land-price ranges, FSI assumptions, supply-gap thresholds, adoption signals, and automated product claims.
Frequently Asked Questions
What can RERA project records contribute to site analysis?
Can RERA data identify land available for acquisition?
Can RERA data be used to estimate land value?
Is RERA data sufficient for parcel due diligence?
Put RERA data inside a wider parcel check
Work through the Tamil Nadu evidence sequence without treating RERA as title proof.
Open the Tamil Nadu due-diligence guideContinue reading
Agricultural Land Conversion in Tamil Nadu
Agricultural land conversion in Tamil Nadu: 2025 non-planning-area rules, planning-area reclassification, charges, documents, CRZ and due diligence.
Stamp Duty and Registration Charges in Tamil Nadu: 2026 Guide
Current Tamil Nadu stamp duty and registration charges for sale deeds, gifts, settlements, partitions, releases, mortgages, and first-sale homes, with TNREGINET-backed rates and worked examples.
RERA Registration Check: Step-by-Step Guide
How to verify a project against the official state RERA record, preserve the evidence, read updates and orders, and keep parcel due diligence separate.