Define events
Record booking, actual arrival, reception, handling and departure separately with clear ownership.
LOGISTICS / CAPABILITY
See waiting time
where it can be changed.
Use arrival, reception, handling and departure events to explain dwell time. Compare sites and customers using consistent event definitions and missing-data rules.
Explore the delivery scope ↓OPERATING MODELILLUSTRATIVE
- 01Orders, dispatch & WMS
- 02Match visits and events
- 03Separate waiting and work
- 04Adjust plans with operations
Conceptual data-to-operation flow, adapted to the agreed project scope.
What makes
this workflow difficult.
Treating all time between arrival and departure as waiting can misdirect improvement. Distinguish early arrivals, queues, handling and inspection, with a capture method the site can sustain.
THE SHORT ANSWER
Use arrival, reception, handling and departure events to explain dwell time. Compare sites and customers using consistent event definitions and missing-data rules.
DESIGN & DELIVERY
Design in the order the work happens.
Match individual visits
Use date, trip, location and booking identifiers rather than vehicle registration alone.
Show actionable patterns
Review long stays and congestion windows alongside averages to inform slots, staffing and load preparation.
DATA READINESS
Required data and the conditions to check.
A consistent format does not ensure operational usefulness. Confirm meaning, refresh and exceptions with owners, and keep missing information explicit.
| Data | Required fields | Checks |
|---|---|---|
| Gate events | Trip, vehicle, site and time | Re-entry and overnight visits |
| Handling | Start, end and operation type | Do not convert unknown values into zero |
| Bookings and shipments | Planned time, shipper and volume | History of revisions |
EVALUATION
Measure value in the workflow.
These are candidate evaluation measures. Establish a baseline and agree on data, period, targets and exclusions before work starts. They are not claimed performance results.
| Measure | Evaluation method |
|---|---|
| Event completeness | Visits with all required events divided by in-scope visits |
| Reconciliation effort | Dispatch and site time spent matching records |
| Dwell distribution | Median and long-tail stays for comparable trips |
Regulatory reporting requires separate confirmation of applicability and current official guidance. This scope designs measurement and integration for operational improvement.
Define deliverables
and acceptance.
Review data mappings, workflow, prototype and evaluation evidence before choosing production scope. Estimates distinguish assumptions because permissions and interface terms affect implementation.
Validate one site and a defined period of dispatch or waiting records.
QUESTIONS BEFORE YOU START
Questions before starting
Must we replace the dispatch system?
No. Begin with read-only analysis; design write-back separately after confirming interfaces and responsibilities.
How are targets set?
Measure current completeness and review effort, then agree on comparable metrics rather than adopting national averages as targets.
RELATED FIELD GUIDE
LOGISTICS / GUIDE
Where to start with waiting-time analytics: from gate events to operating changes
Before using a single arrival-to-departure duration, agree on reception, waiting and handling events. Build evidence that shippers and operating teams can use together.
Read the guide ↗YOUR OPERATION / OUR STARTING POINT
Start with the work you do today.
Tell us about the workflow, systems and reporting or documents that need attention. We will define a suitable phase, deliverables and assumptions.
Logistics and transport — discuss your project How scope and estimates work ↗