# Motive integration: hours of service and DVIR > Motive feeds Roadmark hours of service, location, inspections and diagnostics, so tracking, dispatch planning and detention billing use current ELD data. URL: https://roadmark.ai/integrations/motive Language: en Last updated: 2026-10-01 **TL;DR:** Roadmark reads hours of service, location, inspection results and vehicle diagnostics from Motive. Location and hours of service feed tracking's ETAs, and hours of service tell dispatch planning how much of a driver's day is left; the same ELD data is what detention is billed against. ## What syncs One row for each kind of record: which way it moves, and when. | What | Direction | When | | --- | --- | --- | | Hours of service | Motive to Roadmark | Every few minutes | | Location | Motive to Roadmark | Every few minutes | | Inspections | Motive to Roadmark | When one is submitted | | Vehicle diagnostics | Motive to Roadmark | When Motive reports a fault code | ## Setting up Motive 1. **Sign in to Motive:** An admin authorizes Roadmark from Motive, so it can read hours of service, location, inspection results and vehicle diagnostics for the fleet. 2. **Choose what syncs:** Turn on hours of service, location, inspections and vehicle diagnostics, or leave any of them off. 3. **Test with a real load:** Run one load through it and check that the hours a driver has left match what Motive shows, before turning it on for everything. ### Before you start - A Motive admin who can authorize the connection. A driver's pre-trip inspection, hours of service, the truck's location and its own diagnostics all go through Motive before Roadmark ever sees them. Connecting the two means Roadmark reads that data instead of a dispatcher asking for it over the radio: location and hours of service feed [tracking](https://roadmark.ai/tracking)'s ETA math, hours of service tell dispatch planning how much of a unit's day is left before it's put on the next load, and an inspection result lands on the same record as the truck it belongs to. The connection is read-only from Roadmark's side and doesn't change how a driver uses Motive day to day. Motive's own [developer documentation](https://developer-docs.gomotive.com/docs/authentication) describes how its REST API authenticates: with an organization's API key, or with OAuth for partner apps. An admin creates the key from the admin section of Motive's dashboard, under Developers, and Roadmark uses it to read the records it's been granted. The ELD's location and hours of service are one of the sources tracking checks for a load's status, alongside the [driver app](https://roadmark.ai/driver-app), a carrier's own app or an EDI 214, visibility networks, and a check call when nothing else is reporting. The same clock a plan checks before assigning a driver to a load is the one tracking uses to explain an ETA, and it's also where a detention charge on the invoice comes from: Roadmark measures the ELD's dock arrival and departure times against the free time in the rate confirmation and adds exactly what's owed, rather than a dispatcher totalling times off the back of a BOL. For a fleet already running Motive, the change is mostly what shows up downstream of it: a plan that respects the hours actually left on a driver's clock, an ETA that reflects what the ELD is reporting, and an invoice with a detention line that matches the dock clock instead of an estimate. ## Questions about Motive and Roadmark ### What does Roadmark read from Motive? Hours of service, location, inspection results (DVIR) and vehicle diagnostics, the same four the Motive integration is listed for in the directory. ### Does Motive's hours of service feed dispatch planning? Yes. Hours of service come from the connected ELD every few minutes, so a plan never sends a driver somewhere their remaining hours won't cover. ### Does connecting Motive change how detention is billed? No. Roadmark bills detention from the ELD's arrival and departure times at the dock, measured against the free time in the rate confirmation, whichever ELD is connected. ### Do drivers need to do anything differently in Motive? No. Roadmark reads from the Motive device and app already in use; the pre-trip inspection a driver already submits is what Roadmark reads. ## Related pages - [Tracking](https://roadmark.ai/tracking): The few loads that need you, with reasons - [Asset carriers](https://roadmark.ai/carriers): Fleets that plan, dispatch and settle - [Billing and settlements](https://roadmark.ai/billing): Invoices, driver pay and carrier pay - [Driver app](https://roadmark.ai/driver-app): Stops, documents and pay on the phone - [Detention calculator](https://roadmark.ai/tools/detention): What a truck's time at the dock past its free time comes to, on the invoice and on the driver's pay. - [Truck detention: how to measure it, bill it and pay drivers](https://roadmark.ai/blog/truck-detention-billing): How detention time is measured (ELD, geofence and dock timestamps against the appointment), free time, billing without disputes and the driver's share. - [Samsara integration: hours of service and ETAs](https://roadmark.ai/integrations/samsara): Samsara feeds Roadmark hours of service, location and engine data every few minutes, so tracking ETAs, dispatch planning and detention all use current data. - [Geotab integration: location, fault codes and idle time](https://roadmark.ai/integrations/geotab): Geotab feeds Roadmark GPS location, engine fault codes and idle time, so tracking's ETA, a unit's card and dispatch planning all use current data. Companies, people and shipment figures in product examples are fictional. They illustrate workflows and are not customer testimonials or measured results.