01 / Capture the facts
Record the load reference, appointment time and timezone, latest verified update, its source and the time received. Write unknown where evidence is missing. An absent update is not proof that a driver is late.
FROM THE FIELD GUIDE / 03
Close the
exception loop.
One issue. One owner. One next action. One update time.
02 / Name the impact
Separate a confirmed service failure from a risk that needs checking. Note the customer commitment affected, any cutoff and who can authorize a change. Follow your company's escalation rules.
03 / Assign the next action
Use a specific verb: contact dispatch, confirm the appointment, request the document. Assign one accountable owner and a next-update time. Contact dispatch to confirm ETA by 13:30 CT is actionable; follow up is not.
04 / Communicate what is known
Use this structure: current facts, action underway, next update time. Do not turn an unconfirmed ETA into a customer promise. If the commitment needs changing, route it to the authorized decision-maker.
05 / Close with evidence
Record the resolution source and timestamp. Confirm the customer record and next operator's view are updated. Reopen the issue if new information contradicts the resolution.
Try it on one load.
Choose an open exception. Can the next operator identify its owner, next action and next update without asking you? If not, fill those gaps before the handoff.