Utility Lone Worker Safety FAQ: Communications, Check-Ins, and Emergency Response

Utility lone worker safety combines task-specific policies, worker preparation, reliable check-ins, suitable communications, and a documented response process. Technology can support worker visibility and emergency coordination, but it does not replace hazard assessment, staffing requirements, job briefings, training, or qualified human response. 

This guide is for utility safety, field operations, emergency management, dispatch, information technology, and procurement teams evaluating how to support employees across remote infrastructure, isolated facilities, large service territories, and areas with inconsistent cellular coverage. 

Table of Contents 

Key Takeaways 

What Does Lone Worker Safety Mean in Utility Operations? 

Utility lone worker safety is the set of policies, procedures, communications, and response measures used when an employee works without nearby direct assistance. The controls required depend on the task, the hazards involved, applicable regulations, and the utility’s own policies. 

A lone worker is not necessarily far from a facility or populated area. An employee may be considered alone when no qualified person is close enough to provide direct assistance. Conversely, an employee working in a remote location may still be part of a crew and may not meet the organization’s definition of a lone worker. 

Are Utility Employees Allowed to Work Alone? 

Utility employees may work alone in some situations, but the answer depends on the task and applicable safety requirements. A phone, mobile application, or satellite communicator does not make otherwise prohibited work permissible. 

The Occupational Safety and Health Administration’s 29 CFR 1910.269 applies to specified work involving electric power generation, transmission, and distribution. Certain work on or near exposed energized parts requires at least two employees, subject to defined exceptions. The standard does not create one universal working-alone rule for every employee at every electric, gas, water, or wastewater utility. 

Permit-required confined-space work also has separate attendant, communication, and rescue requirements. Utility organizations should review all applicable federal, state, local, and company requirements with qualified environment, health, and safety or legal personnel. 

How Is Remote Work Different From Lone Work? 

Remote work describes the location or operating environment. Lone work describes the employee’s access to nearby assistance. 

The organization should base its controls on the task, hazards, operating environment, and available support rather than distance alone. 

What Should a Utility Lone Worker Safety Program Include? 

A utility lone worker program should define eligible tasks, communication requirements, check-in rules, escalation responsibilities, training, and review procedures. It should also explain what employees must do when a device fails, communication becomes unavailable, or the work can no longer continue safely. 

A practical program connects five layers. 

1. Policy 

The policy establishes which employees, tasks, and locations are covered. It should distinguish among: 

The policy should also define terms such as lone worker, remote worker, check-in, missed check-in, and emergency alert. 

2. Preparation 

Before work begins, the utility should assess the task, environment, communication conditions, and available response options. 

Preparation may include a job briefing, confirmation of the assigned work area, equipment checks, and an expected completion time. It should also identify the primary communication method and the action required if that method becomes unavailable. 

A routine inspection and a higher-risk response near energized equipment should not automatically use the same check-in interval or escalation threshold. 

3. Connection 

The communication plan explains how the worker and the organization will exchange routine messages, status updates, and emergency information. 

Depending on the environment, approved methods may include cellular service, Wi-Fi, radio, a dedicated satellite communicator, or compatible direct-to-device satellite service. The plan should identify the preferred method, available alternatives, and the procedure to follow when no approved path can be used. 

4. Awareness 

Operational awareness may include the worker’s reported status, completed or missed check-ins, available location information, assignment details, and active alerts. 

These data points should be interpreted together. A recent map location without a status update does not confirm that a worker is safe, and a completed check-in does not prove that the work area is free of hazards. 

5. Response 

The response layer defines who receives an exception or emergency alert, what that person does, when the issue is escalated, and how the event is closed.

The Environmental Protection Agency provides emergency-response planning, incident-action, and telecommunications resources for drinking water and wastewater utilities. Its guidance recommends including communication plans and telecommunications technologies within emergency response planning. 

The utility should train employees on the complete process, test it under field conditions, and review incidents or false alarms for potential improvements. 

How Do Mass Notifications, Check-Ins, Messaging, and Alerts Support Field Safety? 

Check-ins confirm expected worker status, messaging supports routine coordination, and alerts identify conditions that require attention. Each function needs a defined recipient and an expected human action. 

Using more than one possible communication path can improve resilience, but it does not guarantee uninterrupted communication. 

How Do GPS Visibility and Geofencing Support Utility Response? 

GPS visibility can help a response team understand a worker’s reported or last transmitted location. Geofences can identify when a device enters or exits a defined area.

Both depend on the device, signal, transmission status, and configuration. They provide operational context but do not confirm a worker’s condition or guarantee precise, continuous tracking. 

What Does a Location Point Tell Dispatch? 

