Mandatory front/rear/side setbacks and the resulting buildable footprint, from plot dimensions and authority — with a plan diagram. Covers Delhi (DDA), Gurugram and Noida with cited numbers; Delhi (MCD) and Greater Noida are shown honestly as “read this off your local bylaw”.
Front
3 m
Rear
0 m
Side 1
0 m
Side 2
0 m
Source: DDA Handbook 2021, p.3
Max ground-floor footprint
1,350 sq ft
Binding constraint: ground coverage — the smaller of the setback-geometry footprint (1,505 sq ft) and the ground-coverage cap of 75% (1,350 sq ft).
Setbacks are looked up from the same cited bylaw table as the FSI calculator, indexed to plot area for Delhi (DDA), Gurugram and Noida.
The geometric buildable footprint is plot width minus the two side setbacks, times plot depth minus the front and rear setbacks — the rectangle physically left after every mandatory margin is subtracted.
The ground coverage cap is a separate, independent constraint — a percentage of total plot area the footprint may occupy on any floor, regardless of shape.
The actual maximum footprint is the smaller of the two — a plot can satisfy the geometry and still fail the coverage cap, or vice versa, so this calculator checks both and reports which one binds.
A setback is the open margin measured inward from each plot boundary that must be left clear of construction, mandated for light, ventilation, fire access and privacy between adjacent buildings. It's set by the local building authority and usually scales with plot size.
Two independent constraints apply: the geometric footprint left after subtracting every setback from the plot dimensions, and the ground coverage cap (a percentage of plot area) set separately by the same bylaw. The actual maximum footprint is whichever constraint is tighter — you can't exceed either one.
For Delhi (DDA), Gurugram and Noida, setbacks are indexed to plot size, not road width — road width only affects Delhi DDA's height formula, not shown on this page. The calculator still collects road width for authorities where a future update may need it.
No. All calculation happens in your browser — nothing is sent to a server or saved.