What
Picture the audit before it happens. An investigator sits down with your records and asks two questions that decide whether the day goes smoothly or turns expensive. First, who was driving when the vehicle moved with no driver logged in? Second, can you prove that any change a driver made to their hours-of-service record left a clear, unbroken trail? Answer those well and the rest of the review tends to follow. Answer them poorly and you are explaining gaps instead of documenting compliance.Start with the phrase itself. Unassigned driving time means the vehicle recorded movement, but no driver was attached to that event. It happens constantly in normal operations. Someone shuffles a truck across the yard before a shift. A driver takes a different tractor for a short repositioning move. A unit rolls onto a ferry and off again. The device logs the motion, the location, and the engine status, but nobody claims it. Left alone, that segment sits in your system as an unidentified driver event, and during an ELD compliance audit it reads as a gap in your records.How you handle it day to day matters more than any last-minute scramble. Make reconciliation a routine, not a project. In practice, an unassigned event should be reviewed and assigned within the window long before anything becomes permanent. Set a fixed time each morning for your back-office team to open the unassigned driving list, match each event to a driver using the vehicle assignment, dispatch records, yard logs, or the driver's own recall, and assign it. Then note who made the assignment and why, because that note becomes part of the record you may have to show later.Some events are awkward. The driver may have left the company, or nobody remembers who moved the truck. When that happens, you still cannot leave it open. Assign it through an administrative process that reflects reality as closely as you can, and keep the supporting detail with the event. An auditor reviewing the record wants to see that you investigated and documented, not that you ignored it. A stack of unresolved entries with no explanation is what triggers trouble.Now the second question, and arguably the tougher one. Driver log edits have to be traceable. Any compliant system must store both the original entry and the edited version, along with who changed it and when. If your fleet tracking software only shows the final number, you cannot demonstrate that trail, and the log loses its credibility. When you review your setup, test it: have someone edit a log in the test environment and confirm you can pull up the before and after records side by side. Ask whether those records can be exported.That export matters because submission happens in a defined format. FMCSA regulations require ELD records to be transferable to an investigator through the standard output file, so confirm your system produces it cleanly and that your drivers can hand over data at the roadside. Before an audit, pull a sample of HOS logs, the unassigned driving reconciliation history, and the edit trail for those same days. Check that the Required Data Elements, meaning engine hours, vehicle location, miles driven, and engine status, are captured automatically through the engine control module connection rather than typed in by hand.One honest caveat. Good fleet tracking software is necessary, but it is not sufficient on its own. The hardware needs ELD certification, your process has to run consistently, and your team has to understand what the records mean. No tool removes the daily reconciliation work, and no checklist replaces human judgment when an edge case appears. Treat the software as the foundation, and your audit-day preparation as the walls built on top of it. Do both, and you walk into the review with evidence instead of explanations.