blanket four-month force majeure extension moves the completion date on the MahaRERA register — but leaves interest liability, the contractual possession date and lender covenants untouched. What the order does, what it doesn’t, and what to document now.
The order
By Order No. 66/2026 (No. MahaRERA/Secy/388/2026) dated 7 August 2026, MahaRERA has ordered that registered projects whose completion dates, revised completion dates or extended completion dates fall on or after 28 February 2026 shall stand extended by four months. Projects registered on or after 1 August 2026 are excluded. The extension is granted automatically, without any separate application by the promoter, and the Registration and IT Cell is to give effect to it in the records and on the web portal. The order takes effect immediately.
The recitals set out the chain. The Ministry of Finance, by Office Memorandum dated 29 April 2026, treated the prevailing West Asia situation as ‘War’ for the purpose of invoking force majeure. The Ministry of Housing and Urban Affairs, by Advisory No. O-17024/66/2018-HOUSING-UD/E-9042100 dated 31 July 2026, advised all Real Estate Regulatory Authorities to issue suitable common orders rather than require separate applications from promoters. MahaRERA has acted under Sections 6 and 37 of the Real Estate (Regulation and Development) Act, 2016.
Why the Finance Ministry memorandum is doing the heavy lifting
The Explanation to Section 6 defines force majeure exhaustively: war, flood, drought, fire, cyclone, earthquake or any other calamity caused by nature affecting the regular development of the real estate project.
A supply-chain disruption originating overseas does not sit comfortably in that list. What makes it fit is the single word ‘War’ in the Finance Ministry’s memorandum of 29 April 2026. That characterisation, made for entirely separate purposes in government contracting, is what brings a foreign conflict within the four corners of the Explanation and makes this extension statutorily available at all.
It is worth pausing on that. A definition drafted with natural calamities in mind has been engaged by an executive classification issued elsewhere in government. Whether that classification, made in a procurement context, does the work required of it in a real estate statute is a question that has not been argued anywhere yet.
Why Section 37 appears alongside Section 6
Section 6 contemplates an extension granted on an application made by the promoter, in such form and on payment of such fee as may be specified by regulations.
Order 66/2026 dispenses with both. There is no application, and no fee. That is not a criticism — the MoHUA advisory expressly recommended this route, and case-by-case adjudication of thousands of pleas would have consumed the Authority’s entire bandwidth. But it explains why the order invokes Section 37, the power to issue binding directions, alongside Section 6. Section 6 alone does not obviously support a blanket, application-free, fee-free extension, and the direction-making power is carrying that weight.
Two consequences follow. First, the order records no project-specific satisfaction that force majeure affected any particular project — eligibility is determined entirely by a date. Second, the proviso to Section 6 caps extensions granted in reasonable circumstances at one year in the aggregate; whether that ceiling constrains a force majeure extension under the main limb is unsettled, and it becomes a live question for projects that have already drawn on COVID-era relief and subsequent extensions. The order is silent on it.
What exactly was extended
Read the operative paragraph carefully. It extends the completion dates of registered projects. The subject line of the order, and the section under which it is issued, both speak of extension of registration.
That is the register. It is the completion date declared to the Authority under Section 4(2)(l)(C) at registration and reflected on the portal.
The date on which possession was promised to a particular allottee sits somewhere else — in the registered agreement for sale, a contract between promoter and allottee. Section 18(1) attaches liability to the promoter’s failure to complete or give possession in accordance with the terms of the agreement for sale. An administrative order under Section 6 does not amend a registered contract between two parties, and Order 66/2026 does not purport to.
The drafting will nonetheless be pressed into service. “Completion dates shall stand extended” is broad language, and promoters will read it as extending the promise itself. That reading has to contend with the fact that the order is issued under a section headed extension of registration, on the recital that Section 6 empowers the Authority to extend the registration of a project.
Two clocks. The order moves one of them. Whether it reaches the second is exactly what will be litigated.
The order is silent on interest, and that silence is deliberate
There is nothing in Order 66/2026 about interest, about compensation, or about the computation of delay. Three operative paragraphs, none of which touches Section 18.
The MoHUA advisory, as recited, concerns extension of registration and corresponding completion timelines. It does not advise Authorities to grant an interest holiday.
So the position is open. Promoters will argue the four months should be excluded when computing delay, drawing on the COVID-era approach where MahaRERA treated the force majeure window as a moratorium for that purpose. Allottees will argue that Section 18 rights arise from the agreement, that the Supreme Court in Newtech Promoters read the refund right under Section 18(1) as unconditional and independent of any other consideration, and that an administrative extension of registration cannot dilute it.
Both readings are arguable today. Until a clarification issues or an appellate forum settles it, this is an unresolved question — not relief already banked. Anyone stating either position as settled is overstating.
Separately: the Supreme Court has held that RERA does not bar a homebuyer from proceeding under the Consumer Protection Act. A reset of a registration date closes neither door.
Eligibility is a date test, not an impact test
The order asks one question: when does your completion date fall. It does not ask, and cannot ask on a blanket basis, whether your project was actually affected by disrupted supply.
That is an administrative proxy, adopted for sound reasons of workload. It is not a finding.
The COVID experience is the warning. Blanket extensions were granted, and adjudicating authorities subsequently examined force majeure claims closely, allowing the period of genuine disruption and holding promoters answerable for delay beyond it. Force majeure has been read as a shield for a defined period, not as a general amnesty.
So the operative question is not whether you qualify on 28 February 2026. It is whether, three years from now, you can demonstrate that the West Asia disruption was real for this project.
What will decide that is a contemporaneous file: purchase orders and supplier correspondence showing revised lead times, import invoices and logistics records, documented material substitution or re-tendering, and site progress records from within the window. Cheap to assemble now. Impossible to reconstruct later.
Nobody has asked what this does to the books
If liability attaches to the contractual date, a four-month extension on the portal does not by itself justify releasing, or not creating, a provision for delay interest. The obligating event sits in the agreement, not in the order.
For promoters recognising revenue on completion, a regulatory reset is not evidence about the transfer of control. That is answered by the underlying construction status, not by the register.
And a revised expected completion is a change in accounting estimate, with consequences running through cost-to-complete, the assessment of whether a contract has become onerous, and the carrying value of project work-in-progress.
The regulator moved a date. Nobody moved the liability.
Check what your facility agreement points at
Construction finance and structured debt documentation frequently defines milestones by reference to the RERA completion date, for the simple reason that it is the one date a lender can verify independently on a public portal.
Order 66/2026 changes that date automatically, without the promoter doing anything, and the portal will reflect it.
Does a regulator-initiated change trigger a review event or a reporting obligation? Do withdrawal and certification mechanics under Section 4(2)(l)(D), and the designated-account arrangements built around them, reference the registered date? Does the shift push any milestone past a maturity or a servicing test? And has the lender been told — or will they find it on the portal?
The portal updates itself. Covenant compliance does not.
In redevelopment, three documents now disagree
The development agreement carries the negotiated timeline, the extension mechanics and the consequences of delay. The MahaRERA record now shows a completion date four months later, changed without either party doing anything. And the transit rent obligation is usually tied to the development agreement, not to the RERA date.
An extension of the RERA completion date does not extend a developer’s liability for transit accommodation unless the agreement provides for it. In the MMR, where societies drive a large share of supply, that gap is where redevelopment disputes begin.
Managing committees should be reconciling all three documents in writing now, not in year three.
The larger point
Applied to projects genuinely constrained by disrupted supply, a blanket order is proportionate relief. It substitutes an orderly, uniform, publicly recorded decision for a chaotic case-by-case one, and it keeps the register honest — a portal showing dates everyone privately knows are unachievable corrodes trust in the register itself.
Applied as cover for delay that has nothing to do with West Asia, it erodes the single most valuable thing RERA gave homebuyers: a deadline that means something.
