Every visit moves through the same stages: through the gate, at a dock, work started, work complete, off the dock, out of the gate — and, for a dropped trailer, dropped and collected. YARDtwin records when each stage happened (from the gate, the dock screens, a connected warehouse system, a dock sensor or the fleet's own telematics) and measures the time between them. Stage targets say how long each of those gaps may take; when one runs long, the people you choose are told once, and the stage shows amber or red on the dock board, the arrivals board, the yard map and the booking's timeline.
Stage targets are off until an administrator switches them on here. The timings are recorded either way, so the Stage performance report fills up from the day the site goes live.
Switch it on and choose who is told
- Open Site Admin → Features and find Stage targets & alerts.
- Switch Stage targets and alerts on.
- Warn at is the share of the target at which a stage turns amber (80 % by default); it turns red at the target.
- Built-in bell sends the alert to the roles under Bell goes to (ops managers and yard managers by default). Webhooks and notification rules get the same alert as the events stage.warning and stage.overdue, so a Teams channel, an e-mail or an SMS can carry it too.
- Trailer targets says when a dropped trailer gets its own targets: on drop visits only (the default), whenever a trailer is tracked, or never.
The stages and their targets
The table lists each stage with its switch, its mode and its configured minutes:
- Not docked — from the gate (for a dropped trailer: from the drop) until the vehicle stands at a dock.
- Work not started — at the dock, nobody has pressed Start.
- Unloading / loading — work under way; pauses are not counted. By default the target is the booking's estimated duration; set a fixed value to override it.
- Still at the dock — work complete, the vehicle still at the door.
- Not departed — off the dock, not yet out of the gate (on a drop visit: the whole time the tractor is on site).
- Trailer not collected — a dropped trailer whose work is complete, still on the yard (needs keep dropped trailers open under Handling).
Mode decides where the number comes from:
- Configured — the minutes in the table (or a rule, see below).
- Learned — the typical time for similar visits at your site, learned from its own history. YARDtwin groups closed visits by direction, handling mode, material, trailer type, carrier and pallet band and uses the closest group that has enough history (Minimum history, 8 visits by default). The learned column shows the site-wide figures: p50 is the typical visit, p90 the time 9 in 10 visits finish inside — the target.
- Learned, never below configured (the default) — the larger of the learned and configured values, so a tight learned value cannot alert on a normal day.
The learned figures are rebuilt once a day. Recompute baselines rebuilds them now; Backfill 180 days of history reads your closed visits from before stage targets existed, so learning can start the day you switch it on.
Rules for particular loads
A rule sets targets for the bookings it matches — by load type, material, handling mode and pallet band. The first matching rule wins over the configured and learned values. For example: Frozen loads get 90 minutes of unloading; drop visits of 34 pallets and more get 4 hours before "trailer not collected".
What you see when a stage runs long
- On the dock board, the arrivals board and the yard map: an amber (running long) or red (overdue) chip such as Not docked 42 / 30 min, with the basis of the target when you hover (site rule, site default, booking estimate, learned from 41 visits).
- In the booking's timeline: every stage with its time and where that time came from (gate, operator, WMS, dock sensor, GPS), and each measured gap against its target.
- In the bell, once per visit and stage: first the warning, then the overdue.
A truck followed by its own telematics gets a little slack: an hourly tracker cannot prove a stage was not passed between two fixes, so the overdue alert waits one reporting interval.
Where the numbers go
Every closed visit writes its stage timings. The Stage performance tab of SLA monitoring shows them per carrier, dock, material, handling mode or week — how many visits, the typical and the p90 time, and the share over target — and the report builder has a Stage timings dataset for your own reports.