TacDesk
All articles

Nobody Remembers a Description Passed Over the Radio

Passing an accurate description over a town-link radio is harder than it sounds. Here is why it goes wrong, and what good practice looks like.

By Michael Bryce · 25 September 2026 · 4 min read

Anyone who has worked a night on a door or a town-link radio scheme knows the moment. Someone has just been ejected, or a shop has called in about a person they want watched, and a description goes out over the air. Male, dark top, jeans, short hair. Maybe a hat. Then everyone who heard it goes back to what they were doing.

I have always thought this is one of the weakest points in how our industry shares information. It is also one of the least talked about.

Why a radio description fails

A radio is a good tool for urgent, short messages. It is a poor tool for detail. Three things go wrong, every time.

It is heard once. There is no scrolling back. If you were dealing with a customer, walking between venues or had the volume down for a moment, you missed it. Nobody likes to ask for it to be repeated on an open channel, so most people don't.

It gets shorter as it travels. The person who saw the incident gives a decent description. The person who relays it drops a detail. The next person passes on what they remember. By the third hop, "tall, dark jacket, white trainers, limping slightly" has become "bloke in a dark jacket".

It is not written down. A description that exists only in the air cannot be checked later. If there is a dispute the next morning, or the police ask what was circulated, all you have is people's memories, and memories of a busy Saturday night do not agree with each other.

None of this is anyone's fault. It is what happens when you ask people to hold detail in their heads while doing a job that already demands their attention.

What good looks like

The better operators I know treat a description as a piece of information with a life after the moment it was spoken. That comes down to a few habits.

Say it in a fixed order. Pick one order and stick to it, so people know what is coming and what is missing. Build, clothing top to bottom, distinguishing features, direction of travel, what they were last seen doing. When everyone uses the same order, gaps are obvious and the listener can ask for the one thing that is missing.

Keep it to what you actually saw. "Looked like he was up to something" is not a description. Height, clothing, hair, and where they went are. Guessing at age, intent or background makes it less useful and can make it unfair.

Get it written down at the time. Whoever passes the description on should also log it, with the time and location, in a place the rest of the team can see. Not in a notebook on one person's desk.

Make it findable by the next shift. A description that mattered at 11pm often matters again at 1am, or next weekend. If it only lives in the head of whoever was on the radio, the next shift starts from nothing.

Say when it is no longer relevant. Stand descriptions down as well. Otherwise people carry a lookout for someone long gone, or worse, keep an eye on the wrong person.

The paperwork problem underneath it

Most of the resistance I hear is about time. Nobody wants to write things down in the middle of a busy shift, and I understand why. Officers are there to be seen and to deal with what is in front of them, not to sit typing.

That is the same problem I see with paperwork across the whole industry. Good people spend their energy on admin that could be lighter, and the admin gets skipped or done badly because it is a chore. The answer is not to demand more diligence. It is to make the record quick enough that it happens without a fight.

Where TacDesk fits

This is part of why we built TacDesk. It gives your team one shared place to record what is going on, so information is not stuck in one person's head or one radio channel. I would rather your officers spent their attention on the people in front of them, with the record taking care of the rest.

I am not going to tell you a piece of software fixes radio discipline. It doesn't. Training, a fixed format and a team that takes it seriously do most of the work. But a shared written record makes all of that stick, and it means the description still exists when the radio has gone quiet.

A small change to try this week

You don't need anything new to start. At your next team briefing, agree the order for passing a description and get everyone to say it back once. Then agree who logs it, and where.

It will feel slightly formal for about a week. After that it will just be how you work, and you will find you are repeating yourself on the radio far less.

If you want to see how TacDesk gives your team a shared record, have a look at tacdesk.co.uk.

Michael

MB

Michael Bryce

Founder of TacDesk. Writes about SIA compliance, operations, and running a UK security company — from someone who actually works the shifts.

Connect on LinkedIn →

See TacDesk in action

Win contracts, pass SIA audits, and run your whole operation from one place. Book a free 30-minute demo.

Book a Free Demo

Get Field Notes

The ACS traps, licensing changes and ops shortcuts we write about, one straight email every week or two, from someone still doing the shifts, not a marketing team. Unsubscribe anytime.