On this page
Quick Overview
A practical slot audit that connects dock bookings, gate events, door time, and the decision owner without inventing a benchmark.
Why a dock appointment slot needs an audit
A dock schedule can look full while the building still runs late. The booking sheet shows a promised window, but it rarely shows when the trailer arrived, when the gate cleared it, and when a door actually became free. A slot audit connects those records so a manager can see where the planned time was lost. The audit is not a scorecard for carriers; it is a short evidence review that separates a scheduling problem from a receiving or shipping problem. That distinction matters before anyone changes capacity or penalizes a partner.
Define the slot record before pulling data
Start with one row for each booked appointment in the review period; record the carrier, load type, booked window, gate-in time, door assignment, door-open time, and release time. Add the person who changed the slot and the reason code for each change. If the facility uses a yard system, keep the yard move timestamp beside the door event. The row should identify the shipment or load without copying commercial documents into the analysis file. A stable row definition is what makes the next audit comparable.
Compare booking, gate, and door clocks
The booked window, the gate clock, and the door clock answer different questions. Booking shows what the facility promised, gate-in shows when the vehicle entered the property, and door-open shows when work could begin. Compare them in that order instead of collapsing them into one arrival time. A trailer that arrives early but waits for a door is a capacity signal, while a trailer that arrives after its window is a carrier or traffic signal. Record both conditions before assigning a cause, because a single late timestamp rarely explains the full wait.
Check whether slots match usable capacity
Count the appointments booked in each half hour and compare that count with the doors and labor the facility actually staffed. A schedule can promise more simultaneous arrivals than the receiving team can unload, especially when one door is reserved for a dedicated account. Mark blocked doors, planned maintenance, and shift meetings on the same timeline. If the booking count exceeds usable door capacity, the fix may be a scheduling rule rather than a faster unload. Keep the capacity number visible so the audit does not become a debate about memory.
Separate carrier delay from facility delay
A late arrival and a late unload are not the same finding; use gate-in, door-open, and release events to split total time into arrival variance, door wait, and processing time. Assign each segment to the party that controlled it, but leave disputed cases marked for review. Do not rank carriers by a single late appointment when traffic, weather, or a dock closure explains the gap. The useful output is a count of segments by owner and a short list of repeated patterns. That evidence supports a conversation without turning the audit into an accusation.
Test one change with a dated follow-up
Choose one change that the evidence supports, such as staggering a peak window or protecting a door for a recurring account, and write the change, the owner, and the effective date in the audit record. Re-run the same measure after the change and keep the original sample for comparison. If the result is mixed, report the mixed result rather than selecting the favorable week. A small test with a clear before-and-after window is more credible than a broad redesign. The follow-up should also confirm that the change did not shift the problem to another door.
Keep the audit short enough to repeat
The audit works when a supervisor can prepare it from existing records in under an hour; keep the fields small, the reason codes controlled, and the capacity note current. Store the export and the notes with the review date so the next analyst can reproduce the counts. Review the audit monthly during peak season and quarterly when volume is stable. If the file grows into a second appointment system, remove fields until it fits the original purpose. The test is whether the team can name the next action after one short review.
