You already collect everything an ETA needs. The work is turning it into a message that goes out before the customer asks.
Key takeaways
You do not need a person watching a map because you do not need a map. An ETA is arithmetic on three numbers: where the unit is, how much legal driving time the driver has left, and what time the receiver will actually take it. Two of those three are already being recorded automatically on every Canadian commercial vehicle that runs an electronic logging device, and the third is sitting in the rate confirmation. The job is to put a rule around them and let the rule send the message.
What you should not automate is the decision. Software can tell you at 03:10 that a Winnipeg–Thunder Bay load will miss an 08:00 window by ninety minutes. Whether you re-power it, ask for a later door or phone the customer is a judgement, and it should stay one.
The regulatory floor does most of the work for you. Under the federal hours-of-service rules, a motor carrier shall ensure that each commercial vehicle that it operates is equipped with an electronic logging device. Transport Canada is specific about what counts: the device must comply with the Commercial Vehicle Drivers Hours of Service Regulations and the latest version of the ELD Technical Standard, must be certified by an accredited certification body, and must be listed on Transport Canada’s list of certified electronic logging devices.
That device is a position feed as well as a compliance record. Telematics vendors build the arrival logic on top of it. Samsara, for example, describes a platform where GPS collects location data every second, providing fleets with continuous, real-time visibility, and lists geofencing as a driver-facing feature because geofence notifications upon arrival minimize wait time. Geotab and Motive publish comparable fleet management platforms and ELD compliance products. Those are capability statements, not performance claims — what a geofence gives you is a timestamp you did not have to ask a driver for.
Routing software will happily tell you a load is six hours from the door. If the driver has four hours of drive time left, that number is fiction. The hours-of-service regime is the binding constraint on almost every long ETA in Canada, and it is also the reason a delay can be legitimate and documented at the same time.
The regulations recognise two situations where the clock bends. In an emergency, the requirements in respect of driving time, on-duty time and off-duty time do not apply to a driver who requires more driving time to reach a destination that provides safety for the occupants of the vehicle and other road users or the security of the vehicle and its load. And on a trip south of latitude 60°N, a driver who meets adverse driving conditions — snow, sleet, fog or other adverse weather or road conditions that were not known to the driver or the dispatching carrier immediately before the driver began driving and could not reasonably have been known to them — may extend the permitted 13 hours of driving time and reduce the required 2 hours of daily off-duty time, provided the extension is no more than 2 hours, the driver still takes the required 8 consecutive hours of off-duty time, and the trip could have been completed under normal conditions without the reduction. Either way, the driver shall record the reason for doing so in the record of duty status.
That last sentence is worth more to your customer conversation than any tracking screen. It means the reason for a weather delay is not a claim you make afterwards; it is an entry made at the time, in a record a regulator can read.
The rule that actually works
Send on exception, not on schedule. A message every two hours trains the customer to ignore all of them. One message when the projected arrival moves outside the agreed window — and one when it moves back inside — is the pattern people read.
Four rules cover most of what a small fleet needs.
Departure confirmed. Geofence exit at the shipper, timestamped. This is also your detention evidence, so record it whether or not you send it.
Projection outside window. Projected arrival, computed from remaining distance and remaining legal driving time, falls outside the appointment. Send once, with the new time and a one-line reason.
Stopped longer than expected. Unit stationary beyond a threshold that is not a scheduled break. This one goes to dispatch, not the customer — it is a question, not news.
Arrival. Geofence entry at the consignee. Pair it with the proof of delivery so the customer gets both in one message rather than chasing the second one a day later.
An Ontario carrier running 14 tractors moves five loads a week from Brampton to Dorval on a 06:00–10:00 receiving window. Dispatch used to phone each driver around 04:00 and relay a time to the customer’s inbox. Two people, both awake, both guessing.
The replacement is three rules. Geofence exit at Brampton posts a departure notice with the load number. Every thirty minutes the system recomputes arrival from position, remaining drive time and the window; if the projection crosses 10:00, one message goes out with the new estimate and a reason code drawn from the driver’s duty status. Geofence entry at Dorval posts arrival and attaches the signed delivery document once it is scanned.
The customer now hears from the carrier before they think to ask. Dispatch handles the one case a week where the projection is wrong, which is the case that always needed a person anyway.
There is a difference between telling a customer when a shipment will arrive and giving them a live position feed for a named employee. The Office of the Privacy Commissioner’s workplace guidance is that employers should have policies and procedures covering any monitoring of employees, that monitoring should be addressed in a way that is reasonable, proportionate and minimally intrusive, and that those policies should be made readily available to employees. A shipper needs an arrival estimate. It does not need your driver’s route history, and handing it over is the kind of scope creep a policy is supposed to catch.
The practical setting: share load-level events (departed, projected arrival, arrived, delivered) and keep unit-level position inside the business. If a customer genuinely needs live visibility, agree it in the contract and tell the drivers.
Automation here is narrow and useful: it watches the projection, drafts the notice, attaches the document, and files the timestamps. It can also read the appointment window out of a rate confirmation so nobody keys it twice, and flag the loads whose window was never captured at all — usually the ones that go wrong.
It does not decide. Whether a delay is reportable, whether to offer a concession, whether a driver is fit to continue, and whether an hours-of-service extension was lawfully taken are judgements a person makes and signs. The tool shortens the search and removes the 04:00 phone call.
A status update on a shipment the customer has already tendered is not prospecting. Canada’s anti-spam law carves out messages that solely facilitate, complete or confirm a commercial transaction that the person previously agreed to enter into from the consent requirement in paragraph 6(1)(a). Keep the message operational — the moment you add a sales pitch, you are in different territory.
You fall back to a person, briefly. Transport Canada’s instruction to drivers is to tell the motor carrier as soon as the vehicle is parked, switch to paper daily logs until returning to the home terminal, and record the malfunction code, the date and time the malfunction was noticed and the time the carrier was notified in the record of duty status. Your customer messaging should degrade gracefully to a manual update rather than going silent.
Whoever is paying you gets it by default, and whoever is opening the door gets it by agreement. Set that in onboarding, in writing, with named contacts — an arrival notice sent to the wrong inbox counts as no notice at all.
A 30-minute call is enough to tell you whether AI pays for itself in your back office.
