When the signal drops, the logs shouldn’t.

Technology and Intelligence 6 Min Read

TL;DR Rural highways, mountain passes, farm roads and long stretches of interstate between towns all have one thing in common: places where the cell signal disappears. For drivers, that’s just part of the job. For the office, it raises a fair question.

What happens to the logs when the truck loses coverage?

Why dead zones matter for compliance.

Hours of service records have to be accurate and complete. Under the FMCSA’s ELD rule, an electronic logging device records driving time automatically from the truck’s engine, along with location at set intervals. A record with holes in it isn’t a small problem. It can mean a day someone has to reconstruct, drive time that shows up unassigned, or questions at a roadside inspection.

Fleets that run rural lanes, agriculture routes or remote job sites know the pattern well: the truck drops out of coverage, and everyone hopes the record holds together until it comes back.

The cost of a gap rarely shows up all at once. It shows up later, in small pieces of somebody’s time. A safety manager notices a stretch of the day that doesn’t add up. A dispatcher calls the driver to ask what happened between two stops. A driver who has already put in a long shift is asked to explain hours they drove days ago. None of it is dramatic, but across a fleet and across a year, it adds up to real hours spent fixing records instead of moving freight.

Where the signal runs out.

Dead zones aren’t limited to the middle of nowhere. They show up anywhere the towers are far apart or the terrain gets in the way:

  • Rural highways and farm roads, where coverage thins out between towns.
  • Mountain passes and river valleys, where hills and canyon walls block the signal.
  • Remote job sites, such as quarries, pits, construction sites and logging roads, often well off the main network.
  • Agricultural routes, where trucks spend harvest season moving between fields that were never built with cell coverage in mind.
  • Long interstate stretches in sparsely populated states, where a few miles of no service is normal.

For many carriers, these aren’t occasional detours. They’re the regular route. That’s why the question of what happens offline isn’t an edge case. It’s part of choosing an ELD.

How My20 handles a coverage gap.

My20 ELD doesn’t stop recording when the signal drops. While the truck is out of coverage, it keeps logging hours of service and location data and stores it. Once the connection returns, the stored records upload automatically.

The key is the connection to the truck itself. The My20 device plugs into the truck’s diagnostic port, and as long as it stays plugged in, it keeps capturing the record whether or not there’s a cell signal. Coverage only affects when the data reaches the office, not whether it gets recorded. So the one thing that matters in a dead zone is the same thing that matters everywhere else: keep the ELD plugged in.

Then, once the driver is back in signal, My20 takes care of the rest. Everything recorded during the gap uploads automatically, so the hours and locations from the dead zone land in the log right where they belong. The driver doesn’t have to press anything or re-enter anything, and the office doesn’t have to request it. The record simply catches up.

That means:

  • The record stays continuous. The hours driven through the dead zone are captured, not lost.
  • No one has to chase missing logs. The data syncs on its own once the truck is back in range.
  • The office sees the full day. Once synced, the hours and locations flow into the Konexial platform alongside dispatch and safety data, where Ki™ technology turns them into a complete picture of the day instead of a day with a gap in the middle.

What it looks like on a typical day.

Picture a driver hauling a load from a grain elevator to a processing plant two counties over. Twenty minutes out, the road drops into a valley and the phone shows no service. The truck keeps rolling, and so does My20. With the device plugged into the truck, drive time and location keep getting recorded, just as they would on the interstate.

Back at the office, the dispatcher sees that the truck hasn’t checked in for a while. On a route like this, that’s expected. Nobody needs to pick up the phone.

Forty minutes later, the truck climbs out of the valley and the signal returns. My20 uploads what it stored, and the log fills in. The dispatcher now sees the full trip, the safety manager sees a clean record, and the driver never had to stop, call in or fix anything.

That’s what a dead zone should feel like: a short delay in the data reaching the office, not a hole in the record.

Set up for the road.

A few habits keep logging smooth on routes with spotty coverage:

  1. Run My20 on a dedicated device. The My20 app must stay open in the foreground at all times to stay compliant, so we recommend a separate phone or tablet used only for the ELD.
  2. Keep the required documents in the cab. FMCSA rules require drivers to carry the ELD user manual, data transfer instructions, malfunction instructions and at least eight days of blank paper log sheets. That last one matters if a device ever does malfunction, under the malfunction rules in §395.34.
  3. Know where your routes go dark. When dispatch knows which stretches lose coverage, a short delay in syncing is expected rather than a surprise.
  4. Make “plugged in” part of the pre-trip. Since My20 records offline as long as it’s connected to the truck, a quick check that the device is seated in the diagnostic port belongs on the same list as tires, lights and brakes.
connected fleet intelligence

Logs you can count on, wherever the route goes.

Coverage gaps aren’t going away. Your hours of service records shouldn’t depend on them. My20 keeps recording through the dead zones and catches up on its own, so drivers can focus on the road and the office can trust the record.

Want to see how My20 and the Konexial platform would work on your routes?