Keystone
2026-09-08

Buildable Area Is Not the Same Question as FAR

"What's the FAR on this plot?" answers one question: how much floor area you're allowed, in total. It doesn't answer a different, equally binding question — how much of the plot's *ground* you're allowed to build on, and where. That second question comes down to ground coverage limits, setbacks, and marginal open-space rules, and on a small or irregular plot it can cap what actually gets built well before FAR does.

Three separate constraints, not one

Ground coverage is the percentage of the plot area the building footprint may occupy at ground level. It isn't fixed — most Indian residential bye-laws scale it inversely with plot size, so smaller plots get a higher coverage allowance and larger plots a lower one. Haryana's building code permits roughly 66–75% ground coverage on smaller residential plots, stepping down to around 66% as plot size passes 250 sq. m.; Uttar Pradesh allows coverage as low as 35% in some zones, paired with a correspondingly modest FAR. The specific numbers vary, but the mechanism doesn't: coverage percentage is itself a variable, and it moves with plot size and zone the same way base FSI does.

Setbacks are the mandatory open margins between the building and each plot boundary — front, rear, both sides. These aren't one fixed distance either. Under Mumbai's DCPR 2034, the front setback scales with the width of the road the plot fronts: roughly 3.0 m on a narrow city-suburb road, up to 7.5 m on a highway or a road wider than 52 m, with residential and commercial thresholds differing slightly. Side and rear margins in DCPR 2034 are tied to building height instead of road width — roughly height ÷ 4, with a 3.6 m floor for residential buildings and stepped caps around 12 m, then 16 m, then a flat 20 m above 120 m height. A taller scheme on an otherwise identical plot needs *more* open margin around it, not the same margin — something a flat FAR number gives no hint of.

Marginal open space and height interact directly, and the direction is easy to get backwards. DCPR 2034 caps building height at roughly 1.5 times the sum of road width and front open space provided, unless the front open space exceeds 12.0 m on a road wider than 18.0 m, in which case the height restriction lifts entirely. Give up more ground-floor open space in front of the building, and you can actually *raise* the height ceiling — the opposite of how ground coverage behaves, where more footprint used means less floor-plate flexibility. These two levers pull against each other, and a feasibility pass that only checks FAR sees neither.

Why this binds before FAR does, on some plots

A plot with generous FAR can still be hard to build on if its shape or size makes the required setbacks eat a large share of it. A small or narrow plot loses proportionally more of its area to a fixed-width setback margin than a large one does — the same 3.0 m front setback removes a much bigger share of a 200 sq. m. plot than a 2,000 sq. m. plot. Add a ground-coverage cap that shrinks on larger plots and grows on smaller ones — working, if anything, in the opposite direction — and the constraints don't move together. The buildable footprint on a given plot can end up meaningfully smaller than "plot area × FAR" suggests, regardless of what the FAR figure itself allows.

That's exactly the gap a single "what's the FAR here" answer hides. FAR describes a *volume* of permitted floor area, assuming it can be efficiently stacked. Ground coverage, setbacks, and the height/open-space linkage describe whether that volume can actually be shaped onto that specific plot.

Why this generalizes beyond Mumbai

The specific figures above — Mumbai's road-width setback tiers, its H/4 marginal-open-space rule, Haryana's coverage-by-plot-size table — are local. The 2016 Model Building Bye-Laws set a non-binding national template, but implementation happens state by state: only a subset of India's states and union territories have done a comprehensive bye-law revision since the model was issued, and each defines its own coverage, setback, and height-linkage numbers. The mechanism — coverage tied to plot size, setback tied to road width or building height, height sometimes tied back to open space provided — shows up in most state bye-laws in some form. The numbers themselves don't transfer between states, or even between zones in the same city.

This is not legal or regulatory advice. The figures above illustrate Mumbai DCPR 2034 and Haryana's building code as summarized in publicly available regulatory-reference and planning publications, current as of this writing. Coverage, setback, and height norms get amended over time and vary further by zone, plot classification, and any applicable redevelopment or incentive scheme — verify against the current regulation and sanctioning authority before using these figures for a real filing or investment decision.

What this means for an early feasibility number

A buildable-area estimate that only reports FAR-derived floor area is answering half the question. A useful one also has to:

  1. Check ground coverage against the actual footprint the massing needs — a scheme can sit comfortably under the FAR cap and still fail on footprint.
  2. Derive setbacks from the plot's specific frontage and the scheme's actual height — not one flat margin, since both road width and building height change the required distance.
  3. Flag where height and open-space rules interact, since a scheme that trades footprint for taller massing can shift its own height ceiling — in either direction, depending on how much open space it gives up out front.

That's the difference between a feasibility pass that reports "the FAR fits" and one that reports whether the building actually fits on that ground. On a tight or irregularly shaped plot, that's very often the tighter constraint of the two.

Sources

Retrieved 13-08-2026. Figures illustrate the published mechanisms and are not a substitute for consulting the current regulation.