A real estate developer with multiple active projects faces an insolvency petition from homebuyers in one stalled development. The NCLT admits it. Suddenly, every other project — with its own buyers, its own lenders, its own construction schedule — is frozen under a moratorium triggered by a dispute it has nothing to do with.

That outcome, which the Insolvency and Bankruptcy Code almost certainly did not intend, has been a persistent source of anxiety in India's housing sector. A March 2026 ruling from the NCLAT has significantly curtailed it.

The Problem Built Into How the IBC Works

The IBC allows financial creditors — a category that, since a 2018 amendment, includes homebuyers — to trigger a Corporate Insolvency Resolution Process against a developer. Once the NCLT admits the petition, a moratorium takes effect across the entire corporate entity: all proceedings are stayed, and management passes to a Resolution Professional.

The difficulty is structural. Most developers operate as a single legal entity even though their projects are entirely separate in terms of land, funding, and buyer commitments. A CIRP that covers the whole company sweeps in everything — including projects where deliveries are on track and creditors have no complaint.

In the case before the NCLAT, allottees of the Raheja Shilas (Low Rise) project filed a Section 7 petition against Raheja Developers Ltd. The NCLT admitted it against the whole company. The suspended director appealed, arguing that the proceedings must be confined to the one project that gave rise to the dispute.

What the Tribunal Held

The NCLAT Principal Bench, presided over by Justice Ashok Bhushan and Technical Member Barun Mitra, modified the NCLT order.

The CIRP is restricted to Raheja Shilas (Low Rise). No other project of Raheja Developers falls within its scope.

Homebuyers of Raheja Shilas are financial creditors of that project — not of the developer's entire balance sheet. A resolution process initiated by those creditors cannot extend beyond the source of the default that triggered it.

Why This Actually Matters

The ruling provides real structural protection for multi-project developers. But it comes with a condition the NCLAT has consistently emphasised: the protection is only as strong as the project-level separation underneath it.

Where a developer has maintained dedicated escrow accounts, ring-fenced revenue streams, and clean project-specific books, there is now a firm precedent to argue that an insolvency proceeding on one project must stay confined there. Where funds have been co-mingled and projects run as a single financial pool, that argument is considerably harder to sustain — and courts are unlikely to extend the same protection.

For homebuyers, the message is equally direct. The IBC remains a powerful tool against a developer in default. But the petition must be project-specific. An admission on one development does not open every other project to the same process, nor does it relieve buyers in other projects of the need to file separately.

The Takeaway

Developers should read this ruling as both protection and instruction. The protection is genuine: a CIRP on one project need not bring down the whole business. The instruction is equally genuine: that protection only holds where your projects are financially separate in fact, not just on paper.

If they are not, an insolvency petition from any one project's allottees could still reach further than this ruling might suggest.