AI TextQuick Glance (AI)Headnote
Issues: (i) Whether resolution should proceed project-wise, with Ambrosia taken first as a pilot. (ii) Whether the insolvency process, moratorium, control and claims should be confined to Ambrosia or extend across the corporate debtor. (iii) Whether Ambrosia may be divided by phase or completion status. (iv) Whether an apex coordination body and project monitoring committees should supervise the arrangement. (v) How project liabilities, common liabilities, process costs and interim finance should be addressed.
Issue (i): Whether resolution should proceed project-wise, with Ambrosia taken first as a pilot.
Analysis: The Code and the insolvency regulations recognise project-specific features, including separate accounts and project-wise plans. The applicable rule favours project-wise real estate resolution unless circumstances justify a different approach. The projects have distinct registrations, creditors, receivables and stages of completion. Ambrosia was the project of default and had received preliminary proposals.
Conclusion: Resolution is to proceed project-wise, with Ambrosia as the pilot. The remaining projects may proceed when their individual proposals are ready and tested.
Issue (ii): Whether the insolvency process, moratorium, control and claims should be confined to Ambrosia or extend across the corporate debtor.
Analysis: The insolvency application concerned Ambrosia, but the corporate debtor remains one legal person to which the moratorium attaches. A single committee of creditors could allow creditors of one project to determine another project's plan. The other projects had operated under the interim resolution professional's supervision, and removing moratorium protection could expose them to recovery action.
Conclusion: The corporate insolvency resolution process, moratorium and interim resolution professional's control continue across the corporate debtor. The committee of creditors, claims process and plan are confined to Ambrosia. The other projects remain separately supervised, subject to review and applications for relief.
Issue (iii): Whether Ambrosia may be divided by phase or completion status.
Analysis: The regulations permit project-specific plans, and separate registrations, assets and allottees can support a genuine division. Common assets and approvals require identification; launched-phase receipts require ring-fencing, and affected homebuyers require notice and participation in relevant decisions.
Conclusion: Division between launched and unlaunched phases, or completed and incomplete parts, is permitted on the prescribed safeguards. Ambrosia's launched Phases I to III must remain together.
Issue (iv): Whether an apex coordination body and project monitoring committees should supervise the arrangement.
Analysis: The corporate debtor retains common statutory duties and liabilities while projects require separate stakeholder representation. The Tribunal's inherent powers support supervisory bodies distinct from statutory committees of creditors and from a monitoring committee constituted under the insolvency regulations to supervise an approved plan.
Conclusion: An apex coordination committee and project monitoring committees are to be constituted with the prescribed composition, powers and limits. They cannot approve plans or decide creditor claims.
Issue (v): How project liabilities, common liabilities, process costs and interim finance should be addressed.
Analysis: Project-specific debts, ongoing process costs and unallocated legacy liabilities require separate treatment. Project receipts are subject to statutory restrictions, while common costs require an approved allocation. Projects without a committee of creditors require a supervised route for interim finance and necessary asset dealings.
Conclusion: Project liabilities are to be addressed from the relevant project's resources. Process costs are to be shared on an approved basis, and unallocated legacy liabilities are to be addressed through a separate entity pool. Interim finance and necessary asset dealings for projects without a committee of creditors require the Tribunal's approval.
Final Conclusion: The directions establish a supervised, project-specific resolution framework while preserving corporate-wide protection and control. The main appeal and other applications remain pending.
Ratio Decidendi: Project-wise real estate insolvency resolution may be implemented through separate project claims and plans while corporate-wide moratorium and supervision continue where the circumstances justify that arrangement.
Project-wise real estate insolvency resolution separates claims and plans while preserving corporate-wide moratorium and insolvency professional control.
Project-wise real estate insolvency resolution can use separate creditor committees, claims and plans while the moratorium and insolvency professional's control continue across the corporate debtor. The defaulting project proceeds first as a pilot, with other projects separately supervised until their proposals are ready. Project phases may be divided where registrations, assets and allottees support a genuine separation, subject to identifying common assets and approvals, ring-fencing receipts and involving affected homebuyers; the pilot's launched phases remain together. Coordination and monitoring committees cannot approve plans or decide claims. Project liabilities are addressed from project resources, process costs are allocated on an approved basis, and unallocated legacy liabilities are addressed through a separate pool. Interim finance and necessary asset dealings for projects without creditor committees require Tribunal approval.
Project-wise resolution of real estate insolvency - Corporate-debtor-wide CIRP and moratorium - Segregation of launched and unlaunched real estate phases - Judicially supervised insolvency committees - Allocation of project and entity-level liabilities - Interim finance for projects without a committee of creditors Project-wise resolution of real estate insolvency - Project-wise rather than pooled resolution of a developer where the initiating insolvency application and default concern a single real estate project - HELD THAT: - Real estate insolvency should ordinarily be resolved project-wise unless circumstances justify otherwise, as laid down in Mansi Brar Fernandes v. Shubha Sharma [2025 (9) TMI 879 - SUPREME COURT] The regulatory framework recognises separate project accounts and plans. Here, separate registrations, allottees, receivables, approvals and counterparties, together with materially different stages of completion, supported project-wise treatment. Concerns about control and homebuyer participation could be addressed through supervised representation rather than pooling projects and exposing one project's homebuyers to another project's creditors. No departure from the project-wise rule was justified on the facts. [Paras 29, 30, 31, 32, 56] Resolution was directed project by project, with Ambrosia as the pilot. Other projects may proceed independently when their proposals are ready and tested, without awaiting completion of another project's resolution. Corporate-debtor-wide CIRP and moratorium - Project-specific CoC, claims and resolution plans - Continuation of corporate-debtor-wide CIRP, moratorium and IRP control despite confining the CoC, claims process and resolution plan presently to Ambrosia - HELD THAT: - A company-wide CIRP with project-wise plans is legally permissible, but a common CoC here would allow one project's creditors to determine another project's plan and impede progress until all projects' claims were processed. Section 14 attaches to the corporate debtor as one legal person; its protection neither adjudicates claims nor confers voting rights. Withdrawing that protection after prolonged judicially supervised operation would expose the remaining projects to coercive recovery and undermine their continuation. Confinement of creditor processes therefore did not restore authority to the suspended board or displace the IRP's control over any project. [Paras 43, 44, 45, 46, 47] CIRP, moratorium and IRP control continue across all projects; the CoC, substantive claims process and plan presently remain confined to Ambrosia. Other claims are only to be recorded and sorted. The remaining projects require quarterly review; if not resolved or released within twelve months or such other period as fixed, the IRP must seek a regular project CIRP or another statutory course. Creditors may apply for relief from the moratorium. Segregation of launched and unlaunched real estate phases - Ring-fencing of homebuyer receipts and common assets - Conditional separation of Ambrosia's launched and unlaunched phases, and of completed and incomplete portions, within the insolvency process - HELD THAT: - Phase-wise division may follow genuine differences in registration, assets and allottees, but not the convenience of an individual stakeholder. Shared land, development rights, infrastructure and approvals must be identified as common. Launched-phase receipts cannot finance the unlaunched phase, although support for a launched-phase deficit may flow in the opposite direction with approval in each case. Homebuyers' interests continue beyond delivery until occupancy certification, registration, handover of common areas and maintenance security, and functioning shared services. They must receive information on unlaunched-phase matters affecting them even without representation on that phase's committee. Selection of a strategic partner for launched phases requires objective, scrutinizable criteria and homebuyer participation; the lender's views receive due weight, but its consent is required only to the extent of its security, subject to statutory plan approval. [Paras 50, 51, 52] Ambrosia includes every phase, launched or otherwise. Conditional segregation of launched and unlaunched phases and completed and incomplete portions was permitted, but launched Phases I to III must remain together. Judicially supervised insolvency committees - Limits of supervisory and coordinating powers - Constitution, representative composition and limits of an Apex Coordination Committee and project monitoring committees during project-wise resolution - HELD THAT: - The supervisory machinery rests on Rule 11 of the NCLAT Rules and assists the IRP in discharging statutory duties without replacing a statutory CoC. Apex Heights Pvt. Ltd. v. Ram Kishore Arora [2026 (2) TMI 915 - SC ORDER] supported an apex-and-project committee structure. Each project committee includes homebuyer representatives, representatives of secured project lenders and the common IRP. The apex body represents the projects and secured lenders, with the IRP as non-voting chair. Its remit covers corporate compliance, common costs and litigation, separation of project funds and review of progress. Neither level may approve plans or adjudicate claims, and the apex body cannot override a project committee within its field. These project committees remain distinct from post-approval monitoring committees constituted by a CoC under the CIRP Regulations. [Paras 61, 62, 63, 64, 65] Project monitoring committees and an Apex Coordination Committee were directed to be constituted with the prescribed composition and supervisory limits. Approval of Ambrosia's CoC and authorised representative must be taken up first, with constitution of the apex body following settlement of that question. Allocation of project liabilities and common process costs - Entity pool for unallocated legacy liabilities - Allocation of project-specific debts, common process costs and unallocated legacy liabilities under project-wise resolution - HELD THAT: - Project debts are to be met from the corresponding project's assets and receivables rather than pooled with those of other projects. Running costs necessary to preserve the corporate debtor and conduct the process must be paid in full and apportioned on an approved basis from receipts available outside RERA-protected construction funds; they cannot be imposed on Ambrosia alone. Unallocated legacy debts require a separately maintained entity pool comprising unsold inventory not charged to lenders, project surpluses remaining after completion and payment of creditors, and permissible avoidance or wrongful-trading recoveries not attributable to a project. Claims against that pool rank under the Code. Any established diversion from a project must be restored to that project. [Paras 70, 71, 73, 74, 82] Separate project and entity-level liability arrangements were prescribed, with common cost-sharing subject to Tribunal approval. The corporate debtor's residual revival was reserved for later consideration on the closing report. Interim finance for projects without a committee of creditors - Judicial approval of project asset dealings - Approval and repayment treatment of interim finance, and approval of necessary asset dealings, for projects without a CoC - HELD THAT: - Projects without a CoC lack the body ordinarily required to approve interim finance and asset dealings under Section 28. For the present supervised arrangement, the IRP may seek Tribunal approval on the recommendations of both the project monitoring committee and the Apex Coordination Committee, with notice to affected parties. Interim finance so approved constitutes insolvency resolution process costs and is repayable in the statutory order from the resources of the financed project. [Paras 72] Interim finance and necessary asset dealings require the prescribed Tribunal approval. Approved finance cannot become a charge on another project without specific approval. Final Conclusion: Project-wise resolution was directed, with Ambrosia as the pilot, under continuing corporate-debtor-wide CIRP, moratorium and IRP control, subject to the prescribed supervisory and funding safeguards. The concerned interlocutory applications were disposed of, while the appeal and other pending matters remained for further consideration.