01 · The Perspective
The same pothole, five times
The story below is illustrative. It is not about a real street.
A resident reports a pothole outside her lane. Three days later, the complaint is marked resolved. A thin patch of tar has been laid. After the next rain, the pothole is back. She complains again; a new ticket opens and closes.
By the end of the year, the same pothole has generated five resolved complaints. The city's dashboard shows five successes.
02 · The Perspective
Fast closure, unknown outcomes
According to a written reply in the Rajya Sabha, reported by PTI in July 2025, central ministries and departments received 6,60,091 grievances on CPGRAMS between 1 April and 24 July 2025 and redressed 4,47,431, with an average redressal time of 16 days. A feedback call centre has run since July 2022 to check citizen satisfaction.
Speed has improved. The harder question is how many problems stay solved.
03 · The Perspective
More is in place than most citizens use
- CPGRAMS. The national online grievance system for central ministries, with appeals and feedback.
- State grievance portals. Many states run their own, such as Karnataka's Janaspandana.
- Municipal complaint apps. Most cities accept complaints by app, phone or web.
- Feedback calls. Some systems call citizens to check satisfaction after closure.
04 · The Perspective
Where resolution breaks
- Repeat complaints are separate tickets, so recurring failures are hidden.
- "Resolved" is not defined. A temporary patch counts the same as a permanent repair.
- No evidence of work. Closures do not record location, asset, material or sign-off.
- Safety and repair are mixed. A barricade may close a ticket meant for a repair.
- Dashboards reward closures, not lasting fixes.
05 · The BIBD proposal
The redesign: engineering permanent fixes
A design to test. Not a claim of achieved outcomes.
A Shared Service Incident ID that links repeat complaints to one underlying failure.
A Resolution Contract defining what "fixed" means for each type of problem.
Evidence of work: location, asset, material, time and sign-off for every closure.
Temporary safety action kept separate from permanent repair.
Dashboards that reward fewer repeat complaints, not more tickets closed.
06 · Design + AI
Where AI helps, and where people decide
AI can detect recurring failures, flag weak closures and reveal hidden infrastructure priorities from complaint patterns.
Engineers decide how to fix the problem. Citizens confirm whether it stayed fixed.
07 · A testable next step
Start with one city's roads and drains
One city can pilot shared incident IDs and resolution contracts for roads and drains for a year. Our planning estimate is ₹40 to 60 lakh.
The measures that matter are repeat complaints for the same asset, time to permanent fix and citizen-confirmed resolutions.
08 · Who must act
What each of us can do
| Citizens | reopen a complaint if the problem returns, and mention the old complaint number. |
|---|---|
| DARPG | add repeat-complaint tracking to CPGRAMS. |
| State grievance cells | define what "resolved" means for common problems. |
| Municipal corporations and engineering departments | record evidence of work for every closure. |
| Elected representatives | ask for repeat-complaint data, not only closure rates. |
09 · The Perspective
Fixed means fixed
A grievance system should be judged by how few people need to complain twice. That requires data that tracks the problem, not just the ticket.