A trailer's location is known continuously for 1,400 miles and then becomes a matter of opinion for six hours. It arrives at the facility, checks in at the gate, and enters a zone where the system of record is a clipboard, a whiteboard, or a guard's memory.

This is the yard, and it is the least instrumented segment of the entire freight journey. It is also the segment that generates detention, breaks appointment schedules, and produces the "the truck arrived hours ago, where is it" conversation that consumes an afternoon.

Why the gap exists

The yard falls between systems. The TMS tracks the load to the facility and considers its job complete. The WMS starts when goods hit the dock. The interval between gate-in and dock-assignment is owned by neither, and in most operations it is managed by people talking to each other.

That produces a specific set of failures:

• Trailer lost in the yard — What actually happened: Parked, not logged to a spot · Downstream cost: Hours of search
• Driver waiting, unaware — What actually happened: No dock available, nobody told them · Downstream cost: Detention
• Dock idle with trailers waiting — What actually happened: Assignment not communicated · Downstream cost: Throughput loss
• Appointment marked missed — What actually happened: Truck arrived on time, processed late · Downstream cost: OTIF penalty
• Empty not released — What actually happened: Nobody tracking equipment status · Downstream cost: Carrier relationship
• Live-unload became drop — What actually happened: Decision made verbally · Downstream cost: Billing dispute

Every one is a coordination failure rather than a physical one. The trailer is there. The dock exists. What is missing is a shared, current record of which is where and what happens next.

Detention starts in the yard

The economics make this hard to ignore. The American Transportation Research Institute puts driver detention at roughly $15.1 billion annually — about $3.6 billion in direct expenses and $11.5 billion in productivity losses — with drivers detained in 39.3% of all stops and accumulating 117 to 209 hours a year of waiting.

A large share of that clock runs in the yard, and most of it is a driver waiting without information. The gap between "arrived" and "being unloaded" is where detention accrues, and it is precisely the gap nobody is watching.

That connects directly to whether the charge can even be billed later. Detention entitlement depends on arrival and departure timestamps, and if the yard is not producing those as structured records, the accessorial is unbillable regardless of what actually happened.

How do you get visibility into yard operations?

You get yard visibility by treating gate-in, spot assignment, dock assignment and departure as recorded events with timestamps rather than as verbal handoffs — and by pushing status to the driver and the broker automatically, so the arrival-to-dock interval is observable instead of being reconstructed afterwards.

The four events that need to be structured:

1. Gate-in. Timestamp, trailer, carrier, load reference. This starts the detention clock and it is the one most often captured on paper.
2. Spot assignment. Where the trailer physically is. Without it, finding a trailer is a search.
3. Dock assignment. When it happened and which door — the event that ends the waiting interval.
4. Departure. Timestamp and equipment disposition, which closes the clock and the appointment loop.

Once those exist as events, everything else becomes derivable: dwell time by carrier, by customer, by shift; detention exposure in real time rather than in arrears; and an honest answer to "when will this be unloaded."

The communication half

Structured events solve measurement. They do not, by themselves, stop a driver sitting.

What stops the driver sitting is somebody telling them what is happening — and telling the carrier's dispatcher, and telling the broker whose customer is waiting. That is a continuous stream of small notifications across three parties, which is exactly the work that does not get done when a yard is busy.

An agent handling it changes the experience materially: the driver knows they are third in line rather than wondering; the dispatcher can plan the next load; the broker can update the customer without calling the facility. This is the same proactive notification principle that reduces inbound volume everywhere else — the questions stop arriving because the answers arrived first.

It also matters commercially. With 86% of brokers reporting that capacity is harder to find, a facility that treats drivers well is one carriers will accept loads to, and that reputation is built out of exactly these small interactions.

Where to start

Yard management systems are a real product category and a real project. Most operations do not need to begin there.

Begin by making the four events structured and the notifications automatic, using the data and channels you already have. Gate logs, appointment records and driver communications exist in every operation — they are just not connected, timestamped or shared.

That gets you dwell measurement, detention visibility and a materially better driver experience without a capital project, and it tells you whether a full system is justified. It also feeds the warehouse-side automation that depends on knowing what is actually in the yard waiting to be worked.

What to measure

• Gate-to-dock dwell, by shift, carrier and customer. The core metric, and one most facilities cannot currently produce.
• Percentage of arrivals exceeding the free window. Direct detention exposure.
• Trailer location accuracy. How often a trailer is where the record says it is.
• Driver notification rate. The share of waiting drivers who received a status update.
• Appointment adherence versus dock adherence. The gap between arriving on time and being worked on time, which is where OTIF misses hide.

That last one is the diagnostic that reframes the conversation. A facility can hit its appointment numbers while systematically failing to work trucks on schedule, and only measuring both reveals it.

Frequently asked questions

Do we need a yard management system to fix this? No, not to start. Structuring four events and automating driver and carrier notification delivers most of the operational benefit using existing data. A full YMS is a reasonable next step once dwell is measured.

Who owns the yard, operationally? That is often the root problem — it falls between transportation and warehouse ownership. Assigning it explicitly is usually a prerequisite for fixing it.

How much detention is actually yard-related? It varies by facility, but the arrival-to-dock interval is where most on-site waiting accrues. Measuring gate-to-dock dwell is the way to find out for your own operation.

Does this help with OTIF? Yes. Trucks arriving on time and being processed late produce appointment failures that count against you, and the gap between appointment adherence and dock adherence is invisible without yard timestamps.

The bottom line

The yard is the one segment of the journey with no system of record, sitting directly upstream of a $15.1 billion detention problem and a meaningful share of OTIF failures.

Make gate-in, spot, dock and departure structured events with timestamps, notify the driver and carrier automatically instead of leaving them to wonder, and measure gate-to-dock dwell. You do not need a yard management system to start — you need the interval to stop being invisible.

Debales deploys AI agents for freight quoting, order processing, ETA updates, and multi-channel customer communication — keeping drivers, carriers and customers informed through the arrival-to-dock interval that nothing else watches. Book a demo.