How to Track BTW Hours Defensibly (Audit-Proof Timekeeping)

Here's the paradox at the center of ELDT compliance: federal law sets no minimum behind-the-wheel hours — and yet BTW hour records are the single most important thing an investigator will ask your school for.

Both halves of that are worth understanding, because schools that internalize only the first half are the ones producing the "no real BTW training" findings that headlined the 2025–26 enforcement sweeps.

No Federal Minimum Hours — So Why Do Hours Matter?

FMCSA's ELDT framework is performance-based. Per the agency's TPR FAQ, there is no minimum number of hours for BTW training and none for theory either. Completion standards are outcomes: theory requires an overall minimum assessment score of 80 percent, and BTW completion turns solely on the instructor's determination that the trainee has demonstrated proficiency in the required elements. The curriculum itself — every topic in the applicable appendix of 49 CFR Part 380 (Appendix A for Class A, B for Class B, and so on) — is mandatory; the clock is not.

So why keep meticulous hour records? Four reasons, in ascending order of severity.

1. State minimums exist even where federal ones don't. Some states layer BTW hour requirements on top of the federal floor — California and Texas are commonly cited examples, though you should verify your own state's current rules with its licensing agency rather than rely on any list. If your state sets a minimum, your hour log is your compliance proof, full stop.

2. Proficiency claims need evidence behind them. "The instructor determined proficiency" is the legal standard — but a proficiency determination with zero documented seat time behind it is an assertion, not a record. When trade press reports that top sweep violations included two-to-seven-day full programs, what made those programs indefensible wasn't an hour rule; it was that no plausible training history existed to support the certifications submitted.

3. Audits run on records. Your TPR listing rests on a self-certification, under penalty of perjury per FMCSA's TPR FAQ, that you comply with 49 CFR Part 380 Subpart G — including its recordkeeping requirements (§380.725). When investigators visited roughly 1,500 providers in December 2025 and conducted 1,426 inspections in a five-day February 2026 sweep (figures per trade press and CVTA reporting), the question on the table was whether certified training actually happened. Hour logs are how you answer.

4. Falsified records are the kill-shot violation. Falsification was a headline finding of the sweeps. A school with thin-but-honest records has a remediation conversation; a school with fabricated logs has an existential one. Your timekeeping system's first job is to make your honest records look as honest as they are.

Range vs. Public Road: Log Them Separately

BTW training has two components — range and public road — and your records should distinguish them for every session. Two reasons.

First, the curriculum appendices treat them as distinct instruction settings with distinct required elements, so proficiency documentation naturally maps to each.

Second, there's a structural rule operators sometimes miss: per FMCSA's TPR FAQ, theory and BTW may be delivered by separate registered providers — but both BTW portions, range and public road, must come from the same provider. You cannot accept a student who did range training elsewhere and finish only their road work. If your logs don't cleanly show that you delivered both components, your own BTW certification is the record that looks wrong. (This also means a student transferring mid-BTW effectively restarts BTW — worth stating in your enrollment agreement.)

What a Defensible BTW Record Looks Like

A defensible record has five properties. Miss any one and the record weakens; miss two and it invites the question you never want asked — "was this reconstructed?"

Contemporaneous. The record is created at the time of training, not batched at week's end from memory. Backfilled logs betray themselves: uniform durations, identical phrasing across sessions, ink and handwriting that don't vary across supposed weeks. Contemporaneity is the number-one credibility signal an investigator reads.

Timestamped. Start time and end time, not just a date and a duration. "4 hours" is a claim; "07:02–11:04" is an event. Timestamps also let your records cross-check against themselves — fuel receipts, vehicle telematics, scheduling calendars — and consistency across independent sources is what makes a record file convincing.

Attributed to a specific instructor. Every session names the instructor who delivered it — the same instructor whose qualification file shows a valid CDL and the credentials required under §380.713 and §380.605. This matters doubly because instructors without CDLs were a top reported sweep violation: attribution is how you prove your sessions were taught by qualified people, and it's also how one bad instructor's problem stays contained instead of contaminating every record in the building.

Signed by the student. A student signature or verified acknowledgment on each session (or each day) does two things: it creates a second witness to the training event, and it protects you against the fraud pattern regulators most fear — certifications for students who were never in the truck. A falsification allegation is much harder to sustain against records the trainee countersigned in real time.

Specific about content and setting. Range or public road; vehicle used; maneuvers or curriculum elements covered. This ties the hours to the appendix topics and turns your hour log into proficiency evidence — the actual completion standard — rather than a bare attendance sheet.

The Audit-Proof BTW Log: Field Checklist

Every BTW session entry should capture:

• Student name and ID
• Date, start time, end time
• Setting: range or public road
• Vehicle identifier (matching a vehicle documented under §380.711)
• Instructor name (matching a qualification file current under §380.713/§380.605)
• Curriculum elements / maneuvers covered (mapped to the applicable Part 380 appendix)
• Student signature or verified acknowledgment
• Instructor signature or authenticated entry
• Cumulative hours to date — split by range and road

And at the program level:

• A dated, instructor-signed proficiency determination for each student, referencing the session history behind it
• Totals that meet your state's BTW minimum, where one applies
• Records retrievable within an hour — sweep inspections were effectively unannounced

Paper Can Work — Until It Has to Scale

Nothing above requires software. A disciplined school with carbonless session sheets, a signature routine, and a filing cabinet can produce defensible records. The failure modes are human: the instructor who fills in the week's sheets on Friday, the clipboard that rides in a truck through a rainstorm, the totals column that drifts from the session entries, the one instructor whose logs are always vaguer than everyone else's.

Digital timekeeping earns its place by making the five properties automatic instead of habitual — entries timestamped at creation, instructor identity attached by login, student sign-off captured on a device at the end of the session, range and road tallied without arithmetic. That's the design behind DriverTrack's time and attendance module: the log your instructors keep in the truck is, unaltered, the file you hand an auditor.

The operating principle, however you implement it: record training the way you'd want to defend it — because since late 2025, "defend it" is no longer hypothetical.