This guide is the commercial and operational companion to Society vs RWA vs Apartment Association: Which Redevelopment Rules Apply? and Apartment Redevelopment Rules in India. Those articles explain why the legal structure matters. This one explains how the project record should be designed once that structure is known.
The wrong starting point: one giant folder for everybody
Redevelopment teams often begin with folders named “Legal”, “PMC”, “Developer” and “Members”. That works for a few weeks. It becomes fragile once documents are revised, members ask different questions, approvals arrive in stages and a committee changes midway through the project.
A usable record system needs to answer five questions immediately:
- What is this document? Notice, resolution, report, approval, contract, member entitlement, invoice or progress record.
- Which decision or milestone does it support? PMC appointment, developer selection, vacating, commencement, construction stage or possession.
- Which version is current? A revised plan should not silently replace the plan relied upon six months earlier.
- Who is allowed to see it? A general meeting minute is different from a member's bank details or succession papers.
- What happened next? Every important record should connect to an action, responsibility or subsequent document.
The common redevelopment record every entity needs
Regardless of entity type, most projects need a core record covering the entire redevelopment lifecycle.
| Record area | Examples | Why it matters |
|---|---|---|
| Governance | Notices, agenda, attendance, minutes, resolutions, written consents | Shows how authority was obtained and what was actually approved |
| Title & governing documents | Conveyance/lease, declaration, deeds, bye-laws, property schedules | Explains who owns what and who may grant redevelopment rights |
| Consultants | PMC/architect appointment, scope, quotations, reports, invoices | Creates technical independence and accountability |
| Feasibility | Structural audit, development potential, FSI/FAR/TDR assumptions, cost model | Records the assumptions behind the project |
| Developer selection | Tender/RFP, bids, comparison matrix, due diligence, negotiation record | Preserves the commercial selection trail |
| Agreements | Development agreement, owner/member agreements, guarantees, amendments | Defines enforceable project obligations |
| Approvals | Plans, NOCs, commencement permissions, RERA, OC/completion records | Distinguishes official permission from informal progress claims |
| Member/owner entitlements | Existing unit, replacement unit, carpet area, parking, rent, corpus, specifications | Lets each person verify the project promise made to them |
| Payments & security | Transit rent, deposits, bank guarantee, insurance, escrow/security records | Tracks financial protection and missed obligations |
| Construction | PMC reports, certificates, photos, milestones, defects, variations | Creates an evidence-based progress record |
| Handover | OC, possession, snagging, warranties, common-area documents, final accounts | Closes the project without losing the history |
If it is a cooperative housing society: the system must mirror society governance
A cooperative housing society already has a formal member-governance structure. The redevelopment record should therefore preserve the chain from member notice to meeting to resolution to implementation.
For Maharashtra cooperative housing societies, the 4 July 2019 directions under Section 79A are a clear example of this design principle. Clause 6 directs a society proposing redevelopment to create an internet website and make redevelopment information such as notices, minutes and the PMC report available to members. It also requires project notices and minutes to be communicated to members and the Registrar to be informed about the website.
That is not a nationwide rule for every RWA or apartment association. It is, however, a useful example of why a society record should be member-facing rather than committee-only.
A society portal should normally make it easy to trace:
- the member request or proposal that initiated the process;
- Special General Body and General Body notices, agenda and minutes;
- PMC/architect quotations, appointment and scope;
- feasibility and project reports;
- tender issue, bid receipt, comparison and developer-selection resolutions;
- registered Development Agreement and member-specific agreements where applicable;
- approvals, guarantees, rent schedules and construction reports;
- member communications and acknowledgements.
For the Maharashtra-specific website requirement, see Does Section 79A Require a Redevelopment Website?.
If it is an apartment owners' association: declaration and unit ownership become central
An apartment-ownership project should not simply copy a cooperative-society portal. The legal record often begins with the declaration, deeds of apartment, common-area interests and association bye-laws.
For example, the Maharashtra Apartment Ownership Act defines an apartment owner as a person owning an apartment together with the undivided interest in common areas and facilities stated in the Declaration, and defines the Association of Apartment Owners as all apartment owners acting as a group under the bye-laws and Declaration. That means the portal should make the governing instruments easy to locate before it displays redevelopment votes or developer offers.
Likewise, Tamil Nadu's 2022 Apartment Ownership Act establishes an association framework, while the 2024 Model Bye-Laws expressly include maintaining financial records and facilitating redevelopment in compliance with the Act and Rules. The exact legal route differs by state, but the information architecture lesson is consistent: the record must preserve the documents that establish each owner's voting and property rights.
An apartment-association portal should therefore give special prominence to:
- registered declaration and amendments;
- association bye-laws and amendments;
- deeds/ownership schedules and percentage or undivided interests where relevant;
- common-area and limited-common-area records;
- owner voting register and resolution evidence;
- state-law redevelopment procedure and authority filings;
- individual replacement-unit and consideration schedules.
If it is an RWA: prove authority before building the workflow
“RWA” can describe very different organisations. Some are registered associations managing community services; others operate alongside separate apartment deeds, developer-controlled common areas or another statutory ownership structure.
The portal should not imply that an RWA owns land or can grant development rights merely because it collects maintenance. Before creating approval workflows, the project record should hold the evidence showing what the RWA is authorised to do.
At minimum, the record should identify:
- registration and constitution of the RWA;
- memorandum, rules or bye-laws;
- actual land and common-area ownership documents;
- owner deeds, declaration or apartment-ownership documents where applicable;
- specific resolutions or owner consents authorising redevelopment steps;
- any federation, developer, landowner, government authority or lessor whose approval is required.
The three record architectures side by side
| System layer | Cooperative housing society | Apartment association | RWA / owners' body |
|---|---|---|---|
| Authority record | Registration, bye-laws, conveyance/title, general-body powers | Declaration, deeds, bye-laws, ownership/common-interest structure | Registration, constitution plus proof of actual property/development authority |
| Decision record | Member meetings, resolutions, notices and acknowledgements | Owner voting register, statutory resolutions and declaration/bye-law compliance | Owner consents and resolutions within the RWA's proven powers |
| Individual record | Member flat, PAAA/entitlement, rent and payments | Apartment/deed, undivided interest, replacement entitlement | Owner deed/entitlement and any separate association record |
| Regulatory layer | Cooperative + planning + RERA as applicable | Apartment ownership + planning + RERA as applicable | Underlying property law + planning + RERA as applicable |
| Portal access | Member role plus committee/PMC/admin roles | Owner role plus board/manager/consultant roles | Owner/member role aligned to the RWA's actual mandate |
RERA is an external official record—not your internal project database
For a project that is registered under the Real Estate (Regulation and Development) Act, the promoter has continuing public-disclosure obligations. Section 11 requires the promoter to create a web page on the relevant RERA Authority website and keep specified information updated, including approvals obtained and pending and the status of the project. Section 19 gives allottees rights to information including sanctioned plans and stage-wise completion schedules.
A redevelopment portal should therefore link to and reconcile the RERA record, not duplicate it blindly. A practical RERA card can show:
- registration number and authority link;
- registered promoter/co-promoter;
- original and revised completion dates;
- last verification date;
- latest approvals shown on the official record;
- difference, if any, between RERA progress and PMC-certified progress;
- extensions, corrections and material changes.
For the detailed workflow, see RERA Project Tracking for Redevelopment.
The system should begin with an “entity and authority register”
Before the first project document is uploaded, create one controlled page that answers the legal-structure questions that otherwise get rediscovered every time a new lawyer, PMC or committee joins.
| Field | What to record |
|---|---|
| Entity type | Cooperative society, apartment association, RWA or other structure |
| Registration | Registration number, date, statute and current office bearers |
| Governing documents | Bye-laws, declaration, memorandum/rules and amendments |
| Property rights | Land title/lease, conveyance status, common-area ownership and encumbrances |
| Voting basis | Member count, ownership interest or other statutory basis |
| Redevelopment authority | Specific sections, resolutions, owner consents and required third-party approvals |
| Legal review | Date, lawyer, opinion or unresolved issue requiring action |
This prevents the project team from treating “member majority” as a universal concept when the governing law may count ownership interests differently or require a specific resolution type.
Build a decision log, not just minutes
Minutes describe what happened in a meeting. A decision log makes that information operational. Each major decision should have its own record showing:
- decision title and unique ID;
- meeting/resolution that authorised it;
- date and voting/consent result;
- documents considered;
- responsible person or consultant;
- deadline or condition;
- subsequent amendment or superseding decision;
- links to resulting agreement, approval or payment.
If a developer's revised offer changes the carpet area or rent, the record should connect the revised offer to the meeting that approved it and the final agreement that implemented it.
Document control: current, superseded and historical
Redevelopment can generate multiple versions of the same plan, feasibility report, agreement and programme. The system should never make a superseded document disappear.
Use clear statuses such as Draft, For Review, Approved, Registered/Executed, Superseded and Historical. Every version should carry an upload date, source, document date and—where practical—the decision or approval that made it effective.
For agreements, keep signed schedules and annexures together. For approvals, record the issuing authority, reference number, issue date, validity, building/phase and conditions. For plans, identify the revision and approval reference so members do not compare different drawings without realising it.
Give every member or owner a private entitlement page
General project transparency does not mean publishing each person's private documents to the entire building. The system should separate project-wide visibility from individual records.
An individual page can contain:
- existing unit and documentary reference;
- replacement unit, RERA carpet area and allocation status;
- parking/specifications and agreed benefits;
- signed individual agreement and schedules;
- transit rent, deposit and payment status;
- vacating/possession record;
- queries and responses relevant to that member;
- documents requiring signature or action.
The member should see their own private record; committee members and authorised administrators may need controlled broader access; other members should not automatically see it.
Design permissions before uploading sensitive documents
| Role | Typical access | Typical restrictions |
|---|---|---|
| Member / owner | Project notices, minutes, key agreements, approvals, progress, own entitlement/payment record | Other members' personal, succession, banking and private correspondence |
| Committee / board | Governance records, project contracts, member-level administration where authorised | Need-to-know restrictions on highly sensitive personal material |
| PMC / architect | Technical reports, plans, approvals, construction records and assigned workflows | Member banking or unrelated legal files |
| Lawyer | Title, governing documents, agreements, disputes and instructed member issues | Technical or financial data not needed for the legal mandate |
| Developer | Executed project documents, approvals workflow, obligations, authorised owner/member data | Internal committee deliberations or private records beyond contractual need |
| Auditor / finance | Invoices, payments, guarantees, rent ledger and financial reports | Unrelated personal documents |
Permissions should be explicit, logged and reviewed when committee members, consultants or developers change.
Connect documents to milestones
The most useful portal answers “what is holding up the project?” without forcing a member to read 40 PDFs. Build the milestone timeline from evidence:
- Governance complete.
Resolution, consent and appointment records linked. - Feasibility approved.
Structural/planning reports and approved project assumptions linked. - Developer appointed.
Bid comparison, due diligence and resolution linked. - Agreements executed.
Registered/executed agreements, guarantees and individual entitlements linked. - Approvals in progress.
Obtained and pending approvals shown with conditions and dates. - Vacating / demolition.
Preconditions, rent payments and handover records linked. - Construction.
Contract programme, PMC-certified progress, RERA status and delays compared. - Possession and closeout.
OC/completion, defects, warranties and final handover documents linked.
Turn communication into a project record
Not every WhatsApp message belongs in the permanent record. But every material project communication should.
Use the portal for formal notices, meeting minutes, approval changes, delay notices, rent updates, milestone announcements and responses to material member queries. Keep delivery/acknowledgement evidence where the governing process or agreement requires it.
For Maharashtra cooperative societies, the 2019 directions specifically contemplate notices and minutes being sent to members and the project website making redevelopment information available to them. That reinforces a broader record-management principle: communication should be traceable back to the document or decision it describes.
Where AI actually helps
An AI member assistant becomes useful only after the record is organised. It should answer questions from controlled project documents and provide the source document or section used.
Examples:
- “What is the current registered completion date?”
- “Show me the latest PMC report.”
- “Has my transit rent for September been marked paid?”
- “Which resolution approved the developer?”
- “What carpet area is recorded in my agreement?”
- “Which approvals are still pending?”
- “What changed between the previous and current construction programme?”
The minimum viable redevelopment record system
A smaller society or association does not need dozens of modules on day one. The minimum useful system has seven controlled areas:
- Entity & authority — registration, governing documents, title and legal structure.
- Meetings & decisions — notices, minutes, resolutions, consent and decision log.
- Documents — versioned consultant reports, bids, agreements and approvals.
- Member/owner pages — individual entitlement, agreement and payment information.
- Milestones — approval and construction timeline with evidence.
- Communications — formal project notices and acknowledged updates.
- Audit & access — permissions, activity history and controlled downloads.
What to ask before choosing a redevelopment portal
- Can the system model a society, apartment association and RWA differently?
- Can it keep one private entitlement page per member/owner?
- Can every document carry a status, version and related decision/milestone?
- Can we restrict sensitive records by role?
- Can members search notices, minutes, reports and approvals without seeing private files?
- Can the portal link to official RERA/project records rather than pretending to replace them?
- Can we track approval reference numbers, conditions and expiry dates?
- Can PMC progress be compared with the contractual programme and RERA status?
- Can committee or consultant access be revoked when people change?
- Can we export the full project record if we change providers?
- Can the AI assistant cite the source document behind an answer?
- Is there a clear audit trail for uploads, revisions and key actions?
Build the portal around your actual redevelopment structure
Rudh Systems can configure a controlled redevelopment record for cooperative societies, RWAs and apartment associations—covering governance, documents, approvals, member or owner entitlements, project milestones and AI-assisted retrieval without treating every organisation as legally identical.
Frequently asked questions
What is a redevelopment record management system?
It is the controlled project record used to organise redevelopment decisions, notices, minutes, title and governing documents, consultant reports, developer selection records, agreements, approvals, member or owner entitlements, payments, construction updates and handover documents. It should complement—not replace—official statutory filings.
Should a housing society, RWA and apartment association use the same redevelopment portal structure?
No. The software can share a common core, but the record architecture should reflect the actual legal entity, governing documents, voting structure, ownership model and state-specific process. A cooperative society may need society resolutions and Section 79A records; an apartment association may depend more heavily on its declaration, deeds, bye-laws and owner voting interests; an RWA may need proof of the authority it actually has.
Does a redevelopment portal replace the RERA website?
No. For registered projects, Section 11 of RERA requires the promoter to maintain prescribed project information on the relevant RERA authority website. An internal member portal should link to and reconcile that official record while also holding society or association records that the RERA portal does not contain.
What should members be able to see?
Members or owners should generally be able to see governing decisions, notices, minutes, project reports, developer-selection records, key agreements, approval status, construction updates and their own entitlement or payment records. Access to personal, banking, succession or other member-specific records should be restricted to authorised users.
Why should the system keep document versions?
Redevelopment documents change: plans are revised, approvals are superseded, agreements are amended and project schedules move. Version history helps show what changed, when it changed and which document was relied on for a particular decision.
What is the difference between a document folder and a redevelopment record system?
A folder stores files. A redevelopment record system also connects each file to the relevant decision, owner or member, approval, milestone, payment, version and access rule so the project can be audited and understood over several years.
Should WhatsApp and email remain the main record?
They are useful communication channels but weak as the sole project record. Important notices, decisions, approvals and contractual documents should be placed in a controlled repository with consistent naming, dates, permissions and retention.
Can AI answer member questions safely from redevelopment records?
Yes, if it is restricted to authorised project documents and respects the user's access level. The AI should point users back to the underlying document rather than inventing legal conclusions or exposing another member's private data.
Primary sources and further reading
- Government of Maharashtra — 4 July 2019 redevelopment directions under Section 79A, including the member-facing redevelopment website provisions for cooperative housing societies.
- India Code — Real Estate (Regulation and Development) Act, 2016, especially Sections 11 and 19 on project information and allottee rights.
- India Code — Maharashtra Apartment Ownership Act, 1970, including the definitions of apartment owner, common areas and Association of Apartment Owners.
- India Code — Tamil Nadu Apartment Ownership Act, 2022.
- Tamil Nadu Apartment Ownership Rules, 2024 — Model Bye-Laws.
- Rudh Systems — Society vs RWA vs Apartment Association.
- Rudh Systems — RERA Project Tracking for Redevelopment.