Delivery exception triage
Sort arriving shipment exceptions by customer impact and route each one to an owner with a next step.
Every morning, pre-check yesterday's deliveries against our open orders, and send me the late or short ones with a draft note to each supplier.
| Situation | What to do |
|---|---|
| More than 2 days late | Draft a chase note |
| Short by 5% or more | Draft a claim note |
| Wrong item | Flag it for me |
The job, and what good looks like.
## What breaks Every exception looks the same in the tracking feed, so the delivery that matters most is worked last and the customer calls you first. ## What the workflow does - Open exceptions are pulled from carrier tracking with their cause, revised date and affected order. - Exceptions are ranked by customer impact: named account and contract date first, minor delays last. - Each one gets a single owner and a single next step, including whether the customer is told. - Repeat causes from the same carrier or lane are grouped so the pattern is visible. - Reshipment, credit and claim decisions are drafted with the supporting evidence attached. ## What a human approves The logistics lead decides who gets contacted, the account owner approves any commitment to the customer, and finance approves any credit.
When it is handled
- Customer contact before the customer asks
- Every exception has a named owner
- Time to resolve exceptions cut in half
Works with tools like
- project44
- FourKites
- Descartes
- Motive
Ready-made automations. Pick the one that fits.
Each one is a plain-language document. Run it as it is, or change the timing, the rules and the tools to match your team.
Carrier exception digest
Every weekday at 8am, group open carrier exceptions by cause and post the summary with counts.
Every weekday at 8:00am
Delivery pre-check
Every morning, pre-check yesterday's deliveries against our open orders, and send me the late or short ones with a draft note to each supplier.
Every morning
Proof of delivery chase
Find delivered shipments with no signature after 48 hours and email the carrier contact for the record.
When a delivered shipment has no proof of delivery after 48 hours
Reshipment approval draft
When a carrier claim is confirmed, draft the reshipment or credit decision for the account owner to approve.
When a carrier confirms a shipment lost or damaged
Shipment delay alert
When a shipment turns delayed, notify logistics and the account owner with the revised date and the cause.
When a shipment status changes to delayed
You stay in charge.
At every step.
It checks and drafts. Your team decides what is ordered and sent.
- No order placed on its own
Requisitions and supplier notes wait for a buyer to approve and send.
- Undo what you don't want
Every step is recorded, and a file it changed can be put back.
- Only the systems you connect
Each automation reaches only the folders and apps you give it.
Delivery pre-check
Approve before it updates the sheet and sends the email?
Before you download.
- Where does it run?
- On your Mac or Windows computer, in the background. It keeps working after you close its window, and only reaches the folders and apps you connect for each automation.
- How does it connect to our CRM and other tools?
- Through each app's own connection where it offers one, signed in once by you, or by using the app in a browser the way you would. Each automation gets only the connections you give it, and the tools a page names are examples you can swap for your own.
- Does it run when my computer is asleep?
- It keeps your computer awake while a job runs and just before a scheduled one. While the computer is closed or off, nothing runs; when it wakes, it checks the inbox, calendar and other sources it watches for anything that arrived meanwhile.
- How does my team use it?
- Each person who runs automations installs the app. Keep a project in a shared folder, such as Google Drive or a network drive, and teammates can open it and follow every run, while one person owns it and runs it.
- Do I need anyone technical to set it up?
- No. Download the app, add an automation in plain words, and connect only what that job needs. Nothing runs until you switch it on.
Already have tools for this? Here is the difference.
Your ERP's alerts and rules
Flagging thresholds inside the ERP.
They can't read a supplier's email or a scanned delivery note, or draft the next step.
Flowchart automation tools
Moving data between apps at high volume.
Real-world exceptions multiply branches until the flow is harder to follow than the work.
AI chat assistants
Explaining a document when you paste it in.
Deliveries keep arriving while nobody is asking, and the procedure lives in a chat.
AUTOMATE.md
Your routine, written in plain words. It runs on its own, follows your rules, handles the exceptions a flowchart can't, and asks you when it matters. The file stays yours, whichever AI model runs it.
Related workflows.
Supply chain tracking
Shows where goods sit across every tier and supplier, with the date at risk named while there is still time to change the plan.
Write your own
SLA monitoring
Measures carrier and supplier performance against the service levels actually agreed, and warns the owner before a missed target becomes a credit.
Write your own
Incident logging
Records every failure with its asset, cause and fix at the moment it happens, so a repeat fault stops being diagnosed from scratch.
1 automation
Start with one job.
Make it your own.
macOS — coming soon- 1
Get the app
It runs on your computer, next to your files.
- 2
Add the automation
Paste the instructions into the app, or save them as a file next to your work.
- 3
Try it, then turn it on
Run it once and check the result. It only runs on its own once you switch it on.