Skip to content
AxleGuard
Demo

Roundup

Six dispatch systems, read from a heavy haul desk

All six of these run a freight business well. The question here is narrower and harder: what happens when the load is a transformer, the permit expires on Thursday, and the route needs an escort through two counties. That is where the published documentation gets quiet.

  • Six systems
  • Read for the heavy haul case
  • Assessed August 2026

Method

How we assessed them

This is a roundup with a deliberately narrow lens, and it would be unfair not to say so at the top.

Everything below is read from documentation each supplier publishes openly, as of August 2026. We have not run these systems, and a meaningful head-to-head across six transportation management systems is a six-month project rather than a page.

The lens is heavy haul specifically: non-divisible freight, oversize and overweight permits, escorts, specialised trailers with more axles than a van has, and routes that have to be approved rather than merely chosen. Every product here does much more than that, and a system that scores thinly on this page may be an excellent choice for general freight. Read it as an assessment of one corner, not a ranking.

What the not-published marks mean

Three of the ten rows come back as not published across all six columns: a permit register attached to the load, escort requirements tracked, and specialised multi-axle equipment geometry modelled. That is a finding about documentation rather than about capability. Several of these vendors may well support all three, through a module, a configuration or a partner. What we can say is that none of them lead with it, which tells you something about where heavy haul sits in the category's priorities.

Why two rows are marked not supported everywhere

Per-axle weight solved from cargo placement, and the bridge formula across every consecutive axle subset, are marked not supported for all six. This is not a criticism. A dispatch system's job is to move a load through a lifecycle — order, cover, dispatch, deliver, invoice, settle — and it was never built to solve statics. The rows are in the table because buyers frequently assume a system that holds the load also checks it, and it does not.

None of them lead with heavy haul, which tells you something about where it sits in the category's priorities.

The six

What each one is for, and where it stops

Two of these are built for asset carriers, one for multi-modal networks, one for collaboration, and two for getting a growing operation off email quickly.

01 · Deep, configurable, built for asset carriers

McLeod Software

What it is genuinely good at

McLeod has run the back office of asset-based carriers for a long time. Its depth shows in settlement, driver pay, accounting, documents and configuration. If you run your own trucks and drivers with complicated billing, this is a category heavyweight. Its brokerage product also covers the capacity side of the business.

Where it stops

Depth costs implementation time, and a system this configurable rewards operations with the staff to configure it. For heavy haul specifically, we did not find a published permit register, escort requirement tracking or multi-axle equipment modelling described as standard capabilities, so the comparison marks those rows as not published rather than guessing.

02 · A family of systems, tied to mileage and in-cab

Trimble Transportation

What it is genuinely good at

Trimble's transportation software is a family, not a single product. That lets small and large carriers choose different systems. Its strongest argument is a coherent stack: rating mileage, planned routes and in-cab devices can come from one supplier. That removes many arguments about whose miles are right.

Where it stops

A family means the question of which product you are buying is as important as the decision to buy from them at all, and capabilities differ between them. As with everything else on this list, the load in the trailer is not modelled: dispatch systems move loads through a lifecycle, they do not solve where the weight sits.

03 · Multi-modal, and strongest for 3PLs and shippers

MercuryGate

What it is genuinely good at

MercuryGate is built around the complexity of moving freight across modes and across parties. Rating, procurement, tendering and optimisation across truckload, less-than-truckload and other modes are the core of it, which makes it a natural fit for a third-party logistics provider or a shipper managing a network rather than a fleet. If your problem is choosing the cheapest compliant way to move a thousand shipments, this is a different and more useful kind of optimisation than a carrier system offers.

Where it stops

The further a product sits from the truck, the less it knows about the truck. Heavy haul is an asset-carrier discipline built on specific equipment, permits and routes, and a multi-modal network product is not where that detail naturally lives. The permit and equipment rows below are marked as not published for that reason.

04 · Collaboration and visibility across parties

Turvo

What it is genuinely good at

Turvo's distinctive idea is that a load involves several organisations and most of the pain is in the communication between them. It puts shippers, carriers, drivers and customers in a shared view of the same shipment, with a modern interface and real-time updates, which addresses the part of the job that otherwise happens in phone calls and forwarded email. For an operation whose failures are coordination failures rather than dispatch failures, that is the right diagnosis.

Where it stops

A collaboration layer is not a compliance engine. Nothing about visibility across parties tells you whether the load is legal on the drive tandem, and the heavy-haul specifics — permits, escorts, oversize routing — are not capabilities we found published.

05 · Modern, and quick to get running

Rose Rocket

What it is genuinely good at

Rose Rocket targets small and mid-sized carriers. Setup is measured in weeks rather than quarters. Customer portals let shippers see freight without calling, and the product is designed for people who were not trained on it. For a growing carrier leaving spreadsheets and email, that adoption curve can matter more than a longer feature list.

Where it stops

Breadth is the trade for that accessibility. Heavy haul is a specialised corner of trucking with its own paperwork, and a system designed for general freight will need help at the edges. We did not find permit registers, escort tracking or multi-axle equipment configurations published.

06 · Cloud-native, workflow-driven

