AOBRD grandfathering ended for federal ELD compliance in December 2019. Fleets subject to the ELD rule should evaluate a currently registered ELD and should not treat an old AOBRD label or legacy mode as a compliance substitute.
What this means for your fleet
The useful comparison today is migration evidence: exact registered device and software version, current vehicle connection, retained legacy records, driver retraining, and a verified transfer workflow.
What fleets should use now
A fleet subject to the current federal ELD rule should use an exact active ELD hardware/software combination from FMCSA’s registered list. It should not treat an AOBRD label, old mode, or legacy hardware name as a substitute for current registration and operation under the ELD requirements.
| Legacy question | Current decision |
|---|---|
| Does the device have an old AOBRD mode? | Do not rely on the label; verify the active ELD registration and installed software version. |
| Are historical records still available? | Retain the required set and document the old-to-new system boundary. |
| Were drivers trained on the ELD workflow? | Rehearse login, statuses, edits, certification, unidentified driving, malfunction, and transfer. |
| Can the fleet prove the cutover? | Record last legacy event, first ELD event, vehicle/driver mapping, export, defect, and approval. |
What to check
Use these checks before changing a log, policy, device, integration, or buying decision.
| Check | How to verify |
|---|---|
| 1. Verify current ELD registration | Save the dated official-list match for exact device name, hardware, software, registration ID, current status, and installed version. |
| 2. Remove undocumented legacy modes | Retain configuration screenshots, provider documentation, vehicle/device inventory, removed legacy setting, approver, and post-change acceptance test. |
| 3. Retain required historical records | Keep the required legacy and current record ranges, originals, edits, certifications, file hashes, retention owner, retrieval test, and gaps. |
| 4. Retrain drivers on edits and certification | Retain role-specific training on login, statuses, edits, certification and unidentified driving, with versions, completed tasks, coaching, and retest. |
| 5. Test roadside transfer | Save driver/vehicle, requested range, supported method, routing entry, receipt or displayed result, failure branch, defect, and retest. |
Common failure modes
- Publishing a dated comparison.
- Assuming an old device is compliant after a software change.
- Discarding migration records.
Limits and exceptions
This guide does not decide a fact-specific legal exception, certify a record, or guarantee a compliance, safety, cost, or audit outcome. Keep the original ELD record and any edit history. Use the current official rule for applicability and the exact installed-device manual for screen-by-screen actions.
Sources, review date, and limits
Reviewed August 10, 2026. Each source supports only the point described beside it. Rules and product details can change; recheck dynamic facts before changing a fleet workflow or signing a contract.
- Current 49 CFR Part 395 text covering HOS limits, exceptions, RODS, supporting documents, ELD duties, and technical requirements — Office of the Federal Register and U.S. Government Publishing Office.
- 2015 ELD final rule, rule history, implementation basis, performance requirements, and supporting-document changes — Federal Register / Federal Motor Carrier Safety Administration.
- Official registered-device list and manufacturer self-certification/non-endorsement language — Federal Motor Carrier Safety Administration.
- Official general ELD FAQ covering in-cab information, retention, special driving categories, and vehicle/engine questions — Federal Motor Carrier Safety Administration.
- Current first-party product, plan, feature, and support representations; dynamic facts require release-date recheck — Factor ELD.
Verify the rule and the installed workflow
Bring the exact device registration, installed manual, app version, carrier policy, and one example record. Factor ELD can demonstrate its current product; rule applicability remains a fleet compliance decision.