Compliance Check Methodology

Seemankan shows factual compliance flags for every CG-RERA project — sourced from public government records. No editorial scoring. Every flag is verifiable.

Overview

Each project is checked against 6 compliance criteria derived from the RERA Act. Every check produces a factual flag: ✓ Passed, ⚠ Warning, ✗ Issue, or — Not Available. Each flag links to its source on the CG-RERA portal.

RERA Registration
Section 3
Penalty Orders
Sec 38–63
Recent Orders
Last 12 mo
Completion Timeline
Section 4
Quarterly Updates
Section 11
Annual Audit
Sec 4(2)(l)(D)

Flag Statuses

Each compliance check results in one of four factual statuses. No subjective judgment is applied.

Status Icon Meaning
Passed This compliance requirement is met based on publicly available CG-RERA data
Warning Potential concern found — review the linked source for details
Issue A compliance failure is recorded in official CG-RERA data
Not Available Data not available on the CG-RERA portal — no penalty applied, shown as informational

Overall Compliance Status

Each project receives one of four overall compliance tiers based only on its RERA registration status and proposed completion date. Other compliance checks (orders, audits, quarterly updates) are shown in the project detail for homebuyers to review, but do not affect the overall tier.

Tier Icon When Applied
Compliant Compliant Project is Completed; or registration is active (Ongoing, New, Extended) with proposed completion date in the future
Partial Compliance Partial Compliance Registration is still active (Ongoing, New, Extended) but the proposed completion date has passed — the project is overdue
Non-Compliant Non-Compliant Registration is Expired or Lapsed (completion date not yet passed or not available)
High-Risk High-Risk Registration Revoked, Suspended, or De-registered; OR registration Expired/Lapsed and proposed completion date has also passed
What Determines the Tier

Only two data points decide the overall status: RERA registration status and proposed completion date. The system evaluates from most severe to least — High-Risk first, then Non-Compliant, then Partial Compliance, then Compliant. Other compliance checks (penalty orders, recent orders, quarterly updates, annual audit) are shown separately in the project detail page for homebuyers to review independently.

Compliance Check Details

Here is exactly how each compliance check works and what data sources it uses.

RERA Registration Status
RERA Act Section 3

Checks whether the project has an active, valid RERA registration. The status is read directly from the CG-RERA portal.

Criteria
  • ✓ Pass: Status is Ongoing, New, Extended, or Completed
  • ✗ Issue: Status is Expired, Lapsed, Revoked, Suspended, or De-registered
  • — N/A: Status not available on the portal
Penalty Orders
RERA Act Sections 38, 39, 40, 59, 61, 63

Checks whether any RERA orders against this project cite penalty sections of the Act. These sections relate to financial penalties, directions, and compensation orders.

Criteria
  • ✓ Pass: No orders on record, or orders exist but none cite penalty sections
  • ✗ Issue: One or more orders cite sections 38/39/40/59/61/63
Recent Orders
Orders filed in the last 12 months

Flags whether any complaints or orders have been filed against the project in the last 12 months, indicating active regulatory attention.

Criteria
  • ✓ Pass: No orders in the last 12 months
  • ⚠ Warning: One or more orders filed in the last 12 months
Completion Timeline
RERA Act Section 4

Compares the proposed completion date against today's date. Projects past their promised deadline are flagged.

Criteria
  • ✓ Pass: Project completed, or proposed completion date is in the future
  • ⚠ Warning: Completed but after the originally proposed date
  • ✗ Issue: Proposed completion date has passed and project is not marked complete
  • — N/A: No proposed completion date on the portal
Quarterly Updates
RERA Act Section 11

Promoters are required to submit quarterly progress updates to RERA. This flag checks whether the latest snapshot shows a submitted status.

Criteria
  • ✓ Pass: Latest compliance snapshot shows quarterly update submitted
  • ⚠ Warning: Quarterly update is missing or stale
  • — N/A: No compliance snapshot data available
Annual Audit
RERA Act Section 4(2)(l)(D)

Promoters must file an annual financial audit report with RERA. This flag checks the latest compliance snapshot for audit status.

Criteria
  • ✓ Pass: Latest compliance snapshot shows annual audit submitted
  • ⚠ Warning: Annual audit is missing or stale
  • — N/A: No compliance snapshot data available

Builder Reputation Score

