A practical starting point
Start with a unique identifier, the latest confirmed status and the unresolved issue. Separate shipments that need review, assign a next action and record the decision. Detecting an actual delay also requires a promised date and an updated source.
Download the delivery tracker
Track the promised date, the latest update, the owner and the next action for each shipment. The workbook includes a blank template and a worked fictional example.
XLSX · Spanish · 15 KB · Editable in Excel or Google Sheets.
Start with the blank template. Enter the review date and use one row per shipment. Confirm each update with its source before changing the status.
Six steps to organize pending deliveries
Collect information by shipment
Use the same identifier in the spreadsheet or system and in conversations. Record origin, destination, status and the source of the latest update. Check that identifiers match before connecting chats.
Define what counts as a delay
Compare the promised date with a reliable update. Distinguish a confirmed delay from a shipment with no recent information. Agree on a threshold with the team for that operation rather than using a universal deadline.
Separate exceptions
Create a list of shipments that need a decision. Examples include an unconfirmed destination, a missing detail or a delivery awaiting verification. RC-1003 in the demo illustrates the first situation.
Assign the next action
For real operations, define who will confirm the detail, where they will check it and when they will review the shipment again. If information is missing, keep the case open instead of assuming it is resolved.
Record the decision and its reason
Confirm the detail before continuing. Keep the change and its reason visible so another person can understand what happened. The demo lets you continue transit after confirming the destination or place the shipment on hold because information is missing.
Review open cases and communicate confirmed facts
Check unresolved cases and verify that the status is consistent before updating the customer. Measure how long the team takes to find context and resolve each exception before estimating potential savings.
What to do with the information available
| Situation | Next action | What to avoid |
|---|---|---|
| Destination unconfirmed | Check the detail and record a decision with a reason | Proceeding with an assumed address |
| An update is missing | Check the source and keep the uncertainty visible | Treating missing data as confirmed delivery |
| The promised date has passed with no confirmed delivery | Review with the responsible person and agree on the next update | Promising a new deadline without confirmation |
| Destination confirmed and transit cleared | Record the confirmation and continue according to the process | Repeating the review without checking the earlier decision |
| Delivery confirmed by a valid source | Update the status with the relevant evidence | Closing the shipment just to remove it from the list |
Try reviewing a shipment
Find a shipment, review its destination and record the decision to continue transit or keep it on hold.
Read the English transcript
This ZaTek demo brings together six shipments. When information is scattered, answering a query means piecing the journey back together.
Here, the list and the summary show the same operation.
We find a shipment and see its origin, destination, parcels and status.
An exception needs a human decision and a reason.
Saving the review changes the status and updates the summary.
The activity log keeps the decision. Changes stay in this browser, even after reloading.
We can export the shipments as a CSV file. Bringing the context together helps reduce searching and repeated reviews, with decisions recorded.
We reset the data to try the workflow again.
- Select EN in the demo. Find RC-1003 and open its details.
- Choose Continue transit and Destination confirmed, or Place on hold and Information pending.
- Save the review and check the new status in the summary and activity.
- Export the CSV to see current statuses. Use Reset demo to restore the sample.
Bring this workflow into your operations
The demo brings together six shipments and saves changes in your browser. You can search, review and record decisions. To use this workflow in your operation, we first define data sources, owners and connections to your tools.
Common questions
Do I need to replace my TMS or spreadsheet?
Start by identifying the missing information and decisions. A solution may use the existing system if it provides access to the required data. Scope depends on those capabilities and the process.
How can we connect this workflow to WhatsApp or Slack?
We define the information your team needs and assess the available access to connect your tools. The demo lets you try shipment search and review in your browser.
Is a shipment with no updates delayed?
Compare the promised date with a reliable update. If either detail is missing, mark the shipment for review.
What should I measure before automating?
Time spent reconstructing status, the number of exceptions and time to resolution. Record the source and measurement period so you can compare the same process later.