How a Listed NBFC Turned 10 Fragmented State RERA Portals into One Lending-Grade Real Estate Database

Introduction

10

markets covered across 6 states

85,000+

projects normalized into one schema

Monthly

refresh incl. QPR & status changes

Client: Listed Indian NBFC, AUM ₹35,000+ Cr (name withheld)

Industry: BFSI — Construction Finance

Use Case: Market monitoring & underwriting intelligence

Coverage: Mumbai, Pune, Nashik, Ahmedabad, Vadodara, Surat, Delhi-NCR, Chennai, Bengaluru, Hyderabad

Delivery: Monthly refresh to client data warehouse + analyst dashboard

About the Client

Our client is a listed non-banking financial company with assets under management exceeding ₹35,000 crore. Construction finance and real estate account for roughly a fifth of its book. For its asset-management and underwriting teams, understanding each market — how active it is, what product mix developers are launching, which promoters are delivering on time — is fundamental to both origination decisions and portfolio monitoring.

In the post-RERA era, the single richest public source for this is project registration data: every new project, its promoter, its approvals, its inventory mix and its quarterly progress reports (QPRs) are filed with state RERA authorities. The problem is not that the data doesn't exist. The problem is where — and how — it exists.

The Challenge

RERA is a central act implemented separately by every state. In practice, that means:

• Every portal is different. MahaRERA, Gujarat RERA, K-RERA, TNRERA, TSRERA, UP-RERA and Haryana RERA each have different site structures, search flows, field names, document formats and levels of detail. There is no common API.
• Key data hides in tabs and PDFs. Promoter details, approvals, unit inventory, financial disclosures and quarterly updates sit across multiple tabs — often as scanned or generated PDFs, not structured fields.
• The data changes constantly. New registrations, status changes (ongoing → completed → lapsed), registration extensions and fresh QPRs land every month. A one-time download is stale within a quarter.
• Analysts were doing this by hand. The client's teams were manually checking portals project by project — fine for one underwriting file, impossible for market-level views across 10 cities.

The client's brief: a single, clean, continuously refreshed database of RERA projects across its 10 focus markets — structured enough to feed both an analyst dashboard and its internal risk models.

The Actowiz Solution

1. Portal-Specific Extraction, One Common Schema

We built dedicated extraction pipelines for each state portal, then normalized everything into a single project-level schema — so a project in Surat and a project in Chennai carry the same fields, whatever their portals call them. State-specific quirks (Maharashtra's promoter grouping, Karnataka's tab structure, Tamil Nadu's document formats) are handled inside the pipeline, invisible to the client's analysts.

2. PDF & Document Digitization

Approvals, encumbrance details, inventory tables and QPR forms locked inside PDFs are parsed into structured fields, with source-document links preserved for audit — a non-negotiable for a regulated lender.

3. Change Detection, Not Just Snapshots

Each monthly cycle delivers not only the current state but a delta file: new registrations, status changes, extension filings and fresh QPRs since the last cycle. Portfolio-monitoring teams watch the deltas; research teams query the full base.

4. Promoter-Level Rollups

Projects are linked to normalized promoter entities across states, so the client can view any developer's full multi-city footprint — total projects, delivery track record by status, and pace of new launches — in one query. For a construction-finance lender, this promoter view is often worth more than any single project record.

The Results

• 85,000+ projects across 10 markets normalized into one lending-grade schema — from seven differently-structured state portals
• ~90% faster market-scan turnaround: city-level activity and product-mix views that took analysts weeks of manual portal work are now standing dashboard queries
• Monthly deltas on status changes and QPR filings now feed portfolio early-warning — lapsed registrations and stalled progress surface automatically, not on renewal
• Promoter 360° multi-state promoter rollups now inform every new construction-finance underwriting file as a standard input

Client Feedback

"We always knew RERA data could answer our questions — how active is this market, what is this promoter really delivering. What we didn't have was a way to ask those questions across seven portals at once. Now it's one query."

— Head of Projects (Real Estate), Listed NBFC

Why It Worked

• Normalization is the product. Anyone can download one portal. Value came from one schema across all of them — plus promoter linkage across states.
• Deltas over dumps. A lender's real question is "what changed?" — delivering change files made the data operational, not just archival.
• Audit-ready by design. Preserved source links and timestamps meant the data could enter regulated credit processes without friction.

Frequently Asked Questions

Which states can you cover?

All Indian state and UT RERA portals. Depth of available fields varies by state — we share a state-by-state coverage matrix before you commit, so there are no surprises.

Can refresh be faster than monthly?

Yes — weekly and near-daily refresh cycles are available and are commonly used by proptech CRMs and brokers tracking new registrations for lead generation.

Can this integrate with our CRM or data warehouse?

Yes. Delivery options include API, SFTP file drops, and direct loads to BigQuery/Snowflake/S3. Several clients consume RERA deltas directly inside their real estate CRMs.

Is extracting RERA data compliant?

RERA portals exist to make project information public — that is the statute's purpose. We extract only publicly disclosed regulatory filings, preserve source references for every record, and collect no personal data beyond what the regulator itself publishes.