User Manual
Help Center/User Manual/Drayage Driver Performance: Trips, On-Time Rate, Turnaround and Waiting Time by Driver

Drayage Driver Performance: Trips, On-Time Rate, Turnaround and Waiting Time by Driver

Last updated 2026-10-26

See how each driver is doing — trips, containers, on-time rate, average turnaround and waiting time — all from the order events you already record.

Driver Performance answers the question dispatchers and owners ask every week: "Who is carrying the work, who is on time, and where does waiting pile up?" Open Drayage → Driver Performance (/drayage/driver-performance), pick a date range, and Docklify ranks every driver by trips completed in that period, with containers, on-time rate, average turnaround and waiting time side by side. Everything comes from the order events your drivers and dispatchers already record — no extra data entry.

How each number is counted#

Trips: an order counts as one trip for its driver when it is completed inside the period. Containers: completed trips that carried a container. On-time rate: Docklify compares the actual arrival event with the order's appointment — arriving exactly at the appointment time counts as on time. Orders with no appointment, or no recorded arrival, are left out of the rate (you will see the sample size next to the percentage, like 18/20). Average turnaround: from pickup to completion, averaged over the trips that have both events. Waiting: the waiting start/end events drivers record on each order, paired up and summed. Containers are counted one per completed order — the current model is one container per order, so the same container moved on separate orders counts once per order. Note: the on-time rate here is based on actual arrival events; the on-time figure on the Drayage overview (dashboard) is calculated on a different basis, so the two numbers can differ — use this page when judging a driver.

Approximate work hours — read this first#

The "Approx. work hours" column is an approximation: for each day, Docklify takes the time between the driver's first and last recorded event that day and adds the days up. It is NOT attendance time and NOT hours-of-service (HOS) time — standby and driving time with no recorded events is not included, and a day with a single event counts as zero. Use it to compare workload patterns between drivers, not as payroll hours. If you settle drivers by trips, the settlements in Docklify use the trip list, not this column.

Drill into a driver's orders#

Click "Orders" on any driver row to see every completed order behind the numbers: order number, container, completion day, whether it was on time, its turnaround and waiting time. If a figure looks wrong, this is where you check it — the order's own event timeline (on the order page) is the source of every number. Drivers with no completed trips and no events in the period are listed separately under the ranking instead of appearing with zeroes, so an empty row never looks like a bad score.

Accept-confirmation time#

When drivers confirm orders on their phones after dispatch, the ranking also shows the average time from dispatch to confirmation — a quick way to spot orders that sit unconfirmed. There are two different "No data" situations: (1) your organization does not have dispatch-confirmation data yet — then the page shows a short note above the ranking, and this column fills in automatically once that data exists; (2) confirmation data is already there, but no driver confirmed an order in the selected period — then there is no note, and the column simply has no sample for that period. In both cases no number is invented.

Docklify features used in this article: Driver Performance (/drayage/driver-performance) for the ranking and drill-down; order events on each order page for the underlying timeline; Driver Settlements for per-trip pay (a separate, money view of the same completed trips).