How to Cut Freight Detention Costs with Sixfold Alerts

You can cut freight detention costs with Sixfold by turning its exception engine into a rules layer instead of a map overlay. The mechanics: set arrival thresholds per facility, flag dwell over 120 minutes automatically, and pipe those flags into your TMS as a cost event. Most teams using Sixfold for map visibility never configure step three, which is where the savings hide.

Detention runs $50-$100 an hour at most US facilities. A shipper moving 900 loads a month with a 15% detention rate and two hours average dwell is looking at $13,500 to $27,000 a month. That is a big enough number to justify a rules project.

Why does detention keep showing up on invoices?

Because nobody is measuring dwell in the same place the invoice measures it. Carriers start the clock at the appointment time on their paperwork. Your dock starts it when the truck checks in at the guard shack. Those two timestamps can differ by 40 minutes at a busy distribution center.

Sixfold gives you the carrier-side timestamp. That is the one that wins disputes.

How do you build detention rules in Sixfold?

Work through this in order. Each step produces something usable even if you stop early.

1. Pull 90 days of detention invoices. Group by facility and carrier. You are looking for the top five facilities producing 60%+ of the charges.
2. Create a facility profile for each. Add geofence radius, appointment window, and average check-in to dock time. Sixfold lets you store these per location.
3. Set a dwell alert at your contract threshold minus 20 minutes. If your carrier agreement allows two free hours, alert at 100 minutes. That gives dispatch time to act before the clock becomes billable.
4. Tag alerts by cause. Late arrival, gate delay, dock delay, paperwork. Use Sixfold’s driver notes field; a 30-second note from dispatch beats a three-day email thread.
5. Export the alert log weekly. Save as CSV and reconcile against that week’s accessorial charges. Any invoice line without a matching alert entry gets disputed.

What does the reconciliation actually save?

In practice, teams that do weekly reconciliation report dispute win rates of 40% to 65%. The reason is boring: you arrive at the conversation with a timestamp the carrier’s own telematics produced. Carriers drop weak claims fast when the evidence is theirs.

The second-order effect matters more. Once drivers know their arrival is logged independently, arrival punctuality improves without any new policy. That is Sixfold’s real value — not surveillance, but a shared record of what happened.

Which alerts should you turn off?

The default set is too chatty. Every facility and every lane firing exceptions creates alert fatigue within two weeks, and then nobody reads anything.

Turn off:

• Every mid-route deviation alert on lanes under 100 miles. Short hauls generate noise without signal.
• Dwell alerts at facilities with dedicated drop trailers. The driver is not waiting; the trailer is.
• Weather-based ETA shifts unless you have a customer SLA tied to a specific delivery window.

Keep:

• 90-minute position gaps during drive windows. This catches unplugged ELDs and abandoned loads.
• Arrival window misses over 60 minutes at your top five facilities.
• Yard dwell over four hours. That is a trailer problem, not a truck problem, and it needs a different team.

Does this work if your carriers are small fleets?

Less well, and you should plan for it. Sixfold’s timestamps come from carrier telematics. A 12-truck fleet on a phone-based app gives you checkpoints every 30-45 minutes, which is fine for detecting a two-hour dwell and useless for measuring a 25-minute gate delay.

For that segment, keep manual check calls for gate timing and use Sixfold for the macro view — is the truck on the right lane, is it moving, will it arrive today. Accept the mixed model. Pretending a phone app does the job of a hardwired telematics unit leads to bad disputes.

How should you roll this out without a fight?

Start with one facility and one carrier group. Run it for four weeks. Publish both the savings and the friction points.

Carriers push back hardest in the first month, usually because they see logging as an accusation. Frame it as shared documentation for disputes and the tone changes. One operations manager I spoke with sent carriers the alert log proactively each week — disputes dropped by half because nobody had to argue.

Budget for a person. This is a 10-15 hour a month job, not something that runs itself. If you cannot assign those hours, skip the project; half-configured alarm systems create work instead of removing it.

Key Takeaways

• Detention savings come from reconciling Sixfold alerts against invoices weekly, not from watching the map.
• Alert at contract threshold minus 20 minutes so dispatch can act before charges start.
• Default alert sets cause fatigue; disable mid-route deviation on short lanes and drop-trailer dwell rules.
• Expect 40-65% dispute win rates when you bring carrier-generated timestamps to the table.
• Small fleets on phone-based telematics need a mixed manual-plus-platform model.

Pair this with our Sixfold setup walkthrough on iAIFeed for the initial carrier onboarding steps.