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
If your fleet still uses a legacy system, verify the registered ELD and installed software version, test the vehicle connection and data transfer, retain the old records, and retrain drivers.
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 document the changeover? | Record the last legacy event, first ELD event, driver and vehicle assignments, exported records, any problems, and who approved the switch. |
What to check
| 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. Review legacy modes with the provider | Ask the provider which legacy settings should be disabled under the documented procedure. Save the configuration before and after the change, record who approved it, and test the ELD afterward. |
| 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
- Relying on an outdated AOBRD comparison.
- Assuming an old device is compliant after a software change.
- Discarding migration records.
Limits and exceptions
Use this guide to plan your checks; it does not determine whether a legal exception applies, certify a record, or guarantee compliance, safety, savings, or audit results. Preserve original ELD records and edit history. Use the current rules to determine applicability and the manual for your installed device for operating instructions.
Sources and review date
Reviewed August 10, 2026. Check the latest rules and product information before changing your procedures or signing a contract.
- 49 CFR Part 395: hours of service and ELD requirements — Office of the Federal Register and U.S. Government Publishing Office.
- 2015 ELD final rule — Federal Register / Federal Motor Carrier Safety Administration.
- FMCSA registered ELD list and self-certification guidance — Federal Motor Carrier Safety Administration.
- FMCSA general ELD questions — Federal Motor Carrier Safety Administration.
- Factor ELD products, plans, and support — Factor ELD.
Verify the rule and the installed workflow
Have your device registration, manual, app version, carrier policy, and a sample record ready for the demonstration. Factor ELD can show the product workflow; your fleet remains responsible for deciding which rules apply.