Carrier and trucking TMS · Compliance

Hours of service tracking: live ELD clocks for dispatch

Connect Samsara or Motive and Tezify shows each driver's remaining hours on Drivers and DQ, on the dispatch planner and on the driver page. Clocks that have stopped refreshing are marked as not live, so nobody plans on old numbers.

Updated Open this in Tezify

The hours-of-service rules in short

Hours of service are set in 49 CFR Part 395. For property-carrying drivers the main limits are 11 hours of driving inside a 14-hour on-duty window after 10 hours off, a 30-minute break after 8 hours of driving, and 60 hours in 7 days or 70 hours in 8 days. Your ELD records the duty status and keeps the official log.

Dispatch does not need the log. It needs to know, before booking a run, how much time a driver has left. That is what the clocks in Tezify are for.

See the live clocks

  1. Connect Samsara or Motive under Connections. See connect your ELD.
  2. Open Safety, then Drivers & DQ, and read the Hours of Service live clocks card.
  3. Each driver shows status, Drive left, Shift left, Cycle (70h) and Break in. The driver with the least drive time sits at the top.
  4. Check the dispatch planner before giving a driver a long run. The same clocks show there and on the driver page.

When you assign a load to a driver who does not have the hours for it, Tezify shows a conflict warning. It is a warning, not a block. The person dispatching decides.

Stale clocks

A clock that has not refreshed in 12 hours or more is shown for reference and not counted as live. Motive clocks on the dispatch board go stale if they are not re-synced within 5 hours. PeopleNet does not publish hours through its connection, so Tezify does not show them for PeopleNet fleets.

If the clock table itself cannot be read, the card says so. It never shows an empty list as if no driver were short on hours.

Log an ELD malfunction

Under 49 CFR 395.34, when an ELD stops working the driver keeps paper logs and the carrier has 8 days to repair or replace the device. If FMCSA revokes a model's registration, you get 60 days to switch.

  1. On Drivers & DQ, open ELD malfunctions.
  2. Press Record a malfunction.
  3. Enter the unit, the driver code and the device.
  4. Enter the detection date: the day someone noticed, not the day you write it down.
  5. Pick the kind: device stopped working (8 days) or model registration revoked (60 days).
  6. Enter paper-log days if you know them. Leave it blank if nobody recorded it.

Common mistakes

  • Reading a stale clock as current. Check the time stamp before you promise a broker a delivery.
  • Logging a malfunction late with today's date. The 8 days run from detection.
  • Treating the Tezify clock as the legal log. It is a copy for planning.

Common questions

Does Tezify calculate hours itself?

No. It reads your ELD's clocks. It never works out a driver's legal hours on its own, and the ELD stays your official record of duty status.

Does an out-of-hours driver block dispatch?

No. It shows as a conflict warning when you assign the load, so the dispatcher can pick someone else or plan a reset.

Why is a driver missing from the clocks?

The driver is not matched to a driver in your ELD, or the ELD has not sent a clock for them yet. On Samsara, link the driver on the driver page or use Auto-link under Connections, then wait for the next sync.

Where does the driver see their own hours?

In the Tezify Driver app. See duty status and hours.

Ready to do it? This lives at /admin/compliance in Tezify.

Open this in Tezify

Still stuck?

Inside Tezify, press the ? at the top of any page to file a ticket with that page attached. Not a customer yet? Ask us anything.