This article is the operational companion to RERA and Redevelopment Projects in India: What Societies and Allottees Should Know. That guide explains when RERA applies. This guide starts after the project is registered and asks a different question: what should the society and members actually track?
Start with the RERA registration baseline
Before monitoring changes, the society needs a frozen baseline of what was originally registered. Keep a copy or verified record of the project registration details current at the time of registration.
- RERA registration number and registration date;
- name of the registered project and phase, where phased;
- promoter and any landowner/co-promoter details shown by the authority;
- declared project completion date;
- registered land and building particulars;
- sanctioned plans and layout details available on the authority portal;
- approvals disclosed at registration;
- encumbrance and title-related disclosures required by the state authority;
- project professionals identified in the registration record;
- sale/allotment inventory shown for the registered project.
What Section 11 expects after registration
The central RERA Act does not treat registration as static. Section 11 requires the promoter to create a project page on the relevant Authority website and enter the registered project details for public viewing.
The Act specifically refers to quarterly updated information including:
- number and types of apartments or plots booked;
- number of garages booked;
- approvals obtained and approvals pending after commencement;
- the current status of the project;
- other information and documents specified by the relevant Authority.
That makes the RERA page useful as a regulatory audit trail. It also creates a simple society question: does the public record tell the same story as the PMC, developer and site?
The exact tracking fields depend on the state authority
RERA is a central Act, but state and Union Territory authorities operate their own portals, rules, regulations and update workflows. The appearance and detail of a project page therefore vary.
Maharashtra provides a useful example. MahaRERA's current guidance for quarterly/annual project updates says promoters should keep project information up to date under Section 11 and lists update areas such as:
- actual project cost;
- document uploads, certificates and encumbrance details;
- building details including apartments booked, sold or allotted;
- task/activity percentage of work;
- common areas and facilities and their work-completion percentages;
- project professional details;
- promoter/landowner/investor details;
- building-wise completion dates.
MahaRERA also states that failure to make the required quarterly project update can violate Section 11 and expose the promoter to penal action. Other state authorities may use different forms, terminology and interfaces, so a society should build its checklist around the authority governing its project.
What a society member should be able to see at a glance
| Tracking item | RERA authority record | Society/member portal |
|---|---|---|
| Registration number & validity | Primary source | Link, status and last-checked date |
| Registered completion date | Primary source | Compare with DA/PAAA and current project programme |
| Approvals obtained/pending | Quarterly public disclosure where required | Actual approval PDFs, dates, conditions and next actions |
| Construction progress | Quarterly/status fields | PMC reports, photos, certified milestones and delays |
| Sale/allotment data | Authority disclosure fields | Only what the society is legally entitled/required to retain |
| Member rehab entitlement | Usually not the full member-specific record | PAAA/flat-level area, parking, corpus and specifications |
| Transit rent | Normally not a complete member payment ledger | Month-wise status and supporting record |
| Society decisions | Not the full governance record | SGBM/AGM notices, minutes and resolutions |
| Developer obligations | Selected statutory disclosures | DA milestones, guarantees, insurance, rent and handover obligations |
| Member correspondence | No | Controlled access to notices, queries and responses |
The table explains why a RERA project page and a redevelopment member portal are complementary rather than competing systems. The Authority portal is the statutory external record. The society portal is the project-specific internal record.
Track approvals as documents, not labels
A common update says simply “approval received.” That is not enough for redevelopment governance. Members should be able to identify exactly what was received, by which authority, on what date and with what conditions.
For each material approval, store:
- authority name;
- approval/document title;
- reference number;
- issue date;
- validity period, if any;
- building/phase covered;
- conditions to be complied with;
- next approval dependent on it;
- copy of the approval;
- whether the RERA project page has been updated to reflect it.
In Mumbai, for example, members may hear terms such as IOD, commencement permission and occupancy approval. Those municipal milestones are separate from the RERA registration itself. See What Is IOD in Redevelopment? for that distinction.
Construction progress: compare three records
A reliable progress view compares three different sources:
- RERA public progress.
The status and percentage-completion information published through the authority update process. - PMC/architect certification.
The society's technical record of actual work completed, defects, variations and critical-path issues. - Contractual programme.
The milestone schedule in the Development Agreement, PAAA or approved construction programme.
If the RERA portal says 70%, the PMC report says 58%, and the contractual programme expected 80%, the discrepancy itself is the issue that needs explanation. A single percentage without its source is not useful project control.
Watch the completion date and every extension
The registered completion date should appear prominently in the society's project dashboard. When an extension is sought or granted, members should be told:
- the original registered completion date;
- the extension application date;
- the reason given for extension;
- the new date requested;
- the date and terms of the Authority's decision;
- the revised registered completion date;
- whether the DA/PAAA completion obligations and transit-rent obligations change;
- the financial effect of the delay on members.
Corrections and revised information should leave an audit trail
Registered project information can be revised or corrected through the relevant authority process. A society should not simply overwrite its own internal record when that happens.
Maintain:
- the earlier disclosed value/document;
- the revised value/document;
- the date of change;
- who requested the correction;
- authority approval/order where applicable;
- impact on member entitlement, project cost, completion, approvals or sale inventory;
- the General Body/committee communication issued about the change.
This is especially important for sanctioned plans, completion dates, promoter details, phase structure and material project disclosures.
What RERA gives allottees the right to know
Section 19 of the central Act gives an allottee the right to obtain information relating to sanctioned plans and layout plans with specifications approved by the competent authority, and the right to know the stage-wise time schedule of completion, including agreed infrastructure and services.
For redevelopment, this matters because existing residents are not merely observers of the construction. In Maharashtra, MahaRERA's published FAQ specifically states that existing residents of a redevelopment scheme are covered as allottees under the Act.
That does not mean every society member should receive unrestricted access to every financial, buyer or personal-data record. It means the society should design visibility around legal entitlement and project relevance, using role-based access where documents contain sensitive information.
What RERA registration does not prove
A RERA number is valuable, but it is not a certificate that every redevelopment risk has disappeared.
- It does not prove the society followed its own redevelopment governance correctly.
- It does not by itself prove title/conveyance is free from every dispute.
- It does not prove the developer has sufficient liquidity to complete the project.
- It does not prove transit rent is current.
- It does not prove every municipal approval required for the next construction stage has been received.
- It does not prove member-specific PAAA obligations are being honoured.
- It does not replace independent PMC monitoring.
Members should therefore use the RERA portal as a verification source, not as the only project-management system.
A practical quarterly RERA verification routine
- Open the official project page.
Verify registration status, project name, phase and promoter details. - Record the last-updated date.
If the authority displays one, capture it in the society dashboard. - Check the registered completion date.
Flag any extension, revision or approaching expiry. - Compare approvals.
Match authority disclosures against the approval PDFs held by the society. - Compare construction progress.
Reconcile RERA progress with the latest PMC/architect report. - Check uploaded documents and encumbrances.
Identify new or changed disclosures. - Review sale/allotment data where relevant.
Look for changes that affect project finance or inventory. - Publish a member summary.
State what changed, what did not and what requires follow-up. - Keep the evidence.
Archive the verification date and supporting copy/link.
How a redevelopment portal should present RERA tracking
A useful member portal should not copy the RERA website. It should translate the statutory record into the redevelopment context.
| Portal component | Recommended display |
|---|---|
| RERA status card | Registration number, status, authority link, original/revised completion date, last verified |
| Update timeline | Quarterly verification entries with date and material changes |
| Approval tracker | Approval obtained/pending, reference, conditions, document and next dependency |
| Construction tracker | Contract milestone, PMC-certified progress and RERA-reported progress |
| Extension log | Application, reason, order, old/new date and member impact |
| Document vault | Registration certificate, plans, approvals, orders, certificates and update documents |
| Member alerts | Material change notifications rather than raw-data overload |
| AI retrieval | Questions such as “What is the current RERA completion date?” answered from controlled project records |
The objective is traceability: a member should be able to see what the official record says, when it was checked, what the society holds, and whether the two match.
Questions members should ask when the RERA record looks stale
- When was the last quarterly update filed?
- Has the developer submitted the latest approval or progress information?
- Is the registered completion date still realistic?
- Has an extension or correction application been filed but not yet decided?
- Why does the PMC progress differ from the RERA portal?
- Are there approvals received by the developer that have not yet appeared online?
- Has any material encumbrance, promoter or investor information changed?
- Which person is responsible for RERA compliance and updating?
- What member communication has been issued about the discrepancy?
Connect the official RERA record to the member record
Rudh Systems can organise RERA registration details, quarterly verification, approvals, PMC reports, member notices, PAAA records, transit-rent updates and project documents in one controlled redevelopment portal—so members can see the official status and the society's supporting record together.
Frequently asked questions
Is RERA registration a one-time compliance step?
No. Registered projects have continuing disclosure and update obligations. Section 11 requires specified project information to be maintained and updated on the Authority website.
What information is normally updated quarterly?
The central Act identifies booking information, approvals obtained and pending, and project status. Individual authorities may require additional project-cost, document, construction, facilities, professional and completion-date fields.
Should a society reproduce the entire RERA portal?
No. It should link to the official record and maintain the redevelopment information members actually need: verified RERA status, approval documents, PMC reporting, member entitlements, rent, society decisions and contractual milestones.
What if the RERA progress percentage differs from the PMC report?
Do not choose one figure without explanation. Record the source and date of each, ask the promoter/PMC to reconcile the difference, and preserve the response in the project record.
Does an extension of RERA registration automatically extend transit rent or the Development Agreement?
Not automatically. Regulatory extension and contractual rights are different questions. Review the extension order, DA/PAAA terms and applicable law.
How often should members receive a RERA update?
Quarterly is a sensible minimum for a registered active project, with immediate updates for material events such as extensions, plan changes, major approvals, promoter changes or completion/occupancy milestones.
Authoritative sources and further reading
- India Code — Real Estate (Regulation and Development) Act, 2016.
- MahaRERA — Project Registration.
- MahaRERA — Project Updates.
- MahaRERA — Guidance for Project Update (Quarterly/Annually).
- MahaRERA — Additional FAQ on redevelopment and allottees.
- Rudh Systems — RERA and Redevelopment Projects in India: What Societies and Allottees Should Know.
- Rudh Systems — Redevelopment Portal for Societies, RWAs and Apartment Associations in India.