Panchkula’s pothole complaints have exposed a deeper failure in the way municipal grievance systems measure resolution. At least 10 complaints on Haryana’s Mhari Sadak app were reportedly closed with identical remarks and photographs that continued to show damaged roads, while the responses acknowledged that some locations required recarpeting. The episode raises a basic but consequential question for urban governance: when does a complaint count as resolved?
The reported problem is not limited to the condition of individual roads. It concerns the chain linking citizen reporting, departmental inspection, repair decisions, evidence collection and administrative closure. If a complaint is closed because work is promised for a later date, or because patchwork is said to be under way, the digital record may show activity without demonstrating that the hazard reported by a resident has actually disappeared.
That distinction matters because grievance applications are increasingly being used as public interfaces for municipal administration. Their value depends on more than accepting complaints. A functioning system must allow residents and officials to establish what was reported, which department assumed responsibility, what action was taken, when it was taken and whether the original defect was rectified. In the cases reported from Panchkula, complainants said the closure process did not provide that chain of evidence.
The Mhari Sadak app was launched statewide by Haryana chief minister Nayab Singh Saini in October last year. At the time, the chief minister said that once complaints were registered, road repair or strengthening work would be initiated immediately by the concerned department, with time-bound monitoring to ensure accountability. The complaints described in the report put that commitment against the practical experience of residents who said their cases remained unresolved even after a month.
The standard response cited in the complaints said that the road required recarpeting, that regular patchwork was being carried out to make it motorable, and that the complaint was a duplicate because there were numerous complaints about the same location. This wording appears to combine three separate administrative positions: the defect is recognised, temporary maintenance is being undertaken, and the complaint can be closed as repetitive. Each position may have a legitimate place in a road-maintenance system, but together they create uncertainty about whether the reported location has been inspected and whether the immediate risk has been addressed.
A duplicate complaint is not necessarily a resolved complaint. Multiple reports about one road can indicate that a defect is persistent, visible to several users or not being addressed quickly enough. Treating repetition as a reason to close cases may reduce the number of open complaints without reducing the underlying road hazard. The reported cases therefore illustrate the difference between managing a workload on a dashboard and managing a physical problem on the street.
The geographic details cited by complainants further complicate the explanation that the cases related to the same location. The aerial distances recorded in the app reportedly ranged from 12.13 metres to 66.05 metres, and residents said the complaints concerned different roads and locations. These distances do not by themselves establish whether complaints were duplicates, but they show why individual inspection and location-specific records are important before cases are consolidated or closed.
Anik Gupta, a student and resident of Sector 15, said he had filed complaints about different locations in Sector 20 and received the same reply for all of them. He said the issues remained unresolved after a month and questioned why photographs uploaded to support the closures showed cracks, depressions and potholes. He also said some images showed broad views of streets or surrounding areas rather than close-up evidence of completed repairs.
That complaint goes to the evidentiary weakness at the centre of the reported episode. A photograph can document a site visit, but it does not necessarily document a repair. A wide image may show that officials reached a road while leaving unclear whether the reported pothole was filled, whether the surface was made safe, or whether the image corresponds precisely to the complaint location. Without a time, location reference and a clear before-and-after comparison, residents have limited means to verify the administrative claim of resolution.
Mohit Gupta, founder of Solution Box and another complainant, said that closing complaints on the basis of work promised for the future defeated the purpose of grievance tracking. He also pointed to identical remarks, including the same spelling errors, across all 10 cases as a reason to question whether the complaints had been assessed individually. These observations are allegations by complainants, not an independent finding about the app’s internal processes. However, they identify the precise checks that a credible grievance system would need to make visible: individual inspection, case-specific reasoning and evidence tied to the reported location.
The issue also reveals a tension between emergency road maintenance and capital roadwork. The response cited in the report distinguishes between regular patchwork intended to keep a road motorable and recarpeting that would address a larger surface failure. Those are different interventions, with potentially different budgets, approvals and timelines. A road may therefore remain open while awaiting recarpeting, but that should not automatically mean the complaint has been resolved. The system needs to show whether an interim safety measure was completed, what remains outstanding and when the larger work is scheduled.
This is where municipal administration becomes central. Residents do not usually distinguish between the municipal corporation, a roads department or another agency when reporting a pothole through a public app. They experience one road and one hazard. The administration, however, may divide responsibility across departments, contracts and maintenance categories. If those institutional boundaries are not reflected clearly in the complaint record, responsibility can become difficult to trace. A case may move from reporting to closure without giving the resident a clear answer about which authority is accountable for the next step.
The report said Panchkula residents sought the reopening of the complaints and individual inspections of the reported locations. They also called for time-stamped, geo-tagged close-up photographs showing both the defects and completed repairs, along with work orders and schedules for roads awaiting recarpeting. These demands describe a more verifiable model of digital governance, in which the application is not merely a channel for receiving complaints but a public record of the response.
The numbers in the report are modest but significant. At least 10 complaints reportedly received the same closure response, and no resolution was reported even after a month. The affected cases were not presented as one isolated image or one disputed exchange; they formed a pattern across complaints that residents said involved different roads and locations. The reported aerial distances, from 12.13 metres to 66.05 metres, also suggest that the question of duplication required closer examination rather than an identical administrative conclusion in every case.
The larger policy landscape is shaped by the promise of time-bound monitoring. Such a promise changes the meaning of a complaint closure. If the app is intended only to acknowledge that a department has received a report, closure may mean that the case has been transferred or reviewed. If it is intended to assure residents that a road defect has been addressed, closure should require evidence of completion or a clearly recorded interim action and deadline. The reported responses appear to leave that distinction unresolved.
This ambiguity has consequences for both public trust and infrastructure management. When residents see complaints closed while potholes remain visible, they may become less willing to use the system or more likely to submit repeated complaints. Repeated reporting can then be interpreted as duplication, creating a cycle in which unresolved defects produce more complaints and more complaints are used to justify consolidation. The result is a cleaner administrative dashboard but a less accurate picture of road conditions.
For the administration, the same problem can undermine planning. Complaint data can help identify recurring defects, unsafe stretches and areas where patchwork is failing. But that data becomes less useful when closure status reflects administrative action rather than physical outcomes. A road marked resolved may continue to require maintenance, while repeated complaints may be suppressed as duplicates. The quality of the database then affects not only individual grievance handling but also decisions about resurfacing, contracting and resource allocation.
The reported case does not establish that every closure on the Mhari Sadak app is improper, nor does it independently confirm the condition of each road mentioned. The municipal corporation’s commissioner, Vinay Kumar, did not respond to the Times of India’s request for comment. That leaves unanswered how duplicate complaints are defined, what evidence is required before closure, whether photographs are geo-tagged and time-stamped, and how complaints awaiting recarpeting are meant to remain visible to residents.
Those unanswered questions are more important than the wording of any single reply. The effectiveness of a civic technology platform is ultimately determined on the street. A complaint system can process thousands of reports, assign them to departments and produce closure statistics, but its public value depends on whether the record corresponds to the condition residents encounter. In Panchkula, the reported pothole closures show what happens when the administrative definition of completion is not clear enough to be tested against physical evidence.
The immediate developments to monitor are whether the complaints are reopened, whether the reported locations receive individual inspections, and whether the authorities publish repair evidence, work orders or schedules for roads awaiting recarpeting. Until those steps are documented, the central issue remains unresolved: the app may be recording the movement of complaints, but the available evidence does not show that the reported road damage has been repaired.
