Fleet ELD and Telematics Upgrade

Pull the current ELD device list by VIN with firmware version, contract end date, and any open malfunction tickets. Flag any units running on the FMCSA revoked-device list — those are unauthorized for HOS recording and must be replaced before the next compliance review.

List the functional needs the new platform must meet: HOS per Part 395.20, DVIR capture per Part 396, IFTA-grade GPS mileage by jurisdiction, inward/outward dashcam, AI event detection, two-way driver messaging, and TMS integration. Note which are must-have vs. nice-to-have so vendor scoring is honest.

Only consider devices listed on FMCSA's registered ELD page — Motive, Samsara, Geotab, Omnitracs, EROAD, and similar. Confirm none of the shortlist appears on the revoked-device list. Request a sandbox tenant from each finalist for hands-on dispatcher testing.

Cross-reference each tractor's engine model and ECM port (J1939 9-pin, OBDII, or older J1708 6-pin) against the vendor's supported-vehicle list. Pre-2000 engines and some legacy Detroit and Cat ECMs need adapter cables or fall under the pre-2000 ELD exemption.

Pin down term length, per-unit pricing, hardware warranty, SLA for support response, data ownership on contract termination, and an explicit clause for FMCSA-revocation replacement at no cost if the vendor's device is delisted. Have legal review the data ownership and indemnification language.

Pick five to ten tractors covering each engine family and route type — long-haul OTR, regional, and any local P&D. Have the shop document install time and any wiring quirks; that data drives the labor estimate for the full rollout.

Cover duty-status changes, sleeper-berth split, personal conveyance, yard moves, ELD malfunction procedure (paper logs within 24 hours, repair within 8 days per 395.34), and DVIR completion in-app. Each pilot driver signs the training acknowledgment for the DQ file.

Pilot drivers log on both the old and new device for two weeks so dispatch can reconcile duty-status records and confirm GPS, mileage by jurisdiction, and HOS clock match. Reconciliation gaps are the most common reason a fleet-wide cutover fails on day one.

Build the install calendar tractor-by-tractor against the dispatch board. Stack installs on home-time days or during the weekend reset so drivers don't lose revenue miles. Plan for two hours per tractor including the dashcam mount and calibration.

Export each driver's prior eight days of duty status from the legacy ELD and import to the new platform so the 60/70-hour clock carries over correctly. A clean cutover happens at midnight Sunday so the new device starts with the weekly recap intact.

Pull the FMCSA registered-ELD page on the day of cutover and save a dated screenshot to the compliance folder. Check the revoked-device list at the same time. Roadside inspectors will ask for the device name and model — drivers should know where to find both in-app.

Rewrite the ELD section of the driver handbook to match the new device's malfunction codes and recovery steps. Per 395.34, drivers revert to paper logs within 24 hours of a malfunction and the carrier has 8 days to repair. Each driver signs the updated handbook acknowledgment for the DQ file.

Add dashcam lens cleaning, SD card health check, and ELD cable seating to the A-service PM checklist in Fleetio or Whip Around. Dashcams ride dirty for months on grain or dump fleets — a dirty lens means useless footage when you need it for an accident defense.

Set up the after-hours phone tree so a driver stuck at a scale at 2 a.m. with a malfunctioning device reaches vendor support, not a voicemail. Document the escalation path from driver to dispatcher to vendor in the malfunction SOP.