Election asset tracking should be designed as a supporting operational layer. It can provide location and movement context, but it must not be presented as a replacement for the statutory, procedural and physical controls governing ballot boxes and election materials.
Start with the established process
The Electoral Commission’s guidance for candidates and agents explains that Returning Officer staff deliver ballot boxes from polling stations to the count venue, check them in as they arrive and then verify ballot papers against the relevant ballot paper accounts. That sequence already has defined responsibilities and records.
The Commission’s UK Parliamentary election count guidance describes delivery, check-in and verification as distinct stages. Any digital visibility service must fit around those stages rather than create a competing custody process.
The operational question between departure and arrival
After polling closes, multiple teams and assets may move from distributed polling stations towards one or more receiving locations. The formal arrival and verification processes remain in place, but an operations team may still need a shared answer to practical questions while movement is underway:
- Which tracked assets have started their journey?
- Which are moving towards the expected destination?
- Which have reached the relevant operational site?
- Which have not reported recently and require a proportionate check?
- What movement history is available if an exception needs review?
Without a common view, routine status checking can depend on calls and messages from people who are already carrying out time-critical responsibilities.
What a digital visibility layer can add
An ATLAS tracker travels with an agreed physical asset and reports its available location through the platform. Authorised users can see the latest reported position, last-seen time and relevant site context. Historical reports can provide a chronological view after the event.
The value is not that the map becomes the election record. The value is that an operations team has an additional source of timely information and a movement history it can use when deciding whether to make contact or investigate.
Design the dashboard around exceptions
A useful view should help the team distinguish normal progress from situations that need attention. Sites and geofences can give locations operational meaning. Last-seen information can make data age visible. Search and filtering can help staff focus on the relevant polling station, asset or destination.
The response to any apparent delay or route difference remains an operational decision. Tracking information may be delayed or inaccurate, and staff should follow the organisation’s approved escalation and election procedures.
Keep the assurance boundary explicit
Location information shows the reported position of the tracker, not independent proof of every physical handover or the contents of a ballot box. Mounting, handling and exception processes should therefore be agreed before deployment.
Questions to settle before election day
- Which physical assets will carry trackers?
- How will each tracker be associated with the correct asset and polling station?
- Which operational sites and destinations need to be defined?
- Who can see live data and who can review history?
- What does the team do when an update is old, missing or unexpected?
- How will tracking sit alongside existing transport, handover and verification instructions?
- What information should be retained, for how long and under which approved policy?
Answering those questions turns a technology deployment into an operationally usable supporting service.