Stop treating closed resident requests as proof of service delivery. Those counts collapse once the system drops any obligation to confirm the fix survived the first complaint cycle.
Local councils now route every lodged issue through a single workflow that flags completion the moment a contractor uploads a photo or a status note. No second field visit, no resident callback, and no cross-check against the original defect description is required before the case is archived.
The result is a growing stack of reopened tickets that never appear in monthly dashboards because each new lodgement receives a fresh identifier. Procurement teams still meet their key performance indicators while the same pothole or drainage fault cycles through the queue.
Vendors optimise for the closure event itself. They allocate resources to high-visibility jobs that trigger quick sign-off and leave lower-priority assets untouched until volume metrics force attention elsewhere.
Accountability evaporates further when external contractors control the case-management platform. Their reporting layer only surfaces the final status code, never the time elapsed between closure and the next resident report on the same asset.
Councils that want credible numbers must insert an independent verification gate before any case can be marked resolved. That gate needs its own budget line and separate reporting line outside the primary contractor.
Without it, published service statistics continue to describe an operating model that exists only inside the ticket system, not on the streets residents actually use.