Disclaimer: This article is general information, not legal, compliance or procurement advice. arjankc.com.np does not rank or recommend software vendors and does not receive referral fees or commissions. Regulations, vendor features and pricing change; confirm current requirements with FMCSA, your legal counsel and each vendor’s own documentation.

Last reviewed: 13 October 2026

Fleet telematics and dispatch software sits at the center of trucking, delivery and field service operations. The same platform may need to keep hours-of-service records that satisfy federal law, route and schedule work, feed data to accounting and customer systems, and handle sensitive data about drivers. Choosing badly can mean compliance gaps, lost productivity and a multi-year contract that is hard to leave.

This guide sets out a vendor-neutral way to evaluate fleet telematics and field service dispatch management software. It covers the federal electronic logging device (ELD) rules, what telematics captures, dispatch and routing capabilities, integration and data questions, driver privacy, security attestations, total cost of ownership and contract terms. It ends with an RFP checklist and a weighted scoring template. It does not rank vendors or quote prices.

The regulatory baseline: the FMCSA ELD rule

For US motor carriers whose drivers must keep records of duty status (RODS), the ELD rule in 49 CFR Part 395, Subpart B (sections 395.20 to 395.38) sets the minimum the telematics platform must handle. If your fleet is covered, ELD compliance is not a feature to trade off against others; it is a pass or fail requirement.

Table of key FMCSA electronic logging device rules: registered devices, data recorded, malfunction deadlines, record retention and driver harassment protections

Chart: arjankc.com.np, from 49 CFR Parts 390 and 395 and FMCSA ELD guidance.

Who must use an ELD

The rule applies to carriers and drivers who are required to keep RODS. FMCSA’s ELD fact sheet lists the main exceptions: drivers who keep RODS no more than 8 days in any 30-day period, certain driveaway-towaway operations, and drivers of vehicles manufactured before model year 2000. Drivers using the short-haul timecard exception do not keep RODS and so do not need ELDs. Carriers may still choose to use ELDs voluntarily (FMCSA, ELD Fact Sheet).

Registered devices only

Under 49 CFR 395.22, a carrier may only use an ELD that appears on FMCSA’s list of registered devices. Vendors self-certify their devices, and FMCSA can revoke a registration. When a device is revoked, carriers generally have 60 days to replace it; FMCSA’s ELD news page records revocations, including devices removed on 9 July 2026. Ask vendors for their registration ID and check it against the current list yourself.

Section 395.22 also requires the carrier to keep a backup copy of ELD records on a separate device for six months, and to make sure drivers carry an ELD information packet: a user manual, instructions for transferring data to safety officials, malfunction instructions and a supply of blank paper graph-grids for at least eight days.

What an ELD records

Under 49 CFR 395.26, an ELD automatically records:

  • date and time;
  • vehicle geographic location;
  • engine hours and vehicle miles;
  • driver or authenticated user identification;
  • vehicle identification and motor carrier identification.

These elements are recorded at each change of duty status, at engine power-up and shut-down, and at least once an hour while the vehicle is moving. During authorized personal use, location is recorded at reduced precision, roughly within a 10-mile radius, and engine hours and miles are left blank in intermediate records.

Data transfer, malfunctions and retention

FMCSA requires ELDs to support one of two transfer options for roadside inspections: telematics (wireless web services and email) or local (USB 2.0 and Bluetooth). A display or printout must be available in either case (FMCSA, ELD Data Transfer).

When an ELD malfunctions, 49 CFR 395.34 requires the driver to note it and notify the carrier within 24 hours, and to reconstruct and keep paper RODS if hours-of-service recording is affected. The carrier must correct, repair or replace the device within eight days, or request an extension from FMCSA within five days of notification (FMCSA ELD FAQ, malfunctions). Carriers must keep RODS and supporting documents for six months under 49 CFR 395.8(k).

For evaluation, this translates into concrete questions: how the vendor detects and reports malfunctions, how quickly it ships replacement hardware, how backups are kept, and how the system handles personal conveyance and yard moves.

What telematics platforms capture beyond the ELD

Most commercial telematics platforms collect more than the ELD minimum. Typical data categories include:

