Your Drivers Spent 1,144 Hours Last Year Sitting at Warehouse Docks at $28/Hour While You Paid Them to Scroll Their Phones

By Ryne Bandolik · June 29, 2026 · 7 min read

Last Tuesday, three trucks from a 15-truck regional carrier arrived at three different warehouses at their scheduled times. All three waited 2-4 hours. The Walmart DC had a shift change and "lost" the appointment booked 48 hours prior. Sysco's Bob in receiving called in sick — and nobody else knew about the appointment. The third warehouse overbooked their docks and had five trucks ahead. Total driver wait time that day: 11 hours. At $28/hour loaded driver cost, that's $308 in paid wait time in ONE DAY.

Multiply that across the week: 22 hours of collective dock wait time. Across the year: 1,144 hours. Annual cost: $32,032 in paid driver time spent sitting. That doesn't count the opportunity cost — 1,144 hours that could have moved 280+ additional loads. And the fleet owner is paying drivers to scroll their phones because a warehouse employee can't find an appointment confirmation.

Why every dock scheduling tool fails the small carrier

Search for "dock appointment scheduling" and you'll find Opendock, MercuryGate, C3 Solutions, queueme.io, MobiDock, and Dashdoc. All of them are built for the warehouse side. The shipper or receiver pays for them. The carrier — the one doing the delivering, the one whose driver is burning $28/hour in the cab — has no seat at the table.

Here's what a small fleet (5-30 trucks) actually faces:

• Facility A requires appointments booked 48 hours in advance via a web portal — but the portal doesn't send confirmations and the shift supervisor doesn't check it until 7am
• Facility B uses a phone call to "Bob in receiving" who works 6am-2pm — Bob is great, but when Bob calls in sick, nobody knows your truck is coming
• Facility C uses a third-party scheduling platform (Opendock) — and your dispatcher now has to learn yet another login for one facility
• Facility D has no system at all — first-come-first-served, and if you arrive after 8am you're behind seven other trucks
• Facility E is a Walmart DC that will NEVER adopt your scheduling tool, no matter how good it is

The dispatcher tracks all this in a spiral notebook: "Mon — Walmart DC 6027, appt 7:30am, door 14. Sysco — call Bob. Kroger — portal, conf# 88472." The system works until it doesn't. And when it doesn't, a driver sits for three hours while you pay them.

The 5-part dock scheduling system that works with every warehouse's chaos

This system is built on one principle: you cannot change the warehouse's process, so you document it, systematize around it, and catch failure points before trucks leave the yard. Five components, $0 cost, 3 hours to set up.

1. The Facility Playbook — one page per delivery location

Create a Google Sheets workbook. Tab 1: "Facility Playbook." One row per delivery location you serve regularly. Columns:

• Facility name & address — the official name (not "the Walmart on 35") plus the exact dock address so drivers don't GPS to the front entrance
• Scheduling method — Portal / Phone / Third-party platform / None (first-come-first-served). This tells the dispatcher in one glance what process to follow
• Portal URL / login — if it's portal-based, the exact URL and shared login credentials. Bookmark these in the dispatcher's browser too
• Phone number & contact name — if it's phone-based. Include the backup contact for when the primary is out
• Contact hours — Bob works 6am-2pm. If you need to confirm at 4pm, you need a different number
• Lead time required — 48 hours? 24 hours? Same-day OK? Knowing this prevents the "we can't schedule you for tomorrow" panic
• Typical wait time — based on your own data (see Wait Time Tracker below). "Usually 30 min but can spike to 2hr if arrival is after 9am"
• Fastest doors — experienced drivers know: door 12 is always faster than door 3. Write it down so new drivers don't learn the hard way
• Special notes — "Must have PO# on BOL or they reject," "Security requires driver's license at gate," "No restroom access — use the gas station on Route 9"

This is the single most valuable document in your operations. When a dispatcher quits, the Facility Playbook means their replacement isn't starting from zero. When you add a new delivery lane, the first driver to that facility fills out the Playbook entry and the knowledge is captured forever.

2. The Weekly Dock Schedule — Gantt-style view

Tab 2 of the workbook: "Weekly Schedule." This is your command center. Columns:

