Field Team Visibility: 2:10 p.m., and a Technician Isn't Answering

What is field team visibility? Field team visibility is an operations office's ability to see, during the working day, where field staff are, what job each is on, and what they've reported from site. Without it, dispatch relies on a morning plan that goes out of date within hours, and response time in an emergency depends on whether someone picks up the phone.

When a field worker goes quiet, assignment history, live status and location are operational context, not optional extras.

The dispatcher calls him at ten past two. No answer.

She calls again four minutes later. No answer. She sends a message. It never shows as read.

In front of her is the morning dispatch sheet: three visits under Khaled's name today. Where is he now?

The sheet answers a completely different question. It says where he was supposed to be at eight in the morning. Where he is now, after six hours of changes and delays and the emergency call-out added at ten, nobody in the office can say with any certainty. Not which of the three sites. Not whether he's at any of them.

So the dispatcher does what every operations office does at this moment: she calls the three customers one by one and asks whether the technician is with them.

01The seventy-five minutes in which nothing happened

At quarter past three, Khaled surfaces. His phone died in an underground substation room at the second site, where there's no signal to begin with. Nothing happened. He came up, found a charger, called in, and apologised for the trouble.

Incident over. It won't appear in any report, and nobody will mention it in a week.

But look at what was actually consumed in those seventy-five minutes.

A dispatcher who stopped doing everything else. Three calls to customers who learned, from the question itself, that their contractor doesn't know where its people are. An operations manager who went on alert and mentally prepared for a worse phone call. And a decision to postpone a fourth visit that could have been reassigned to another technician, had anyone known where the other technician was.

Most importantly: during those seventy-five minutes, if Khaled had genuinely been in trouble, nobody would have had anything to do other than exactly what they did. Call the customers.

The inability to respond wasn't a lapse in judgement. It was the default state the organisation operates in every day, and today it simply became visible.

Incidents where "nothing happened" aren't good news. They're free drills that reveal your actual response time, and then get forgotten before anyone acts on the result.

02You don't manage a field team. You manage reports about one

This is the part that's hard to say politely, so let's say it directly.

Most operations offices can't see the field. They see three documents about it: the morning plan, scattered phone calls during the day, and an end-of-shift report the technician writes from memory while tired.

The first loses accuracy at the first change, usually before half past nine. The second depends on the person being available and the phone working. The third arrives after the moment it could have informed any decision.

Between those three sits an eight-hour gap in which everything that matters happens: the delays, the rerouting, the visit that took twice as long, and the technician who was five minutes from an emergency call that got assigned to a colleague forty minutes away.

You're not short on discipline. You're short on the present tense. Everything you hold about the field is either the past or an intention.

03"This is surveillance": the objection that deserves a straight answer

This will come up in the first meeting, and it may well come from you. It deserves an answer with no evasion in it.

Yes: knowing an employee's location during working hours is information about that employee. Ignoring that, or wrapping it in soft language, is the fastest route to the app failing, because the team will understand exactly what's happening whatever it's called.

But put the question where it belongs. Khaled was already working under full visibility: the customer's, not his employer's. The customer knows precisely when he arrived and when he left. The organisation carrying legal and contractual responsibility for him is the only party that doesn't know.

And when his battery died in an underground room, visibility wasn't a tool against him. It was the only thing that would have let anyone reach him.

The difference between surveillance and protection isn't technological. It sits in three management decisions you make: that visibility is confined to working hours, that it's declared to the team rather than hidden from them, and that it's used for dispatch and safety rather than for policing coffee breaks.

Field teams accept the first framing and reject the second, and they're right on both counts.

04What you actually see

Tawasol's Tracking module shows where field teams are, what they're working on, and what they're sending back. Tasks go straight to technicians' devices, positions and task status update live, and an at-risk employee's position is available immediately.

Read that last point again, because it isn't a technical line. It's a liability line. An organisation that sends someone into a substation, a construction site or a remote station carries a duty toward that person that doesn't end when the work order is handed over. A duty you have no tool to discharge is a duty resting on luck.

At ten past two, the question you need answered isn't "where was he supposed to be?" It's "where is he?" This is a tool that answers the second one.

Before you read on, do this now. Pick three of your field staff and write down, on paper, where you think each one is at this moment. Then verify: call them, ask the dispatcher, or ask the customer. Start a timer from the first second. It takes twenty minutes at most, and you need nobody's help. The number on that timer is your real emergency response time, and the number of people you placed correctly is your field visibility rate. Those two figures are enough for a full meeting with your safety lead, and you produced them yourself in twenty minutes.

05The job goes to the device, not to memory

The other side of visibility isn't safety. It's economics, and it's the side that convinces the CFO.

