Some projects have a registration number, an official page and a price list. Others have a name, a hoarding and half a dozen channel partner pages contradicting each other. Purva Hennur is closer to the second. Here is the method we use when there is almost nothing to work with — and what it is reasonable to conclude.
Key takeaways
- Start from the RERA portal, not from a search engine.
- Search the promoter name, not just the project name.
- Check the developer’s own site for what it does and does not list.
- Treat agreement between channel partner pages as one source, not many.
- Where you cannot establish something, say so rather than estimating.
The case: Purva Hennur — no price, no registration number we could find, and not on the developer’s own project list. Our listing page shows exactly how we handled that.
Start at the portal, not the search bar
The instinct is to search the project name. That returns channel partner pages, which is the least reliable source available, and it anchors you to whatever they say.
A better first move is the Karnataka RERA portal, searching the promoter name rather than the project. That returns everything that developer has registered, with real figures attached.
If the project appears, you have extent, block and unit counts, carpet areas and a declared completion date in one place — see how to read a RERA filing.
If it does not appear, that is itself the most important finding about the project, and you now know that everything else you read is unverifiable against a filing.
Either way you have learned more in ten minutes than an hour of reading marketing pages would give you.
Then the developer’s own site, for what is absent
The second source is the developer’s own project list, and you are reading it for absence as much as for content.
A project on the official list gives you authoritative figures for name, location, land area and configuration — the things the developer has a legal exposure on.
A project absent from it tells you that every figure circulating is second-hand. That does not make the project bad; several perfectly sound projects are missing from their developer’s site for ordinary reasons — see what to do when a project is not on the developer’s website.
It does mean you should ask why, and treat the answer as information. “The site update is pending” is checkable; vagueness is not.
While you are there, note what the developer does list nearby. A developer with several current projects in the same corridor is easier to assess, because their other work is comparable.
Reading channel partner pages without being led by them
These are often the only source of pricing and unit detail, so you cannot simply ignore them. The discipline is in how you weight them.
| Signal | What it means |
|---|---|
| Twenty pages agree | One source, copied — not corroboration |
| A page carries a RERA number | Post-registration, so more current |
| A page has no date | Treat every figure on it as undated |
| Figures differ between pages | The differences are the finding |
| A page uses an old project name | Likely pre-registration estimates |
The first row is the trap. Repetition across sites feels like verification and is the opposite — it usually means one early page was copied, errors included.
The fourth row is the most useful. Where pages disagree, the disagreement tells you something about the project’s history, and it is worth noting both figures rather than choosing — see why codename pages carry stale figures.
The other sources worth ten minutes each
Beyond the three above, four more are worth checking and rarely are.
Company disclosures, if the developer is listed. Press releases, investor presentations and results carry project pipelines with values and are written for people who can hold the company to them — see what listed developers tell investors.
Established news coverage of land acquisitions and launches, which is dated and usually accurate on the facts it reports.
The RERA complaints record against the promoter, which tells you where this developer has friction.
The developer’s completed projects, which you can physically visit. On a thinly documented project this is the single strongest evidence available — see visiting a builder’s completed project.
That last one is worth more than all the reading combined, and it is the step almost nobody takes.
There is a fifth source worth remembering on an established corridor: people already living nearby. Residents of a neighbouring project will often know what is being built next door, who is building it and what the hoarding said six months ago.
That is genuinely useful local knowledge and it costs a conversation. It is also the only source that can tell you what the site looked like before the marketing started.
What to conclude, and what to leave open
The hardest discipline is being willing to end with a gap rather than a number.
Where we cannot establish a price, we do not publish one, and we say why. Where we cannot find a registration, we say that too, plainly, at the top rather than in a footnote.
That is not caution for its own sake. A buyer who budgets from an estimate we invented is worse off than one who knows the figure does not exist yet and asks for it in writing.
So the honest output of research on a thinly documented project is usually a short list of established facts, a longer list of reported ones, and a clear statement of what is missing and what would resolve it.
That is a genuinely useful document, and it is the one we wish more people published. A project you cannot yet assess is not a project to avoid — it is one to watch, with a list of things to ask the moment someone will answer.
Set a reminder to check back. Registration, a price list and an official page can all appear within months of a launch, and the project that was unassessable in September may be fully documented by March.
Keep your list of open questions, and run the same method again when it is. The work you did the first time is not wasted — it tells you exactly what changed and what did not.
Common questions
How do I research a project with little information online?
Start at the RERA portal searching the promoter name rather than the project, then check the developer’s own site for what it does and does not list, then read channel partner pages while weighting agreement between them as one source rather than many.
Why search the promoter rather than the project name?
Because searching the project name returns channel partner pages first, which are the least reliable source and anchor you to their figures. Searching the promoter on the RERA portal returns everything registered, with real figures attached.
Is agreement between many websites good evidence?
No. Repetition across sites usually means one early page was copied, errors included. It feels like verification and is the opposite. Where pages disagree, the disagreement is more informative than the consensus.
What sources do most buyers miss?
Company disclosures for listed developers, established news coverage of land deals and launches, the RERA complaints record against the promoter, and most of all the developer’s completed projects, which you can physically visit.
What should I do if I cannot establish a project’s price?
Note that it is not established rather than working from an estimate, and ask for a written price for your configuration. Budgeting from an invented figure is worse than knowing the number does not exist yet.
Researching a project with almost nothing online?
Send us the name and we will run the full method — portal, promoter record, official site, disclosures — and tell you what is established, what is reported and what is missing. No charge.
Related reading
Figures above are drawn from published project information and are indicative. Verify any registration yourself on the Karnataka RERA portal before paying a booking amount.
