trucking back office operations

What a Driver No-Show Rate Can and Cannot Prove

A research brief on driver no-show rates for small carriers, separating a driver who missed a shift from a schedule that was never realistic.

Trucking VA Research Team · · 6 min read · 4 sources

Trucking operations visual for What a Driver No-Show Rate Can and Cannot Prove
Table of contents17 sections

Key takeaways

  • A no-show records that a driver did not report, not why the shift failed.
  • Separate voluntary absence, assignment error, and schedule infeasibility.
  • Report counts by driver, route, and notice time rather than one percentage.
  • Use the pattern to fix planning and communication, not to label drivers.

A dispatcher builds a Monday schedule and two drivers do not appear. One called in sick on Sunday night; the other was assigned to a load that started 300 miles from where his previous shift ended. The attendance report counts both as no-shows.

A driver no-show rate is a useful reliability signal and a poor judgment about people. This brief reviews what the measure can show, what it hides, and how to record it so the number supports a better schedule.

Defining the event

The conventional definition divides shifts with no report by total scheduled shifts. The edges decide the number: a driver who called in sick, a driver reassigned at the last minute, and a driver who arrived two hours late all produce different records.

Write the definition down and keep it stable. A rate that changes as the team learns the problem is not a trend; it is a series of different measures.

What the rate can show

The rate can show that scheduled capacity did not appear. It can show whether the problem is concentrated in one day, one route, or one group of drivers.

It can support a planning conversation when paired with notice time. A driver who gives two days' notice is a different planning problem from one who disappears on the morning of the shift.

What the rate cannot show

The rate cannot show why the driver did not report. Illness, family emergency, a licence issue, a misunderstanding about the start time, and a deliberate absence all produce the same event.

It cannot show whether the schedule was realistic. A load assigned with an impossible deadhead is not a driver failure, and the attendance report will not reveal the planning error.

It also cannot show whether the driver was the right assignment. A driver who refuses an unsafe load is not a no-show in any meaningful sense, even if the record says so.

Methodology and limits

This brief reviews public guidance on workplace records, internal control, and small-business operations, and maps it to a private dispatch schedule. The sources support documentation and review discipline; they do not establish a target attendance rate.

We tested the proposed fields against four common cases: a sick call with notice, a reassignment, a late arrival, and a driver who never received the schedule. The fields described here kept those cases distinguishable.

Separate the categories

Record voluntary absence, involuntary absence, assignment error, and late arrival as separate categories. Each has a different cause and a different response.

A single no-show count mixes a driver with a family emergency and a dispatcher who sent the schedule to the wrong number. The categories make the pattern honest.

Record the notice time

Record when the driver notified the carrier and how. A call at 6 a.m. for a 6 a.m. shift is not the same as a call two days earlier, even though both end in an uncovered load.

Notice time is the field that supports planning. A carrier with two days' notice can cover the load; a carrier with none cannot. The rate should show both.

Report by route and day

A total percentage hides the concentration. Report the count by route, by day of week, and by driver group.

A cluster on Monday mornings may reflect weekend scheduling or communication. A cluster on one route may reflect an unpopular assignment or a chronic deadhead. The fix differs.

A worked example

A carrier schedules 60 shifts in a week. Four do not report. Two called in sick with more than 24 hours' notice, one was reassigned to a different load, and one never received the schedule.

The headline rate is just under seven percent. The categories show one genuine coverage gap and three process issues. A response focused on driver discipline would have addressed the wrong problem.

Communication and scheduling

Most no-show events start with a schedule that was not clearly communicated. Confirm the shift, the start location, and the reporting time in one message the driver can find.

Record when the schedule was sent and whether the driver confirmed. A schedule sent at 9 p.m. for a 5 a.m. start is technically delivered and practically missed.

When to change a schedule

If a load cannot be covered, change the schedule before the shift rather than after. Record the change and the reason so the coverage gap is separated from a driver absence.

A schedule that changes constantly is a planning problem. The no-show rate will look unstable even when the drivers are reliable.

A note on fairness

A driver may refuse a load that is unsafe, illegal, or incompatible with hours-of-service rules. That refusal should never be counted as a no-show.

Record refusals separately with the reason. A rate that penalises a safety refusal will teach the wrong behaviour and damage trust.

Escalation

When a shift is uncovered with no notice, record the escalation to the operations lead and the action taken. The escalation is part of the record, not a separate conversation.

A repeated pattern with one driver needs a direct conversation. A repeated pattern across drivers needs a scheduling review.

Review cadence

Review the rate weekly and the categories monthly. The weekly pass covers immediate coverage; the monthly pass looks for planning and communication causes.

Keep the same definitions across reviews. A rate that changes shape cannot show whether a fix worked.

What to report to the carrier

Report the count by category, the notice times, and the routes affected. Add the coverage action taken for each uncovered shift.

A report that names drivers without the categories invites blame. A report that names the process invites a fix.

Seasonality

Freight volumes and driver availability change with the season. Compare the same month with the prior year where possible, and note the seasonal context beside the result.

A rise in the rate during a known peak may reflect the market rather than the schedule. The note prevents the number from being read as a sudden decline in reliability.

Data quality

Check for shifts with no assigned driver, schedules sent after the start time, and duplicate entries. These defects inflate the rate and make the review unfair.

Record the number of incomplete records beside the report. A high count is a finding about dispatch administration, not about attendance.

Conclusion

A driver no-show rate is a starting signal. Used with categories, notice time, and route data, it shows where coverage fails and what to fix. Used as a single number, it invites conclusions the record cannot support and puts the blame in the wrong place.

Sources and citations

  1. U.S. Government Accountability Office, Standards for Internal Control in the Federal Government, https://www.gao.gov/greenbook, retrieved 2026-11-19
  2. U.S. National Archives and Records Administration, Records Management, https://www.archives.gov/records-mgmt, retrieved 2026-11-19
  3. National Institute of Standards and Technology, Time and Frequency Division, https://www.nist.gov/time-frequency, retrieved 2026-11-19
  4. Federal Motor Carrier Safety Administration, Hours of Service, https://www.fmcsa.dot.gov/regulations/hours-of-service, retrieved 2026-11-19