Of the declared rows that claim a project finished on time and can be checked against the register, 940 belong to projects whose own registration shows they finished after their first deadline. As updated on 11 October 2026, that is 940 of 10,937 such rows. The likely mechanism is mundane: a revised completion date typed into a box labelled original. But the promoter past projects table in a RERA registration is no longer a form nobody opens. Buyers can read it before booking, lenders before sanctioning and landowners before signing a joint development agreement, and any of them can check a numbered row against the register in a minute.
Key takeaways
- As updated on 11 October 2026, 16,232 published MahaRERA projects file at least one earlier project in the promoter's past-experience table, 51,570 rows in all.
- Read against their own dates, 64.7 percent of rows declare completion on or before the declared original date, 21.4 percent after it, 3.7 percent no completion with the date passed, and 10.2 percent no completion with the date still to come.
- Only 19,019 rows (36.9 percent) name a MahaRERA registration number; the rest are the promoter's own words and can be checked against nothing on the register.
- Of 18,735 numbered rows that resolve to a published registration, 2,139 give a later original date than the registration holds, and 1,777 of those are exactly the revised deadline the project carries after an extension.
- Filling the table well comes down to three things: a registration number on every row that has one, the original date as originally promised, and completion dates that match the register.
What the Act asks, and how MahaRERA's table asks it
Section 4(2)(b) of the RERA Act asks a promoter applying for registration for brief details of the projects it launched in the past five years, completed or being developed, with their current status, any delay in completion, cases pending and payments pending. MahaRERA's registration form turns that into a table. Each row asks for the earlier project's MahaRERA registration number, its name and address, its status, land area, number of buildings or plots, number of apartments and total cost, the original proposed completion date, the actual completion date, and whether the project has litigation.
The table is public, like the rest of the filing, and the portal publishes it as filed. Every row is the promoter's declaration, and every figure in this article presents the rows as declared, never as verified. The rest of the application is covered in registering a project on MahaRERA.
Why the table is read now
Three readers open it, each for a reason of their own.
- Landowners. ANAROCK counted 17 joint development agreements among the 76 land deals it tracked in the first half of 2025, covering 782 acres with an estimated market value of Rs 6,765 crore, and at least 126 land deals on about 3,772 acres over the whole of 2025, with the Mumbai Metropolitan Region accounting for the most deals, 32. A landowner choosing between developers for a JDA, under either of the structures a JDA can take, reads this table early, because it is the bidder's own account of its record, filed with the regulator. A landowner's diligence on a developer sets out the full counterparty file; this table is one page of it.
- Lenders. Under the Reserve Bank of India (Project Finance) Directions, 2025, in force from 1 October 2025, a lender holds an extra provision for each quarter a completion date is deferred. A promoter's history of meeting dates is now priced, and underwriting a developer from the MahaRERA record treats the declared rows as the promoter's own account, to be checked against the register. The lenders doing that reading are mapped in construction loan lenders in Maharashtra.
- Buyers. The table sits in the public filing that a buyer opens before booking, and a numbered row names a registration whose own dates anyone can look up.
What 51,570 declared rows show
Source: ReraGenie analysis of the past-experience tables filed with 16,232 published MahaRERA projects, as updated on 11 October 2026, after dropping rows where a promoter listed the registration itself as its own earlier project. Every row is declared, not verified.
On their own terms, two in three rows declare an on-time finish. But the row is graded against the date the promoter typed, and that date is where the table and the register part company.
Source: ReraGenie analysis of declared rows naming a MahaRERA registration number, as updated on 11 October 2026; 19,019 rows name a number and 18,735 of them resolve to a registration published on ReraGenie.
Most numbered rows agree with the register. Where they do not, the pattern points one way: of the 2,139 later dates, 1,777 are exactly the revised deadline that project carries after an extension. A MahaRERA registration page shows a project's proposed completion date beside its revised or extended one, and the obvious way to fill a box marked original is to copy the date the page shows today. That is the likely mechanism, and nothing in the data says anyone meant to mislead. Where such a row also declares completion by that date, it reads on time while the registration shows the first deadline was missed. Of 10,937 checkable rows declaring completion on or before the declared date, 940 finished after the original date the registration itself holds.
Before you file, open each numbered row's registration and copy the completion date it was first registered with, not the date it shows as current. That one check would have caught most of the mismatches above, and it costs a few minutes a row.
What you need before you start
- A list of every project you launched in the past five years, completed or under way, including those under entities you control.
- The MahaRERA registration number of each one that was registered.
- Each registration's original proposed completion date, as declared when it was registered, and any revised or extended date, kept separately.
- The actual completion date of each finished project, and its occupancy or completion certificate.
- Status, litigation, land area, buildings or plots, apartments and total cost for each, from your own files.
The steps
Step 1. List the right projects, and not the one you are registering
Action. Start from the five-year window the Act names and list every project in it, completed or under way.
What you will see. For many promoters the window holds projects registered on MahaRERA and a few that never needed registration, such as small buildings under the exemption in section 3(2)(a) of the Act, which covers land of up to 500 square metres or up to eight apartments.
Red flag. The project you are registering, listed as its own earlier project. Some filed tables do exactly that, and it reads as padding. ReraGenie drops those rows before counting.
Step 2. Put the registration number on every row that has one
Action. For every earlier project registered on MahaRERA, enter its registration number exactly as issued.
What you will see. Only 36.9 percent of declared rows carry one. A numbered row can be opened and checked; an unnumbered row is your word alone, and a reader weighs it that way.
Red flag. A table with no numbers at all from a promoter whose name appears on several registrations. A reader who finds those registrations under your filed name on the developer pages will ask why the table left them unnumbered.
Step 3. Enter the original date as originally promised
Action. In the original proposed completion date column, enter the date each project declared when it was registered, not the date on its page today.
What you will see. If a project was extended, its registration shows both dates. The table asks for the first one. Extensions under MahaRERA explains how the revised date arises.
Red flag. An original date that matches the extended deadline. It is the commonest mismatch in the data, and it turns a late delivery into an apparently punctual one for any reader who does not check.
Step 4. Make completion dates match the register
Action. Enter the actual completion date that your occupancy or completion certificate supports, and check the registration shows the project as completed.
What you will see. A row whose completion date sits within weeks of the certificate and whose registration status agrees with it.
Red flag. A completion date on a row whose registration still shows another status. Either the register needs its completion filing or the row is early, and a reader cannot tell which.
Step 5. Say what is still under way, and what is in court
Action. For a project still running, leave the actual date empty, enter its original date as first declared, and set the litigation field truthfully.
What you will see. About one row in seven declares no completion: 10.2 percent with the date still to come and 3.7 percent with the date already passed.
Red flag. A project with a passed date and no completion, left unexplained. Readers find it anyway; an explanation in your own pack costs less than the question.
Step 6. Reconcile, and keep the note
Action. Before filing, set every numbered row beside its registration page and confirm the original date, the completion date and the status. Keep the comparison as a one-page note.
What you will see. A table that matches the register line for line, and a note you can hand to a lender or landowner who asks.
Red flag. Rows that differ from one application to the next. The table is filed with every registration, so the same earlier project should read the same in all of them.
An analogy: the tender's list of past works
A contractor pre-qualifying for a public tender lists its past works with values and completion dates, and the client checks the list against completion certificates. A list that matches wins the contractor the benefit of the doubt on everything else in the bid; one entry that does not match puts every other entry under review. Your past-experience table works the same way, except that the client is every buyer, lender and landowner who opens the filing, and the completion certificates are already public.
Deshmukh reads two tables
Deshmukh (our illustrative Nashik land owner) had asked both bidders for the registration numbers of their last three completed and current projects. Before choosing between the 42 percent revenue share from the large Pune developer and the 33 percent area share from the mid-size Nashik builder, he also read the past-experience table each had filed with its newest MahaRERA registration.
The Nashik builder's table had six rows and only two registration numbers. The other four were small buildings below the registration threshold, so there was nothing to number, and the builder sent their completion certificates when he asked. The Pune developer's table ran to fourteen rows, nine numbered, and the snag was in one of them: a row declaring completion a month before its original date, where the registration it named showed an original date eleven months earlier and an extension to the very date the table gave. Asked about it, the developer's team said the form had been filled from the registration page as it reads today. Deshmukh took that as the likely explanation, recorded the project as delivered after one extension, and asked for both dates side by side for every numbered row. Names and numbers in this story are illustrative.
What the project analysis reads in your record
A landowner or lender who wants the record assembled rather than read row by row can use ReraGenie's Rs 2,999 project analysis, and it is worth knowing what it shows about you. It sets out the promoter's record: its registrations, how they ended, a concurrency timeline, and its complaints, litigation and appeals. It reports the self-declared pre-RERA projects worded as declared, never verified. And for completed projects it gives the cycle time and the share with an occupancy certificate uploaded, which is the register's version of the completion column in your table.
Before you file your next registration, open your own earlier projects on reragenie.com: each free project page shows the possession timeline, first promised date against the current one, which is the pair of dates your table has to keep apart.
Checklist before you file
- Every project in the five-year window listed; the project being registered not among them.
- A MahaRERA registration number on every row that has one.
- The original proposed completion date as first declared, never the revised or extended one.
- Actual completion dates that match the certificates and the registration's status.
- Under-way projects and litigation stated plainly.
- A one-page reconciliation against the register, kept for anyone who asks.
- The same earlier project described the same way in every application.
Methodology and sources
- Declared rows: ReraGenie analysis of the past-experience tables of 56,194 published MahaRERA projects, as updated on 11 October 2026. 16,232 projects file at least one earlier project after rows listing the registration itself are dropped; 51,570 rows remain. Outcomes are read against each row's own declared dates.
- The register check: 19,019 rows name a registration number, 18,735 resolve to a published registration, and their declared original dates are compared with the original date that registration holds. Every row is presented as declared, never verified.
- ANAROCK land deal reports for the first half of 2025 and for calendar 2025, as reported in July 2025 and January 2026. Market values are ANAROCK's estimates.
- RERA Act sections 3(2)(a), 4(2)(b) and 60; the Reserve Bank of India (Project Finance) Directions, 2025; Bihar RERA's notice of January 2023 on section 4(2)(b).
This article is educational and not legal advice. Confirm the position for your project with your advocate and the authority concerned.
Evaluating a micro-market or a land parcel?
The ReraGenie project analysis reads the filings around your parcel: supply, absorption and promoter records. Rs 2,999 per project; the area market report is a flat Rs 2,999 per pincode.
See the project analysis