Your Driver's Clock Is Now Part of the ETA

It's eleven in the morning and a broker wants an update on a load going into Atlanta.

Your board says the truck is 380 miles out. Call it six hours of driving. Six hours from eleven is five this afternoon.

You don't tell him five this afternoon. You check which driver it is, you think about when he started, and you tell him first thing tomorrow.

That gap — between what the board says and what you already know — is what we set out to close.

The Board Was Doing Half the Math

An ETA built from distance and road speed is a good answer to the wrong question. It tells you how long the driving takes. It doesn't tell you when the truck arrives, because sitting between those two things is a driver who's been up since five and has two hours of clock left.

Every dispatcher corrects for this in their head, all day, without really noticing. That's the part that bothered us. We had built a number that the person reading it had to quietly fix before it was worth anything — and a number you always have to fix is a number somebody eventually forgets to fix. Usually on the phone. Usually to a broker.

What the Board Does Now

Arrival times get worked out two ways, and you can see both.

The first is the road answer: how long the drive takes. The second is the real one — how long the drive takes once the rest that has to happen in the middle of it is part of the calculation.

We read the driver's hours straight from the ELD. Drive time left, on-duty window left, time until the 30-minute break, hours left in the cycle. Then we run the rest of the trip forward against the same limits your dispatchers already plan around:

• 11 hours of driving
• a 14-hour on-duty window
• a break after 8 hours behind the wheel
• 60 or 70 hours in the cycle

Wherever the rules force the truck to stop, that stop goes into the calculation and the clock keeps running. What comes out the other end is an arrival time you can read off the screen and say out loud.

And What It Takes to Get There

Next to the arrival time is the part dispatchers ended up leaning on more than we expected: how the driver actually gets there. How many 30-minute breaks and how many 10-hour resets stand between the truck and its next stop, and between the truck and the final delivery.

The board also answers the thing you'd normally pick up the phone for. When does this driver have to shut down next, and what's forcing it — the break, the daily reset, or the cycle. On the map you can switch the pins to color by duty status, so a screen full of trucks tells you who's driving, who's on duty and who's parked without opening a single one of them.

The One That Changes What You Do

There's one flag worth pulling out on its own, because it doesn't change what you say to a broker. It changes what you do about it.

When a load can't be finished inside the driver's current cycle — when it needs a 34-hour restart to complete, not just a night's sleep — the board tells you. Not "this looks tight." It will not fit.

We'd Rather the Truck Show Up Early

One thing worth being straight about, because it affects how much you should trust the number.

Where there's any doubt, we lean toward more rest rather than less. We don't assume a driver will split his sleeper time in the most efficient legal way to stretch a day, and we don't assume a perfectly timed restart. So every so often a truck beats our estimate.

That's on purpose, and it's the direction we want to be wrong in. An ETA that runs optimistic gets ignored inside a week — and then everyone is back to correcting it in their head, which is where this whole thing started.

The next-stop time is the one to quote against a delivery window. The final-delivery time doesn't account for how long the truck sits at the stops in between, so read it as a floor: if it already says late, it's late.

A Normal Tuesday

You open the board in the morning and a couple of loads are already flagged late.

Nothing has gone wrong. Nobody broke down, no receiver held anybody four hours. The hours simply don't add up, and the board can see that at eight in the morning instead of at the end of the day.

You can tell which drivers run out of clock this afternoon and roughly where they'll be standing when it happens. You know which two or three loads need a decision before lunch. And when a broker calls at eleven about a load going into Atlanta, the number on your screen is the number you give him.

None of this stops a driver running out of hours. Hours are hours. It means you find out at nine in the morning instead of nine at night, which is the whole difference between calling a broker with a heads-up and calling one with an apology.

It's live now for every carrier running an ELD integration — there's nothing to switch on. If your ELD isn't connected yet, that's the one thing standing between your board and this, and it takes about five minutes.