Rooftop Solar for Residential Projects: Developer ROI

The panel on the brochure, the invoice on your desk

A sales brochure with "solar-powered common areas" sells a certain kind of buyer — the one who has done the math on lift and pump bills before they've even signed the agreement. It is a strong differentiator in a market where the IBEF Real Estate Industry in India report (Feb 2026) notes end-user demand and delivery volumes both rising, and buyers increasingly scrutinizing running costs, not just entry price.

The uncomfortable question sits one layer down. Rooftop solar on an apartment project is, in almost every case, a common-area asset — it offsets electricity for lifts, common lighting, water pumps and clubhouse loads, not the individual flat's meter. The capex sits on the developer's project budget (or is handed off to the RWA), while the monthly savings accrue to residents through their maintenance bill. That mismatch — who spends, who benefits — is the single biggest reason rooftop solar plans get quietly dropped between the sales launch and the final BOQ.

This article is a sizing and ROI framework for developers evaluating rooftop solar on a residential project: how the loads work, what actually drives payback, what PM Surya Ghar and state net-metering rules mean for a group-housing project (as distinct from an individual homeowner), and how to hand the asset off to the RWA without creating a dispute six months after possession.

How rooftop solar works on an apartment project

Three structural facts shape every decision that follows:

1. The load is the common area, not the flat. Unlike an independent house where a rooftop system can be sized against the owner's own consumption, an apartment tower's terrace serves shared infrastructure. The generation offsets the society's electricity connection — lifts, common lighting, water and sewage pumps, and clubhouse/amenity loads — not what an individual resident draws inside their unit.
2. Roof area is a scarce, contested resource. The terrace is also where the water tanks, terrace garden, DG set, satellite dishes, HVAC condensers and (increasingly) EV-charging infrastructure want to sit. A solar array claims a large, shadow-free footprint and effectively locks out competing uses. Sizing solar without first locking the terrace layout is a common way projects end up retrofitting a smaller-than-planned array.
3. Ownership and metering follow the connection, not the panels. Since the common-area electricity connection is typically registered in the name of the association/RWA (or the developer during the pre-handover phase), the net-metering agreement with the DISCOM is signed against that connection — which has direct implications for who "owns" the system on paper after handover.

A sizing framework developers can actually use

Work through this sequence before committing capex to a solar line item:

Step 1 — Load assessment. Pull twelve months of common-area electricity bills if the project has a comparable running society, or model expected common-area consumption (lifts, pumps, lighting, clubhouse) from the sanctioned load and expected occupancy. This is the number solar is trying to offset — not the building's total connected load.

Step 2 — Roof area audit. Net usable, shadow-free roof area after subtracting water tanks, lift machine rooms, DG yards, planned terrace gardens and setback requirements. Factor in shading from adjacent taller structures, which varies significantly by plot and city.

