Stops and tracking

Dispatcher uses the stop schedule to plan the next pickup, delivery or service visit. Each stop belongs to a load and carries its sequence, location and appointment information. Window start and end describe the expected interval. Actual arrival and departure record what happened, giving the team a basis for explaining a delay after the truck moves on.

Tracking events add reported milestones against the load. An event identifies its occurrence time and source, with location or coordinates where available. A reported arrival and a completed delivery stop serve different purposes. Dispatcher checks the event against the stop before changing the operating status or asking Evidence Reviewer to verify delivery.

• Prepare the stop window. Review the sequence and location before releasing the schedule. Pickup and delivery stops need clear appointments and contacts so the receiving shift can coordinate with the right site.
• Identify the report. Keep the milestone type and reporting source with the event. A dispatcher entry, partner message and telematics observation can arrive at different times and need a consistent interpretation.
• Confirm actual progress. Update stop arrival and departure from operational evidence. Review missed appointments and exception events with the linked load, then carry the agreed next action into the dispatch handoff.

Agree who confirms an event and how the team handles contradictory reports. Decide which time zone applies to appointment displays and how external timestamps will be mapped. Telematics and partner feeds are connections to configure with an identified owner. Start by rehearsing the same milestones through the team’s normal dispatch entry process.

Keep the load’s delivery promise visible when a stop changes. An appointment correction may explain a revised operating plan, but the team still needs the actual delivery outcome when reviewing performance. Agree whether a late report corrects an earlier observation or becomes a separate event requiring investigation.

Load L-410 has a delivery window from 14:00 to 15:00. A partner reports arrival at 14:40, while Dispatcher later receives confirmation that the truck reached the gate at 15:10. Retain the source of each report and investigate which observation describes the actual stop arrival. The confirmed time should support the stop record and the explanation for any missed window.

Next, the driver completes delivery and supplies the receiving evidence. Dispatcher records completion against the delivery stop belonging to L-410. Evidence Reviewer can then examine that same stop when checking the proof of delivery. During rehearsal, substitute a pickup stop and confirm that it is recognized as the wrong context for delivery verification.

• Stop window schedule — Upcoming and exception stops with their appointment intervals.
• Reported tracking events — Load milestones awaiting confirmation, with their reporting source.

Use stop execution to delivery evidence to connect milestones to delivery checks. Review load planning to dispatch when a stop change affects resource commitments.