These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Logistics Tracking System
- Process
- Review carrier events
Review carrier events
Match a reported event to its parent load, preserve event time and inspect its effect before acceptance.
Step by step
-
Identify event Dispatcher
Dispatcher matches the tracking number and provider event identifier to the intended load and operating organization. The carrier-reported occurrence time stays with the event.
- Ties the event to the right operating scope
- Updates Carrier milestones, Loads, Organizations
-
Submit milestone Dispatcher
Dispatcher moves a Draft milestone to Submitted with the available event details and supporting evidence. The parent load and milestone revisions establish the review scope.
- Preserves reported event time and supporting file
- Updates Carrier milestones, Record attachments
-
Check evidence Dispatcher
Dispatcher checks the current load state, event identity and any recipient or stop evidence related to the report. A repeated provider event should resolve to its earlier result.
- Compares report with current load and stop history
- Updates Loads, Load stops, Carrier milestones
-
Record outcome Dispatcher
The review outcome and decision time are recorded on the milestone. Its receipt retains the operation key and linked effect, with Completed reserved for reconciled work.
- Records decision time and operation result
- Updates Carrier milestones, Operation receipts
Who does what
Roles and permissions- Dispatcher
- Submits and checks the event; Operations Reviewer examines disputed effects; Load Owner sees the impact on the load; Operations Analyst compares reported delay with final delivery timing.
Set up Logistics Tracking System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.