Why a log screenshot gets waved off
Carriers hear the same thing from a broker's accounts payable: the signed BOL with in and out times is what gets paid, an ELD screenshot is a step down, and a handwritten note on the BOL is hardly proof at all. The ranking is not unfair. A screenshot of the hours-of-service log shows a duty status change at a time near a town. It does not show which facility, when the appointment was, when free time ran out, or when the truck left. Accounts payable cannot turn it into a number, so they do not.
The second problem is that the person on the other end has to compare it with the rate confirmation, the shipper's dock log and the appointment time, and those three are often in a different time zone from the log. A log that reads 09:40 beside a dock log that reads 07:40 looks like a carrier padding the claim. It is usually a Texas home terminal and a California receiver.
Both problems have the same fix: stop sending the logbook and send the record behind it, in a form the reader can check in two minutes.
What the ELD is required to record
The federal ELD rule is an hours-of-service rule, not a tracking rule, and the log it requires is built for that. FMCSA's own summary is that location data must be recorded at 60-minute intervals when the vehicle is in motion, and when the driver powers up and shuts down the engine, changes duty status, and indicates personal use or yard moves. Between those events there may be nothing in the log at all.
The position itself is deliberately rough. The specification requires it to be accurate to half a mile and recorded to two decimal places of a degree, which FMCSA describes as about a one mile radius during on-duty driving. During personal conveyance the precision drops to one decimal place, about ten miles. The log then converts the coordinates into a description such as a distance and direction from the nearest town of any size, and FMCSA says plainly that this is not precise enough to identify a street address.
So the logbook, read honestly, proves this much about a stop: at a stated time the driver went from Driving to On Duty Not Driving somewhere within a mile or so of a point a few miles outside a named town, and some hours later went back to Driving. For a receiver in open country that may be enough to place the truck. For a distribution park with six consignees, a truck stop and a staging lot inside the same mile, it places the truck in the park. That is why a careful AP desk calls it a step down, and why the record you want is a different one.
The GPS trail behind the logbook
Most of the ELD platforms carriers run today are fleet telematics systems that also produce the log. The same device reports the truck's position to the carrier's dashboard far more often than once an hour, and that history is kept separately from the driver's log, usually under a name like location history, trip history or breadcrumbs. It is the record a fleet manager opens to see where a truck was at 3 p.m. last Tuesday, and it is usually precise enough to place the truck in a yard rather than in a town.
That trail is the detention evidence, and three things about it matter for a claim. It is owned by the carrier, so the carrier's dispatcher has to pull it; a broker cannot see it unless the carrier shares a link or an export. How far back it goes and how often it recorded depends on the vendor and the plan, so find out on a quiet day, not when a claim is due. And it is not the log, so it does not carry the duty status change that the driver tapped at the dock; the two records are read together, the tapped time and the observed time side by side.
If a carrier tracks the load through its ELD on a broker's board, the broker has an observed record of the same stop and can read arrival and departure from it. ELD tracking covers what a share link carries, and the geofence guide covers how the two crossings are read from positions. The rest of this page is for the carrier side, where the record starts.
The time zone dispute you create yourself
The specification requires the device to keep time synchronised to UTC, within ten minutes, and to show the driver's record in the time standard of the driver's home terminal. That is right for a log, because a driver's day has to add up in one zone. It is wrong for a dock. A carrier based in Dallas delivering in Fontana has a log in Central time, a dock log in Pacific time, an appointment on the rate confirmation in whatever the broker's TMS assumed, and a shipper in Atlanta who reads all three in Eastern time.
Most of the two-hour discrepancies that turn a claim into an argument are this and nothing else. The fix costs one line: every time in the claim carries its zone, and the arrival, free time, departure and appointment are all converted to the facility's local time before anyone compares them. Write the conversion out rather than asking the reader to trust it.
Pulling the report
A process the carrier's dispatcher can run on every stop that goes past free time, without any tool the carrier does not already have.
- Make the call before free time ends. Almost every rate confirmation requires the broker to be told that detention is about to start, often 30 minutes before. A claim with no notice is denied on the clause, however good the GPS. Log the call or the email on the load with its time.
- Get in and out times on the BOL. Ask the receiver to write arrival and departure on the signed paperwork and photograph it before leaving the yard. When the receiver will not write times, which happens, the driver writes them and the GPS record below is what backs them up.
- Export the location history for the stop, not a screenshot of the log. In the ELD dashboard, open the vehicle's location or trip history for the delivery date, set the window from an hour before arrival to an hour after departure, and export it as a PDF or spreadsheet. If the platform offers a stop or idle report that lists where the truck sat and for how long, export that too. Note the time zone the export uses; it is usually the carrier's.
- Pull the duty status log for the same day. The rule requires the device to produce the driver's record for the current day and the previous seven days on demand, and to give the driver a copy of their own records. The On Duty Not Driving change at the dock and the Driving change at departure are the driver's own times, and they should sit within a few minutes of what the GPS trail shows.
- Check the pin against the address. Open the first position inside the yard on a map and confirm it is the consignee named on the rate confirmation, not the staging lot down the road or the truck stop across it. If the driver was sent to wait somewhere else, say so in the claim with the position that shows it.
- Convert everything to the facility's local time and write the arithmetic: arrival, appointment, the later of the two, free time added, departure, the difference, the rate from the rate confirmation.
Do this the day of delivery. A location history export is easy on day one and may be impossible on day forty, and the person answering the dispute six weeks later was not the person on the load.
The claim packet
What the broker's AP desk needs is one message it can approve without opening a second system. In practice that is one page of arithmetic and four attachments.
- The calculation, with the load number, the stop, every time in the facility's local time with the zone written out, and the rate and free time quoted from the rate confirmation.
- The signed BOL or POD showing the in and out times, or the driver's written times with a note that the receiver would not record them.
- The location history export for the window, showing the truck at the consignee's coordinates from arrival to departure, with the export's time zone stated.
- The notice: the email, text or call log showing the broker was told before free time ended, with its time.
- The duty status log for the day, as supporting evidence rather than the headline, because it is the record that shows the driver was on duty and not resting during the wait.
A broker who receives that packet has the same job the carrier had: pass it to the shipper in a form the shipper's AP will pay. The broker's own position record of the load, if the carrier shared the ELD or a driver tracking link, goes in beside it. When the carrier's GPS and the broker's board agree on the two crossings, the shipper has very little left to argue with.
Where software helps
The work above is real work on every stop that runs past free time, and it only gets done on the stops someone remembers. A track and trace board that already follows the load records the two crossings on every tracked stop by itself, from the carrier's ELD, the driver app or a tracking link, and keeps the trip record for the day the claim is questioned.
LoadSignal keeps two clocks on every stop: the time the driver tapped and the time the GPS saw the truck cross the facility's fence, side by side, with a note when they disagree. The trip record lists every place the truck stopped with its GPS arrival, departure and duration, as text and as a PDF that includes the positions behind it, one every 15 minutes plus each stop's arrival and departure, each with its time, place, source and a map link. When a truck leaves a stop after its GPS time there ran past the customer's free time, the detention claim and the email carrying the evidence are drafted and wait for a dispatcher to approve; nothing is billed or sent until someone decides. The trip record says how much of the stop it observed and never claims the truck did not move while it was not being watched, which is what a shipper's auditor checks for.
It does not replace the paperwork. The signed BOL with in and out times is still the first thing a shipper asks for, the notice before free time still has to be sent, and a facility geocoded to a ZIP code is marked approximate rather than used as proof. Track and trace is where the loads and their stops live, and the rate confirmation guide covers the free time and notice terms that the whole calculation runs from.
Questions dispatchers ask
Can ELD logs prove detention time?
Partly. The hours-of-service log proves when the driver changed duty status and roughly where, to about a mile and relative to the nearest town, so it supports a claim but rarely settles one on its own. The fleet GPS history most ELD platforms keep alongside the log is finer, and a signed BOL with in and out times is still what brokers and shippers accept first.
Why did the broker reject my ELD screenshot?
Usually because it cannot be read against the rate confirmation. A cropped log shows a duty status change at a time, in the carrier's home terminal time zone, near a town. It does not show the facility, the appointment time, the free time or the departure. Send the location history for the stop as an export, with the time zone stated, beside the signed BOL.
How accurate is ELD location?
The rule requires the position to be accurate to about half a mile and recorded to two decimal places of a degree, which FMCSA describes as roughly a one mile radius during on-duty driving and about ten miles during personal conveyance. The log then describes the position as a distance and direction from a nearby city, not as a street address.
What time zone does an ELD log show?
The driver's home terminal time zone. The device keeps time in UTC and converts it for the record, so a Texas carrier's log shows Central time at a California dock. State the time zone on every time in the claim and convert the appointment and the dock log to the same one before comparing them.
How long do we have to file a detention claim?
The rate confirmation decides. Most require the broker to be told before free time runs out, and many want the claim with the invoice or within a stated number of days of delivery. Read the detention clause on the day of booking and put the deadline on the load, because a correct claim filed late is still denied.