PropVision

How PropVision scores a project

Every score on this site is computed by one published formula from data we hold on file. This page is that formula. Last updated 12 September 2026.

This is our opinion, not a user rating. No buyer, resident or visitor votes on it. It is a single editorial assessment produced from filed and measured data, which is why you will not see it as a star rating in Google search results — we do not publish review markup for it, because presenting one editorial score as if it were an aggregate of many would misrepresent what it is.

The five measures

Each is scored 0–10, then combined with these weights:

MeasureWeightWhat it asks
Price vs locality30%Is it fairly priced against its own micro-market?
Legal & approvals25%Are the statutory approvals actually in hand?
Livability20%Green cover, noise, convenience, metro distance
Space efficiency15%What you receive for the area you pay for
Delivery confidence10%How much construction risk is already retired

Price vs locality (30%)

The project's average rate against the locality benchmark. Cheap is not automatically good — a deep discount usually signals a problem — so the curve peaks at fair value rather than at the bottom.

Premium over locality averageScore
25% or more below5.0
10–25% below9.0
Within 5% of the average10.0
5–15% above8.0
15–30% above6.0
30–50% above4.0
More than 50% above2.0

Legal & approvals (25%)

The share of statutory approvals we hold a status for that are actually cleared, across ten types: khata, development plan, building plan, water NOC, pollution board NOC, height NOC, fire NOC, legal opinion, development rights and city development plan.

Scored only over approvals we have a status for. A project missing fire-NOC data is not the same as a project whose fire NOC was refused, and is not scored as if it were. Fewer than four known approvals and this measure is dropped entirely.

Livability (20%)

The mean of whichever of these we hold: green cover, a convenience score, a composite noise score (inverted — quieter scores higher), and distance to the nearest metro station — under 1 km scores 10, 1–3 km 8.5, 3–5 km 7.0, 5–10 km 5.0, beyond that 3.0.

Space efficiency (15%)

The mean of whichever we hold: carpet-to-saleable efficiency (75%+ scores 10, under 55% scores 3), units per acre (30 or fewer scores 10, over 150 scores 1.5) and open area percentage (70%+ scores 10, under 30% scores 4).

Delivery confidence (10%)

Sale status (ready to move 10, under construction 6.5, pre-launch 4.0), how far out possession is (this year 10, falling to 4.0 beyond three years), and the project's Google rating where one exists.

Missing data is never counted as a bad score

If we hold no data for a measure, that measure is excluded and the remaining weights are rebalanced across what is left. A project with no livability data is not given a zero — it is scored on the other four and the result is stated as being out of however many measures applied.

If the measures we can score account for less than 60% of the total weight, no score is published for that project at all. A rating nobody can stand behind is worse than no rating.

Where the data comes from

MeasureSource
PriceProject and locality rates in the PropVision property database
LegalApproval documents on file, most linked directly on the project page
LivabilityAir-quality, noise and distance measurements per project location
SpaceConfiguration-level carpet and saleable areas as published by the builder
DeliveryFiled possession dates, sale status, and Google ratings

What the score does not tell you

It does not account for construction quality, the builder's delivery history on past projects, litigation, or title. It is computed from what is on file, and what is on file is not everything that matters. Treat it as one input, read the page it sits on, and verify the RERA record before any payment.