What’s inside: connections to your systems · step-by-step flow
The question this file answersHow often does “is my window still good?” get answered from an inbox rather than from the calendar?
Fits: logistics operators handling 100–500+ orders a day, where documents still arrive by email.
Typical pattern, not a measured desk — slot requests are not counted in the logistics playbook. Carriers e-mail for a time at the gate; someone types each into the yard calendar, then answers follow-ups from the same pile. It hurts the morning after a vessel, when everybody wants the same hours.
The morning after a vessel, the gate planner sees confirmed slots already sitting in the calendar and a short queue of clashes to settle by phone — not a mailbox to work through in order of arrival. Carriers asking whether their window still stands get the answer from the calendar record, not from a person’s memory.
Typical, not a measured client result. Every figure here comes from the playbook source named below.
slot requests booked into the calendar, clashes handed to the planner — same build as our email-order intake file; no published figure for gate appointments
Before: someone types every mailed slot request into the terminal calendar. After: free slots are booked and confirmed from the calendar; clashes go to the gate planner. No percentage here — the order-intake range lives with the parent.
No published benchmark covers gate-appointment intake. The McKinsey (2023) / Deloitte (2022) order-intake range belongs to the parent file and is not applied to slot mail. Not a dwell-time or turnaround claim.
Your yard or terminal system keeps the calendar — CargoWise, your yard tool or the shared calendar everyone really uses. Built like our email-order intake file, pointed at slot mail:
Overbooked hours. Breakdowns. Priority customers. Anything the calendar cannot absorb.
Not a dwell-time or turnaround claim.
If the calendar’s capacity per hour is not set honestly — trucks per door, breaks, shift change — the build books slots you cannot serve and the clashes arrive at the gate instead of at the planner. A request that names the wrong container number books nothing until a person looks.
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.