When should a shipper status update say unconfirmed?
Format: Article.
Say unconfirmed when the evidence does not support the event you are about to report. A planned arrival is not an arrival. A source's report may still need a check. An old location does not establish a shipment's current state.
Use the label for the claim in doubt, not as a vague warning on the whole load. “Delivery unconfirmed” leaves out what the team knows. Try: “The carrier says it delivered. We still need the receiver to confirm.” This keeps the report without treating it as proof.
The evidence ladder below is a proposed operating method. It is not a universal freight standard or a feature claimed as installed in Core Agentic software.
Define what each event means
Define arrival, unloading, and delivery before sharing those labels. Which source can prove each step? What must staff check? A truck's location near a site may help with that review. It does not by itself prove that staff unloaded the goods or that the receiver accepted them. Keep those steps separate.
For this proposed event record, ask what happened, when and where it happened, who reported it, and what proof supports it. These are design questions for your team, not a claim that a standard requires this review method. A well-filled record still needs a source check.
Keep event time separate from the time your system received the update. A late message can describe an earlier event. Sorting only by receipt time may make an old event look like the newest physical state.
Use an event evidence ladder
| State | Meaning in this proposed method | Appropriate use |
|---|---|---|
| Planned | An approved plan names a future event | Explain the plan without claiming it happened |
| Reported | A named source says the event happened | Attribute the report and show what remains unchecked |
| Verified under policy | Required evidence was checked by the allowed reviewer | State the event with source and time context |
| Unconfirmed | Required evidence is absent, stale, or in conflict | Name the gap and next review owner |
Not every event will pass through each state. A plan may be canceled. A source may correct its report. New proof may cast doubt on an event staff already checked. Keep those changes in view. “Verified” means it passed the stated checks at that point. It is not a reason to ignore new facts.
The operations lead should set how old each kind of report may be for its use. One age limit will not fit all freight data. An old delivery record may still prove that past event. The same age may be too old for a claim about where a truck is now.
Match the wording to the gap
| Evidence condition | Suggested wording | Next owner |
|---|---|---|
| No arrival report | “Arrival is not yet confirmed. We are checking with the carrier.” | Assigned shipment coordinator |
| Old location only | “Last location report is from the stated time. Current arrival remains unconfirmed.” | Tracking or carrier contact owner |
| Carrier says delivered, receiver disagrees | “Delivery reports conflict. Our team is checking both sources.” | Exception lead |
| Delivery document received but not reviewed | “Delivery paperwork was received and is awaiting review.” | Document reviewer |
| Future appointment accepted | “Delivery is scheduled for the confirmed window.” | Appointment owner |
Before using a sentence, make sure its second half is true. “We are checking” should mean a person owns an actual check. Otherwise say that confirmation is pending and assign the task before sending.
A hypothetical conflicting update
Suppose a carrier message says a shipment was delivered. The receiving team says it has not found the goods. A location report shows the truck near the facility. These are hypothetical inputs, not customer records.
The person handling the shipment keeps all three sources. The truck's location does not settle the clash. Delivery stays unconfirmed because the carrier and receiver disagree. The last event both sides support stays in view. Staff do not discard a report just because it makes the screen harder to read.
The issue owner asks both parties to check the load number, site, and event time. A draft customer note states the conflict. It does not blame either party or promise when the team will settle it. Staff check the draft before sending it. The draft is not permission for an AI tool to send.
If the receiver later confirms the correct reference, the team records that new evidence and its source. If the answer remains unclear, the held state remains. The record should not advance merely because someone sent another request.
Make escalation useful
Each unconfirmed claim needs a reason, next check, owner, and due point. Is proof missing, or do two sources clash? Keep those reasons separate. They may need different people and questions. The owner should be able to tell what fact would clear the hold and who must check it.
If AI drafts the summary, use only approved records. A selected cloud model may process the prompts and files you send it. Agree on allowed data and provider terms first. Each factual claim needs a source. Test whether AI turns “expected,” “reported,” or “awaiting review” into a firm event. Reject that draft even if the rest reads well.
Bring your event labels and review rules to Core Agentic. Discuss a custom update design that keeps known facts and open questions apart. This is a design to discuss, not a claim that a live shipment feed is ready. Book a Demo.
Sources and scope
Core Agentic TMS and design context. The operating steps and fictional examples are first-party recommendations, not verified installed controls or customer results.