What’s inside: monitoring · output checking
The question this file answersWhy does a clerk write a note about every returned container, including the ones that came back with nothing wrong?
Fits: logistics teams where claims and exceptions share an inbox with routine mail.
A typical pattern, no measured desk behind it — the logistics playbook carries no empty-return volume, and we state none. Return instructions, depot confirmations and damage photos arrive together. A clerk opens each, matches the box to its booking and writes a line in the pool record — damaged or not.
Typical, from the industry playbook — not a client's day.
At the end of the day the equipment clerk has a short queue of returns with something wrong — a photo, a depot mismatch — each with the paperwork already in it, and the pool record is current for everything else without their typing. What used to be an afternoon of notes becomes a few decisions.
Typical, not a measured client result. Every figure here comes from the playbook source named below.
clean returns closed in the pool record, disputes to the equipment clerk — same build as our BOL/POD-to-tracking file; no published figure for empty returns
Before: a clerk writes a note for every box, including the ones that just went home. After: matched returns close in the pool record on their own; damage and depot disputes open a file for the equipment clerk. No source, no percentage.
No published benchmark covers empty-return administration, so this file carries no percentage. The DHL (2022) dispatch-document figure stays on the parent file and is not borrowed here. Not a container-pool recovery rate.
Your container-pool record and TMS stay — CargoWise, SAP TM or the spreadsheet that is honestly the pool today. The same document-to-tracking build as our BOL/POD file, aimed at empties:
Damage liability. Depot arguments. Customer-owned equipment. No model closes a pool dispute.
Not a container-pool recovery rate.
Depots that confirm by phone, or by a photo of a paper form, leave little to read — those returns stay manual until the depot sends data. If your pool record does not hold the expected depot, every return looks like a mismatch for the first weeks.
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.