Opens in a new tab

Environmental Work

Environmental fieldwork starts with the next check-in.

Surveys, environmental inspections and reclamation work can take people into changing terrain. Agree how the worker stays in touch and what your team does when a check-in is missed.

24/7 human monitoring is included. Your organization maintains its emergency arrangements.

Field worker recording observations among trees
Illustrative field setting.

The working context

The field plan can change while the work continues.

Surveys and inspections can take people through forests, wetlands or reclamation areas. Make contact arrangements part of the field plan.

Survey and observation work

Plan the working period and expected check-ins before the worker heads into the field. Review the task and terrain when assessing suitability for lone work.

A changing route or task

Follow the organization’s procedure when plans change. Do not assume the available communication path stays the same across the working area.

Distance from nearby colleagues

Make the responsible contacts and follow-up arrangements practical for the working location. Monitoring does not establish a rescue or dispatch service.

Check-ins and follow-up

Plan check-ins and follow-up before heading out.

Keep the check-in interval, supported equipment and follow-up arrangements together.

  1. Before entering the field

    Agree the task, working period, check-in interval and Emergency Contacts.

  2. As plans change

    Update Contact Notes when terrain, tasks or expected coverage change, and adjust the check-in interval as risks change.

  3. If a check-in is missed

    A Be Safe Operator manually calls and messages the worker, using the ERP Group’s response instructions and coordinating with the Emergency Contact as needed after a missed check-in in the field.

  4. Keep your Emergency Contact involved

    A Be Safe Operator uses your response instructions and can continue coordinating with your Emergency Contact by phone.

Confirm the available settings and exact worker actions for your setup. An interval does not establish legal compliance. Confirm monitored events, Be Safe Operator actions and service boundaries.

Connectivity and equipment

Take the communication plan into the field.

Review the exact worker actions and communication path. A remote location does not mean every app action uses satellite.

The phone's role

The app is optimized for low bandwidth and can support core functions over satellite cellular data with a compatible phone and service. Confirm supported actions and plan for unavailable connections. App actions do not automatically switch to SMS.

Linked communicators

Confirm supported hardware, actions, subscriptions and location behavior. Geography, sky-view and service availability limits apply; communication is not guaranteed.

Two-way conversation

During escalation, a Be Safe Operator can initiate two-way phone SMS or linked-communicator conversations depending on equipment and service. This is not automatic app failover or delivery confirmation.

Supported actions and location information depend on the equipment, service and subscription. Check compatibility for your exact devices.

Review equipment and connectivity

The supervisor's side

Use location context with its limits in view.

Review supported last-location and device-power information with authorized users.

Availability, refresh behavior and permissions vary by device and integration. The map may show the last available location; it does not establish live connectivity.

Keep contacts ready

Keep the primary and secondary Emergency Contacts for the worker's ERP Group current.

Review the working period

Discuss available shift reports and map archives for your team. Fields, access and retention depend on your setup.

Before choosing a setup

Review the setup for the actual fieldwork.

  • Which worker actions are supported on the proposed communicator and subscription?
  • What happens when the planned communication path is unavailable?
  • What location refresh behavior and record access are actually available?
Explore the Be Safe program

Keep the field procedure with the people who know the work.

Assess task and terrain suitability. Maintain training, supervision, emergency planning and primary and secondary Emergency Contacts. Be Safe does not replace arrangements for isolated work or unavailable communication.

When escalation is needed, the Be Safe Operator uses the response instructions and Emergency Contact order configured for the worker’s ERP Group. Urgent situations may require emergency services. The Be Safe Operator continues managing the alarm until an Emergency Contact accepts responsibility and can continue coordinating by phone.

Review the records

Discuss available shift reports and map archives for the field working period. Be Safe Operators record response actions and outcomes in the Be Safe Activity Log. Available fields, access and retention depend on your setup. Records support review; they do not prove compliance.

See how records support follow-up

Be Safe supports a work-alone program. It does not guarantee compliance, communication, emergency dispatch, rescue or outcomes.

Common questions

Before heading into the field.

Can we assume every app action works through a satellite link?

No. Confirm the exact supported worker actions, hardware, subscription and location behavior. Conversations initiated by a Be Safe Operator do not mean every app action automatically switches connections.

Does the map show a worker’s current connection?

No. Authorized users can review supported last-location and device-power information, but it does not show live connection status. Availability and refresh depend on the device and permissions.

What should we agree before an isolated field visit?

Review task suitability, check-in settings, supported communication, maintained Emergency Contacts and coordinated follow-up. Be Safe does not guarantee communication, emergency dispatch, rescue or outcomes.