What’s inside: monitoring · output checking
The question this file answersWhen did we last learn that a container’s free time had run out from the carrier’s invoice rather than our own screen?
Fits: logistics teams where claims and exceptions share an inbox with routine mail.
No measured desk behind this file — the playbook has no demurrage volume, so none appears here. Free-time terms sit in the carrier contract, gate events in the terminal portal, the invoice in accounts’ mailbox. Nobody watches the clock run; someone rebuilds the timeline after the charge has landed.
Typical, from the industry playbook — not a client's day.
Tuesday morning the operations lead sees which containers are close to their free time today and can act — collect, return, or phone the customer — rather than reading about it on next month’s invoice. When the demurrage invoice does arrive, the timeline is already there to check it against.
Typical, not a measured client result. Every figure here comes from the playbook source named below.
free time watched per container before the invoice — same build as our shipment-status file; no published figure for demurrage admin
Before: someone rebuilds a demurrage timeline after the charge has already landed. After: the clock is visible per container while there is still time to act, and the invoice is checked against a timeline that already exists. No percentage without a source.
No published benchmark covers demurrage administration. The DHL (2022) and Capgemini (2023) figures on dispatch documents and status replies belong to the parent file and are not applied here. Not a demurrage-recovery claim.
Your TMS and the tracking feeds stay — CargoWise, SAP TM, project44 or the ones you run. It shares the status build of our shipment-status file, pointed at the clock:
Who owes the charge. Reading the contract. Customer goodwill. No model writes off a charge.
Not a demurrage-recovery claim.
Free-time clauses differ per carrier, port and contract year; if they are not written down as rules, the first weeks are spent extracting them, not saving time. Terminals without a feed leave gaps — a box with no gate-out event looks late when it is not, so those go to a person.
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.