Setting up coverage zones that actually pay in Perth
Why most operators pick their zones badly, how Perth metro geography changes the answer, and a method for choosing suburbs that earn their fuel.
Updated 25 August 2026 · 8 min read
Ask an operator which suburbs they cover and the answer is usually a list of places they like. Ask which suburbs actually produce paid jobs and the list gets shorter, and different.
The mistake almost everyone makes
The instinct is to select everything. More coverage feels like more opportunity, so operators tick the whole metro area and then find themselves ignoring alerts within a fortnight. That is the worst outcome available: you have taken on all of the noise and none of the benefit, and you have trained yourself to disregard the channel entirely.
Alert fatigue is not a minor annoyance. It is the failure mode that kills the whole approach, because an operator who has learned to swipe away notifications will also swipe away the one that mattered.
Perth geography does not reward symmetry
Perth is long and thin. The metro area runs roughly eighty kilometres north to south and is pinched against the coast, which means a circular radius around your base is almost always the wrong shape. Half of it is often ocean, parkland or industrial land that generates nothing.
The corridors matter more than the distance. Mitchell and Kwinana Freeways carry the northern and southern commuter loads. Reid, Roe, Leach and Tonkin Highways handle the cross-town and freight movements. Great Eastern Highway carries traffic to and from the hills. A zone that includes a stretch of one of these is worth several that do not.
A method that works
- Start with your yard, not the map. Where does the truck actually sit between jobs?
- Draw your honest response envelope — the area you can reach before it stops being worth going, in the traffic you actually drive in, not at 3am.
- Inside that envelope, keep only suburbs touching a major corridor or a known trouble intersection.
- Add nothing outside the envelope for the first month, however tempting.
- After a month, cut anything that has never converted and add one adjacent suburb.
The last step is the one people skip. Zones are not a set-and-forget decision; they are a hypothesis you should be revising with evidence.
Time of day changes the shape
A zone that makes sense at 8am can be indefensible at 6pm. If you can only get across Perth in one direction during peak, your effective coverage narrows even though the map has not changed. Operators who work nights have the opposite problem and can usually justify a much wider footprint.
Overlap is not automatically waste
Multi-truck operations often assume zones should be carved up so no two drivers share an area. That is right for dispatch efficiency and wrong for coverage — if two trucks genuinely both service a corridor, both should hear about it, and the dispatcher decides who moves. Splitting the alert is a decision made too early with too little information.
Reviewing without kidding yourself
Keep it simple. For each suburb, track alerts received and jobs won. Any suburb with a long run of alerts and no jobs is either outside your real response envelope or is being serviced by someone closer. Both are reasons to drop it, and dropping it makes every remaining alert more meaningful.