Trucker Path for Fleets + McLeod

McLeod TMS and Truck-Safe Navigation

Your dispatcher builds the stop in McLeod. Driver Sidekick sends the stop details to Trucker Path, and the driver taps once to start navigating.

Move from the McLeod TMS to navigation in the Trucker Path app with a single tap
Send pre-configured custom routes straight to a driver in the Trucker Path app
Route on truck size and weight, around low bridges and weight-restricted roads

Start Free Trial

Illustration: a stop planned on a dispatch computer is sent to navigation on the driver’s phone.

One tap: From the McLeod TMS to navigation
UC2024: Announced at the McLeod user conference
7 days: Free trial on Trucker Path for Fleets

Alongside McLeod

What the Driver Gets

McLeod remains the system of record for the load, the customer and the billing. Trucker Path takes the stop and routes the truck to it.

The stop, already filled in

Customer, address and appointment window arrive from McLeod. Your driver stops keying navigation details in by hand.

A route for the truck

Truck size and weight dimensions are applied. The route avoids low bridges, weight-restricted roadways and tight turns.

The route your dispatcher chose

Fleet managers send pre-configured custom routes directly to drivers rather than describing them over the phone.

01Plan
Build the Stop in McLeod
Your dispatcher enters the customer, the address and the appointment window in McLeod, the same way as today.
02Send
Driver Sidekick Sends the Stop
McLeod's Driver Sidekick mobile app sends the stop details directly to Trucker Path. Your dispatcher can send a pre-configured custom route the same way.
03Drive
The Driver Taps Once
The driver moves from the McLeod TMS to navigation in the Trucker Path app with a single tap, then drives a route built for the truck's size and weight.

Reporting

Empty Miles and Detention Times

Read the API Documentation

Loaded miles, empty miles, and scheduled against actual time, per driver and per date range
Actual arrival, actual departure and dwell time on every stop
Your developers read these from the Trucker Path for Fleets API, not from the McLeod connection

How the figures break down

Per driver
Per date range
Per trip
Per stop

Product names and logos are trademarks of their respective owners, used here to describe compatibility.

FAQ

Questions From McLeod Fleets

Does this replace McLeod?

No. McLeod stays the system of record for the load, the customer and the billing. The stop is built in McLeod and Trucker Path routes the driver to it.

How does the stop reach the driver?

Through McLeod's Driver Sidekick mobile app, which sends the stop details directly to Trucker Path. The driver moves from McLeod to navigation in the Trucker Path app with a single tap.

Can my dispatcher send a specific route rather than a stop?

Yes. Fleet managers can send pre-configured custom routes directly to drivers in the Trucker Path app.

What do my drivers install?

Drivers use the Trucker Path app they already know. The stop arrives in the app they open for parking and fuel prices.

Does the route account for my trailer height and weight?

Yes. Truck size and weight dimensions are applied. The route avoids low bridges, weight-restricted roadways and tight turns.

Can McLeod read empty miles and detention times back?

Not through this connection. Those figures come from the Trucker Path for Fleets API: loaded miles, empty miles, on-time trips, and actual arrival, actual departure and dwell time for every stop.

When was this announced?

At the McLeod Software UC2024 User Conference.

Still have questions?navpro@truckerpath.com

McLeod stays