Category Typical data points Evaluation questions
Location and trips GPS position, speed, heading, geofence events, stop durations Ping frequency, accuracy, offline buffering, coverage in your regions
Vehicle health Engine fault codes, fuel use, idling, odometer, battery voltage Supported vehicle buses and makes, mixed-fleet support
Driver behavior Harsh braking, acceleration, cornering, seat belt use How events are defined and whether thresholds are configurable
Video Road-facing and driver-facing camera clips, event triggers Retention, who can view, whether in-cab analysis uses biometrics
Assets and trailers Trailer location, reefer temperature, door sensors Battery life, sensor compatibility, alerting
Compliance HOS logs, driver vehicle inspection reports, IFTA mileage by jurisdiction Audit trail, edits and annotations, export formats

Ask each vendor to state, in writing, which data it collects by default, which is optional, and where it is stored.

Dispatch, routing and scheduling

For field service and delivery fleets, dispatch is where telematics data turns into daily work. Capabilities to evaluate include:

  • Job creation and assignment: manual, rule-based and automatic assignment by skills, location, availability and hours-of-service remaining.
  • Route planning and optimization: single and multi-stop routes, time windows, vehicle capacity, truck-specific restrictions such as height, weight and hazmat, and re-optimization when jobs change.
  • Scheduling: recurring appointments, technician calendars, shift rules and overtime limits.
  • Real-time tracking and ETAs: customer notifications, live ETA updates and proof of delivery or service with photos and signatures.
  • Mobile apps: offline mode, forms, parts and inventory lookup, and ease of use for drivers and technicians.

Vendors increasingly describe routing and dispatch features as AI-driven. Treat such claims as hypotheses to test, not facts. In a pilot, compare the software’s plans with your current process on the same historical jobs, measuring miles, on-time arrivals, overtime and dispatcher time. Ask how the optimizer handles constraints, whether dispatchers can override it, and whether decisions can be explained.

Integrations and data ownership

A telematics or dispatch platform rarely stands alone. It typically needs to exchange data with:

  • ERP and accounting systems for invoicing, payroll, fuel cards and cost allocation;
  • CRM and customer portals for service requests and status updates;
  • Transportation management systems (TMS) for loads, rates and carrier settlements;
  • Maintenance and parts systems for work orders based on fault codes and mileage;
  • Identity providers for single sign-on and user provisioning.

Evaluation criteria for integrations:

  • published, versioned REST APIs with documentation you can review before signing;
  • webhooks or event streams for real-time updates, not only scheduled exports;
  • rate limits and historical data access through the API;
  • prebuilt connectors, and who maintains them;
  • bulk data export in standard formats, including on contract exit;
  • clear contract terms that the customer owns its data and can retrieve it within a defined period.

Driver privacy and monitoring

Telematics collects detailed information about where drivers are and how they behave, and driver-facing cameras can capture images of their faces. Federal and state rules shape what a carrier can do with that data.

Harassment protections. 49 CFR 390.36 prohibits a motor carrier from using ELD information or other technology to harass a driver, defined as action the carrier knew or should have known would result in the driver violating hours-of-service or certain safety rules. FMCSA has stated that carriers may still use ELD data to monitor productivity, as long as they do not use it to harass.

State consumer privacy laws. Since the California Consumer Privacy Act’s employee data exemption expired on 1 January 2023, California employees and job applicants have privacy rights over personal information that covered employers collect, including notice at collection and rights to know, delete and correct (California Privacy Protection Agency, FAQ).

Biometric laws. Some driver-facing camera systems analyze faces, for example to detect distraction or identify drivers. In Illinois, the Biometric Information Privacy Act (740 ILCS 14/15) requires a private entity to inform the person in writing, state the purpose and retention term, and obtain a written release before collecting biometric identifiers such as a scan of face geometry, and to publish a retention and destruction policy.

Questions to ask vendors:

  • Does any feature create biometric identifiers, and can it be disabled?
  • Can video retention, access and audio recording be configured by role and region?
  • Does the platform support driver-facing privacy modes during off-duty and personal conveyance?
  • Which subprocessors handle driver data, and in which countries?

Involve legal counsel and, where relevant, unions or works councils before rolling out driver monitoring.