When an emergency call comes in at eleven, how is it assigned? Usually to the name the dispatcher remembers and believes is free. That belief is built on the morning plan, which stopped being true two hours ago.

The result is a pattern that repeats daily in every field services business: a technician drives thirty kilometres to a job his colleague was four kilometres from, because nobody knew that at the moment it mattered. Nobody measures this cost, because it doesn't appear as a line item. It's spread across fuel, labour hours, and the fourth visit that didn't get done today.

When locations are visible on a map, the basis for the decision changes from memory to geography. The job goes to the nearest available person rather than the person who comes to mind first.

Then comes the step that closes the loop: the job is assigned directly to the technician's mobile device, and its status is tracked live.

Notice what that means in practice. Assignment is no longer a call that may or may not connect, or a message the office assumes was read. The job is on the technician's screen, and its status is visible to whoever assigned it. The office doesn't just know where the team is. It knows where the work itself has got to.

Optimise scheduling and allocation on that basis and you gain an extra visit per day from the same fleet and the same team. That extra visit is where the whole system pays for itself.

06A report that knows where it came from

Visibility without reporting is only half the picture, because half of what happens in the field needs a decision from the office.

In Tawasol, the technician submits a report from his phone with photos, video and GPS location attached, and selects a subject from a predefined list so the report routes to the right function. It lands in the central inbox on the dashboard with its category and location.

Look at the practical difference. The verbal report says: "the unit at the second site is damaged and I need a part." The same report through the app arrives with a photo of the model number, a photo of the fault, and the location fixed by coordinates. The first needs two phone calls and a second trip tomorrow. The second can be closed today, because the warehouse supervisor is already looking at the model number.

The responsible person replies inside the same thread, attaches what's needed, and closes it when resolved, moving it from active to closed.

And note where those reports, photos and location data go: into the organisation's own system, not into a messaging app on someone else's server. Photographs of customer sites, layouts and faults stay inside your infrastructure.

What you're left with at the end of the month is something you didn't have before: a record of what actually happened in the field, tied to locations and times, instead of a collective memory of a busy month.

07What the technician needs at that same moment

Everything above looks at the field from the office. Flip the direction, because visibility the technician gains nothing from is visibility the technician will resist.

On site, what he usually needs is one thing: the correct document. The installation spec, the safety procedure, the manual for a model discontinued two years ago. The Library puts those in his hand on his phone, organised into topics and searchable, instead of a call to a colleague who may or may not pick up.

Sometimes he needs a person rather than a document, and one-to-one and group chats put him in touch with the specialist directly, by text, voice notes, images or documents.

He needs to know about changes issued while he's out of the office, so management announcements reach his phone the same way they reach colleagues at head office. That alone answers an old complaint in every field team: that the people working outside are always the last to hear anything.

And he needs his safety training documented. Courses are organised through the Events module with dates and locations, he registers from the app, and a certificate is issued to everyone whose attendance is confirmed. When the safety auditor asks who completed confined-space training, the answer is a document rather than a guess.

08Replay 2:10

Now replay that day with all of this in place.

At ten past two the dispatcher calls and Khaled doesn't answer. She opens the dashboard. Khaled's current job shows as in progress at the second site, started at 1:40. She doesn't know his battery has died, but she knows the thing that actually matters: where to look.

She calls the site supervisor directly, one number instead of three, and gets an answer in four minutes: he's in the substation room, and there's no signal down there.

It's over at 2:14. No calls to customers, no alert, no seventy-five minutes.

And the emergency call that comes in at half past two is assigned to the technician six minutes away, not to the first name that came to someone's mind. The job lands on his device, and its status appears on the same screen.

If it had been something more serious than a dead battery, those four minutes would have been the entire difference.

09The day it isn't just a flat battery

This will recur in your organisation, because it recurs in every organisation with people working outside the walls. Most of the time the answer will be a flat battery, a site with no coverage, or a phone left in the van.

One time it won't be.

And the difference between a response that starts in minute four and one that starts in minute seventy-five is a decision you make today, on a quiet day, while reading a page.

The dispatcher did nothing wrong. She performed exactly to the limit of the tools in her hands, and those tools were a sheet of paper written at eight in the morning.

Send us one day's dispatch sheet for one field team (names, sites, planned times) and we'll return it as a written Field Visibility Gap Analysis: the hour of that day when the sheet lost contact with reality, how many jobs could have been assigned better had locations been visible, and what would have happened if one of those names had stopped answering at two in the afternoon. It's a document you can put in front of safety and operations together. Send it to info@it-blocks.com with "Field Visibility Gap Analysis" in the subject line.