A delivery estimate moves from 2 November to 4 November. That is the headline, but it is not yet an explanation. Has the cargo arrived? Is a replacement collection slot confirmed? Can the receiving team rely on the new date?
Our shipment milestones and exceptions workspace separates those questions. The exception page explains the interruption; the arrival plan records the response and who must act. A changed date alone would conceal too much.
State what changed and what did not
The sample shipment loses its planned terminal appointment. A replacement collection window is requested for 3 November, moving the delivery estimate by two calendar days. The cargo remains 18 pallets; no discrepancy is recorded.
This is a scheduling exception. Keeping the quantity and the reason visible prevents a general warning from implying loss, damage or a different operational problem. The person reading the record can focus on the affected leg: terminal to local depot.
Explain what the changed delivery date depends on
Separate confirmed events from conditional plans
Arrival is recorded in the milestone history. The replacement slot has been requested. Collection still requires an acknowledged appointment and release readiness; final delivery still requires transfer completion and receiving acceptance.
Those states should not look equally settled. The new arrival plan is labelled conditional and its receiving window is requested, not confirmed. An operations team can discuss the proposed plan without presenting it as a promise.
| Record | Meaning in this example |
|---|---|
| Arrival recorded | An event appears in the shipment history |
| Replacement slot requested | A response is still needed |
| Collection proposed | Depends on acknowledgment and readiness |
| Delivery estimated | Depends on the preceding transfer and acceptance |
Give the response its own record
Revision 02 identifies the next steps: confirm the terminal appointment, collect and transfer, then receive the delivery. Each step has an owner. The receiving instructions retain the shipment reference, requested window and expected quantity.
The plan also gives an escalation point. If the slot is not acknowledged at the review time, the local legs need replanning before another delivery estimate is issued. That is more useful than a red badge that remains on the screen indefinitely.
When work stops
- 01IdentifyName the interruption and affected record.
- 02AssignGive the response an owner and permitted action.
- 03ResolveRecord the event that allows work to continue.
Our maintenance timeline applies the same idea to a failed visit. The return appointment is understandable because the access problem remains in the history. Our backorder workspace applies it to stock decisions. The response differs, but each exception needs a relationship to the work it interrupted.
Do not confuse a retry with a new decision
A failed notification may be suitable for a controlled retry. A changed collection plan needs coordination. A proposed substitution may need approval. Labelling all three “retry” hides the authority and information each response requires.
For a live integration, establish whether an earlier action already took effect before repeating it. The workflow orchestration guide covers tooling for retries and approvals. The interface must expose enough state for the operator to understand what the system knows and what remains uncertain.
Resolve the work, not just the warning
Closing an exception should correspond to an event that permits progress: acknowledgment received, access confirmed, replacement approved or another defined resolution. Dismissing the alert alone does not establish that the underlying problem is fixed.
Turn the delay into an owned response
The dashboard guide explains how summary counts should lead into these records. In automation systems, we use interrupted scenarios alongside normal completion when reviewing the workflow. The person handling the exception should be able to explain what stopped, what is known and what they are responsible for doing next.
Sources and calculation notes
The shipment example follows EX–019 and arrival-plan revision 02. The estimate moves from 2 to 4 November (two calendar days), while the sample quantity remains 18 pallets. Collection acknowledgment and receiving acceptance remain conditions of the revised plan.
- Our shipment milestones and exceptions project. The project page includes the design account, delivered scope and screenshots discussed in this article.
- Our residential property maintenance project. The project page includes the design account, delivered scope and screenshots discussed in this article.
- Our stock allocation and backorder desk project. The project page includes the design account, delivered scope and screenshots discussed in this article.
External references checked on 31 October 2026.