How Perth tow operators find accident jobs faster
The four ways Perth operators hear about a crash, what each one actually costs in minutes, and where the time goes missing.
Updated 25 August 2026 · 7 min read
Every tow job on a Perth freeway is won or lost in the first few minutes. Not because the work is a race in any formal sense, but because the operator who arrives first is the one having the conversation with the driver while everyone else is still on the Kwinana heading south.
The interesting question is not whether speed matters. It is where the minutes actually go. Most operators assume the gap is in driving. In practice, most of it is spent before the truck moves at all.
The four ways you hear about a crash
Almost every job in the Perth metro arrives through one of four channels, and they have very different latencies.
A call from a panel shop, insurer or repeat customer
The best kind of work, and the least time-sensitive — the job is already yours when the phone rings. Nothing in this guide applies to it. If most of your volume comes this way, your problem is sales, not speed.
Radio and scanner traffic
Fast when someone is listening. The failure is not the technology, it is attention: a scanner only works while a human is actively parsing it. At 3am, during a job, or while you are under a car, it broadcasts to nobody.
Group chats and Facebook groups
Genuinely useful, and genuinely slow. A post has to be written by someone who already knows, then read by you, then decoded — "Reid Hwy near the Alexander turnoff" is not an address. By the time a group chat has a legible location, the incident is usually several minutes old and several operators already have it.
Driving past it
The fastest channel and the least controllable. It is also why operators fall into the habit of parking near known trouble spots, which is an expensive way to buy information — you are paying for fuel and hours to be in the right place by chance.
Where the minutes actually go
Break a typical response into its parts and the driving is rarely the largest slice:
- Detection — how long between the crash and you knowing anything at all.
- Confirmation — deciding whether it is real, and whether it is worth moving for.
- Location resolution — turning a description into a place you can navigate to.
- Dispatch — deciding which truck goes.
- Driving — the only part most operators try to optimise.
Steps one to four happen while the truck is stationary. An operator who shaves four minutes off detection and location has gained more than one who drives ten kilometres an hour faster, and has not taken on any additional risk to do it.
What good looks like
A well-run operation collapses the first four steps into something close to one. The incident arrives with a road name, a suburb, a timestamp and a route that opens in whatever maps app the driver already uses. There is no interpretation step, because there is nothing to interpret.
That is a process change more than a technology one. The tooling only matters because it removes the interpretation.
What not to optimise
Two things are worth saying plainly. Do not drive faster — the liability and licensing exposure dwarfs the value of any single job. And do not chase every alert; an operator who responds to everything burns fuel on jobs that were never theirs. Filtering to the suburbs you genuinely cover is what makes a fast channel usable rather than exhausting.