Treadstone Associates
Article · 11 min read

Dispatch shift handover checklist

A regulatory clock started on the outgoing dispatcher’s shift does not pause when they go home. Build the handover around the deadlines, not around the trucks.

Treadstone Associates · Updated 2026

Key takeaways

  • • Hand over four hours numbers per working driver, not one: daily driving, elapsed time, cycle position and the last 24-hour reset.
  • • An hours violation found during the shift triggers an immediate obligation to act and to record what was done — it cannot wait for the morning.
  • • A trip inspection defect that has not been certified as corrected means the vehicle does not move on the next shift.
  • • Generate the clocks from your logging data; keep the judgement, and the signature, with a person.

The short answer

A handover has to pass on three things, and only the first is usually done well: loads in motion, clocks that are running, and open obligations with a legal deadline attached. The third is where handovers fail, because a regulatory clock started on the outgoing dispatcher’s shift does not pause when they go home. Build the checklist around the deadlines rather than around the trucks and it stops being a conversation and starts being a record.

Section one: loads in motion

The conventional part. For every load on the board: truck and driver, current position, next appointment and its window, whether the appointment is confirmed or assumed, any accessorial already incurred, and who at the customer has been spoken to. Note which appointments were rescheduled during the shift and by whom — a rescheduled appointment that nobody at the receiver has confirmed is the single most common source of a next-morning surprise. See missed warehouse appointment slots and proving detention time to a shipper.

Section two: clocks that are running

For each driver still working, the incoming dispatcher needs four numbers, not one: driving time accumulated today against the 13-hour driving and 14-hour on-duty limits; elapsed time against the 16-hour rule, which prohibits driving after 16 hours have elapsed since the last period of at least 8 consecutive hours off duty; on-duty hours accumulated in the cycle against 70 hours in 7 days on cycle 1, or 120 hours in 14 days on cycle 2; and the date of the last 24 consecutive hours off, since a driver must not drive unless they have taken at least 24 consecutive hours of off-duty time in the preceding 14 days.

Two flags belong in the handover because they change what the next shift may do. If a driver is deferring off-duty time under section 16, the record of duty status must carry a declaration stating that, and clearly indicate whether the driver is on day one or day two — day two has a hard 20-hour combined off-duty floor and a 26-hour combined driving ceiling. And if anyone extended their hours because of an emergency or adverse driving conditions, the reason must be recorded in the record of duty status. Both are things the outgoing dispatcher knows and the incoming one cannot infer.

Section three: open obligations with a deadline

This is the section worth building the checklist around.

An unresolved non-compliance. If the shift found an hours violation, the obligation has already started. A motor carrier must monitor each driver’s compliance and, on determining non-compliance, must take immediate remedial action and record the dates on which the non-compliance occurred and the action taken. British Columbia goes further: the carrier must issue a notice of non-compliance to the driver, record the date of the non-compliance and of the notice, record the action taken, require the driver to sign and date an acknowledgment of receipt, and retain both for 6 months from the date of the non-compliance. “I’ll deal with it tomorrow” is not one of the options in that sentence.

A vehicle with an uncorrected defect. In British Columbia a carrier must not permit a driver to drive before the carrier or its agent has repaired or corrected the defects listed on the trip inspection report that may affect safe operation and certified on the report that the defect has been corrected, or certified that correction is unnecessary. If that certification has not happened, the truck does not move on the incoming shift, and the handover has to say so explicitly rather than leaving it in a maintenance queue.

An out-of-service driver. An out-of-service declaration applies for 10 consecutive hours where the driver contravened the daily driving limit, 8 hours for the mandatory off-duty provisions, and 72 hours where records were duplicated or falsified, and the director or inspector notifies both the driver and the motor carrier in writing of the reason and the period. The incoming dispatcher needs the end time, not the fact.

A border transmission not yet sent. In the highway mode the CBSA requires cargo and conveyance information to be received and validated within 30 days and no later than one hour before arrival at the first point of arrival; anything received less than one hour before the transmitted estimated time of arrival is accepted but flagged with an “insufficient review time” warning, with penalties potentially applicable. A pending transmission is a deadline, not a task.

A cargo claim in its notice window. Where a load originated in British Columbia, notice of loss, damage or delay must be given in writing to the originating or delivering carrier within 60 days after delivery, or within 9 months of the date of shipment where delivery failed, with the final statement of claim filed within 9 months. A shipper who called at 16:40 to say a skid arrived crushed has started a clock that the next dispatcher inherits.

Section four: paperwork clocks in the background

These rarely change hands mid-shift, but a weekly handover should surface them. A driver must forward the record of duty status and its supporting documents to the home terminal within 20 days of completing it, and the motor carrier must ensure they do; the carrier must then deposit them at its principal place of business within 30 days of receipt and keep them in chronological order per driver for at least 6 months. In British Columbia, trip inspection reports must be placed at the carrier’s principal place of business within 30 days of receipt and the originals kept for at least 3 months, and the carrier’s copy of each bill of lading must be retained for at least 3 years and made available for inspection. These are the records an auditor asks for; see how to prepare for an MTO facility audit.

Worked example: an 18:00 handover that went wrong, and the checklist that came out of it

A six-truck carrier ran two dispatch shifts with a verbal handover and a shared spreadsheet. One Tuesday the day dispatcher noted a driver had run 15 minutes past his daily driving limit at a delayed receiving door, mentioned it in passing, and left.

Nobody issued a notice. Nobody recorded a date. The driver was dispatched again the following morning by someone who had not been told. When the file was reviewed months later, the failure was not the original overrun — it was that no remedial action or record existed, which is a separate obligation the carrier owes in its own right.

The handover is now a form with three sections and a required field in each. Section three cannot be left blank; if there is nothing open, the outgoing dispatcher types “none” and their name is on it. The form takes about four minutes. The one line that changed the outcome is the one asking whether any non-compliance was identified this shift and what was done about it before the shift ended.

What to automate here, and what not to

The clock section should be generated, not typed. Remaining hours, elapsed-time windows, cycle position and the last 24-hour reset all exist in your logging data, and a handover that recopies them by hand introduces errors at exactly the point where errors are expensive. The same is true of pending border transmissions and open claim windows.

What must not be generated is section three’s judgement: whether a defect is safety-affecting, whether a driver should be stood down, whether a customer needs a call tonight. A tool can assemble the list and flag the deadline. A dispatcher decides and signs the handover. Keep the signature — it is the part that makes the record worth anything.

Common questions

How long should a handover take?

If the clock section is generated, five to ten minutes for a small fleet. If it is being typed from memory, it will take longer and be wrong.

Do we need a written handover, or is a call enough?

A call is fine for loads in motion. It is inadequate for section three, because several of those obligations require a dated record to exist — the carrier must record the dates on which non-compliance occurred and the action taken, and in British Columbia a signed driver acknowledgment must be retained. Write those down.

Who owns an obligation that spans the handover?

Name someone in the form. An obligation owned by “dispatch” is owned by nobody. The carrier remains responsible either way.

What about weekends and overnight gaps?

Same three sections, with a longer clock horizon. If nobody is covering, the handover has to say which deadlines fall inside the gap. Who covers dispatch after hours works through the staffing side.

Turn your handover into a record instead of a conversation.

We build the generated half from your existing logging data and leave the judgement with your dispatchers.