← All insights

Stop Calling Drivers for Location Updates

I walk through a 30-day operating change I run with desks: replace location calls with trip tracking, using driver-shortage reality as the reason to redesign the control tower.

By Vishal · Updated 2026-09-11

I've told desks for years: calling feels free. It isn’t. Each location ping costs attention. With a reported shortage of more than two million skilled drivers, the remaining crew is already stretched. Adding “please share live location” every hour makes highways less safe and offices more noisy.

Replace the habit with a system

I put trip tracking in place before the truck leaves. Check status on a dashboard. I call only for exceptions. Drivers usually prefer this: fewer interruptions, fewer arguments, clearer delivery instructions when I do call.

Lorryman’s promise in practice

I stop chasing drivers. I start tracking loads. Visibility that doesn't depend on someone picking up the phone.

The 30-day habit replacement, in detail

I've sat with desks that live this. Week 1: tracking on before dispatch, board open during the shift, calls still allowed but tagged. Week 2: location calls require a reason code. Week 3: customer updates drafted from the board. Week 4: publish a before/after: outbound calls down, exception quality up, self-scored calm up. If I skip measurement, the old habit returns on the first stressful Friday. Habits die when a metric makes them embarrassing.

Drivers usually prefer fewer location pings. They don't prefer silence when a gate is closed. I keep a human path for instructions. Remove the human path for coordinates. That split is the entire redesign. Mixing them again, “quick call just to be sure”, is how I undo a month of work in an afternoon.

Shortage is the moral argument as well as the ops argument

A country short of skilled drivers can't also use those drivers as always-on IVR. Every unnecessary ring is attention stolen from the road. If the brand talks safety in decks and then mandates hourly pins, the deck is fiction. I stop calling for location and I'm not being soft. you're being consistent.

Coordinators fear that without calls they will look idle. I give them exception work: dwell that exceeds a threshold, RC mismatch, customer recovery, dock sequencing. People need a job to replace the job I'm deleting. Otherwise they will recreate the phone tree to feel useful.

What “calm” looks like in a control tower

Fewer overlapping WhatsApp groups. One trip object. A rule that nobody asks a driver where they're if the board already says. A weekly 20-minute review of false ETAs. That's a proper tower. Noise isn't the same as being on top of the work. Indian freight will always have chaos outside the gate. Inside the room, I can choose not to add more.

Our practical promise is the missing piece of that room: a trip I can watch when the person I would have called is driving. I stop chasing. I start tracking. Then call like an adult, with a reason.

Scripts for the first awkward week

To drivers: we'll call less for location; please keep the phone for instructions. To customers: we'll update from the trip, not from a guess. To transporters: we're not installing anything; we're following the RC I assigned. I say it until it's boring. Boring is adoption.

If a senior leader still wants a “quick confirmation call” on every load, show them the tagged call log from week 2. Data changes culture faster than slogans. I keep the log. It's the change-management tool.

Tag every location call until the habit is ashamed

I've sat with desks that live this. Week one: tracking on before dispatch, board open during the shift, calls still allowed but tagged. Week two: location calls require a reason code, board unclear, customer screaming, habit, plant demand, suspected RC swap. Week three: customer updates drafted from the board. Week four: publish a before/after, outbound calls down, exception quality up, self-scored calm up. If I skip measurement, the old habit returns on the first stressful Friday. Habits die when a metric makes them embarrassing. I keep the log. It's the change-management tool. If a senior leader still wants a quick confirmation on every load, show week two’s tags. Data changes culture faster than slogans. Coordinators who “just quickly call to be sure” are the regression. I make that sentence expensive by counting it. What gets counted gets awkward. Awkward is how a phone tree ends in an Indian control room.

Drivers usually prefer fewer location pings. They don't prefer silence when a gate is closed. I keep a human path for instructions. Remove the human path for coordinates. That split is the entire redesign. Mixing them again (a quick call just to be sure) is how I undo a month of work in an afternoon. I write the split on the wall: location from the trip; voice for gate, labour, breakdown, unloading bay. New joiners should see it on day one. Old heroes of the phone tree should see their call counts. I don't humiliate them in public. Do give them exception work so they don't look idle. Idle coordinators recreate rings to feel useful. Usefulness should move to dwell that exceeds a threshold, RC mismatch, customer recovery, and dock sequencing. Delete the job of being a transponder. Replace it. Replacement is the project. Software is only the enabler.

Shortage and safety are the same argument

A country short of skilled drivers can't also use those drivers as always-on IVR. Every unnecessary ring is attention stolen from the road. If the brand talks safety in decks and then mandates hourly pins, the deck is fiction. I stop calling for location and I'm not being soft. you're being consistent. A stretched driver on a ghat with a ringing pocket is a safety incident waiting for a slide. Public remarks on a multi-million shortfall only make the remaining crew more precious. I treat them as precious. That looks like fewer interruptions and clearer instructions when I do call. It doesn't look like a coordinator competition to collect pins. Collecting pins isn't operations. It's a habit from a time when there was no shared object. There's a shared object now, if I start the trip from the RC before the truck leaves. I use it. I leave the driver’s attention on diesel, fatigue, and the next check-post.

