How to structure dispatch teams when you cross 10 people

One dispatcher can hold the whole picture in their head. Five can still shout across the room. Somewhere past ten, the shared inbox that felt effortless starts to feel like a scramble, and the question becomes how to split the work without splitting the fleet.

We looked at how 80 carrier fleets on Mailex organize once they cross that line. Three patterns show up, and the right one depends less on size than on what varies most in your business.

Pods by lane

Split the team by geography or corridor. The Southeast pod, the reefer-heavy Midwest pod. This works when your lanes have genuinely different rhythms and the knowledge is regional. The risk is coverage gaps: a lane pod is fragile when two people are out.

Pods by broker

Assign key brokers to specific dispatchers or small pods, so the relationship stays warm and the broker always talks to someone who knows their quirks. Strong for fleets whose revenue concentrates in a handful of accounts. Weak when a broker relationship depends too much on one person who then leaves.

One big queue with round-robin

Keep everyone in one shared inbox and let assignment rotate. Simplest to run, best coverage, and the fairest workload. The cost is relationship depth: brokers do not get a consistent face. Most fleets in our data run this until a specific account or lane earns its own pod.

Structure should follow what varies. If your lanes are similar and your brokers are many, do not invent pods you will spend all quarter maintaining.

A rule of thumb

Start with one queue and round-robin. Carve out a pod only when a real constraint appears: a lane with its own logic, or an account too important to rotate. Structure you added on purpose is easy to explain; structure you inherited from a reorg nobody remembers is where handoffs get dropped.