RERA Compliance Project Management Guide

RERA compliance is often treated as a legal or accounts task. But on a live construction site, compliance becomes a project management discipline: clear schedules, reliable progress reporting, controlled changes, and audit-ready documentation.

That shift matters because RERA is now at scale. The Economic Survey 2024–25 reported that, as of January 6, 2025, India had ~1.38 lakh real estate projects and 95,987 agents registered under RERA, with ~1.38 lakh complaints disposed nationwide.<!-- citeturn7search4 -->

At the state level, Maharashtra has been one of the most active markets: MahaRERA crossed 50,000 registered housing projects by May 2025.<!-- citeturn0news14 -->

If you are a small or mid-sized builder, contractor, or site engineer, the good news is: you do not need a huge compliance department. You need a simple system that converts site reality (work done, approvals pending, money spent, risks, photos, and communications) into clean, consistent updates.

This guide explains RERA compliance project management in practical terms: what to track, who should own it, and how to run a repeatable workflow on Indian construction sites.

Note: This article is for operational awareness. For state-specific interpretation and filings, consult your legal and CA/architect/engineer advisors.

What RERA compliance really means for a project team

RERA compliance is not only about registering a project and getting a registration number. For day-to-day execution teams, it usually boils down to five ongoing responsibilities:

1. Truthful disclosures and regular updates on the state RERA portal (progress, approvals, inventory/bookings, etc.).
2. Schedule discipline (what you promised vs what you built, and why any slippage happened).
3. Financial discipline (especially project-wise segregation and withdrawal support documents).
4. Document control (plans, approvals, change history, site records, and communication trails).
5. Customer-facing consistency (what sales says must match what the site can deliver).

RERA has been implemented across almost all states and UTs (with the Economic Survey noting an exception of Nagaland for notified rules at that time).<!-- citeturn7search4 -->

Why project management is now a compliance requirement

Most RERA trouble is not caused by one big mistake. It is caused by small, repeated gaps:

• Quarterly updates prepared in a rush, with inconsistent progress percentages
• Approvals list not maintained (what is obtained vs pending)
• Site photos scattered across WhatsApp groups
• Variation work happening without a documented change order
• Vendor bills and RA bills not mapped to actual work done

RERA requires promoters to update project information on the authority website on an ongoing basis, including quarterly updates like bookings, approvals, and project status.<!-- citeturn5search0 --> If your site reporting is weak, your compliance becomes weak.

Think of it this way: RERA portal updates are the output. Project management is the engine.

The RERA obligations you can manage with site-level systems

You do not need to memorise every clause. You need to build a workflow that consistently produces the data RERA expects.

1) Quarterly updates: treat them like a deliverable, not paperwork

Under RERA, promoters have ongoing duties to maintain a project web page and keep key details quarterly up to date (for example, bookings, approvals, and status).<!-- citeturn5search0 -->

What this means on site:

• A monthly progress summary is not optional; it is the raw material for quarterly filings.
• Your progress percentage must be backed by measurable quantities (not just opinion).
• Every delay needs a reason code (approval delay, labour shortage, rain days, design change, cashflow, vendor delay).

Indian site example:

A G+14 residential project in Pune is at slab level. The site engineer says progress is 60%, but the contractor’s RA bills suggest only 45% of construction value is complete, and the latest drawings changed after MEP coordination. When quarter-end comes, your portal update becomes a risk because numbers don’t reconcile.

Project management fix:

• Track milestone completion (excavation, PCC, footing, plinth, slab-by-slab, masonry, plaster, waterproofing, MEP rough-in, finishing).
• Attach proof: inspection checklists, cube test reports, pour cards, DPR photos, and measurement sheets.
• Keep a simple “approvals obtained vs pending” register.

2) The 70% separate account rule: map cost, progress, and certificates

RERA requires that 70% of amounts realised from allottees be deposited into a separate account, to be used for land and construction cost.<!-- citeturn2search1 -->

Withdrawals are expected to align with the percentage completion of the project and are commonly supported by professional certifications (engineer, architect, and CA), as reflected in RERA guidance/circulars in multiple states.<!-- citeturn6search1 -->

What this means on site:

If your accounting team asks, “What is the percentage completion this quarter?” you must answer with a defensible number backed by:

• BoQ / work package completion
• RA bills and measurement books
• Photo evidence for key milestones

Practical tip for SMB builders:

Even if your CA is handling withdrawals, the site team must maintain the supporting evidence. If not, you end up doing last-minute document hunting.

3) Stage-wise schedule commitments: build a schedule you can defend

RERA expects promoters to share stage-wise time schedules and keep the public-facing status updated.<!-- citeturn5search0 -->

What this means in project management terms:

• Your baseline schedule must be realistic for Indian conditions (monsoon productivity, labour migration cycles, festival slowdowns, local approval lead times).
• You need a look-ahead plan (2-week and 6-week) so delays are identified early.

Indian site example:

A site in Noida faces a 3-week delay in basement waterproofing due to dewatering challenges. If you capture this in a risk log early (and adjust downstream milestones), your quarterly update remains consistent. If you ignore it, you get a sudden schedule gap that looks like non-performance.

4) The 10% payment rule: align sales collection with documentation

RERA restricts promoters from taking more than 10% of the cost as advance/application fee from an allottee without first entering into a written agreement for sale and registering it (as reflected in state RERA FAQs).<!-- citeturn6search7 -->

What this means operationally:

• Sales and accounts need a clear checklist: booking form, KYC, payment schedule, agreement draft, registration appointment, and receipts.
• Site teams should not be surprised by promised possession dates. Align the possession timeline with your actual construction plan.

5) Non-compliance risk is real: plan to avoid penalties

