Why scanning and group chats quietly cost you jobs

This is not an argument that scanners and group chats are useless. Plenty of Perth operators have built solid businesses on both. It is an argument that each has a specific failure mode, and that the failures cluster at exactly the times the work is most valuable.

The attention problem

A scanner is a broadcast into a room. It only produces value while somebody is in the room, awake, and listening carefully enough to catch a street name said once. That constraint is invisible when the business is one owner-operator sitting in a yard. It becomes expensive the moment you are on a job, driving, sleeping, or doing anything else that a growing business requires.

The result is a channel whose reliability is inversely correlated with how busy you are. When you have the most capacity to take work, you hear everything. When you are at your most productive, you hear nothing.

The translation problem

Group chats fail differently. The information is durable — it sits in the thread, you can scroll back — but it arrives in human shorthand. "Two cars, Leach near the Kwinana on-ramp, looks bad" is a useful sentence to a person who knows that interchange and a useless one to a new driver.

Every message needs a person to decode it into a location, and that decoding is where minutes disappear. It also does not scale: the knowledge lives in the head of whoever has been driving Perth the longest, which makes the operation fragile in a way that does not show up until they are on leave.

The competition problem

There is a structural issue with any shared channel. By the time an incident is posted in a group, everyone in that group knows. The information is real, but it is no longer an advantage — you are now in a straight race with every other reader, decided by who happened to be looking at their phone.

What to keep

Do not throw either away. Group chats are genuinely valuable for context that no automated feed will ever carry — which panel shops are paying on time, which stretch of road has had three crashes this month, who is worth working with. That is community knowledge and it has real commercial worth.

What is worth changing is the dependency. If your ability to hear about a job at 2am depends on a person being awake and reading a thread, that is not a process, it is luck with extra steps.

The honest comparison

• Scanner — fastest when monitored, silent when not. Reliability drops as you get busier.
• Group chat — durable and social, but slow and needs local knowledge to decode.
• Driving past — fastest of all, entirely uncontrollable, expensive to engineer.
• Automated alerts — consistent regardless of attention, but only as good as the filtering behind them.

Most well-run operations end up using more than one. The point is to know which one you are relying on when everything else is quiet.