Workers Who Move Between Sites

A worker visiting twelve addresses in a day is a different problem from one who arrives at a shop and stays.

Why it suits geofencing

Each site is a separate boundary, far apart, so error matters much less.

Arrival and departure at each is genuinely useful: it confirms the visit happened and how long it lasted.

And the alternative methods are harder — you cannot put a beacon in every client's home.

This is the strongest case in the category, and it is also the one where the collection quietly grows.

Where it grows

Twelve punches a day is twelve positions.

Add travel between them and it becomes a route, which is a different thing from attendance.

Products that track continuously between visits are collecting a day of movements to answer a question about twelve moments.

Ask what happens between punches, and require the answer to be nothing.

The client's home is not a workplace

A geofence around someone's house records that address in your systems.

Which is the client's personal data, and in care work frequently reveals that they receive care.

Store the client reference, not the coordinates, where the product allows.

And think about who can see the visit list, because a list of addresses a care worker attends is sensitive in both directions.

Lone working

Many of these roles are lone working, and the safety case is real.

But safety needs position on alarm, not a record of every visit.

Keep the two separate: attendance punches at visits, position available if an alarm is raised, and no continuous trail serving either.

A system that logs continuously and calls it safety is using a genuine concern to justify collection that safety does not need.

Travel time

Between visits is usually working time and is a common source of underpayment claims in care and cleaning.

Punch data can evidence it — departure from one site, arrival at the next — without needing the route in between.

Which is a use that favours the worker, and worth saying so when introducing it.

Check what your product calculates and whether the travel is paid.

The design that fits

A boundary per site, sized for that site.

Punches at arrival and departure only.

Nothing recorded between punches.

Client addresses held as references where possible.

Position on alarm for safety, separately.

This answers attendance, supports travel pay, and collects a fraction of what a continuous product would.

Nothing between punches

The requirement to state in the specification.

Twelve visits need twelve arrival points and twelve departures.

Not a route.

Ask the vendor what the app does between punches and require the answer to be nothing.

A product that logs continuously is collecting a day of movements to answer a question about twenty-four moments.

A concrete product reference

When translating this principle into a buying test, remote workforce management software provides a concrete workflow reference. Verify current behaviour in a trial and judge it against the purpose and limits above.

Independent reference

For an external point of reference, see the GSMA. Use this established source as an external check before turning the principle into a workplace rule.