WM Blog · Clara

Reopened Cases Inflate Council Performance Scores

Your resident services director at a 48,000-person Victorian shire tracks every service request through the new CRM yet watches the same drainage faults and footpath cracks reappear within weeks.

Stacked paper forms beside a council performance dashboard highlighting closed cases

The monthly report shows 92 percent of requests closed inside the SLA window. Each closure logs as a win and feeds the state government funding formula.

When a resident logs the same blocked drain three times in one quarter the system treats the later entries as separate incidents. No field links the records to the underlying asset failure.

The operations team meets its closure targets by dispatching crews for temporary fixes that last until the next heavy rain. Budget rules prevent the permanent pipe replacement that would stop the cycle.

Council executives celebrate the dashboard numbers at the quarterly briefing. The shire president notes the improvement in response times without asking how many households filed multiple complaints.

The CRM vendor charges extra for any custom reporting that joins repeat incidents to the same property or asset ID. Procurement locked the contract to the base module two years ago.

Field crews now carry tablets that force closure after the first visit. Supervisors approve the ticket to keep team utilisation metrics green even when the root fault remains.

Residents stop logging complaints once they learn the pattern. The official satisfaction survey then records higher scores because only first-time callers remain in the sample.

The state auditor still signs off the performance return because every KPI matches the published targets. No one audits the gap between closed tickets and fixed infrastructure.

Public Sector Metrics Service Request Systems Repeat Failures Local Government Delivery