VIPRATECH LABS

RERA and Project Document Data Extraction

Collect project listings, unit inventory and filed documents from state RERA portals into a clean, comparable dataset, with quarter-on-quarter changes flagged for analysts.

Who it is for

  • Head of Business Development or Land Acquisition
  • Market Research Analyst at a developer or brokerage
  • Construction Finance Credit Manager
  • RERA Compliance Manager

The problem

State RERA portals hold the most reliable public record of what is being built: promoters, approvals, unit counts, bookings and declared completion dates. But each state publishes it differently, much of it sits in scanned PDFs, and analysts copy it into Excel by hand, one project at a time.

Every state portal is different

Field names, page layouts and document lists vary by state, so a template built for one portal breaks on the next.

Key facts are buried in PDFs

Registration certificates, architect certificates and quarterly progress reports are often scanned, so booked units or revised completion dates never reach the spreadsheet.

Changes between quarters go unnoticed

Completion date extensions, new towers or jumps in booked inventory matter for pricing and credit decisions, and they are easy to miss without a diff.

Stale, inconsistent datasets

Manual collection is done once for a land deal or a credit memo and then not refreshed, so different teams quote different numbers for the same micro-market.

What we build

We build a collector for each state RERA portal you care about, plus a document pipeline for the files attached to each project. Browser automation walks the listings at a polite pace, captures project detail pages and downloads filed documents. OCR and a large language model extract the fields you define, such as promoter, registration validity, land area, towers, unit mix, booked units and declared completion date, and normalise them across states. Each run is compared with the previous one, so changes surface as a list rather than a surprise. Low-confidence values go to an analyst before the dataset is published to Excel, a database or your BI tool.

  • Per-state collectors for RERA project listings and detail pages, scheduled weekly or monthly
  • Download and classification of filed documents: registration certificate, approvals, architect and engineer certificates, quarterly progress reports
  • Extraction of unit mix, carpet areas, booked and unsold units, and declared and revised completion dates
  • Normalisation of field names, area units and promoter names across states, with de-duplication by registration number
  • Quarter-on-quarter change log for extensions, new phases and inventory movement
  • Source link and page reference stored with every extracted value

How it works

  1. 01Agree scope and fieldsChoose states, districts and project types, and fix the field list and output format with your analysts.
  2. 02Collect listings and documentsScheduled browser automation walks the portal listings within agreed rate limits and saves each project page and its attached documents.
  3. 03Extract and normaliseOCR and an LLM read pages and PDFs, extract the agreed fields and map them to a common schema across states.
  4. 04Check confidenceValues below threshold, or that conflict between the project page and a filed PDF, are queued for an analyst.
  5. 05Compare with the last runA diff engine marks new projects, revised completion dates, added towers and changes in booked units.
  6. 06Analyst reviewAn analyst confirms flagged values and notable changes, with the source page shown next to each field.
  7. 07Publish the datasetThe checked dataset is exported to Excel, written to a database or refreshed in your dashboard.
RERA and Project Document Data Extraction: workflow diagram
Open full size

Architecture

  1. Collection
    • Playwright collectors per state portal
    • Scheduler with rate limiting and retries
    • Raw page and PDF archive
  2. Document understanding
    • OCR with table detection
    • Document type classifier
    • LLM field extractor with per-state schemas
  3. Normalisation
    • State-to-common field mapping
    • Area unit and date normalisation
    • De-duplication by registration number
  4. Review and change tracking
    • Run-to-run diff engine
    • Analyst review screen with source links
  5. Delivery
    • Excel export
    • Database or API
    • BI dashboard refresh
RERA and Project Document Data Extraction: architecture diagram
Open full size

Inputs and outputs

Inputs

  • State RERA portal project listings and detail pages
  • Registration certificates and approval documents filed on the portal
  • Quarterly progress reports and professional certificates
  • Target states, districts and project types
  • Field definitions and output template from your analysts

Outputs

  • Project-level dataset with promoter, approvals, land area and timelines
  • Unit mix and inventory table with booked and unsold counts where disclosed
  • Quarter-on-quarter change log
  • Source link and page reference for every value
  • Analyst review log

Where people stay in control

Analysts confirm any value below the confidence threshold or in conflict between a project page and its filed documents, and review notable changes before a refreshed dataset is published. Where a portal requires a login or captcha, a person completes that step.

Integrations

  • State RERA portals (public pages only)
  • Excel or Google Sheets
  • PostgreSQL or your data warehouse
  • Power BI, Tableau or Metabase
  • Internal land acquisition or credit memo templates

Guardrails

  • Collects only publicly disclosed pages, at a request rate agreed in advance and in line with each portal's terms
  • No captcha or login bypass; those steps stay with a person
  • Every value stored with its source URL and capture date
  • Conflicting values are flagged, never silently overwritten
  • Personal details that appear in filings are limited to what the analysis needs

Compliance notes

  • RERA disclosures are public, but personal data inside them is still handled with DPDP Act 2023 principles of purpose limitation and minimisation.
  • Collection schedules and volumes are designed to avoid placing load on government portals.

A typical pilot

Duration: 2 to 3 weeks

One state portal and one city or district, covering residential projects registered in a defined period, with a field list agreed with your analysts.

Deliverables

  1. 01Working collector for one state portal
  2. 02Extraction schema for project pages and two or three document types
  3. 03Sample dataset in your Excel template
  4. 04Change log from two consecutive runs
  5. 05Plan and estimate for adding further states

What we measure

Field-level extraction accuracy
Compared with values an analyst records manually for a random sample of projects.
Coverage of portal listings
Projects captured versus projects listed on the portal for the chosen district.
Share of values sent for review
Count of fields below threshold or in conflict, per project.
Analyst time per refresh
Time to produce the dataset with the pipeline versus the current manual method.

Built on related work

RERA project data aggregator

Real-estate data project (anonymised)

Playwright scraper that collects state RERA project listings and full project details into structured Excel output.

FAQs

01Is it acceptable to collect data from RERA portals?

RERA portals publish this information for public disclosure. We collect only public pages, follow each portal's terms, keep request rates low and do not bypass captchas or logins. Your legal team should still confirm the intended use, particularly if the dataset will be shared outside your organisation.

02What happens when a state portal changes its layout?

Collectors are monitored on every run. When a layout changes, the run reports missing fields instead of publishing partial data, and we update the collector. Ongoing maintenance is part of the production estimate.

03Can it read quarterly progress reports and certificates, not just the web page?

Yes. Filed PDFs, including scanned ones, go through OCR and LLM extraction. Values from PDFs are compared with the project page, and conflicts go to an analyst.

04Can we use this to check our own RERA filings?

Yes. The same pipeline can compare what your projects show on the portal with your internal sales and construction records, and list differences for your compliance team before the next quarterly update.

Related use cases

Akhilesh Mittal

Founded by Akhilesh Mittal. 8 years building a security platform for a New Zealand company. IIT ISM Dhanbad and IMT Ghaziabad. Builds production agentic AI.

Pick one project and one painful workflow

Book a discovery call and we will scope a short pilot on one project, such as RA bill checks for a single contractor or lead qualification for one launch, run in parallel with your current process.