Step 3 — System sizing. A rough sizing exercise (not a substitute for a solar EPC's detailed design) matches expected annual generation per kW of installed capacity — which depends on local irradiance, panel orientation and shading — against the Step 1 load. Irradiance varies materially across Indian cities, so a sizing assumption calibrated for one city should never be reused for another without adjustment.

Step 4 — Net metering check. Confirm the applicable state DISCOM's net-metering policy: capacity caps (often expressed as a percentage of sanctioned load), whether gross or net metering applies, and the export-tariff/banking rules for surplus units. These rules differ by state and change periodically, so the sizing decision should be validated against the current DISCOM circular for the specific project location — not against a general national assumption.

Step 5 — Ownership and O&M model. Decide, before construction, whether the developer capitalizes and hands over the asset free, whether it's financed via a RESCO/PPA model with a third-party solar provider, or whether the RWA takes on capex post-handover through a corpus contribution. This decision should be documented in the sale agreement or allottee disclosure, not left as a verbal assurance.

System component, cost driver, and payback consideration

PM Surya Ghar, subsidies and the fine print for group housing

The Union government's PM Surya Ghar: Muft Bijli Yojana scheme has materially shifted the economics of residential rooftop solar, but its subsidy structure is designed primarily around individual/household rooftop installations rather than group-housing common-area systems. Eligibility criteria, subsidy slabs, and whether a group-housing society's common-area connection qualifies under the scheme (versus schemes aimed at commercial/institutional consumers) can differ from what an individual homeowner reads in scheme marketing. Because subsidy terms, empanelled-vendor lists and application portals are updated periodically, developers should confirm current eligibility and subsidy quantum directly against the scheme's official channels and the relevant state renewable energy agency before building subsidy amounts into a project pro forma — never presenting a subsidy figure to buyers or the RWA as guaranteed until the sanction is in hand.

State-level net-metering policy is the second variable, and it is genuinely state-specific: sanctioned-capacity caps relative to connected load, whether surplus export is credited at full retail rate or a lower feed-in tariff, and banking-period rules for carrying forward unused export credits all vary by DISCOM. A sizing and payback model built for one state's net-metering rules will not transfer cleanly to a project in another state.

Mini scenario: sizing solar for a mid-rise society's common load

Consider a mid-rise residential project with a common-area connection covering four passenger lifts, common-area lighting, two borewell/overhead-tank pump sets and a small clubhouse. The developer's MEP consultant estimates the common-area load profile based on comparable running societies of similar unit count and amenity mix. The terrace audit finds usable roof area after netting out the two overhead tanks, the lift machine room and a planned terrace garden zone reserved in the sales layout.

Working through the sizing framework: the consultant proposes a system sized against the estimated common-area load (not the building's peak sanctioned load), confirms the state DISCOM's net-metering capacity cap against that load, and recommends a phased approach — install to cover the base common-area load now, with conduit and roof space reserved for a future capacity addition if the clubhouse expands. This phased approach is a practical way to avoid over-capitalizing on day one while keeping the option open, and it is a detail worth disclosing transparently to buyers rather than presenting the fully-scaled system as installed from possession day.

Handover to the RWA: the part developers under-plan

The single most common failure mode in developer-installed rooftop solar isn't the engineering — it's the handover. A few practices materially reduce disputes:

• Document the asset in the handover file. Include system capacity, commissioning date, warranty terms (panel, inverter, workmanship separately), net-metering agreement copy, and expected annual generation range.
• Hand over an O&M runbook, not just a system. The RWA managing committee typically has no engineering background; a one-page annual maintenance checklist (cleaning frequency, inverter monitoring app access, whom to call for faults) prevents the system from silently underperforming within a year.
• Clarify who owns the net-metering agreement post-handover. If it was signed by the developer during construction, it needs formal transfer to the RWA's name with the DISCOM — an administrative step that is often missed.
• Set expectations on savings, not guarantees. Actual generation depends on weather, shading changes (a neighboring building going up), and maintenance discipline — frame projected savings as an estimate based on stated assumptions, never as an assured outcome.

Pro tips

1. Reserve terrace space in the layout stage, not after the solar decision is made — retrofitting around water tanks and DG yards after civil work is far costlier than planning for it upfront.
2. Get irradiance and shading studies specific to the plot, not a generic city-average number — an adjacent under-construction tower can materially cut future generation.
3. Model the RESCO/PPA option alongside capex ownership — for some projects, a third-party-owned system with a per-unit purchase agreement removes the capex burden while still delivering resident savings.
4. Separate panel, inverter and workmanship warranties explicitly in vendor contracts — inverters typically need replacement well before panels do.
5. Budget net-metering application and inspection timelines into the project schedule — DISCOM processing times can affect occupancy-certificate-adjacent milestones if a common-area connection is contingent on final electrical inspection.

Common mistakes to avoid

1. Sizing against total sanctioned load instead of realistic common-area consumption, leading to an oversized, undercapitalized system.
2. Skipping the roof-area competition analysis, then discovering post-launch that the terrace garden promised in marketing collides with the solar array footprint.
3. Treating a subsidy or net-metering assumption from one state/scheme cycle as permanent — policies and slabs change, and a stale assumption can blow up the project pro forma.
4. Handing over a system with no O&M documentation, leaving the RWA to discover maintenance needs only after generation has already degraded.
5. Marketing "assured" or "guaranteed" savings figures to buyers — present sizing assumptions and methodology transparently instead, consistent with how any responsible platform should frame projected, not promised, outcomes.

Where this fits into your DrawMagic project listing

Renewable-energy provisioning is exactly the kind of sourced, factual project detail that differentiates a listing on DrawMagic's builder platform — buyers evaluating total cost of ownership respond to specifics (system capacity, common-area load offset, net-metering status) far more than to a generic "eco-friendly" badge. When you set up or edit a project through Builder Projects, list the solar specification as a transparent, dated fact — capacity, commissioning status, and what it's projected to offset — rather than an unqualified claim.

Before committing to a system size, run the capex against your project budget using the construction cost calculator to see how a solar line item interacts with your overall cost structure, and reference DrawMagic's how it works page to understand how transparent, fact-based project details reach buyers who are actively comparing developers on more than just price per square foot.

Value note: the opex story sells the project

Buyers increasingly evaluate an apartment purchase on total cost of ownership, not just the sale price — and a documented, realistically-sized common-area solar system is a concrete, verifiable data point in that conversation, unlike vague sustainability marketing. Presenting the sizing methodology, expected common-area offset, and handover documentation openly on your project profile builds exactly the kind of trust that converts a browsing buyer into a site visit.

Key takeaways

• Rooftop solar on apartment projects almost always offsets common-area load (lifts, pumps, common lighting), not individual flat consumption — plan and communicate it that way.
• Size the system against realistic common-area consumption, not total sanctioned building load.
• Terrace roof area is contested by water tanks, gardens, DG sets and EV charging — lock the layout before finalizing solar capacity.
• PM Surya Ghar and state net-metering rules differ for group-housing common connections versus individual households — confirm current eligibility and terms before budgeting subsidy amounts.
• Net-metering capacity caps and export-tariff rules vary by state DISCOM and change over time — validate against the current circular for your project location.
• Separate panel, inverter and workmanship warranties in vendor contracts; budget inverter mid-life replacement into RWA O&M planning.
• Document the full system (capacity, commissioning date, warranties, net-metering agreement) in the handover file, and hand the RWA an O&M runbook, not just an installed system.
• Never present projected generation or savings as guaranteed — frame them as estimates based on stated, disclosed assumptions.
• Transparent, dated solar-feature disclosure on your project listing is a stronger buyer-trust signal than generic sustainability marketing.

FAQ

Does rooftop solar reduce an individual buyer's own electricity bill? Not directly in most apartment configurations — the system typically offsets the society's common-area connection (lifts, pumps, common lighting), which lowers the maintenance charge component tied to common electricity rather than the individual flat's separate meter.

Can a residential society claim PM Surya Ghar subsidy for a common-area system? Eligibility and subsidy structure differ between individual-household schemes and group-housing/common-area applications; confirm current terms with the scheme's official channels and your state renewable energy agency before assuming a subsidy applies.

Who should own the solar system after possession — the developer or the RWA? This is a commercial and legal decision that should be documented in the sale agreement or allottee disclosure before construction, not decided informally at handover; options include developer-funded-and-gifted, RESCO/PPA third-party ownership, or RWA-funded post-handover.