Two parcels can sit twenty minutes apart in MMR, one inside the BMC boundary and one across it in Thane, and belong to different regulatory planets. The Mumbai parcel builds under DCPR 2034; the Thane parcel under UDCPR. Same market, same buyers, different arithmetic for what a crore of land buys in sellable area. Developers who model both codes fluently arbitrage that line; everyone else pays tuition. Here is the side-by-side.
Key takeaways
- The boundary is jurisdictional: Greater Mumbai (BMC) runs DCPR 2034; practically everything else in Maharashtra, including Thane and Navi Mumbai, runs UDCPR 2020.
- Both codes layer FSI (base, premium, TDR) but with different base values, slabs and paid-area mechanisms: Mumbai's 35 percent fungible versus UDCPR's up to 60 percent ancillary.
- Redevelopment runs on different chapters entirely: Regulation 33 schemes in Mumbai, UDCPR's own redevelopment provisions elsewhere.
- The applicable code belongs in the land underwriting, not the architect's later problem: it moves the sellable-area denominator of every price you pay.
The comparison, line by line
| Dimension | DCPR 2034 (Greater Mumbai) | UDCPR 2020 (rest of Maharashtra) |
|---|---|---|
| Territory | BMC limits only | Nearly all other planning areas, Pune to Nagpur, Thane to Kolhapur |
| Base residential FSI | 1.33 island city, 1.00 suburbs | Varies by zone and city class; congested vs non-congested split governs |
| Paid layers | Premium FSI (RR-linked) plus TDR, by road-width slab | Premium FSI plus TDR, by road width, zone and jurisdiction |
| The extra-area mechanism | Fungible compensatory area, up to 35 percent, RR-linked premium | Ancillary FSI, up to 60 percent residential (80 non-residential), RR-linked premium |
| Redevelopment chapters | Regulation 33 family: 33(5) MHADA, 33(7) cessed, 33(9) cluster | UDCPR's own redevelopment and TDR provisions; separate rest-of-state TDR tradition |
| Reference guides | Our DCPR 2034 FSI breakdown | Our UDCPR rulebook guide |
The deep dives live in the companion pieces: the Mumbai stack under DCPR 2034 and the UDCPR rulebook. This article is about the choice the market forces: where the same equity builds more.
An analogy: two tax codes, one border
Businesses that operate across a state line learn both tax codes not from curiosity but because the border prices decisions: where to warehouse, where to bill. The BMC boundary is that border for residential development. The codes tax buildable area differently, Mumbai monetises the fungible 35 percent, UDCPR sells the ancillary 60, and the border itself becomes a strategy: the same corpus deployed just outside the DCPR line can buy meaningfully more sellable area, which is part of why the Thane-and-beyond belt absorbs so much MMR development energy.
Where the pro forma actually diverges
The sellable-area denominator. Under UDCPR, full ancillary uptake can push effective buildable area past three on paper in the right slabs; Mumbai's equivalent journey runs through costlier premium-and-TDR assembly plus the capped fungible. Two identical Rs 40 crore parcels are not identical projects.
The premium bill's shape. Both codes price paid layers off ready reckoner rates, but what is bought differs: an RR revision reprices Mumbai's fungible and premium stack and UDCPR's ancillary simultaneously, yet by different percentages of project cost. Rate-freeze years, like FY 2026-27, are cheaper assembly windows under both.
Redevelopment economics. A Mumbai society redevelopment runs the Regulation 33 incentive machinery; a Pune society runs UDCPR's chapters. Consent thresholds, incentive FSI and feasibility all shift at the border, which is why redevelopment specialists cluster by code.
Approval texture. One code, one BMC in Mumbai; UDCPR is administered by dozens of planning authorities whose local implementation varies. The unified text did not unify the counters, and timeline assumptions should not pretend it did.
MMR is the trap geography: parcels near boundaries, in newly merged villages or transition zones, get marketed with the more flattering code's arithmetic. Verify the planning authority and applicable code from the development plan documents themselves before underwriting, because "the broker said UDCPR" has financed several very quiet towers.
Deshmukh's border arithmetic
Deshmukh (our illustrative Nashik land owner) faced the choice as capital, not code: a JV stake in a suburban Mumbai plot against buying outright in Panvel. His advisor ran both pro formas to one number, land cost per sellable square metre after all premiums, and the UDCPR parcel's ancillary math beat the Mumbai parcel's fungible math by enough to survive Panvel's lower realisations. The point is not that UDCPR always wins; it is that the codes only compare honestly at that single number, and the register's absorption data supplies the realisation side of it.
ReraGenie's area consolidated reports pair the code-side arithmetic with the filed reality, what nearby registrations actually built and how fast it sold, on either side of any boundary you are weighing. The Rs 2,999 project analysis prices a specific competitive set.
The one-line summary
One state, two codes, one border: identify the planning authority first, model land cost per sellable metre under the code that actually applies, and let the boundary be an input to the bid, never a surprise after it. On the Mumbai side of that border, the paid layer that moves a pro forma most is the certificate market: TDR in Mumbai.
Evaluating a micro-market or a land parcel?
The ReraGenie project analysis reads every filing in your competitive set: supply, absorption, pricing and promoter records. Rs 2,999 per project, area consolidated reports from Rs 2,999.
See the project analysis