What a transportation management system has to do for a Canadian fleet between 5 and 200 trucks — and the four integration questions that decide whether it works.
Key takeaways
Fleet owners shop for a dispatch board and then live in the billing screen. A transportation management system earns its cost by carrying one order record from the moment a customer books through dispatch, driver pay, invoicing and the safety file — without anyone re-typing it. Trimble TruckMate describes exactly this scope for LTL, truckload and intermodal carriers: order entry, dispatch, auto-rating and billing in one product. McLeod LoadMaster takes the same shape for truckload, LTL, brokerage and private fleets.
Smaller and cheaper options exist — AscendTMS is a common starting point for fleets that are outgrowing spreadsheets. The question is not which is best. It is which one your existing hardware and accounting will talk to.
Every fleet that regrets its TMS regrets an integration. Ask these four before you sign, and ask for the answer in writing.
Federally regulated drivers must record duty status on a certified ELD, and Transport Canada is explicit that making sure the devices drivers use are certified is the carrier’s responsibility. Transport Canada publishes the list of certified devices. Confirm your TMS reads duty status from that specific device, and confirm whether it polls every few minutes or once an hour — the difference matters when you are deciding whether a truck can take a 15:00 pickup.
If you run intra-provincially in Ontario, note that the requirement is provincial as well as federal: Ontario has required certified ELDs for covered intra-provincial truck drivers since 12 June 2022, with penalties from 1 January 2023, and the exemption for drivers operating within a 160 km radius of where they started and returning to the same place. The penalties themselves are not nominal: a conviction carries a fine of $250 to $20,000, plus points on the carrier’s safety record that can pull down its CVOR rating, and if the carrier is registered outside Ontario the conviction is shared back to its home jurisdiction.
A CSV export is not an integration. Ask whether the TMS posts invoices and settlements directly, on what schedule, and what happens to a correction made after posting. McLeod publishes a list of off-the-shelf, supported integrations including accounting packages; ask your candidate for the equivalent list and check yours is on it by name.
Drivers must keep supporting documents, and Transport Canada’s list for commercial drivers includes bills of lading, itinerary or schedule documents showing origin and destination of each trip, fuel and repair receipts, and dispatch or trip records showing date, time or location including arrival and departure times. Under s.85(1) of the hours-of-service regulations those records go to the home terminal within 20 days. If your imaging is a separate system your TMS cannot see, you will do that twice.
The trigger for this one is a vehicle weight, not a fleet size or truck count: any truck plated in Ontario, the U.S. or Mexico with a registered gross weight or actual weight over 4,500 kg needs a CVOR certificate, farm plates included. In Ontario the Commercial Vehicle Operator’s Registration programme reviews violation rate, safety rating, convictions, reportable collisions and CVSA inspection results, and the ministry intervenes with letters, interviews, audits and sanctions. A TMS that holds driver files, expiry dates and inspection outcomes turns an audit into an export. One that does not means a filing cabinet and a bad week.
Worked example: the 22-truck test
A 22-truck flatbed carrier in southwestern Ontario was running a dispatch whiteboard, a telematics portal, a scanning app and QuickBooks. The measurable problem was not dispatch — it was that invoices went out 6 to 9 days after delivery because paperwork had to be matched by hand.
The evaluation ignored the map view entirely and scored three systems on one question: can a delivered load with imaged paperwork produce a rated invoice with no re-keying? Two could, conditional on an imaging integration they charged extra for. One could not without a third-party middleware licence. That single test, not the demo, picked the system — and the number to watch afterwards was days-to-invoice, which the fleet already knew.
Route optimisation on a map is the most demonstrated and least load-bearing feature in trucking software. So is a mobile app screenshot. What you cannot see in a demo, and must ask about, is what happens on a bad day: a corrected rate after invoicing, a driver moved mid-load, an ELD malfunction. Transport Canada requires that when a device malfunctions the driver notifies the carrier as soon as the vehicle is parked and reverts to paper logs, and the carrier repairs or replaces it within 14 days — and the driver must keep logging the malfunction code on every subsequent day’s record until it is fixed (s.78(3)-(4)). Under s.78(6), the carrier must also keep a register of every malfunction, naming the driver who found it, every driver who used the truck before the fix, and the ELD’s make, model, serial number and the vehicle’s plate or VIN. That register also has to survive: s.78(7) requires the carrier to keep it for six months from the date the ELD is repaired or replaced, along with the repair date and a description of what was actually done to fix it (s.78(6)(f)-(g)). Ask whether your candidate system builds and retains that register on its own, or whether it becomes a spreadsheet someone maintains by hand, updates inconsistently, and eventually forgets to keep at all.
Often not a full one. The order-to-invoice loop and imaged paperwork are worth systematising immediately; a full dispatch and settlement platform usually is not until owner-operator settlements or LTL rating make manual work unmanageable.
Usually, but confirm the specific integration by product name and version, not by vendor name. Vendors integrate with some of their own products and not others.
A 30-minute call is enough to tell you whether AI pays for itself on your dispatch desk.