Coordinators fear that without calls they will look idle. I name that fear in the week-one briefing or it will run the project from under the table. I give them a queue: stalls, mismatches, recovery, sequencing. I review the queue in the same slot where they used to boast about reaching drivers. Status in this desk should be exceptions closed, not rings completed. If I keep praising people for getting a pin, I'll keep getting pins and missed calls. Praise the person who staffed a dock from a stall timestamp without waking a driver at 1 a.m. That praise teaches the new culture. Indian freight will always have chaos outside the gate. Inside the room I can choose not to add more. Calm isn't laziness. Calm is a tower that knows the difference between a location and a conversation. I teach that difference until it's boring.

Three scripts that must become boring

To drivers: we'll call less for location; please keep the phone for instructions, gate code, labour timing, unloading bay, breakdown. To customers: we'll update from the trip, not from a guess; if we call I, it's because something needs a decision, not because we're hunting a pin. To transporters: we're not installing anything; we're following the RC I assigned; the owner doesn't need a workshop between loads. I say it until it's boring. Boring is adoption. If a customer still demands a live location screenshot from a driver’s WhatsApp, show them the trip and explain that a driver pin may not even be the loaded vehicle. Identity first. Then movement. That explanation, delivered calmly, is how I stop being trained by the noisiest buyer. The noisiest buyer isn't the operating system. The trip is, if I let it be.

Script the internal senior too. If a director walks in and asks someone to “just call and check,” the coordinator should be allowed to say the board already shows movement or stall, and to offer a call only for an instruction. If directors punish that answer, the project is dead. I brief directors in week one. I show them the tagged log in week two. I ask them to model the new behaviour on the stressful Friday, which is the exam. Culture fails at the top when the top wants the old music. Location calls are the old music. Trip checks are the new one. I can't play both all day. Choose. Our practical promise is the missing piece of that room: a trip I can watch when the person I would have called is driving. I stop chasing. I start tracking. Then call like an adult, with a reason, or not at all.

The stressful Friday is the exam

A quiet Tuesday proves nothing. Friday, when three trucks are late, a buyer is shouting, and a plant wants inbound for the night shift, is the exam. If the desk reverts to a pin hunt, I failed the month. If the desk opens the board, tags leftover calls, and sends board-based sentences, I passed. I design the exam. I tell the team in week three that Friday will be reviewed as a tape, not as a vibe. I review who called for location and why. I review which customer updates were invented. Do it without theatre. People can survive an honest tape. They can't survive a slogan that evaporates under heat. Heat is Indian road freight’s normal weather, check-posts, monsoon, a market truck that swapped. The process has to be for heat. A process for Tuesdays is a decoration. Decorations don't stop location calls. Tapes do.

After a pass, don't declare victory and remove the tags. I keep tags for another month until the reason “habit” is rare. Then I can lighten the logging. If I lighten too soon, habit returns wearing “just this once.” Just this once is how phone trees regenerate, like weeds after rain. I assign one person to watch the weed: a weekly twenty-minute review of false ETAs and leftover location calls. That's enough PMO. I don't need a transformation office. I need a stubborn hour. Stubbornness is the operating system change. Software that's not opened before the dial isn't a system. It's a licence. I open it first. Dial second, and only with a reason. When that order holds on a bad Friday, I have stopped calling drivers for location in the only sense that matters. The rest is maintenance.

What the driver hears when you finally call

The call should sound like work, not like surveillance. you're not asking where he is. you're telling him the gate will open at a time, labour will be n, the bay is the one behind the weighbridge, the plant won't take the truck after a cut-off, the consignee’s security needs a name. That's a professional call. A location call is an amateur call. Drivers remember the difference. In a shortage, the operators who respect attention get better crews. The operators who ring for pins get silence and a reputation in the nagar. I can't lecture the way into that reputation. I have to stop the amateur call. The board makes the stop possible. Without a board, the amateur call is the only tool and I'll keep using it. With a board, using it's a choice, and choices can be tagged, counted, and retired.

If a driver goes truly missing, no movement through a driving window, no answer on an instruction call, that's an exception, not a location ritual. Escalate to the transporter with timestamps. Involve the plant. I don't start a mass-calling festival that wakes three other drivers who were doing their jobs. Festivals feel like control. They're how I spread panic across a corridor. Exception paths should be written on one page next to the phones. New staff should run them on a Saturday. I stop calling for location isn't a vow of silence. It's a narrower, adult use of the phone. Narrow phones plus a trip board is a control tower. Wide phones plus a missed-call culture is what I have now in too many rooms. Change the width. I keep the humans for the moments that need a human. Let the load’s position live on the trip, where a missed ring can't delete it.

What you owe the remaining crew

I owe them fewer rings, clearer instructions, and a company that doesn't treat their pocket as infrastructure. I owe my own desk a job that's not humiliation-by-busy-signal. I owe customers sentences that can be replayed on Monday. Those debts are paid by the same habit: start the trip from the vehicle number, look before I dial, call with a reason. Thirty days is enough to install the habit if I measure. It's not enough if I only announce. Announcements are cheap in Indian offices. Tagged calls aren't. Spend the not-cheap thing. Then “stop calling drivers for location” is no longer a blog headline. It's how the tower sounds at 11 p.m., quieter, more specific, and no longer pretending that a human being on a ghat is a satellite. Satellites don't get tired. Drivers do. Plan for that, and the phone becomes a tool again instead of a superstition.

Track trucks without GPS on Lorryman