How we collect facts and compute the numbers
Last updated 2026-10-05.
Where the facts come from
Project facts come from the Karnataka RERA register (rera.karnataka.gov.in): registration numbers, the completion date given at registration and any extension, towers, home types and carpet areas, quarterly progress filings, approvals, complaints and completion applications. We read the public pages and keep the date we last checked each one. Every figure on a page links to its source and shows the date it was checked; when something is not in the record, the page says “Not found in public records yet” instead of guessing.
Other sources, each labelled where used: the builder’s own website (price lists), OpenStreetMap (distances, schools, hospitals, metro, lakes), Esri World Imagery Wayback (satellite photos), and for a few researched projects, court and company registers.
Software, AI and review
Pages are generated by software from those records. AI is used for two things only: reading filings into structured fields, and writing the plain-English summary and FAQ answers shown under “Written by AI”, which are generated only from the RERA record on the same page and checked against it by software (numbers that do not match are not published). AI does not invent prices, ratings or reviews; we do not host reviews or star ratings.
Human review: pages are not reviewed one by one by a named editor yet. Facts are checked automatically against the record they come from, and every error reported to us through Report an error is checked and, where we were wrong, corrected.
Construction pace
From the promoter’s quarterly progress filings to RERA. Pace = percent complete in the latest filing ÷ months since the project start date in the record. At that pace, the remaining work points to a finish month, which we compare with the completion date RERA holds. We show it only with at least one filing, a start date, a completion date and 5–99% complete. A project counts as having a computed pace for indexing with two or more filings. Progress percentages are the promoter’s own statements, not inspections.
Builder delivery record
For every registration where the builder has applied to RERA for completion, we compare the application date with the completion date given at registration. “On time” means applied on or before that date; otherwise we show the months late. Occupancy certificates are shown when uploaded to RERA. Complaints against the builder are counted across all its RERA registrations.
RERA complaints
Complaints are the ones Karnataka RERA lists against each registration and against the promoter, with their number, filing date, subject and status. We never show complainants’ names. Zero complaints is shown as “No complaints listed on Karnataka RERA” with the date checked.
Ready to move
A project is “ready to move” when every registration is completed on RERA and at least one has an occupancy certificate or a completion application recorded. Titles say “with OC” only when every listed project has an occupancy certificate.
Price per sq ft
The builder’s published “from” price for a home type ÷ the smallest and largest RERA carpet area for that type, giving a range; the middle of the range is compared with projects within 5 km and in the same locality (median of at least three). Results outside ₹2,000–₹60,000 per sq ft of carpet are dropped as mismatched. Prices carry the date they were seen and are not offers.
All-in cost
Base price plus GST (5% for an under-construction home that is not affordable housing), Karnataka stamp duty (about 5.6%) and registration (2%), and the builder’s listed charges. It is a calculation from the numbers shown, not a quote.
Commute, metro and nearby places
Straight-line distances from the project’s RERA map point to places mapped on OpenStreetMap. Peak-hour drive times are rough estimates: straight line × 1.35 for the road network at 20 km/h. Schools and hospitals are counted within a fixed radius; volunteers map these, so some may be missing.
Lake check
Distance from the RERA map point to the nearest mapped lake or reservoir edge on OpenStreetMap, with the buffer rules that apply (30 m under the Revised Master Plan 2015 after the Supreme Court’s 2019 order). Mapped shorelines can differ from revenue records; check the approved plan.
How we define localities
RERA records a village (for example Samethanahalli), not the market name people search for (Whitefield). We keep the village on every page and also place each project in one of about 65 market localities, grouped into zones. Area localities are circles around a centre until ward and pincode boundaries are loaded; road corridors (Sarjapur Road, Hennur Road, Kanakapura Road…) are a 1.5–1.8 km band along the road. A project inside a road band and an area counts as the road only when its RERA address names the road.
We place a project from its RERA map point when it has a precise one. A point a little outside every locality is labelled “{village}, near {locality}” and is not counted in that locality. Without a usable point we use, in order: our village alias table, the locality most of the village’s other projects fall in, a locality named in the RERA address, and the pincode. Only projects placed from their own map point count as precisely located. The full table and method are in the code (apps/api/src/rera/market-localities.json).
Locality numbers
Counts by status come from RERA. “Median possession delay” is the median number of months between the completion date given at registration and the date RERA holds now (0 when not extended). “Projects with RERA complaints” is the share of projects with at least one complaint listed. Phases registered separately count as one project.
Which pages search engines see
A project page is offered to search engines only when it has its core RERA facts, at least three computed sections with real data (pace, approvals, complaints check, commute and lake check, builder record, price) and a precise map point. A locality needs five such projects; a 2 or 3 BHK list needs five projects with that home type; a ready-to-move list needs three; a builder’s page in one locality needs three projects there from a builder with at least ten in Bengaluru. Other pages stay available to visitors but ask search engines not to index them.
Visit counts and group numbers
We count visits without cookies or personal data. When a page loads, the browser sends one small signal with the type of page, its name, the website you came from (the site name only) and any campaign tag in the link. To count each visitor once per page per day, our server makes a one-way code from your IP address and browser name mixed with a random value that changes every day; the IP address and browser name are never stored, the daily value is deleted the next day, and the codes themselves are deleted within 48 hours. We keep only daily totals. Nothing is counted when your browser sends Do Not Track or Global Privacy Control, and search-engine robots are not counted.
The line “… people viewed this project this week” appears only when at least 10 different visitors opened the page in the last seven days (each day’s visitors added up, so someone who comes back on another day is counted again). Buyers’ group numbers are real sign-ups. “A buyer joined …” shows the time of the latest real sign-up and nothing about the person. Test entries, duplicates and our own team’s sign-ups are left out. The first ten members of a group are called its founding members; that is only a name for the first ten, not a limit.
Known gaps
- The RERA crawl covers Bengaluru Urban and Rural registrations collected so far; counts say “collected so far”.
- Map points are typed by promoters; placeholders such as “13, 77” are ignored.
- Prices are not on RERA; we show only the builder’s own published prices with the date seen.
- Court and consumer cases are researched only for a few projects.
Corrections
If a fact is wrong, tell us with the page address and what the record says: report an error. We correct facts against the public record, never on request alone. See also how we earn.