Security attestations: SOC 2 and ISO 27001

Fleet platforms hold location histories, customer addresses and employee data, so their security matters. Two independent assurances appear in most enterprise RFPs.

SOC 2. A SOC 2 report is an attestation by an independent CPA firm on a service organization’s controls under the AICPA trust services criteria: Security (always included), and optionally Availability, Processing Integrity, Confidentiality and Privacy (AICPA, Trust Services Criteria). A Type 1 report covers the design of controls at a point in time. A Type 2 report covers whether controls operated effectively over a period. For a production platform, ask for the latest Type 2 report, check which criteria and systems are in scope, and read the exceptions and complementary user entity controls.

ISO/IEC 27001. ISO/IEC 27001:2022 specifies requirements for an information security management system. Organizations can be certified by an accredited certification body. Ask for the certificate, the issuing body, the expiry date and the scope statement, because a certificate may cover only part of the company.

Neither attestation proves a product is secure; both show that a vendor runs a structured, audited security program. Supplement them with your own questions on encryption, access control, single sign-on and multi-factor authentication, vulnerability management, incident notification timelines and penetration test summaries.

Total cost of ownership and contract terms

Pricing for fleet software varies by fleet size, hardware, features and contract length, and vendors rarely publish it. Rather than comparing headline per-vehicle prices, build a total cost of ownership (TCO) model over the full contract term that includes:

  • Hardware: telematics units, cameras, sensors, cables, whether purchased, leased or bundled;
  • Installation: in-house or vendor-managed, per-vehicle time and downtime;
  • Subscriptions: per vehicle, per user or per asset, with add-on modules;
  • Connectivity: cellular data, roaming and coverage gaps;
  • Integration and implementation: professional services, connectors and internal staff time;
  • Training and change management for dispatchers, drivers and technicians;
  • Exit costs: hardware removal, data export and overlap with a replacement system.

Contract terms worth negotiating:

  • term length, auto-renewal notice periods and price increase caps;
  • hardware warranty and replacement turnaround, especially for ELD malfunctions;
  • service level agreements for uptime and support, with credits;
  • data ownership, export format and retention after termination;
  • notice and remedy if the vendor’s ELD registration is revoked;
  • security incident notification timelines and audit rights.

RFP checklist

Use this checklist as a starting point and adapt it to your operation:

  1. Compliance: FMCSA registration ID for each ELD model; supported data transfer methods; malfunction handling and replacement times; personal conveyance and yard move handling; IFTA reporting.
  2. Telematics coverage: supported vehicle types and makes; asset and trailer tracking; camera options; offline buffering.
  3. Dispatch and routing: assignment rules, optimization constraints, re-optimization, customer notifications, proof of service, mobile offline mode.
  4. Integrations: API documentation, webhooks, prebuilt connectors to your ERP, CRM and accounting tools, single sign-on.
  5. Data and privacy: data inventory, retention controls, biometric features, subprocessors and data locations, privacy notices for drivers.
  6. Security: SOC 2 Type 2 report and scope; ISO/IEC 27001 certificate and scope; encryption; incident response.
  7. Implementation: project plan, installation approach, training, named support contacts.
  8. Commercials: full TCO over the term, price protection, renewal terms, exit provisions.
  9. References and pilot: customers with similar fleet size and industry; a time-boxed pilot with agreed success measures.

Weighted scoring template

A weighted score helps a selection committee compare vendors consistently. The weights below are an example only; set your own based on your priorities, and keep ELD compliance as a pass or fail gate rather than a weighted item if your fleet is covered.

Criterion Example weight Vendor A score (1-5) Vendor A weighted Vendor B score (1-5) Vendor B weighted
ELD compliance (gate) Pass or fail        
Telematics data and hardware 20%        
Dispatch, routing, scheduling 20%        
Integrations and APIs 15%        
Security and privacy 15%        
Usability for drivers and staff 10%        
Total cost of ownership 15%        
Contract terms and support 5%        

To use it, score each vendor from 1 to 5 against written criteria for each row, multiply by the weight, and add the weighted scores. Base scores on demonstrations, documentation and pilot results rather than marketing materials, and record the evidence behind each score so the decision can be reviewed later.

Sources