Required ELD events include driver, vehicle, duty-status, time and location data.
Optional dispatch or fleet products may add other operational fields, so fleets should inventory each field instead of treating every data stream as a required ELD record.
What this means for your fleet
Create a data map that names each field, whether it is required ELD data or an optional product field, its purpose, recipient, retention period, and access or deletion process. Treat integrations and downloaded reports as separate copies with their own controls.
Build a field-level ELD data map
| Data group | Typical authorized purpose | Control to document |
|---|---|---|
| Driver identity and duty record | HOS recordkeeping and review | Driver/safety access, edit history, retention, export recipients |
| Vehicle position and movement | Required ELD events or separately purchased fleet operations | Purpose boundary, precision, history, geofence users, after-hours access |
| Optional fleet-product fields | Separately contracted operational workflows | Field inventory, read/write rights, retention, integration copies, legal hold |
| Downloaded files | Inspection, audit, payroll, tax, or support | Named recipient, encrypted storage, deletion date, revocation test |
Driver notice should explain who can see each data group, why, for how long, and where a correction or access request goes. The fleet should test removal of a former administrator and a lost phone rather than relying on a policy sentence.
What to check
Use these checks before changing a log, policy, device, integration, or buying decision.
| Check | How to verify |
|---|---|
| 1. Inventory collected data | List each collected field, source device, purpose, system destination, retention period, owner, and deletion path. |
| 2. Define purpose and lawful use | Map every use to the fleet policy and applicable obligation; flag secondary uses for legal or privacy review. |
| 3. Limit role access | Export roles and permissions, test a least-privilege account, remove access, and retain the revocation result. |
| 4. Review integrations and exports | Diagram each integration and export recipient; record fields, frequency, credentials, contract owner, and shutdown test. |
| 5. Publish an incident and driver-request process | Keep the incident route, driver access/request route, response owner, target times, sample exercise, and corrective actions. |
Common failure modes
- Using location data for undisclosed purposes.
- Unrestricted supervisor access.
- Keeping exports after the business need ends.
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.
- Official ELD technical FAQ covering engine synchronization, VIN, odometer, position, data transfer, events, and device behavior — Federal Motor Carrier Safety Administration.
- 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.
- Small-business cybersecurity quick-start guidance — National Institute of Standards and Technology.
- Current first-party product, plan, feature, and support representations; dynamic facts require release-date recheck — Factor ELD.
Review access and data flow
List every administrator, driver device, integration, export destination, retention rule, and credential-revocation path. Factor ELD can demonstrate its current product; rule applicability remains a fleet compliance decision.