Who Runs It Afterwards
The recurring work a location deployment generates, and what happens in the usual case where nobody was assigned to it.
The project ends at go-live. The system then generates work indefinitely, and in most deployments that work is unassigned.
The recurring work
Geofences: new customer sites added, closed sites removed, misfiring fences resized.
Devices: faults detected, replacements fitted, disposals handled.
Access: joiners, leavers, role changes, quarterly review.
Data quality: the four checks, and acting on them.
Retention: verifying deletion actually ran.
Vendor releases: checking what changed and whether anything arrived enabled.
Requests: subject access, incident exports, authorised investigations.
Totalled, this is a part-time role, and it is usually absorbed by a fleet manager who was not asked.
What goes wrong without an owner
Geofences drift out of date, so attendance events stop matching reality and nobody trusts the reports.
Faulty devices look like driver behaviour, which produces an unfortunate conversation.
Access accumulates. People who changed role three years ago still see the map.
Retention is never enforced, so the system holds a year of positions under a thirty-day policy.
Features arrive enabled in an upgrade and nobody notices.
None of these announces itself. They surface during a dispute or a request.
Naming the owner
One person, named, with allocated time.
With authority over configuration, or every change becomes a request to someone busier.
With a deputy, because the work does not pause for annual leave.
And with the standing to say no, which is most of the job in this category.
The runbook
How to add and test a geofence.
How to handle a gap investigation.
The four data quality checks and what each means.
The post-release check.
Who authorises an individual history lookup and how it is recorded.
Written so the deputy can follow it, which is the test.
What to report
Quarterly: coverage, geofence reliability, access review result, deletion verification.
Annually: did the measures the deployment was bought for actually move, is the collection still limited to the purposes, has the purpose limitation held, and would you deploy it the same way again.
The last question produces the useful decisions, and nobody asks it unless a process does.
The runbook test
One check that shows whether the runbook is real.
Can the deputy handle a geofence complaint and a gap investigation using it, without asking the owner?
Try it once, deliberately, while the owner is available to watch rather than help.
Whatever they had to ask is a gap, and it takes minutes to fill while it is fresh.
A runbook only its author can follow fails on the day it is needed.
Connect policy to configuration
The practical choices behind this note can be compared with the field-mapping example. Keep the written purpose in control of the setup, enable only the data needed and review the result with affected workers.