Development Efficiency: The Path from Permitted FSI to Saleable Area

Direct answer: Development efficiency is the proportion of the area you construct that you can actually sell. It is decided by floor-plate geometry, core sizing, service planning, setbacks and parking — not by the planning index. Define it as carpet area ÷ gross built-up area, set it as an explicit assumption before you price land, and re-test it against the architect's first plate.

The definitions to fix before arguing

• Gross built-up area (GBA) — everything constructed, including parking, services, refuge and non-chargeable areas. This is the cost base.
• Countable FSI area — the portion consuming the index.
• Carpet area — usable area within unit walls. It is the statutory disclosure basis for sale in India: the Real Estate (Regulation and Development) Act, 2016 defines "carpet area" at section 2(k) as the net usable floor area of an apartment, excluding the area covered by external walls, areas under services shafts, exclusive balcony or verandah and exclusive open terrace, but including the area covered by internal partition walls. State RERA rules apply the same definition; confirm the applicable state rules for measurement and disclosure practice.
• Saleable area — carpet plus market-accepted loading.
• Efficiency (design) — carpet ÷ GBA.
• Efficiency (planning) — carpet ÷ countable FSI area. Higher than the design figure because parking and services sit outside the index. Always say which one you mean.

See https://devpartner.in/insights/gross-built-up-vs-net-saleable-area for the full conversion chain.

Where the area goes

1. Setbacks and coverage. Setbacks fix the maximum footprint; coverage rules may cut it further. A small plot loses proportionately more to setbacks than a large one — a 3 m setback on a 15 m frontage removes far more of the plate, in percentage terms, than the same setback on a 40 m frontage. Small urban plots are structurally less efficient, and that belongs in the land price.

2. Floor plate shape. A compact, regular plate serves more carpet per metre of corridor. Long thin plates, deep re-entrant courts and irregular geometry all buy circulation without buying carpet.

3. Core. Lifts, lift lobbies, staircases, shafts and firefighting provisions scale with height and with occupant load. A tower's core is proportionately heavier than a low-rise block's. Two lifts serving eight units per floor is a different efficiency from two lifts serving four.

4. Corridors and units per core. Units per floor per core is the strongest single lever available to the architect. More units per core spreads circulation, but pushes ventilation, privacy and saleability constraints.

5. Services. Pump rooms, tanks, transformer and DG yards, STP, MEP shafts, meter rooms, refuse handling. Frequently underestimated at feasibility stage and then found from saleable area.

6. Refuge and statutory provisions. Refuge floors, fire-tender paths and mandated open areas consume the plate. Requirements are height-linked and jurisdiction-specific. The National Building Code of India, 2016 sets the model fire-and-life-safety provisions that most state bye-laws adopt or adapt; confirm the applicable clause with the project's fire consultant and the local fire authority.

7. Parking. Where parking cannot close, unit count falls even though FSI does not — the sharpest efficiency loss of all. See https://devpartner.in/insights/parking-feasibility-before-design.

Illustrative efficiency ladder (assumptions, not benchmarks)

| Step | Effect on 54,000 sq ft GBA | Running total | |---|---|---| | Gross built-up area | — | 54,000 | | Less parking + ramps | (12,000) | 42,000 | | Less services, plant, refuge | (2,700) | 39,300 | | Less cores, lobbies, corridors | (6,300) | 33,000 | | Less wall thickness (carpet vs built-up) | (2,000) | 31,000 | | Carpet area | | 31,000 | | Design efficiency | 31,000 ÷ 54,000 | 57.4% | | Saleable at 25% loading | 31,000 × 1.25 | 38,750 |

Replace every line with the project architect's numbers. Published "typical" efficiency figures are typology-, height- and city-specific and should not be adopted as benchmarks.

Setting a defensible assumption before design

1. Ask the architect for plate-level efficiency on two comparable schemes of the same typology and height band.
2. Model a band, not a point (for example 55–60% design efficiency) and carry the low end into the land bid.
3. Test the parking constraint first — it can make the efficiency question academic.
4. Recheck after the first sanctionable plate. If efficiency lands below the band, the land price, not the design, must absorb it.
5. Keep loading separate. Loading is a market variable; efficiency is a design variable. Improving one does not improve the other.

Mistakes and risks

• Confusing planning and design efficiency — the two differ by 15+ percentage points, and quoting the wrong one flatters the appraisal.
• Assuming efficiency from a brochure. Brochure areas are saleable, not carpet, and rarely disclose GBA.
• Forgetting height's effect on the core. Efficiency generally falls as height rises.
• Under-provisioning services and recovering the shortfall later from saleable area.
• Optimising efficiency against saleability. Double-loaded corridors with poorly ventilated units are efficient and hard to sell.
• Treating the last 2% as noise. On a leveraged residual, 2% of efficiency can be a material share of land value.

Checklist

• [ ] Efficiency definition stated (carpet ÷ GBA) and used consistently
• [ ] Setback, coverage and height rules confirmed with clause references
• [ ] Core and lift provision sized by the architect, not assumed
• [ ] Service and refuge areas itemised
• [ ] Parking closure tested before efficiency is finalised
• [ ] Efficiency modelled as a band; low end used in the bid
• [ ] Loading assumption evidenced separately, dated
• [ ] Post-plate reconciliation scheduled before land commitment

FAQs

What is a good efficiency? There is no universal figure. It depends on typology, height, plate size and parking. Derive it from the architect's comparable schemes.

Does efficiency improve with a bigger plot? Usually yes, because setbacks and cores are spread over more area — but only up to the point where circulation lengthens.

Can loading fix low efficiency? No. Loading changes the number sold, not the space delivered, and is constrained by the market and by disclosure obligations.

Where should efficiency sit in the appraisal? On the revenue side, as the conversion from constructed area to saleable area — while cost stays on gross built-up.

Next step

Test envelope and efficiency scenarios in /development-potential, cost the constructed volume in /construction-cost-calculator, and see the land-value effect in /residual-land-value-calculator.

Sources

• Real Estate (Regulation and Development) Act, 2016 — full text, India Code, Ministry of Law and Justice (accessed 6 August 2026): https://www.indiacode.nic.in/handle/123456789/2158
• National Building Code of India, 2016 (SP 7:2016) — Bureau of Indian Standards (accessed 6 August 2026): https://www.bis.gov.in/standards/technical-department/national-building-code/

This article states no jurisdiction-specific rate, fee or market figure as fact. Every number in it is either arithmetic on stated assumptions or an explicitly labelled assumption.

Disclaimer. Decision support only, not architectural, planning or valuation advice. All areas, percentages and efficiencies above are illustrative assumptions and not benchmarks. Setbacks, coverage, core requirements, refuge provisions, service standards and parking norms vary by jurisdiction and change over time. Verify with the applicable development control regulations, building bye-laws, the project architect and MEP/fire consultants, and the competent authority.

Methodology: `/methodology`.