What’s inside: company memory · routing
The question this file answersWho on my dispatch team spends the afternoon copying access codes and time windows out of e-mails?
Fits: carriers and forwarders whose dispatch documents still arrive as PDFs and photos.
A typical picture, not a client’s — the logistics playbook gives no count for pickup instructions. Windows, gate codes and “ring the bell twice” notes arrive in customer mail and sit next to the booking in the TMS. Every afternoon dispatch rebuilds tomorrow’s sheet from the same threads.
Typical, from the industry playbook — not a client's day.
After lunch the dispatcher opens a sheet that already carries the windows and codes for tomorrow’s known sites, each note showing which e-mail it came from, and a short list of stops that need a phone call. The scramble becomes the calls, not the copying.
Typical, not a measured client result. Every figure here comes from the playbook source named below.
tomorrow’s stops with codes and windows attached, source shown — same build as our BOL/POD-to-tracking file; no published figure for pickup instructions
Before: dispatch rebuilds pickup windows, gate codes and handling notes every afternoon. After: complete stops are on the sheet with their source shown; the odd site gets a call. We quote no percentage; the sourced range is the parent file’s.
No published benchmark covers pickup-instruction assembly. The DHL pilot (2022) figure of ~55% belongs to dispatch-document processing and is left on the parent file rather than applied here. Not an on-time-pickup claim.
Your TMS and dispatch board stay — CargoWise, Transporeon, SAP TM or the ones you run. Built the same way as our BOL/POD-to-tracking file, but pointed at outbound instructions:
Site constraints. Driver safety. The customer whose “usual” is not written anywhere.
Not an on-time-pickup claim.
A note that says “as usual” means nothing to a system — those stops go to the dispatcher, and if a customer’s rituals live only in a driver’s head they stay there until written down. Reading works on e-mail; instructions given by phone leave no trace to read.
The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →
Scoped in the audit — the playbook has no estimate for this exact desk.
That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.
Not a named Aperanda client. Process file · Logistics.
Short process file. Same build as its parent file; the playbook has no separate volume or benchmark for this desk.