Software doesn't dispatch. People do.

Buttons versus methodology

Most vendor training answers the question "where do I click?". That's necessary, but it's not sufficient. Consider what a modern TMS actually asks of a dispatcher. It offers route optimisation — but using it well means understanding what the algorithm is optimising for, what constraints it's respecting, and when its answer should be trusted over your instinct. It offers capacity and resource planning — but that only helps if you understand how to model your own resources honestly. It offers time-window management, exception handling, automated customer notifications. Each of these is a method, not a screen.

A dispatcher who has been taught the screens will use the system as a faster version of what they did before: an electronic whiteboard. A dispatcher who has been taught the underlying methodology will use it to plan differently — and that difference is where the return on the investment actually sits. This is the uncomfortable part of the argument, and we'd rather say it plainly: the gap between a well-used TMS and a poorly-used one is bigger than the gap between a good TMS and a mediocre one. You can buy the best system on the market and get less out of it than a competitor running something simpler with a well-trained dispatching team.

Which is why we invest in training that isn't about us

Two things follow from that conviction.

The first is our partnership with ASTAG.

The Swiss road transport association runs the certification programme for dispatchers — the course leading to the eidgenössischer Fachausweis for "Disponent/-in Transport & Logistik". It is a nationally recognised qualification, and it covers the profession, not a product: structuring and maintenance of master data, planning methodology, cost structures, legal framework, customer management. X4fleet is the practical training tool in that programme. Participants don't just learn dispatching in theory; they work through it hands-on in a real transport management system.

We're deliberate about what this partnership is and isn't. It isn't a sales channel — the course teaches dispatching, and the fact that the practical work happens in X4fleet is incidental to the curriculum. Graduates go on to work at operators running all sorts of systems, including our competitors'. What we get out of it is something more useful than leads: we help raise the professional standard of the role our product is built for, and we get an unfiltered view of how people who aren't yet our customers approach the work. When forty course participants all misunderstand the same screen, that's a product insight you can't buy.

The second is our learning platform.

Alongside the certification work, we run a learning platform for the people who use X4fleet day to day. It covers the system, obviously. But it's structured around the work — how to plan a tour, how to handle a disrupted day, how to set up resources so that the optimisation gives you useful answers — rather than around the menu structure.

The practical reason for this matters as much as the pedagogical one. Dispatching has meaningful staff turnover, and in most operations the knowledge of how the system is actually used lives in one or two experienced heads. When those people are on holiday, or leave, the operation degrades. A learning platform turns that tacit knowledge into something a new hire can acquire in their first weeks rather than their first year.

What this means for your TMS project

If you're evaluating or implementing a transport management system, a few practical suggestions:

• ‍Budget training as a line item, not a rounding error. If it isn't in the project plan with a number next to it, it will be compressed into the last two weeks before go-live, which is exactly when everyone is busiest.
• ‍Ask what the training actually covers. "Two days of user training" can mean a click-through of the interface or a genuine methodology workshop. Ask to see the curriculum.
• ‍Identify your key users early and involve them in the configuration. People who helped shape a system use it differently from people who had it delivered to them.
• ‍Plan for the second wave. The training that matters most is often not the one at go-live — it's the one three months later, when people have hit the limits of what they learned first time and have real questions.
• ‍Ask about turnover. What happens when your best dispatcher leaves? If the answer is "we'd be in trouble", the training gap is a business risk, not a training issue.

The bottom line

Software vendors have an obvious incentive to tell you that their product is the decisive factor. We build the product, and we think it's a good one — but the decisive factor is whether your dispatchers can use it to plan better than they could before. That's why we put effort into training that reaches beyond our own customer base, and why we'd rather you asked hard questions about the training in a TMS proposal than about the feature list.

‍

Find out more on the ASTAG course and certification here, or get in touch to explore the Learning platform.