Magellan
Dispatch shift handoff: transfer the next action
Hand over load exceptions with the current fact, driver instruction, next trigger and person accepting responsibility, so pending decisions survive a shift change.
At 17:05, the evening dispatcher can see the load number, the driver and tomorrow's delivery appointment. What they cannot see is that the appointment is being changed, the replacement confirmation has not arrived and the driver was told to wait for an update before leaving the current stop.
The load transferred successfully. The responsibility did not. This is how a perfectly ordinary shift change becomes a late-night emergency: the incoming person receives the normal record while the unresolved decision remains in the outgoing person's memory.
A load list answers what exists. A useful handoff answers what the next person must do. Include the exception, the last confirmed fact, the current instruction, the next trigger and the owner. If the record does not change anyone's next action, it may be background information rather than a handoff item.
FMCSA's Safety Management Cycle treats roles, communication, monitoring and meaningful action as connected parts of safety management. FMCSA Safety Management Cycle (https://csa.fmcsa.dot.gov/Documents/FMC_CSA_12_002_SMC_Overview.pdf) The operating method here applies that general principle to the everyday work of moving exceptions across shifts.
Start with the cases that can change while the original employee is gone: unresolved appointments, equipment restrictions, driver availability, missing customer instructions and deadlines for a response. Routine completed loads can remain in the normal system.
Situation: identify the load and the specific issue. “Receiver change pending” is more useful than “customer problem.” Current fact: state the latest confirmed information and its source. Instruction: explain what the driver and other parties have already been told.
Next trigger: identify the time or event requiring action. Owner: name the incoming person responsible and the escalation contact if they cannot resolve it. These fields are a suggested internal format, not a regulatory form.
A complete entry could read: “Load 214, delivery change requested. Original appointment remains the only confirmed slot. Customer emailed at 16:40; driver told no route change until confirmation. Evening dispatcher to follow up at 18:00 and escalate to duty manager if unresolved.” The entry gives the next employee a starting point without forcing them to search a whole conversation.
Shift changes amplify ambiguous wording. “Moved to Tuesday” may mean the customer requested Tuesday, the receiver offered Tuesday or the driver has accepted a verified Tuesday plan. Those are different states with different consequences.
Use words that identify the event: requested, offered, confirmed, acknowledged, assigned. Where possible, link the underlying communication. If the official load field is changed before the new instruction is confirmed, preserve the uncertainty explicitly rather than making the screen appear more certain than the facts.
For equipment, carry the actual operating instruction and its source. “Shop tomorrow” leaves tonight’s availability unresolved. If an earlier message was wrong, the current owner must correct the instruction through the approved safe-contact route and record acknowledgment; editing the historical note alone does not reach the people who already used it.
Sending a message is not proof that another employee accepted responsibility. Build a brief acknowledgment step for material exceptions. The incoming dispatcher confirms ownership and asks about any unclear trigger before the outgoing person leaves when practical.
Do not turn this into a meeting about every active load. Concentrate on the few items that need judgment or follow-up. A crowded handoff containing dozens of routine lines makes the dangerous exception harder to find.
If there is no overlapping shift time, use a monitored queue with assigned responsibility and a defined escalation route. The arrangement must reflect how the business actually operates at night and on weekends. A process that assumes a supervisor is always available should be tested against the supervisor's real schedule.
Consider a hypothetical load whose pickup is delayed. The day dispatcher asks the customer for a revised delivery slot but leaves before receiving an answer. The handoff says “appointment adjusted,” and the evening dispatcher reasonably assumes confirmation exists.
At midnight, the driver reaches a facility that cannot receive the load. The investigation initially blames the evening shift for failing to verify the appointment. That misses the earlier point where a request was described as a completed change.
Keep the original confirmed appointment until a replacement is established, show the pending request and assign its follow-up. In this example, the incoming owner also corrects the earlier driver instruction and records the response. That addresses both the misleading status and its practical consequence.
Choose where the team keeps its current record of open exceptions. That may be the dispatch system or a shared register that designated staff maintain. Everyone handling the work should know where to find the latest decision.
Topics
- SOPs
- Shift handoff
- Exceptions
- Dispatch procedures