The topic of working in isolation is about workers getting into trouble while working alone and not being able to call for help.
When that happens, the primary goal is to find the person quickly. Therefore, the current location of a worker is the most valuable information in case of an emergency.
On the other hand, we do not want to track anyone.
In other words: the ideal system would transmit location information only when it is truly needed.
But what happens if, at the very moment of an incident, no network connection is available? It is even possible that the loss of communication occurs at the same time as the worker’s problem (for example crashes, power outages, etc.).
LoneComply’s Multi-Layer Approach
LoneComply uses a multi-layer approach to ensure that location information is available when needed while avoiding privacy violations as much as technically possible.
In summary: As long as an isolation proceeds as planned, location information cannot be accessed by anyone.
Technical Exception: For completeness, there is a technical exception that should be mentioned. Assume a worker starts an isolation that is configured to use geolocation. That isolation might have a life-tick period of 15 minutes. If the network connection breaks after 10 minutes and does not return, the worker may still attempt to send a life tick or end the isolation, but the server will not receive that information. In that situation, the supervisor cannot be certain that the worker is safe. Therefore, the system must assume the worst-case scenario and grant access to the location information once the 15-minute interval has passed.