Every statutory application, and whose desk it is on.
Approvals tracks every statutory application a development needs — RERA, the planning authority, the corporation — through a status lifecycle that only moves via a recorded transition. Each one carries its checklist, its documents, its expiry and the name of the person it is currently sitting with.
Status moves one way, and only through a transition.
No screen sets a status column. Every movement goes through a service that checks the move is legal, records who made it and writes it to the timeline. That is what makes the board trustworthy six months later.
An expired approval is not a paperwork problem. It stops sales, stops construction, or both — and it is usually noticed in the month it matters.
Your approval types, not ours.
Which approvals a development needs differs by authority, by city and by project type. The catalogue is data your team edits — not a schema change and not a support ticket.
Project registration, quarterly updates, extension and amendment filings
Planning permission, layout approval, revised plan sanction
Building licence, water and sewerage connection, completion certificate
Electricity sanction, fire NOC, environmental clearance where applicable
Illustrative. Your catalogue is configured to the authorities and application types your projects actually go through.
Enough to answer “where is it?” without a phone call.
Approvals, walked through.
From the board and the checklist to handing a file to a vendor, sign-off, the authority’s decision and the renewal warning.
See it against your own project.
A walkthrough runs on your data — one real approval, one live tower, last week’s enquiries. Forty minutes, no slides.