Home Methodology

Methodology

How we compute the Builder Reputation Score. All inputs are sourced from the public CG‑RERA portal — no editorial or proprietary data is used.

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 Builder IQ 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 RealEstateIQ. 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 Projects — rera.cgstate.gov.in — Registered projects, promoter details, status, and filings
  • CG‑RERA Complaints & Orders — rera.cgstate.gov.in — Adjudication orders, complaint filings, section references
  • CG‑RERA Compliance Snapshots — rera.cgstate.gov.in — Quarterly updates, annual audits, project progress

Data is refreshed periodically. Current data was last collected in April 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.
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 or site visits are performed.
Methodology evolves over time. As more data becomes available (compliance snapshots, planning approvals, delivery records), additional compliance checks may be added for a more complete picture.