§395.24 sets the driver-side ELD operating requirements: log in to the ELD using the driver's own credentials, manually annotate duty status when the device cannot capture it automatically, review and certify the prior day's log before driving, and add the required annotations to any edit. The rule's purpose is to make sure the ELD's record matches the duty status actually worked.
Severity weight
Severity weight 1 in the HOS Compliance BASIC. The weight is low, but a §395.24 finding often appears alongside §395.8 "false report" citations (weight 7) and §395.22(h) "ELD not properly used" findings — the cluster is what auditors look at, not the single weight.
How to prevent it
- Train drivers to certify the prior day's log before driving — uncertified logs are the most common §395.24 finding.
- Use unique driver credentials. Shared logins produce both §395.24 and §395.8 false-record findings.
- Annotate every edit at the time of the edit, in plain English ("forgot to switch to on-duty when fueling at 0612").
- Set the ELD to alert on missed certifications, untranscribed unidentified driving time, and prolonged personal-conveyance.
How Roadworthy HQ helps
ELD findings logged in Roadworthy HQ link to the driver's record and surface against the §395.11 supporting-documents file. Patterns — uncertified logs, repeated edits without annotations, unidentified driving time — are visible in the HOS dashboard before they become §385.337 corrective action.