An issue is not resolved because you clicked resolved
Closure rates are the easiest civic metric to improve and the least meaningful. What it takes to make resolution mean something.
Civiq.plus research · Service delivery
If you measure a team on closure rate, closure rate improves. This is not cynicism about public servants; it is what happens to any metric that is easier to move directly than indirectly. The status field is one click away. The water line is a procurement cycle away.
The result is a familiar pattern: a dashboard showing ninety-one percent resolution alongside a helpline receiving the same complaint from the same street for the fourth month running. Both numbers are accurate. Only one of them describes the world.
Separating the claim from the evidence
The fix is not a better metric. It is making the claim expensive to make falsely. In Civiq.plus, where the issue category warrants it, moving to closed requires two things that a dropdown does not provide: documentary evidence submitted by the resolving team, and an independent field or citizen verification.
That second requirement is the one that does the work. Evidence submitted by the person claiming completion is a photograph of whatever they chose to photograph. Verification by someone who was not responsible for the fix is a different kind of statement.
Reopening has to be cheap and visible
The counterpart to expensive closure is cheap reopening. If a citizen reports the same problem in the same place, that should reopen the cluster rather than create a new one — and the reopened issue must preserve its complete history, including the earlier closure and who signed it.
This matters because recurrence is a different signal from incidence. A ward with forty new issues is busy. A ward with forty reopened issues has a systemic problem, and averaging them together destroys exactly the information you needed.
Communication is not a corrective action
The platform deliberately supports corrective actions that are not communication: service escalation, field verification, a local meeting, administrative follow-up. This sounds obvious. It is worth stating because the alternative is extremely common — an issue is detected, a message goes out explaining the situation, and the message is recorded as the response.
Communication has a place in the loop, but it comes after the action and describes what was verified to have happened. It is never the default substitute for solving the underlying problem, and the state machine is ordered so that communicated comes after field verified rather than instead of it.
What this costs
Closure rates go down when you introduce verification. They should — the previous number was measuring something else. Teams find this genuinely difficult in the first quarter, and the honest framing is that the earlier number was never real, not that performance has fallen.
The number that goes up is recurrence-adjusted resolution, and that one is worth defending in front of a council.
