Detention Proof With No Gate Log: What Actually Works

You can build detention proof with no gate log. A gate system is convenient, not required, and no rule anywhere makes a guard shack timestamp the standard of proof. What settles a detention claim is a set of independent records that agree on two moments: when the truck arrived and when it was released. The ELD, the telematics breadcrumb, the driver’s macro or text to dispatch, the lumper receipt, the seal record, and the appointment confirmation each carry one of those moments. Two or three that corroborate each other will carry a claim that one gate ticket would have carried alone.

This matters most to brokers, because a broker sits in the middle of the argument twice. A carrier bills you detention with thin evidence, and you have to decide whether to pay it. Then you try to pass it through to the shipper, who asks for proof you never received. The gap between those two conversations is where broker margin goes to die.

The fix is to know which substitutes exist, which ones a facility cannot dispute, and how to assemble them into a claim before the trail goes cold.

Why the gate log was never the standard

Gate systems live at container terminals, large distribution centers, and rail ramps. Most of the freight economy is not those places. A regional food plant, a job site, a 3PL running two doors out of a leased warehouse, a grocery DC where the guard shack was decommissioned two years ago: none of them will produce an in and out timestamp because none of them generate one.

Even where a gate system exists, it may not measure what you need. Gate in and gate out capture the property line, not the dock. A truck that gate-ins at 07:40, waits ninety minutes in a staging yard, gets a door at 09:10, and leaves the property at 12:20 has a gate record showing four hours and forty minutes and a dock record showing three hours and ten minutes. Which one the free time clock runs against is a contract question, not a fact question, and it is the single most common reason detention disputes stall. That distinction is worked through in when detention free time actually starts.

So treat the gate log as one possible source among several, not as the thing whose absence kills the claim.

What the rules require, and what they do not

Be precise here, because overstating it is how a detention claim loses credibility with a carrier’s billing department.

Federal rules set a floor for shipping paperwork. Under 49 CFR 373.101, a motor carrier’s receipt or bill of lading must show consignor and consignee names, origin and destination, package count, freight description, and weight or volume where those matter to rating. Under 49 CFR 373.103, a freight or expense bill must show the same identifying details plus the exact rates assessed and the total charges due with the nature and amount of each charge.

Read those lists again and notice what is missing. Arrival time. Departure time. Dwell. No federal rule compels a shipper, a receiver, or a carrier to timestamp a trailer. Detention is a contractual charge, governed by the rate confirmation, the transportation agreement, and any rules tariff that agreement incorporates. What the regulations give you is the right to an itemized bill, which is genuinely useful (a line that reads “DET 4.0” with no dates is defective on its face), but they do not give you a right to a gate log that nobody was required to create.

Two clocks do come from statute, and they bound the whole exercise. Under 49 U.S.C. 13710, a carrier billing charges beyond those originally billed must do so within 180 days of your receipt of the original bill, and you must contest a bill within 180 days of receipt to preserve your right to challenge it. Under 49 CFR 378.8, if you have already paid, the processing carrier must pay, decline, or settle a written overcharge claim within 60 days of receipt unless you agree in writing to extend. The full set is in the freight billing deadlines reference.

The substitute evidence stack

Rank substitutes by two properties: whether the record was created automatically, and whether it was created by a party with no stake in the outcome. Automatic beats manual. Neutral beats interested. A record that is both is nearly unarguable.

Three notes on how to use the table.

The ELD is the workhorse. The driver’s electronic logging device records duty-status changes with time and an approximate location, and it does so without anyone deciding to document a dispute. That neutrality is exactly what makes it persuasive. Ask the carrier for the relevant portion of the driver’s log for that day, not a summary retyped by billing. If the carrier will not produce it, that is informative in itself.

Two independent records beat one perfect one. An ELD showing on-duty not-driving from 08:12 to 13:40 at the consignee’s address, plus a lumper receipt printed at 12:55, plus a geofence exit at 13:44 tell one coherent story. No single one of them is a gate log, and together they are better than a gate log, because they came from three unrelated systems.

Ask the facility for its own records. Sites with no gate often still have a dock scheduling tool, a yard board, a receiving log, or a WMS with a receipt-posting timestamp. A receiver will frequently share these when the request is specific and framed as reconciliation rather than accusation. A vague “can you confirm the truck was there a long time” gets nothing. “Can you send the receipt posting time for PO 44821 on 9/3” often gets an answer within the hour.

Building the claim from three records

Whether you are defending against a carrier’s detention bill or pushing one through to a shipper, the structure is the same. Detention is an arithmetic claim: an arrival time, a free time allowance, a departure time, a rate, and a cap. Every dispute attacks one of those five.

Assemble in this order.

1. Pin the contract terms first. Pull the rate confirmation and read the free time allowance, the hourly or per-fifteen-minute rate, the maximum, and the language defining when the clock starts. If the rate con is silent, the carrier is billing outside the agreed scope, which is a different and easier argument than a fight about minutes. The mechanics of that comparison are in rate confirmation versus carrier invoice mismatches.
2. Establish arrival with an automatic record. ELD or telematics. Note the exact timestamp and the location it resolves to. If the location resolves to a truck stop half a mile away, say so and explain it rather than letting the other side find it.
3. Establish departure the same way. The gap between the two is gross dwell, not billable detention.
4. Subtract everything that is not the facility’s fault. Early arrival before the appointment window, the driver’s own break, a delay caused by paperwork the carrier failed to bring, time spent on a second stop. Detention pays for the receiver’s delay, not for total time on site. A claim that quietly bills the forty minutes a driver arrived early will be found, and finding it costs you the credibility you need for the rest of the claim.
5. Show the arithmetic on one line. Arrival 08:12, appointment 08:30, clock starts 08:30, two hours free ends 10:30, released 13:40, billable 3.17 hours at the rate con rate of $65 per hour with a $650 cap, total $206. Anyone can check that in ten seconds.
6. Attach the records, in order, named clearly. Not a forty-page PDF. Three files, named for what they prove.