• Day / Time blocks — rows for each day, columns for each hour block (6am, 7am, 8am…)
• Truck ID — which unit is assigned
• Driver name — who's behind the wheel
• Facility — from the Facility Playbook
• Appointment time — the confirmed slot
• Travel time from previous stop — auto-calculated in Google Sheets using your known drive times between facilities. This is the field that prevents double-booking a truck that physically can't make it from Facility A to Facility B in 45 minutes
• Confirmed? — Y/N. This is the column you check every morning (see Protocol #3)
• Notes — "Load #44892, 22 pallets, need liftgate"

Conditional formatting makes this visual: green = confirmed, yellow = awaiting confirmation, red = conflict (two trucks scheduled same time at same facility with one dock). The dispatcher can see the entire week at a glance — and more importantly, can spot the holes where a truck has 3 hours of unscheduled time between deliveries that could be filled with a backhaul.

3. The Morning Confirmation Protocol — 15 minutes that saves hours

This is the single highest-leverage routine in the system. Every morning at 6am, the dispatcher (or night dispatcher, or early driver supervisor) runs through three steps:

Cost of this protocol: 15 minutes of dispatcher time. Value: preventing even one 3-hour wait per week = $84 saved × 52 weeks = $4,368/year. And that's conservative.

4. The Wait Time Tracker — build the data that justifies change

Tab 3 of the workbook: "Wait Time Log." This is your ammunition. Every time a driver waits more than 15 minutes past their appointment time, the driver texts the dispatcher: arrival time, docked time. The dispatcher logs it:

• Date
• Facility
• Driver
• Scheduled appointment time
• Actual arrival time
• Actual dock time
• Wait minutes (auto-calculated)
• Reason (from driver: "shift change," "overbooked," "couldn't find appointment," "no reason given")
• Cost of wait (minutes × driver hourly rate ÷ 60, auto-calculated)

Within 4 weeks, you'll have a data set that tells you: Facility X averages 72-minute waits on Tuesdays. Facility Y is fastest — 12 minutes average. Facility Z has gotten 40% worse since they changed dock managers. This data does three things:

1. Justifies adding a wait-time surcharge to chronic offender facilities. "Our data shows your average dock-to-unload time is 82 minutes, 3x our lane average. Our new rate includes a detention surcharge after 30 minutes."
2. Informs routing decisions. Schedule Facility Z for 7am when they're fresh, not 2pm when the afternoon chaos has set in.
3. Exposes the cost to your own team. When drivers see the weekly total — "We lost $617 to dock wait time this week" — accountability improves. Nobody wants to be the driver whose facility is the outlier.

5. The Arrive Early vs. On-Time Decision Matrix

Not all facilities behave the same way. Some reward early arrival — if you're there at 6:45 for a 7:00 appointment, they'll take you early and you're out by 7:30. Others punish it — "your appointment is at 7:00, go park in the staging lot and we'll call you." The Decision Matrix, built from your Wait Time Tracker data:

This matrix turns tribal knowledge into an operating procedure. Every new driver gets it. Every dispatcher uses it to sequence the day. Within two weeks, wait time drops because trucks are arriving when each facility is most likely to process them quickly — not when the appointment says to arrive.

When your spreadsheet breaks — the bridge to automation

This manual system works beautifully for fleets with 5-30 trucks delivering to 10-25 regular facilities. At some point — typically around 40+ trucks or 30+ facilities, or when you add a second dispatcher — the spreadsheet hits its limit:

• The Morning Confirmation Protocol takes 45 minutes instead of 15 because there are too many facilities to call
• The Weekly Schedule has too many rows to scan at a glance — conflicts get missed
• The Wait Time Tracker has so much data that nobody analyzes it anymore — it becomes a data graveyard

That's the signal. You've proven the ROI of systematic dock scheduling. You know exactly which facilities are the problem. You know the dollar value of reducing wait time. Now you can justify automation — and you'll know exactly what to automate because you've been doing it manually:

1. Auto-confirm appointments — scripts that log into facility portals at 5am and verify today's appointments are still in the system, flagging cancellations to the dispatcher's phone before they leave for work
2. Auto-route based on real-time dock availability — if Facility A's portal shows no appointments available until 2pm but Facility B has a 10am slot, your dispatcher sees the trade-off instantly
3. Auto-alert on excessive wait time — when a driver's ELD shows they've been stationary at a facility for >30 minutes past appointment time, the dispatcher gets a notification to call the dock office
4. Auto-generate the Wait Time Report — weekly PDF with facility rankings, cost totals, and trend lines, emailed to the fleet owner every Monday morning

This is where Jobs Done Labs comes in. We build the automation layer that connects to your ELD, your facility portals, and your dispatch workflow — so your dispatcher stops being a portal-login-and-phone-call machine and starts being a strategist. And every engagement is covered by our guarantee.