Appointments are rarely lost at the dock. They are lost in the gap between who books, who dispatches, and who knows the truck is running late.
Key takeaways
Run a post-mortem on ten missed appointments and the pattern is almost always the same. The truck was not late. The booking was made by someone who did not dispatch it, in a portal nobody else reads, and the confirmation number never reached the load record. Or the appointment was moved by the warehouse and the email went to a shared inbox.
A useful way to think about it: an appointment has four states, and fleets lose slots at the transitions between them.
The gap between confirmed and committed is where most slots die, and it is entirely an internal process problem.
Whoever books the appointment owns it until it is met or rebooked. If your customer service team books and dispatch executes, the load record must carry the booker’s name. Split responsibility with no name attached is the root cause of most misses.
Not a note. A field on the order in your TMS — TruckMate and LoadMaster both carry the appointment on the order record — that dispatch cannot clear without. If the number is not there, the appointment is treated as unconfirmed. There is a legal reason to be strict about this, not just an operational one: under s.30(1) of the Canada Evidence Act, a record made in the usual and ordinary course of business is admissible in evidence on production of the record alone — a field on the order that is populated the same way every single time is exactly that kind of record, and a sticky note, a shared inbox, or a note typed into the wrong screen is not.
Define the moment: when projected arrival exceeds the window by more than X minutes, dispatch calls the receiver rather than hoping. Telematics platforms including Samsara and Geotab will raise a geofence or ETA exception; the rule turns that alert into a phone call while the receiver can still help.
An appointment the driver cannot legally reach is a missed appointment already. Under the hours-of-service regulations a driver has 13 hours of driving and 14 hours of on-duty time in a day (s.12) and a 16-hour elapsed-time window between 8-hour off-duty periods (s.13(3)). A 06:00 slot 900 km away is not a scheduling decision, it is a violation. That 16-hour window sits inside a bigger one: s.14(1) requires at least 10 hours of off-duty time in a day, not just the mandatory 8 consecutive hours in s.13(1), and s.14(3) requires the extra 2 hours to fall outside that consecutive block. A driver who took exactly 8 hours off overnight and nothing else is already short on the day’s total before the appointment even starts. Section 14(2) lets that remaining time be taken in blocks of no less than 30 minutes each, which means a long dock wait only helps if the driver is genuinely relieved of responsibility for that block, not just idling on-duty in the cab — a distinction a rebooking rule has to account for, not just the elapsed window.
Large receivers increasingly book only through a portal. If three people share one login and nobody owns it, you will lose slots. One account per person, and the portal must be checked on a schedule, not when someone remembers.
Some facilities cancel and reschedule habitually. That is a rate conversation, not a dispatch conversation. Keep the record — date, requested window, granted window, changes — because you cannot have the conversation without it. Keep it longer than feels necessary: under s.4 of Ontario’s Limitations Act, 2002, the basic limitation period for a civil claim is two years from the day it was discovered, so a rate or billing conversation you want to have about a pattern of cancellations — or a claim you eventually have to file over one — needs a log that survives at least that long, not just until the next audit clears it off the shared drive.
The obvious cost is the reschedule. The hidden one is the clock. The federal definition of on-duty time in the regulations expressly includes time spent “waiting before and while a commercial vehicle is serviced, loaded, unloaded or dispatched”. A driver who sits four hours waiting for a door has spent four hours of a 14-hour on-duty day and four hours of the 16-hour elapsed window, and no part of that is recoverable. The receiver is not a bystander to that clock either: s.4 of the same regulations forbids a “motor carrier, shipper, consignee or other person” from requiring or allowing a driver to drive if doing so would put the driver out of compliance — a receiver that holds a truck four hours past its window and then insists the driver make the next drop anyway is asking for something the regulation itself forbids, not just something merely inconvenient for the driver, the dispatcher, or the schedule.
So a missed appointment does not just delay one load. It reduces what that driver can legally do for the rest of the day, and often the next one. The record of that has a legislated shelf life, too, for a federally regulated carrier: s.24(2)(d) of the Canada Labour Standards Regulations requires the hours worked each day — the four hours a driver spent waiting for a door included — to be kept for at least three years after the work was performed. The load record that shows who booked it, the wait, and the confirmation number is not just useful housekeeping for dispatch; it is what that retention duty is actually asking for.
Worked example: the 06:00 slot nobody could keep
A Mississauga-based fleet was missing roughly one in six appointments at a large grocery distribution centre. The assumption was traffic. The log said otherwise: in seven of ten misses the confirmed window was 06:00–07:00, and the appointment had been booked by customer service the previous afternoon and entered as a note rather than on the order.
Two changes fixed it. The confirmation number became a required field, so dispatch could no longer plan against an appointment that did not formally exist. And bookings for that facility were restricted to windows after 09:00 unless the truck was staged in the yard the night before — because a 06:00 arrival from the fleet’s eastern lanes required a start time that did not survive s.13(3). The miss rate did not fall because anyone drove faster.
No. Take the earliest slot you can reliably meet from where the truck actually is, with the hours it actually has. An early slot missed costs more than a later slot kept.
It solves the receiver’s problem. It solves yours only if the confirmation lands on your load record automatically. Ask that question specifically before buying an integration.
A 30-minute call is enough to tell you whether AI pays for itself on your dispatch desk.
