SNN Sarjapur Road Master Plan: How a 30 Acre Apartment Project in Bangalore Uses Its Land

Two things are worth noting before the analysis. First, the six line items add to 1,21,758.77 sq m exactly — the table closes on its own development area, which is a basic internal-consistency check that a surprising number of published master plans fail.

Second, the development area of 12.1759 hectares works out to roughly 30.09 acres, and it sits between the two land extents on file: 30.66 acres in the project information sheet and 28.74 acres (11.6321 ha) in the Common Application Form. That discrepancy is unreconciled in the source documents and is disclosed here once. The land-use table is the internally consistent document, so the ratios below are computed against its own development area rather than either headline acreage.

The plan is organised as seven towers lettered A to G, subdivided into fifteen wings, plus a separate amenity structure. Towers run 2 Basement + Ground + 24 upper floors at 79.95 m; the amenity block is Basement + Ground + 3 floors at 21 m.

Fifteen wings across seven letters means the towers are not uniform — some carry a single wing, others two or three. The roof rainwater sump schedule (further down) is independent evidence of this: sump volumes range from 46 to 272 cubic metres, a nearly sixfold spread that can only reflect very different roof plate areas.

Some useful arithmetic on the wing plates, using the total unit count range on file (2,075+ per one document, 2,359 per another — both provisional):

• 16,056.44 sq m of footprint across fifteen wings and the amenity block gives an average plate near 1,000 sq m.
• 2,075 to 2,359 homes across fifteen wings is 138 to 157 homes per wing, or roughly six homes per floor per wing over 24 upper floors.

Six units on a thousand-square-metre plate is a slim, efficient tower rather than a wide slab. It is the configuration that produces cross-ventilation and corner units on most floors, and it is the direct structural consequence of choosing 13.19% coverage. Treat both unit counts as provisional until the sanctioned plan is on the record.

The amenity block being a separate structure is a deliberate choice, not an accident of layout. Clubhouses inserted into the podium levels of a residential tower push plant noise, party noise and late-hour footfall into the same structure as the homes above them. A standalone Basement + Ground + 3 building isolates all of that, gets its own arrival point and its own basement, and — at 21 m against the towers' 79.95 m — sits well below the tower line, so it blocks neither the southern sightlines nor the maturing tree canopy.

The 79.95 m tower height is itself a designed number. It sits fractionally below 80 m, and heights in that band are set with an eye on the approval and fire-compliance thresholds that apply above them.

A nala runs along the northern, western and eastern boundaries. Combined with the lake to the south, the parcel is hydrologically bounded on all four sides. That single fact explains much of the rest of the plan: the low coverage, the buffer emphasis, the 41 recharge pits and the perimeter green belt that the buffers effectively force into existence.

The buffer widths are not settled in the source documents, and this is the most consequential open item on the page:

The gap is 6 m on the lake and 5 m on each nala edge, and it is real land. On an illustrative 350 m × 350 m parcel — close to the recorded development area — three nala edges at 15 m instead of 10 m is about 5,250 sq m (1.3 acres) of additional reserved strip, and the lake edge at 30 m instead of 24 m adds roughly 2,100 sq m more. Taken together the two readings differ by something on the order of 1.8 acres of buildable versus reserved ground.

Which figure governs matters to a buyer in two ways: it changes how close the nearest tower can stand to the water, and it changes the effective perimeter green belt. The drawing is the wider of the two. Ask for the sanctioned plan and hold the buffer to whatever it records.

The plan commits to 2,300 trees across twelve named species. Scaled against the site, that is roughly 76 trees per acre, one tree for every 21.7 sq m of landscape area, and — on the unit counts on file — very close to one tree per apartment.

Eleven rows for twelve names, and the reason is worth stating: Bilvapatre is the Kannada name for Bael, so the twelve-name schedule resolves to eleven distinct trees. That is a documentation artefact, not a shortfall in the planting count. Note also the balance of the palette — the large-crowned natives (Neem, Kadamba, Arjun, Jamun, Bael, Devil's Tree) carry the structural canopy, while Gulmohur, Jacaranda, Champa and Nagalinga Pushpa are the flowering layer that does the visual work in years one to five.

What a canopy palette does over twenty years is different in kind from what an ornamental one does. A scheme built on palms, bottlebrush and clipped shrubs looks finished on handover day and looks the same in 2046. A palette anchored on Neem, Kadamba, Arjun and Jamun looks thin at handover and becomes a microclimate: large-crowned natives shading the 8 acres of driveway and cutting the hard-surface heat that drives afternoon cooling loads; deep root systems holding the nala buffer edges against monsoon scour; fruiting species creating a continuous bird corridor between the planting and the lake; and leaf litter and shade reducing irrigation demand on the landscape year after year.

The corresponding trade-off is patience and enforcement. Two thousand three hundred saplings are a promise, and planting schedules are a common casualty of value engineering between filing and handover. Two things to verify: that the species mix in the sanctioned landscape drawing still carries the large natives rather than substituting fast ornamentals, and that the maintenance obligation for the first three to five years — the period that decides whether a sapling becomes a tree — is written into the association handover.

The STP split is the smartest line in the schedule. Sequencing batch reactor plant handles the swinging diurnal load a residential project produces better than a continuous-flow system, and splitting capacity into 900 and 700 KLD modules rather than one 1,620 KLD unit means either module can be taken offline for maintenance while the other carries base load. That matters, because total capacity of 1,620 KLD against 1,566 KLD of generation is only about 3.4% headroom — thin enough that a single-train plant taken down for servicing would have nowhere to send the flow. The modularity is what protects the margin. The 20 KLD unit is a small separate stream, most plausibly serving the amenity block.

The roof harvesting reserve is larger than most buyers would guess. Seven sumps, one per tower, totalling 1,022 cubic metres — which is more than the 975 cubic metres of raw water storage. The site therefore holds roughly as much captured rainwater as it does bought water. The spread across the seven (46 cu m at the smallest, 272 at the largest, a 5.9× range) tracks roof plate area and independently confirms that towers A to G differ substantially in size.

Recharge is where the low coverage pays off again. Forty-one pits distributed across 62,005 sq m of soft ground is about one pit per 1,512 sq m of permeable surface. A site at 13.19% coverage with half its area unpaved can actually infiltrate rainfall rather than shed it into the nala — which is the difference between a development that loads the drainage network on the northern, western and eastern edges and one that relieves it.

On stored water, one honest caveat: 9,75,000 litres of raw storage plus a 1,00,000 litre overhead tank is about 0.9 days of the 1,156 KLD fresh-water demand. That is standard for BWSSB-connected projects and it is not a defect, but it does mean the recharge pits, the rainwater sumps and the 1,488 KLD of treated water going back into flushing and landscape are load-bearing parts of the water strategy rather than decorative ones.