Published: September 14, 2026.
Delivery-window changes may arrive through email, portals, calls, or broker messages. A register makes the chronology visible and gives dispatch a clear receipt trail without letting administrative staff make routing or service commitments.
Record each observation
Create an event for the original appointment and every later message. Capture the time received, sender, channel, stated window, timezone, facility, load, and source link. Keep conflicting windows side by side until an authorized owner resolves them.
A phone note should name the caller, recipient, exact reported change, and promised written confirmation. Mark it as a reported statement.
Confirm internal receipt
Route the change to the carrier-designated dispatch owner. Record delivery and acknowledgement separately. If the owner asks for confirmation from the customer or broker, log that request and its result.
Administrative staff should not accept a changed appointment, reroute equipment, promise arrival, direct a driver, or interpret contract consequences. Use the approved escalation path when no owner accepts the handoff.
Keep downstream records aligned
After the carrier decision, record which scheduling, dispatch, customer, and driver-facing systems received the authorized update. Preserve earlier values in history. If one system cannot be updated, leave a visible exception.
Audit change chains
Sample a stable appointment, one accepted change, one conflict, and one late correction. Another reviewer should see exactly what was known at each point and who authorized the current value.
Working standard
The register succeeds when it separates outside statements, internal receipt, carrier decisions, and downstream distribution. That record reduces silent schedule drift without transferring dispatch authority.