§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
Roadworthy HQ has no hours-of-service screen. It does not import ELD data, store records of duty status or supporting documents, or detect HOS violations. On the ELD side it keeps a per-vehicle registry of the device (provider, model, serial, FMCSA registration ID) and checks it daily against FMCSA's revoked-device list, with warnings ahead of the replacement deadline. A driver can be marked short-haul on their profile so the audit-readiness check stops expecting logs from them.