Managing field teams remotely is a different job from managing a team in the office. The team is not in front of you; you know where people are, which job has reached which stage and whether someone is in trouble only as far as the information that reaches you. If that information arrives irregularly, management is irregular too: the same question gets asked five times, one task lands on two teams at once, a fault is heard about hours later. In this article we split remote management into four parts: roles and chain of command, check-ins, task and location visibility, and records. At the end we explain how that arrangement stays standing in the field when there is no network.
In short
- Remote management is not a piece of software but an arrangement: who reports to whom, at what interval people check in, how tasks are assigned, what gets recorded.
- The US National Incident Management System (NIMS) recommends that each person reports to only one person, and gives one supervisor to five subordinates as a guideline for span of control.
- The UK Health and Safety Executive (HSE) asks for regular contact with lone workers at pre-agreed intervals and a reliable system to confirm they have returned to base once the task is done.
- Türkiye’s Law No. 6331 on occupational health and safety requires the employer to set up the organisation, monitor whether measures are followed and prepare an emergency plan; in a remotely managed team these duties are met through the communication arrangement.
- If check-ins depend on the network, management stops when the network does; channel selection is part of the arrangement.
Why is managing a field team remotely hard?
A field team is scattered by definition: the line maintenance crew is under a pole, the search team is in a valley, the security officer is at the far end of the site. A 2021 study on planning and monitoring field employees, published in the Beykent University Journal of Science and Engineering in Türkiye, states the problem plainly: managing field employees and their tasks is difficult in most organisations, because the workforce is spread over different geographical areas and organisations have trouble communicating work plans to employees. As a remedy the study proposes a system that schedules tasks, records the data obtained while tasks are carried out and enables work performance to be tracked.
Those three verbs are the core of remote management: communicate, record, track. The manager sends plans and tasks to the field; the field sends status and location to the centre; information in both directions is recorded; the manager tracks the work by looking at the record. If any link in that flow breaks, management falls back on the phone and on memory.
Structure first: roles and chain of command
The first decision in remote management is not the tool but the structure. Who reports to whom? If a team member receives conflicting instructions from two different managers, even the best application will not help. The 2017 National Incident Management System (NIMS) document of the US Federal Emergency Management Agency, FEMA, settles this with two principles. Chain of command is the orderly line of authority within the incident management organisation. Unity of command means that each individual reports to only one person; the document says this clarifies reporting relationships and reduces the confusion caused by conflicting directives.
The second decision is how many people one manager directs. According to NIMS, the optimal span of control for incident management is one supervisor to five subordinates; but the document adds that this is a guideline and that effective incident management frequently requires ratios significantly different from it. Among the factors that influence span of control it lists the type of incident, the nature of the task, hazards and safety factors, the experience of the supervisor and subordinates, and communication access between the subordinates and the supervisor. In other words, the weaker the communication, the smaller the team one person can safely manage.
The fact that NIMS builds its organisation in a modular way is also a practical lesson for remote management: the structure expands or contracts with the size of the incident, and responsibility for a function stays with the next higher supervisor until it is delegated. In a small operation a single coordinator is enough; as the operation grows, team leaders are placed in between and the coordinator talks to them. For transfer of command, NIMS asks for a briefing that captures the information needed to continue safe and effective operations, and for all personnel involved to be notified. The fact that the manager is also being handed over at shift change is a detail most organisations skip. We covered the chain of command in a crisis in more depth in our article on communication in crisis management.
Check-ins: who reports, when and how?
Once the structure is in place, the next thing is rhythm. If you do not decide in advance when to expect word from a field team, silence has no meaning: is the team quiet because it is fine, or because it cannot reach you? The UK Health and Safety Executive’s guidance on monitoring lone workers requires the employer to monitor lone workers and keep in touch with them, and the workers to understand the monitoring system and procedures in use. The methods it lists give the skeleton of a check-in arrangement:
- When supervisors should visit and observe lone workers,
- Knowing where lone workers are, with pre-agreed intervals of regular contact using phones, radios, email and similar means,
- Other devices for raising the alarm, operated manually or automatically,
- A reliable system to ensure a lone worker has returned to their base once they have completed their task.
In the same guidance the HSE asks for these systems and all emergency procedures to be tested regularly, and for the level of supervision to be based on the risk assessment: the higher the risk, the more supervision. In Türkiye, Law No. 6331 on Occupational Health and Safety points the same way. Article 4 of the law requires the employer to set up the organisation, provide the necessary tools and equipment, and monitor and supervise whether the measures taken are being followed. Article 19 obliges workers to notify the employer or the workers’ representative immediately when they face a serious and imminent danger or see a deficiency in protective measures. That obligation needs a counterpart in the field: a channel to report through, and someone listening at the other end.
The table below shows how check-ins can be defined for a field team. The intervals are examples; set your own values according to your risk assessment.
| Check-in | When | Content | If it does not arrive |
|---|---|---|---|
| Start-of-task notice | On arrival in the field | Location, headcount, planned finish | Manager calls after the planned arrival time has passed |
| Periodic status | At a pre-agreed interval | Status code, location, any obstacle | One missed interval: manager tries to reach the team; two: escalation |
| Task status change | When a task starts, is completed or is blocked | Task ID and new status | Task stays in its old state on the board, manager asks |
| Emergency alert | At the moment of danger | Alarm and location | If there is no receiver, the escalation plan kicks in |
| Return-to-base confirmation | When the task ends | Everyone is in a safe place | Search procedure for a team that has not confirmed |
The last column of the table is the real part of the arrangement. A check-in that has no consequence when it is missed is not a check-in.
Task assignment and status tracking
When a task is given verbally to a remotely managed team, two problems arise: the team may understand the task differently, and the manager cannot tell what stage it has reached. NIMS describes management by objectives in four steps: establishing specific, measurable objectives; identifying the strategies, tactics and tasks that will achieve them; developing and issuing assignments, plans and procedures; and documenting results against the objectives to measure performance and facilitate corrective action. The International Labour Organization’s guidelines on occupational safety and health management systems, ILO-OSH 2001, likewise ask planning to include defined responsibility and clear performance criteria indicating what is to be done by whom and when.
In practice this means that every task has an ID, an owner, a place and a status. Statuses are kept simple: assigned, started, completed, blocked. The person in the field reports a status change with a single tap; the manager sees all tasks in one list. The question “what happened to that job?” disappears, and at shift change the incoming manager takes over the list, not someone’s memory.
Location visibility: seeing instead of asking
The first item in the HSE’s lone-worker guidance is “knowing where lone workers are”. In remote management, location does two jobs. The first is safety: when an emergency alert comes in, you know where to send help. The second is coordination: you direct the nearest team to a new task yourself, and teams do not have to call around. Sharing location periodically and letting the manager see it on a map removes the question “where are you?”. We covered this in detail in our article on seeing where your team is.
Sharing location is processing personal data; put the purpose, the interval and the retention period into a written rule and inform the worker. Article 16 of Law No. 6331 already requires the employer to inform workers about the risks they may face, their legal rights and responsibilities, and the people assigned to emergency duties; the location arrangement is a natural part of that briefing.
Records and review
The fourth part of remote management is the record. ILO-OSH 2001 asks for performance monitoring not to be based only on injury and incident statistics, to include both active and reactive monitoring, and to be recorded. Active monitoring means following whether plans and established criteria are being met: did the check-ins arrive on time, were tasks completed within the planned time? Reactive monitoring is the identification, reporting and investigation of incidents, losses and system failures. The guidelines also ask for arrangements for safety and health communication: receiving, documenting and responding to internal and external communications; passing information between the relevant levels and functions of the organisation; and receiving and considering workers’ concerns and suggestions.
The value of a record shows not while it is being kept but when something goes wrong. Who reported what, when and from where; to whom and when was the task assigned; how many minutes passed before the alarm was seen? These questions are answered with time-stamped records, not with screenshots and memory. We covered what to record and how in our article on operation data logging.
Does the arrangement collapse when the network drops?
Everything described so far runs over a channel. If that channel is the cellular network or the internet, the arrangement is only as resilient as they are. Rural line maintenance, tunnel and basement work, post-disaster search, crowded events: in all of these the channel can fail at exactly the moment the check-in is needed. This is why the HSE’s lone-worker guidance lists alarm devices alongside phones and radios and asks for procedures to be tested regularly; Article 11 of Law No. 6331 likewise requires the employer to assess emergencies in advance, prepare emergency plans and keep the teams ready at all times.
When setting up a remote management arrangement, ask for every check-in: “if there is no network, how does this information get through?” The answer may be voice radio; radio is indispensable for voice coordination, but it does not carry location and task status by itself and leaves no record. Device-to-device mesh networks carry written messages, location and status information without a base station, and can switch to the internet when the network comes back. We explained how that switch works, with diagrams, in our article on hybrid communication. Radio and the written channel stand side by side, not in place of each other.
Step by step: setting up a remote management arrangement
The sequence below scales from a small maintenance crew to a multi-team operation:
- Risk assessmentArticle 10 of Law No. 6331 obliges the employer to carry out, or have carried out, a risk assessment. Which team is left alone in which area, which job has no coverage, in which task do minutes matter? Derive your check-in intervals from this.
- Roles and reporting lineEach person reports to only one person. Limit the number of people one manager directs according to communication conditions; put team leaders in between where needed.
- Check-insDefine the start-of-task, periodic status, task status, emergency and return-to-base check-ins. For each one, write the “if it does not arrive” line and set the escalation chain.
- Task templateEvery task gets an ID, an owner, a place and four statuses. The person in the field reports the status; the manager sees the list.
- Location ruleWrite down the interval at which location is shared, who sees it and how long it is kept; inform the worker.
- Channel planSet a primary and a backup channel for every check-in. State explicitly whether the backup channel works independently of the network.
- Records and reviewDecide where message, task and location records are kept and who can access them. After every operation or shift, review missed check-ins and alarms that were seen late.
- ExercisesRehearse the missed check-in, lost contact and network outage scenarios regularly. ILO-OSH 2001 asks for regular exercises in emergency preparedness, and the HSE for monitoring systems to be tested regularly.
Our approach
When we designed BosNets, we thought of the manager’s screen and the field team’s pocket as the two ends of one arrangement. The browser-based BosLog management interface works as the coordination centre’s screen: who is where, which task is at which stage, which message was delivered when. The team in the field uses BosApp to send written messages, share location, see the team on an offline map and, if needed, raise an emergency alert. A task defined in BosLog reaches the field team’s BosApp screen over the network; its status is tracked, and at the end of the shift the communication and task record can be reported.
We made it a core choice that check-ins should not depend on the network. Where there is coverage BosApp works over the internet; where there is none, the BosMag device that attaches magnetically to the phone builds a mesh network, and the switch is automatic. Because team locations travel over the mesh, live tracking on the map continues without a network. BosLog works as long as it is connected to the network; that connection can be over the internet or over the mesh through a BosBase placed at the operations centre. All communication is archived with timestamps; when a private closed network is set up, records are kept on the organisation’s own server and the organisation sets the access rights.
We do not aim to take the place of radio; voice coordination is radio’s job. We carry the information a manager should see without asking, that is location, task status and written messages, on a network that leaves a record.
— Emir Tanrıver, BosNets co-founder
Frequently asked questions
How often should I ask a field team to check in?
There is no single correct interval. The HSE asks for the level of supervision to be based on the risk assessment, with more supervision where the risk is higher. Shorten the interval for lone work, areas with no coverage or hazardous tasks; what matters is that the interval is agreed in advance and that what happens when it is missed is written down.
How many teams can one manager direct?
NIMS gives one supervisor to five subordinates as a guideline for incident management and notes that it can vary with the type of incident, the nature of the task, experience, and communication access between the supervisor and subordinates. If communication is weak, lower the number or put team leaders in between.
Does location tracking violate workers’ privacy?
Where the purpose, interval, retention period and access rights are set out in a written rule and the worker has been informed, location sharing for safety purposes is a common practice. Set the rule together with your legal team, switch sharing off outside working hours and open the record only to authorised people.
We have voice radio; why do we also need a written channel?
Radio is indispensable for voice coordination and BosNets does not take its place. The written channel carries location and task status by itself, reaches a person who was not listening at that moment, and leaves a time-stamped record. The two complement each other.
Sources
- FEMA: National Incident Management System, Third Edition (October 2017), “NIMS Management Characteristics” section
- HSE (UK): Lone working – Training, supervision and monitoring
- HSE (UK): Manage the risks of working alone
- Law No. 6331 on Occupational Health and Safety (Official Gazette of Türkiye, 30 June 2012, no. 28339), articles 4, 10, 11, 16 and 19 (in Turkish)
- ILO: Guidelines on occupational safety and health management systems, ILO-OSH 2001 (Geneva, 2001), sections 3.6, 3.8, 3.10.3 and 3.11
- Özdenizci Köse et al.: A Scheduling System for Enhancing and Monitoring Work Performance of Field Employees, Beykent University Journal of Science and Engineering, 14(1), 2021