Each promoter (builder) receives a reputation score from 0–100, aggregated across all their registered projects. This score appears on the promoter detail page as a "Builder Report Card" and as a badge on the promoter listing page.

Formula

Reputation Score = Weighted Sum ÷ Total Active Weight

Each factor is scored 0–100, then multiplied by its weight. If a factor has no data (e.g., no orders exist), it is excluded and the score is normalised using the remaining weights.

Builder‑Level RERA Compliance Score
60%
Orders & Violations
40%
Builder‑Level RERA Compliance Score
Weight: 60%

Measures the average compliance health of all the builder's projects based on their RERA compliance status.

Compliance Scoring
Compliance StatusScore
Compliant100
Partial Compliance50
Non-Compliant20
High-Risk0
How it's calculated
  • Each project's compliance status is determined from registration_status and proposed_completion date
  • Each project receives a score based on the table above
  • Projects with N/A status (unknown registration) are excluded
  • Score = Average of all project compliance scores
  • Example: 2 Compliant (100) + 1 Partial (50) + 1 High-Risk (0) = (100+100+50+0) ÷ 4 = 62.5
Orders & Violations
Weight: 40%

Penalises builders who have received actual RERA orders (rulings) under specific sections of the RERA Act. Only complaints where an order was actually passed are counted — dismissed or pending complaints are excluded.

How it's calculated
  • Only complaints where order_under_section contains an actual section (not empty or "-") are counted
  • Count the number of distinct RERA sections cited across all orders
  • Score = max(0, 100 − distinct_sections × 4)
  • Each distinct section type deducts 4 points — 25 or more distinct sections = score of 0
  • Example: Orders under Section 18 and Section 31 = 2 sections → 100 − 8 = 92/100
When excluded
  • If a builder has zero actual orders, this factor is excluded entirely
  • The score is then normalised using only the Builder‑Level RERA Compliance Score (100% weight)
Informational Metrics (Not Scored)

The following metrics are shown on the Builder Report Card for transparency but do not affect the reputation score:

  • Complaints Filed — Total complaint count against the builder (includes dismissed and pending cases). Only complaints with actual orders impact the score via the "Orders & Violations" factor.
  • Buyer Rating — Average star rating from buyer reviews submitted on Seemankan. Will be incorporated into scoring once sufficient review volume is reached.

Reputation Tiers

Score Range Tier Color
85 – 100 Excellent Excellent
70 – 84 Good Good
50 – 69 Average Average
30 – 49 Below Average Below Average
0 – 29 Poor Poor
Example Calculation

A builder with 4 projects (2 Compliant, 1 Partial, 1 High-Risk) and orders under 2 distinct RERA sections:

Builder‑Level RERA Compliance Score (100+100+50+0) ÷ 4 = 62.5 → Score = 62.5 × 60% weight = 37.5
Orders & Violations 2 sections → 100 − 8 = 92 × 40% weight = 36.8
Final Score = 74 / 100 — Good

Data Sources

All compliance flags are sourced exclusively from publicly accessible government portals. No proprietary or editorial data is used.

All data used for compliance checks comes from the CG-RERA public portal:

  • CG-RERA Projectsrera.cgstate.gov.in — Registered projects, promoter details, status, and filings
  • CG-RERA Complaints & Ordersrera.cgstate.gov.in — Adjudication orders, complaint filings, section references
  • CG-RERA Compliance Snapshotsrera.cgstate.gov.in — Quarterly updates, annual audits, project progress

Data is refreshed periodically by the Seemankan scraper. Current data was last collected in May 2026.

Limitations & Disclaimers

Not legal or financial advice. Compliance flags are informational indicators based on publicly filed data, not certifications or guarantees of project quality or delivery.
Data freshness. Flags reflect the most recent data available at time of extraction. Portal data may lag by days or weeks. Current data was last collected in May 2026.
Incomplete portal data. CG-RERA portal data is sometimes incomplete or inconsistently filed. A flag showing "Not Available" does not indicate non-compliance — it means the data was not found on the portal.
No physical site verification. All compliance checks are performed entirely from digitally filed data on the CG-RERA portal. No physical inspections, site visits, or independent verification of construction quality is performed.
Methodology evolves over time. As more data becomes available on the portal (compliance snapshots, planning approvals, delivery records), additional compliance checks may be added for a more complete picture.