Carrier milestones

A Carrier Milestone is a partner-reported event against a parent load and organization. It carries a tracking number, provider event identifier, occurrence time and reported delay minutes where available. The Dispatcher uses these details to identify the event and compare it with the load’s current status and promised delivery time. The event’s own status moves through Draft, Submitted, Approved, Rejected or Completed as the team reviews it.

The time the carrier says an event occurred is distinct from the time a decision is recorded. That separation matters when an event arrives late or is corrected. A late event should not rewrite the physical time, and a repeated provider event should not create an unexplained second operating effect. The milestone’s revision and the parent load’s revision give the reviewer context for any acceptance decision.

• Identify. Dispatcher matches the tracking number and provider event identifier to the intended parent load and organization.
• Submit. A milestone moves from Draft to Submitted with its occurrence time and available supporting evidence.
• Decide. The reviewer checks the linked load and event revision, then records the decision time when the milestone is accepted or rejected.

An event can add visibility without closing delivery. A carrier’s arrival message and a recipient proof reference answer different questions. The Dispatcher should continue to use Load Stops for actual visit times and the load for final delivery time, then compare those records with the reported carrier event.

Choose the carrier event sources and how a tracking number is associated with each Transport Partner. Agree which event types the team treats as useful milestones, what supporting evidence is required and who can submit them. The provider event identifier should be retained as received so repeated imports or corrections can be recognized.

Set a review rule for inconsistent events. If the partner reports delivery but the recipient proof is absent, the team should hold final delivery until the stop evidence is checked. If an occurrence time is later than the promised delivery time, compare it with the original promise while keeping the reported event time. Operation Receipts can hold the resulting operation key, expected revision and effect references for reconciliation.

A partner sends a milestone for a load already in transit. The Dispatcher checks that the tracking number belongs to the partner and that the provider event identifier has not already been accepted. The milestone is linked to the load and organization, records the reported occurrence time and any delay minutes, and moves to Submitted. The reviewer looks at the current load and milestone revision before recording the actual decision time.

If the event is accepted, the milestone may be marked Completed and its receipt can show the recorded effect. If the event conflicts with the route or load, the Dispatcher can mark the milestone Rejected and retain the decision time. Operations Analyst can compare reported delay minutes with the final actual delivery time. The final delivery decision still uses the recipient proof and load record.

• Submitted milestones — Partner events awaiting review with tracking number, event identifier and occurrence time.
• Milestone board — Draft, submitted, approved, rejected and completed events grouped by status.
• Receipts needing review — Event effects whose local receipt still needs reconciliation.

See carrier event review and corrections and reconciliation.