RERA’s transparency promise is working unevenly, not universally

The promise was not a brochure promise

The Real Estate (Regulation and Development) Act was framed as a market-cleaning law: registration, public project details, and continuing promoter updates were meant to reduce information asymmetry before a buyer signs a cheque. The Act’s official text is available through India Code at https://www.indiacode.nic.in/handle/123456789/2158.

That matters because a home is not a repeat purchase. A buyer cannot diversify across five apartments. The regulator’s job is therefore not only to host a registration certificate. It is to make the project legible through its life: what was promised, when the registration expires, and whether construction progress is being reported quarter after quarter.

Quietlist’s read of the official H-RERA and K-RERA registers shows the central finding clearly: the policy is strongest where quarterly filings are a visible habit, and weakest where the buyer must assemble the picture from static fields.

The strongest signal is quarterly progress

Quarterly progress reports are the heart of the continuing-disclosure promise. A registration page tells the buyer what was approved. QPRs tell the buyer whether the build is moving.

On that test, Gurugram stands apart. In the H-RERA register, 869 of 1,032 registered projects have at least one QPR filing in Quietlist’s read. That is 84.2% of registered projects, with 6,678 filings running from 2018 to 2026.

Bengaluru is materially weaker on the same test. In the K-RERA register, 1,986 of 9,441 registered projects have at least one QPR filing. That is 21.0%, with 3,521 filings running from 2025 to 2026.

The two registers are not merely different in size. They differ in the buyer’s ability to see the project as a moving obligation rather than a one-time registration event.

The Noida line is an opacity finding, not a compliance verdict. UP-RERA’s public project pages expose registration details and document catalogues, but the equivalent quarter-by-quarter QPR trail is not visible in the same public register view; UP-RERA’s site is at https://www.up-rera.in/.

Static disclosure also has gaps

The second test is baseline disclosure: does the register give the buyer enough core information at booking?

Here Bengaluru does better than its QPR score suggests. K-RERA exposes declared project cost for 8,525 of 9,441 registered projects, or 90.3%. It exposes official unit count for 4,576 projects, or 48.5%. It exposes registration expiry for 4,669 projects, or 49.5%.

Gurugram is the reverse shape in this read. H-RERA exposes registration expiry for every one of the 1,032 projects counted. But the same register view does not provide comparable unit-count and declared-cost fields in the structured project table used for this comparison. H-RERA still wins on the live-progress test because QPR depth is the more buyer-useful disclosure once construction has started.

Noida is clear on expiry. UP-RERA exposes registration expiry for all 1,432 projects counted. But unit count, declared project cost, and QPR visibility are not present in the same structured comparison.

That split is the policy story. RERA did not create one national disclosure experience. It created a legal architecture that each state regulator has implemented with different public-data habits.

Why this matters before booking

A buyer does not need every regulator to publish identical screens. But the buyer does need the same practical answer: what is this project, what was approved, when does the registration run out, and what has changed since launch?

The H-RERA pattern gives a buyer a stronger time-series view. The K-RERA pattern gives a stronger cost-field view, but far weaker continuing-progress visibility. UP-RERA gives a project catalogue and expiry visibility, while the public QPR trail remains harder to test from the register itself.

That is why a buyer should not treat “RERA registered” as a full stop. It is only the starting line. The next question is whether the regulator makes the project continuously readable.

For a buyer comparing states, the practical checklist is simple:

Quietlist Research keeps this comparison anchored in official registers; the broader methodology surface sits at /research/.

The verdict buyers should act on

RERA’s transparency promise is being kept best where the public register behaves like a running file, not a certificate drawer. Gurugram’s QPR trail shows that this is possible. Bengaluru’s lower QPR visibility shows that registration alone is not enough. Noida’s public register shows another version of the same problem: important project details exist, but continuing progress is not equally visible as a public time-series.

The institution being judged is not one state office. It is the RERA transparency model. The model has worked where regulators turned disclosure into a continuing public habit. It has fallen short where the buyer still has to infer too much from a static registration page.

For buyers, the conclusion is practical. Do not ask only whether a project is registered. Ask whether the register lets you follow the project after registration. The difference between those two questions is the difference between a compliance label and a usable transparency guarantee.