A maintenance truck idles at the kerb while its GPS beacon registers the job complete. The system marks the asset resolved and drops the case from the active register, even though the surface defect remains untouched.
Councils set closure on location data alone because it removes the need for manual verification. Contractors learn the pattern quickly and optimise routes around the ping threshold rather than the repair standard.
Repeat requests for the same segment never aggregate because each new report lands against a freshly closed record. The asset register shows improving response times while the physical inventory degrades.
Budget allocations then follow the false trend. Procurement locks in the next cycle of contracts on metrics that reward rapid pings over durable fixes.
Residents notice the pattern first when the same crack reappears after every wet season. Their follow-up calls trigger new tickets that the system treats as unrelated events.
Internal dashboards hide the loop because closure codes carry no link back to the original location coordinates. Programme reviews therefore approve the same delivery model without seeing the accumulating rework.
Change the rule so that closure requires an independent asset photo or follow-up inspection timestamped against the same GPS point. Only then does the register reflect actual condition rather than truck movement.