A location point can show where a device reported its position and when the information was received. It becomes more useful when viewed alongside the worker’s assignment, last check-in, available device status, and recent messages. 

Dispatch should distinguish between a recent location and a last known location. An updated map point may be delayed or unavailable when a device cannot determine or transmit its position. 

The Duty of Care Dashboard, which links back to the Hub, presents operational views that include active geofences, completed check-ins, missed check-ins, factal news alerts, and SOS alerts. Exact information depends on the customer’s configuration. 

How Can Utility organizations Use Geofences? 

A geofence is a virtual boundary placed around a defined area. A utility may use one to add context around facilities, work zones, service territories, or restricted locations. 

A geofence is not a physical barrier. An entry or exit notification does not prove that a worker completed a task, followed a procedure, or avoided a hazard. 

Utility organizations should also define who can view location data, when monitoring applies, and how long the organization retains the information. Privacy, labor, and access requirements should be reviewed before deployment. 

What Should Happen After a Missed Check-In or SOS Alert? 

A missed check-in or SOS should begin a documented, role-based process. The assigned recipient should review the available information, attempt contact, and escalate according to defined thresholds. 

What Happens After a Missed Check-In? 

A utility may structure the process as follows: 

A missed check-in should receive prompt attention, but the procedure should not treat every missed response as confirmed injury or distress. 

Who Receives an SOS Alert? 

The customer’s configured service and contractual arrangement determine who receives and manages an SOS alert. 

An SOS response may come from the customer’s emergency personnel or the Garmin SOS Monitoring Center, depending on the contract. The monitoring service may act as a liaison with the appropriate emergency response center. 

An approved SOS workflow should identify: 

An SOS alert confirms that the SOS message has been received by the system and begins the configured response process. Response timing and outcome depend on the configured escalation process and available response resources. 

How Does EVERYWHERE Support Utility Field Operations? 

EVERYWHERE Communications supports utility field operations by bringing supported communications, personnel status, check-ins, location information, and alerts into the EVERYWHERE Platform. 

The EVERYWHERE Hub provides a web-based operational interface, and the EVERYWHERE Mobile App supports field communications and check-ins. Supported Garmin inReach products provide a dedicated satellite hardware option for applicable deployments. 

Together, these components can support: 

The exact functions available depend on the selected products, devices, services, and configuration. 

EVERYWHERE does not determine whether a utility task may be performed alone. The platform supports the communication, monitoring, and escalation procedures established through the utility’s safety and operations program. 

Does EVERYWHERE Support Lone Worker Safety? 

Yes. EVERYWHERE supports lone worker safety procedures through capabilities that include scheduled and self-initiated check-ins, messaging, available location information, geofencing, missed check-in notifications, and configurable SOS workflows. 

These capabilities do not replace hazard assessment, required staffing, worker training, emergency planning, or applicable regulatory obligations. The utility should define what each status or alert means before configuring the technology. 

Can the Platform Integrate With Existing Systems? 

The EVERYWHERE Platform supports selected integrations with approved devices, mapping tools, communications technologies, and intelligence services. Exact compatibility depends on the system and deployment requirements. 

The EVERYWHERE Hub includes Esri ArcGIS as a mapping and analysis integration. Other integrations support risk intelligence, messaging, tactical coordination, mesh networking, and specialized operational uses. Not every integration will be relevant to a utility deployment. 

Utility organizations should confirm: 

Review the current EVERYWHERE technology integrations and verify specific requirements before assuming compatibility. 

How Should Utility Organizations Evaluate a Lone Worker Safety Platform? 

Utility organizations should evaluate technology against the full operating process, not a list of features. The review should cover operational fit, field communications, alert ownership, location behavior, integrations, governance, training, and fallback procedures. 

Security, encryption, compliance, and technical architecture should be assessed through current product documentation and direct technical review rather than inferred from general marketing language. 

How Should a Utility Organization Test the Platform? 

Run a controlled pilot using representative workers, locations, and operating conditions. The pilot should include: 

The pilot should identify limitations as well as successful functions. 

The EVERYWHERE utility case study describes a utility organization operating across metropolitan and off-grid regions. The organization used a common platform to address manual check-ins, limited communications from legacy satellite devices, and fragmented emergency coordination. 

Key Takeaways for Utility Safety and Operations Teams 

Utility lone worker safety begins with task-specific policy and ends with a tested response process. 

Communications, check-ins, location information, and SOS functions can support that process when the organization understands their limitations. Utility organizations should assign alert owners, test representative field conditions, and document what workers must do when communications fail. 

Technology is most useful when it supports a clearly defined procedure rather than becoming the procedure itself. 

Related Resources 

Utility organizations should select technology only after defining the work, communication requirements, and response process it must support. 

Discuss your utility field communication requirements with EVERYWHERE Communications.