---
title: "RERA Project Data for Land Deal Site Analysis"
description: "A source-led workflow for using public RERA project records as contextual evidence—without treating them as land-price, title, absorption, or planning proof."
author: "Vignesh Nagarajan"
author_profile: https://proquiro.com/authors/vignesh-nagarajan
date: 2026-04-09
updatedDate: 2026-08-09
category: regulatory
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: [{"title":"The Real Estate (Regulation and Development) Act, 2016","publisher":"India Code","url":"https://www.indiacode.nic.in/handle/123456789/2158","evidence_type":"primary-source","checked_date":"2026-08-09"},{"title":"Tamil Nadu Real Estate Regulatory Authority","publisher":"Tamil Nadu Real Estate Regulatory Authority (TNRERA)","url":"https://rera.tn.gov.in/","evidence_type":"primary-source","checked_date":"2026-08-09"}]
corrections: [{"date":"2026-08-09","summary":"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."}]
tags: ["RERA", "land acquisition", "site analysis", "regulatory data", "due diligence"]
canonical_url: https://proquiro.com/blog/rera-project-data-land-deals-site-analysis
---
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](https://www.indiacode.nic.in/handle/123456789/2158). 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](https://rera.tn.gov.in/). 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

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](/glossary) and [land due diligence checklist](/blog/land-due-diligence-checklist-india) 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](https://www.indiacode.nic.in/handle/123456789/2158) — India Code; primary-source; checked 2026-08-09
- [Tamil Nadu Real Estate Regulatory Authority](https://rera.tn.gov.in/) — Tamil Nadu Real Estate Regulatory Authority (TNRERA); primary-source; checked 2026-08-09

### Updates and corrections

- 2026-08-09: 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.