Somewhere in your city, someone reported the pothole. They called a number, or filled a form, or told an official who happened to be nearby. They did the thing citizens are always told to do. They reported it. And then the most common thing in local government happened: nothing, for a while, followed eventually by either a quiet repair or a slow forgetting.
The reporting is the part everyone focuses on. Make it easy to report, the thinking goes, and problems will get solved. But reporting was never really the hard part. The hard part is everything that is supposed to happen after, and that is precisely the part most systems leave to chance.
The Gap Where Trust Goes to Die
Between a citizen reporting a problem and that problem being fixed, there is a stretch of invisible territory. The report has to reach the right department. Someone has to acknowledge it. It has to be assigned to a person who can act. That person has to actually act. And somewhere in there, ideally, the citizen who reported it should learn that any of this is happening.
In most places, that entire stretch is a black box. The citizen reports and then hears nothing. They do not know if the report arrived, if anyone read it, if it was assigned, or if it was quietly dropped. The silence is not usually malice. It is simply that no system exists to carry the report through those stages and back out to the person waiting. The complaint disappears into an organization that has no structured way to track its own promises.
That silence is expensive, and the cost is trust. A citizen who reports a problem and hears nothing does not conclude "the system is busy." They conclude "reporting is pointless." And once enough people conclude that, they stop reporting altogether, which means the government loses its cheapest, most valuable source of information about what is actually broken in the city. The gap after the report doesn't just fail one pothole. It slowly teaches an entire population to stop telling the government the truth.
Why This Is a Structure Problem, Not an Effort Problem
It is tempting to read unanswered complaints as a story about lazy or indifferent officials. Usually it is not. Usually it is a story about people trying to manage commitments they cannot see.
When complaints arrive across scattered channels, a phone line, a paper register, a WhatsApp number, a walk-in, and live in equally scattered places, no one holds the full picture. No one can see how many reports are open, how long they have been sitting, which are urgent, or which have quietly aged past the point of embarrassment. An official genuinely trying to do their job is working blind, responding to whatever is loudest that day rather than to what matters most. Things fall through not because nobody cares, but because nothing is holding them.
You cannot fix this with a campaign urging staff to try harder, any more than you can fix a leaking bucket by pouring faster. The commitments have to become visible before they can be honored. That is a structural change, not a motivational one.
What Closing the Gap Actually Looks Like
A civic system that takes the after seriously does a few unglamorous but transformative things.
Every report becomes a tracked item with a status, not a message that vanishes. From the moment it is filed, it exists somewhere with a clear state, whether received, assigned, in progress, or resolved, that both the government and the citizen can see. The report is no longer a shout into a void. It is an object moving through a process.
Accountability gets a name and a clock. Each item is assigned to someone, with a sense of how long it has been open. What has been ignored for two weeks stops being invisible. It shows up, plainly, as something overdue. Managers can finally see the shape of the workload, what is piling up, what is moving, where the bottlenecks are.
And the loop closes back to the citizen. The single most powerful thing such a system does is also the simplest: it tells the person who reported the problem what happened. Even a short "received, assigned to sanitation, expected within ten days" transforms the experience, because it proves someone is listening. A citizen who gets that acknowledgment stays a citizen who reports. That is how a government protects its own flow of information.
Reporting Is a Promise. Systems Are How You Keep It.
Every time a government invites citizens to report a problem, it makes an implicit promise: tell us, and we will do something. The invitation is easy to issue. The promise is hard to keep, and it is kept or broken entirely in the invisible stretch after the report is filed.
Most civic technology has focused on making the promise easier to make. The harder and more valuable work is building the structure that lets a government actually keep it, the structure that carries a complaint from a citizen's frustration all the way to a resolution they can see. Close that gap, and reporting stops feeling pointless. People start telling you the truth about your city again, because they have learned that telling you leads somewhere.
That structure, the system that turns scattered complaints into tracked, accountable, visible commitments, is exactly the kind of thing we build.
