A landowner's diligence on a developer: reading the counterparty before the JV

The developer arrives with a corporate film, a landmark portfolio and a term sheet. Your parcel will spend the next six years married to whatever is actually behind those three things, and Maharashtra publishes most of the answer. This is the landowner's counterpart to a buyer's project check: six files, mostly free, that decide whether the JDA structure you eventually pick is a partnership or a hostage situation.

Why landowners under-diligence#

A buyer risking Rs 80 lakh runs more checks than most landowners risking an ancestral parcel worth twenty times that. The asymmetry has a reason: buyers fear losing money they saved, while landowners feel they are receiving, not paying. The feeling is wrong. A JDA hands over possession and development control for years; a stalled project returns land encumbered by half-built obligations, occupier claims and litigation. You are extending the largest unsecured credit of your life, and the borrower brought a film.

The six checks#

What the register makes findable, measured#

Two of those six checks are the ones landowners assume are hard, and the register decides both.

Check one is hard for a real reason, and it is countable. The register carries 42,671 distinct promoter profile ids across 55,885 published projects, but only 32,507 distinct promoter names once spelling is normalised. That gap of about ten thousand is the thing your entity map exists to close: a firm that re-registers, restructures or renames picks up a new profile id, so the same trading name arrives on the register more than once with nothing joining the records. The two largest filed names carry 179 and 141 registrations, and the register does not say they are related to each other or to anyone else, because it files no parent company field at all. There is no group above the row. If a developer's film shows twelve towers, the register will not tell you they belong together; you have to assemble that yourself, which is precisely why the first check is first.

Read that chart as a warning about the counterparty in front of you rather than about the market. 86.2 percent of promoter profiles hold exactly one registration, so the statistically ordinary developer on this register has no delivery record at all under the entity you would be signing with. Grouping by name instead of id takes that to 73 percent, which is the same statement with the re-registrations folded in. A single-project entity is not a red flag, since everyone starts somewhere and an SPV per project is normal practice; it is a reason the check has to reach the people behind the entity rather than stopping at it.

Check six is easier than it sounds. JV registrations name the landowner, and they do it often: 25,888 published projects, 46.3 percent, file at least one landowner by name, with the village, taluka and district, and with the development agreement itself attached to the filing. Nearly half the register therefore hands you a list of people who have already done what you are about to do, which is the reference the developer did not choose. The register publishes their names and locations and not their contact details, so this is the start of a search rather than a phone book, and it is a far better start than a reference list.

An analogy: the bank's credit file, inverted#

When this developer sought project finance, a bank built exactly this file: entity mapping, delivery record, account conduct, litigation, and references. The bank, holding security and covenants, still did the work. The landowner, typically holding neither, usually skips it. Run the bank's file, then borrow the bank's other habit: structure follows risk, so a counterparty with a wandering record either improves the structure's protections, monitoring rights, step-in triggers, area-share instead of revenue-share, or does not get the land.

Reading the findings#

Green: deliveries within months of promises across entities, filings punctual for years, disputes settled early, modest leverage, predecessors who would sign again. This developer exists, and commands better terms because the record is their negotiating asset too.

Amber: one late project with honest filings through the delay; growth outpacing systems; complaints that ended in conciliation rather than warrants. Price the amber into the structure: heavier monitoring, milestone-linked possession, corpus protections.

Red: the record-showreel gap; silent quarters on live projects; serial extensions; warrants; charges stacked across group entities; a predecessor who goes quiet on the phone. No split ratio compensates for red, because the downside is not a worse deal, it is your parcel inside a stalled registration's legal machinery.

Deshmukh's shortcut (illustrative, as ever) is worth stealing: before his Nashik JV, he asked each bidding developer for the registration numbers of their last three completed projects and their current ones, nothing else. One sent them within the hour; one sent a brochure instead; one explained the delivered projects were "group projects" under other entities. The file had sorted itself before he opened a portal.

Where to run the free half#

Checks two, three and four are reading, and the reading material is public. Every covered project's filing is free on ReraGenie: registration status, the promised completion date and every extension against it, construction progress quarter by quarter, disclosed complaints and litigation, and the promoter's other registrations with a delivery bar. The developer pages collect those registrations per promoter, which is the delivery table in check two most of the way built, subject to the entity caveat above: a developer page is one filed name, so a group operating under several still needs assembling by hand.

Checks one and five are where the work actually sits. Entity mapping is manual because no filing joins the rows, and the corporate layer is MCA and NCLT rather than RERA.

The assembled version of all six is the Rs 2,999 project analysis: one registration joined to the whole corpus, the promoter's concurrent commitments, the micro-market's absorption cross-section, the district's slip and filing-gap distributions, and the certifier footprint. For a landowner the concurrency figure is usually the one that matters most, because a developer carrying six live obligations is pricing your parcel with the same attention they are giving the other five. Your land took generations to hold; the counterparty file takes a week.

The one-line summary#

Map the entities, table the deliveries, read the filings, pattern the disputes, run the corporate layer and call the last landowner: six checks, mostly free, before your parcel marries a record that Maharashtra already published.

Methodology and sources#

• Promoter profile counts, name normalisation and the registration-count distribution: ReraGenie analysis of 55,885 published MahaRERA projects, as updated on 17 September 2026. Names are normalised by stripping honorifics and legal forms before counting, which is why 42,671 profile ids reduce to 32,507 names.
• Landowner disclosure: 25,889 published projects file a non-empty landowner block and 25,888 of those name at least one owner, 46.3 percent of the register, with village, taluka and district and the filed development agreement attached.
• MahaRERA files no parent-company field, so no figure here groups entities into a corporate group. Any such grouping in your own file is your inference and should be recorded as one.
• The corporate and insolvency checks sit outside RERA: company filings and registered charges at the Ministry of Corporate Affairs, insolvency proceedings at the NCLT and the IBBI.
• Landowner contact details are not published. MahaRERA files landowner names and locations in clear and holds their contact fields encrypted, so a predecessor is identifiable and not directly reachable from the filing.