RERA provides for penalties for non-registration and continued default, including penalties linked to estimated project cost and, in some cases, imprisonment.<!-- citeturn8search0 -->

You don’t need to run your project in fear of penalties. You need a disciplined reporting and documentation rhythm so you never “fall out of compliance” in the first place.

RERA compliance project management checklist (site-ready)

Use this as a practical checklist you can run on any project. Adapt the exact format to your state RERA portal.

A. Setup (once per project)

• Create one folder structure for approvals, drawings, contracts, BOQ, QA/QC, DPRs, photos, and bills
• Freeze a baseline schedule with clear milestone definitions
• Assign owners for DPR, approvals tracker, and quarterly update inputs

B. Weekly discipline (minimum)

• Update measurable progress and capture dated photos
• Update approvals tracker, issues, and risks (with owners and dates)

C. Monthly discipline (recommended)

• Reconcile progress vs billing; document variations and change orders
• Validate schedule forecast (critical path items and procurements)

D. Quarterly discipline (for RERA updates)

• Lock progress summary + evidence pack; update approvals and bookings (with sales)
• Prepare certification inputs (completion % and cost mapping)

A simple workflow Indian SMB teams can follow

If you’re a lean team, this workflow keeps things manageable.

Step 1: Run a daily site diary (10 minutes)

Capture: labour count, key activities, major deliveries, blockers, weather issues, and a few photos.

Step 2: Update progress weekly against milestones

Use milestone definitions like:

• Excavation and plinth complete
• RCC structure progress (slab-by-slab)
• Masonry and plaster progress
• Waterproofing milestones (toilets/terrace/podium)
• MEP rough-in and testing
• Finishing and snag clearance

Step 3: Maintain an approvals register like a tracker

Even a simple tracker works:

• Approval name
• Required for which milestone
• Applied date
• Expected date
• Current status
• Responsible person

Step 4: Track changes as a formal log

Every change should have:

• Reason (client request, authority requirement, design coordination)
• Drawings/revisions involved
• Cost impact
• Time impact
• Approval (email/letter/sign-off)

Step 5: Keep a quarter-end pack ready

By the last week of every quarter, you should already have:

• Updated progress summary
• Evidence folder (photos, checklists, test reports)
• Approvals register snapshot
• Billing/progress reconciliation note

This reduces the “quarter-end scramble” that often creates compliance mistakes.

Best practices that make RERA compliance easier (and safer)

Centralise documents and control versions

On many Indian sites, the biggest risk is not lack of data—it’s conflicting data. One contractor is working off an old drawing revision, while the office updates the portal based on a newer revision.

Best practice:

• One location for latest drawings (with revision number clearly visible)
• A change log that records when a new revision is issued and to whom
• A rule: only the latest revision is valid on site

Make progress evidence standard, not optional

If you ever need to explain progress to a buyer, lender, or authority, evidence matters.

Use a standard set:

• Date-stamped photos of each major work front
• Concrete pour records and cube test results
• Waterproofing checklists and inspection sign-offs
• Snag lists and closure photos for finishing

Reconcile time, cost, and scope every month

Compliance gets messy when:

• Progress % says 70%
• Cash spent says 90%
• Scope is still changing

Monthly reconciliation helps you catch this early.

Common RERA compliance failures (and how to prevent them)

1. Inconsistent progress reporting (different numbers in site reports, billing, and portal updates)

   • Fix: define a single progress method and reconcile monthly.

2. Approvals not tracked (a missed NOC becomes a timeline shock)

   • Fix: approvals register with dates and owners.

3. Uncontrolled variations (scope creep without documentation)

   • Fix: change log + approvals + impact notes.

4. Scattered evidence (photos and site records lost in chats)

   • Fix: central folder + naming convention + weekly upload routine.

5. Sales promises not aligned with schedule

   • Fix: monthly schedule review with sales/accounting.

Where SiteSetu fits into RERA compliance project management

Many builders already have WhatsApp groups, Excel trackers, and paper files. The challenge is that these tools don’t automatically create a clean compliance trail.

A construction project management tool like SiteSetu can help by making compliance-friendly execution the default:

• Daily progress reporting with photo evidence
• Centralised documents so teams work on the latest drawing revision
• Task and issue tracking so blockers are visible early
• Simple checklists for QA/QC and safety, linked to work fronts
• Faster month-end and quarter-end reporting because data is already organised

The goal is not to “do extra work for compliance”. The goal is to run the project well—so compliance becomes a natural by-product.

FAQs

Does every construction project need RERA registration?

RERA registration requirements vary by project type and thresholds under the Act and state rules. Confirm applicability for your project and state before marketing or collecting money.

How often do we need to update the RERA portal?

RERA requires ongoing disclosures and commonly expects quarterly updates of key project information on the authority website.<!-- citeturn5search0 --> Your state portal may have additional formats and timelines.

Who should own compliance on the ground?

The best model for SMBs is shared ownership:

• Site engineer owns DPR, photos, milestone status
• Planning/PM owns schedule and risk log
• Accounts/CA owns bank/accounting compliance
• A single coordinator compiles quarterly inputs

What is the fastest way to reduce RERA risk?

Start with three habits:

• Weekly progress + photo evidence
• Approvals register
• Change log

Once these are stable, quarterly updates become far easier.

Can software replace legal/CA advice?

No. Software helps you run a disciplined process and keep records organised, but filings and interpretations should be validated by your professional advisors.

Final takeaway

RERA compliance is not a one-time event—it is a continuous operational practice. When you run RERA compliance project management with consistent site reporting, controlled changes, and audit-ready documentation, you reduce legal risk and improve delivery.

For Indian builders and contractors, the best approach is simple: build a repeatable workflow, keep evidence organised, and use tools (like SiteSetu) that make discipline easy instead of burdensome.