Why Radio Calls Fail on the Production Floor (and What to Do Instead)

Every plant I've worked in has run on radios at some point. An operator needs a material handler, a maintenance tech, or a supervisor, keys the radio, and asks for help. It feels fast. Most days it even works.

The trouble is what happens on the days it doesn't, and how little anyone can say about it afterward.

Four ways a radio call fails

It goes to everyone, so it belongs to no one. A call on an open channel is heard by five people. Each of them assumes someone closer will take it. Nobody says "I've got it," and the operator waits.

It reaches someone who's already busy. The person who answers is usually the one who always answers, not the one who's free. The request joins a mental to-do list nobody else can see.

It disappears the moment it's spoken. There's no record of when it was asked, who took it, or when it was done. If the operator asks again twenty minutes later, nobody can tell whether that's the same problem or a new one.

It can't be measured. When the morning meeting asks why the line was down, the honest answer is "we were waiting on someone," and nobody can say for how long. Without a number, the problem never gets prioritized.

Why this matters more than it looks

None of these failures is dramatic on its own. A ten-minute wait here, a forgotten call there. But they repeat every shift, and they hide in the gap between "the line stopped" and "someone showed up." That gap is where a lot of lost production lives, and it's the part most plants can't see.

If you want to put a rough dollar figure on it, the free downtime cost calculator at andontool.com/downtime-cost-calculator lets you plug in your own numbers. Nothing you enter is saved.

What a better request looks like

You don't need to ban radios. You need every request to have four things a radio call can't give it.

A clear owner. One person claims the request by name, and everyone else can see it's taken.

A visible queue. Open requests show on a board the whole area can see, so nothing depends on someone's memory.

Automatic timing. The time from request to claim, and from claim to done, is captured without anyone writing it down.

A history. At the end of the week you can see which requests come up most and which take longest, and fix the pattern instead of the symptom.

Start small

The plants that fix this well don't start with a big rollout. They pick one area where waiting hurts the most, often material delivery or maintenance, and run requests through one visible system for a few weeks. Once supervisors can see response times, the morning meeting changes from "it felt slow" to "material requests on second shift waited this long before anyone claimed them."

That's why I built Andon Tool: requests from any phone or tablet, claimed by name, and timed automatically, counting only working time and not breaks. There's a short intro video at andontool.com/demo.

Whatever tool you use, the principle is the same. A request nobody owns and nobody times is a request that can get lost. Make every one visible, owned, and timed, and the radio goes back to what it's good at: quick conversation.