That is a claim. The absence of a gate log never comes up, because you never needed it.

What the other side will argue

“There is no gate record, so the time is unverified.” Answer that the site does not produce gate records and that verification comes from independent systems instead. List them. Invite the facility to produce any record that contradicts the ELD. This reverses the burden politely and usually ends the exchange, because a facility with no gate system has nothing to contradict it with.

“The driver arrived outside the appointment window.” Often true and often decisive, so check it before you send anything. If the driver was early, the clock generally starts at the appointment time, and your claim shrinks. If the driver was late and the facility still worked him in, some contracts restart free time at the actual start of service. Read the clause rather than assuming.

“Our records show the truck left earlier.” Ask which record and ask for it. A receiver saying “we finished at noon” from memory is not evidence against a geofence exit at 13:44. A receiver producing a WMS posting at 12:04 is, and the honest answer may be that loading finished at noon and the driver sat forty minutes waiting on signed paperwork, which is still detention under most contracts.

“The POD is signed with no times, so the charge stands as billed.” This is the carrier-side version of the same problem, and it fails for the same reason. A blank timestamp field proves nothing in either direction. The full treatment is in how to dispute a detention charge when the POD has no in or out times, and the broader document set is catalogued in the detention dispute evidence documents.

The broker’s specific exposure

A broker faces a pass-through risk that neither the carrier nor the shipper carries. You are billed under one contract and you collect under another, and the two rarely have identical detention terms.

Check for these mismatches on any lane you run repeatedly:

• Free time gap. Your carrier rate con grants two hours. Your customer agreement grants three. You eat the third hour on every delayed load, quietly, forever.
• Rate gap. You are billed at $75 per hour and can recover $50.
• Cap gap. The carrier’s cap is higher than the customer’s, or the customer’s agreement has a cap and the carrier’s does not.
• Notice gap. Your customer requires detention to be reported within 24 hours of delivery. Your carrier bills it three weeks later on the invoice. By the time you know, your right to pass it through has expired.

The notice gap is the expensive one, and it is a process problem rather than an evidence problem. If your customer contract requires same-day or next-day notice, your dispatchers have to flag dwell in real time, not your AP clerk at invoice audit. Any load where a driver is on site past the free time allowance should generate a notice that day, even before anyone knows the final number.

Fix it before the next load

Everything above is recovery. Prevention is cheaper and takes about a week to implement.

• Put detention terms on the rate confirmation every time, with the free time, the trigger event, the rate, the cap, and the required notice window all stated. Silence on the rate con is what turns a $200 charge into a $200 argument.
• Standardize four driver macros: arrived, in-door, loaded or unloaded, departed. Four timestamps per stop, generated automatically, cost nothing and settle almost everything.
• Ask drivers for two photos on any stop that runs long: one on arrival, one on departure, both showing the facility. Device timestamps and location data on those photos are contemporaneous evidence.
• Note dock conditions on the BOL the way you would note dock delivery to head off a liftgate fee on a dock-to-dock load. Recording the condition while it is true is the whole discipline.
• Flag repeat offenders. Detention is not only a billing problem. The DOT Inspector General’s driver detention report estimated that a 15-minute increase in average dwell time raises the average expected crash rate by 6.2 percent, and put the cost of detention to for-hire truckload drivers at $1.1 to $1.3 billion in annual earnings and to truckload carriers at $250.6 to $302.9 million in annual net income. A facility that consistently holds trucks is a safety and capacity problem, not just an invoice line.

The checklist

Run this on any detention charge where no gate log exists.

1. Read the rate confirmation for free time, trigger, rate, cap, and notice window.
2. Request the ELD extract for the driver and date. Do not accept a retyped summary.
3. Request telematics or geofence data if the carrier has it.
4. Collect the lumper receipt, seal record, and any timestamped photos.
5. Ask the facility for its own receipt-posting or dock-scheduling timestamp, specifically, by PO or appointment number.
6. Subtract early arrival, driver break, and carrier-caused delay from gross dwell.
7. Write the arithmetic as one line anyone can verify.
8. Attach three named files, not one large one.
9. Check the calendar against the 180-day contest window, and the 60-day claim clock if the invoice is already paid.
10. If you are a broker, confirm the pass-through terms match before you concede or approve anything.

The habit that pays is step two done early. ELD and telematics data ages out of easy retrieval faster than you expect, and the difference between requesting it in week one and week nine is usually the difference between a claim and a write-off. The ocean side of this problem works differently, with a real regulation behind it, which is covered in what the FMC demurrage and detention billing rule requires on an invoice.

Sources

• 49 CFR 373.101, Motor carrier receipts and bills of lading (Cornell LII)
• 49 CFR 373.103, Freight or expense bills (Cornell LII)
• 49 U.S.C. 13710, Billing and contesting windows (Cornell LII)
• 49 CFR 378.8, Overcharge claim resolution within 60 days (Cornell LII)
• DOT OIG Report ST2018019, FMCSA driver detention final report (U.S. DOT Office of Inspector General, January 31, 2018)