Alvys

What it is genuinely good at

Alvys is a newer cloud system for carriers and brokers built around workflows and document handling, with automation applied to the repetitive parts of moving a load through its lifecycle. For an operation whose staff spend a large part of the day re-typing information between systems and chasing paperwork, that is aimed squarely at the actual cost.

Where it stops

Newer means less accumulated depth in the specialised corners, and heavy haul is one of the most specialised. The same three heavy-haul rows come back not published here as elsewhere, and the load physics is outside the category entirely.

A dispatch system holds the load, its status and its paperwork. Whether the freight can sit on that trailer legally is a statics problem.

Capabilities published as supported, by system

of 10 rows
  • McLeod3 of 10 rows

    1 marked partial, 4 not published

  • Trimble3 of 10 rows

    1 marked partial, 4 not published

  • MercuryGate4 of 10 rows

    1 marked partial, 3 not published

  • Turvo3 of 10 rows

    1 marked partial, 4 not published

  • Rose Rocket4 of 10 rows

    4 not published

  • Alvys4 of 10 rows

    4 not published

Counted from the grid below, through the heavy haul lens this page uses. All six run a freight business well; the rows they separate on are not the rows a heavy haul desk asks about.

Every cell in the grid, by what the documentation said

cells
35%
7%
20%
38%
  • Published as supported21 cells
  • Published as partial4 cells
  • Not supported, and not claimed12 cells
  • Not published23 cells

All 60 cells of the grid below. 23 of them are marked not published, which is a fact about the documentation rather than a claim about any product.

Side by side

The capability grid

Ten rows. The top five separate the products. The bottom five do not, and that is the point of including them.

Published capabilities of six transportation management systems, read for the heavy haul case, from public documentation in August 2026.
CapabilityMcLeodTrimbleMercuryGateTurvoRose RocketAlvys
Order through dispatch to invoice and settlementYesYesYesYesYesYes
Built for asset-based carriers running their own trucksYesYespartpartYesYes
Brokerage and third-party capacityYesYesYesYesYesYes
Multi-modal beyond truckloadn/pn/pYesn/pn/pn/p
Delivered as a cloud serviceseveral of these have on-premise heritage and now offer hostingpartpartYesYesYesYes
Oversize and overweight permit register on the loadnot published by any product in this comparisonn/pn/pn/pn/pn/pn/p
Escort and pilot car requirements trackedn/pn/pn/pn/pn/pn/p
Multi-axle and specialised trailer geometry modelledn/pn/pn/pn/pn/pn/p
Per-axle weight solved from cargo placementno dispatch system in this comparison does this, and none claim toNoNoNoNoNoNo
Bridge formula evaluated on every consecutive axle subsetNoNoNoNoNoNo
supportedpart partly, or with limits not supportedn/p not published by the vendor

The verdict

Which one to pick when

Choose on the shape of your business first, then solve the heavy haul specifics separately, because none of these will solve them for you out of the box.

  1. 01

    If you run your own trucks and settlement is complicated, McLeod

    Driver pay, owner-operator settlements, accounting integration and the volume of configuration a large asset carrier needs. Budget properly for implementation; a system that can be configured for anything has to be configured for something.

  2. 02

    If you want dispatch, mileage and the cab from one supplier, Trimble

    The coherence argument is real, particularly where planned miles and billed miles have to reconcile. Spend the evaluation working out which product in the family fits your size, because that decision matters more than the vendor choice.

  3. 03

    If you are a 3PL or a shipper managing a network, MercuryGate

    Rating, tendering and optimisation across modes and carriers is a different discipline from running trucks, and it is what this is built for. If you also run assets, expect to solve the asset side elsewhere.

  4. 04

    If your failures are coordination failures, Turvo

    When the recurring problem is that the shipper, the carrier, the driver and the customer are each working from a different version of the truth, a shared workspace addresses the actual cause rather than a symptom of it.

  5. 05

    If you are a growing carrier coming off spreadsheets, Rose Rocket or Alvys

    Both are designed to be adopted rather than implemented, and for an operation of a few dozen trucks the difference between a system people use and a system people were trained on is the whole return.

  6. 06

    For the heavy haul specifics, plan to solve them beside whichever you choose

    Permit registers with expiry dates, escort requirements attached to a route, non-divisible freight that cannot be rearranged, and specialised trailer geometry are not what this category leads with. Ask each vendor directly what they do with a permit that expires inside a trip window, and treat a vague answer as an answer.

  7. 07

    For whether the load is legal at all, none of them

    A dispatch system holds the load, status and paperwork. Deciding whether 47,000 lb of freight can sit legally on a trailer is a statics problem. It needs equipment geometry, every consecutive axle subset, and the tire and axle ratings.

Dated, and honest about it

Assessed from publicly published documentation as of August 2026. Where this page says a capability is not published, that is a statement about what we could find documented and not a claim that the capability is absent. These are large products that change often; ask, and get the answer in writing.

Next step

Put the heavy-haul dispatch comparison against one real load.

Bring the route, configuration or scale ticket that made the heavy-haul dispatch comparison matter. We will work through it in plain English and show where AxleGuard changes the decision.