HVNHAI

Blog

Enforcing Demurrage: Documenting Waiting Time Without Gaps

6 min readBy Niclas Hoffmann · HVNH AI

In short

In practice, demurrage claims almost never fail because the right doesn't exist — they fail because of missing proof. An AI agent automatically documents waiting and standing times from telematics, driver reports and timestamps, gathers the evidence per shipment, and prepares the demurrage claim complete with all proof — you review and approve. That turns lost waiting time into money you can actually collect.

Why demurrage so often goes unclaimed

Three hours at the dock of a central warehouse, two hours at the shipper's, plus weekend standing time because the recipient closes at 2 p.m. on Fridays: waiting time is part of everyday life for any forwarding company — and it costs real money. Vehicle and driver are tied up, the next route shifts, and driving-time limits come under pressure.

The frustrating part: the right to demurrage exists, contractually or by law. It's still rarely enforced. The reasons are always the same:

  • The driver notes arrival and departure somewhere — or not at all
  • The pallet slip with the timestamp disappears into the driver's bag
  • Dispatch only hears about the waiting time days later, once the details have faded
  • Compiling the claim takes so much effort that it doesn't happen for small amounts
  • Without gapless evidence, the customer rejects the claim — and after the second attempt, nobody tries again

This creates a silent loss that adds up to substantial sums over the year. Not because the money isn't owed — but because the documentation is missing.

How an AI agent takes over demurrage documentation

An AI agent is a digital employee that systematically captures, documents and prepares waiting time for billing — embedded in your existing systems.

Step 1: Automatically recognise waiting time

The agent pulls time data from what's already available: telematics positions, arrival and departure times, status messages from the driver app, timestamps on delivery notes or pallet slips. Once a vehicle stands longer than the agreed free time at a loading point, the agent automatically opens a waiting-time case.

Step 2: Gather evidence

Evidence belongs to the case: the agent asks the driver by short message to photograph the signed document with the time note, and captures the arrival report, the reason for waiting and, where applicable, the name of the dock contact. Everything gets matched to the shipment and logged with a timestamp — audit-proof and provable later at any time.

Step 3: Check against contract and free time

The agent knows the agreed terms per customer: how much free time is agreed, which rate applies afterwards, which form of proof the customer requires. It calculates the billable waiting time and checks whether the chain of evidence is complete. If something's missing, it flags it while the case is still fresh.

Step 4: Prepare the claim ready to send — approval stays with you

The result is a ready-to-send demurrage claim: cover letter, breakdown of times, all evidence attached. Whether and to which customer it goes out is your call — especially with strategic customers, that's a commercial judgment the agent prepares for but doesn't make. Nothing leaves the building without your approval.

Step 5: Make patterns visible

Along the way, an analysis emerges that never existed before: which loading points regularly cost time? Which customer causes the most standing hours? These numbers are gold — for price negotiations, route planning, and deciding which routes are actually worth running.

Which systems get connected

HVNH AI's agents work with your existing landscape: telematics systems, TMS, driver apps or simple messenger channels, email and file storage. Where there's no modern interface, we tap the data through exports, documents, or the existing user interface. Your programs stay in use — the agent fits in.

Data protection is built in: operation on German servers or within your own environment, a data processing agreement, logging of every step. Driver-related data is processed only within the agreed scope — which can also be structured cleanly with a works council in mind.

What you can realistically expect

A typical result: waiting time becomes systematically visible for the first time — many businesses significantly underestimate their actual standing-time volume. The rate of enforced demurrage claims rises, because every claim goes out with a complete chain of evidence. And the effort for it drops from an unloved research task to a few minutes of review and approval per case.

To be honest: whether a customer pays ultimately comes down to the contract and your negotiating skill. What the agent ensures is that it never again fails on the evidence — and that you have the numbers to negotiate differently with chronic offenders.

An everyday example

Wednesday, 8:05 a.m.: a driver checks in at a retail customer's central warehouse, slot 8:00 a.m. Unloading finishes at 11:40 a.m. Telematics shows the standing time; at 9:30 a.m. — once the agreed free time has elapsed — the agent automatically opens a case and asks the driver to photograph the pallet slip with the timestamp. By the afternoon, the case is complete: 2 hours 10 minutes of billable waiting time, telematics log, document with check-in and check-out times, a cover letter prepared according to the framework agreement's terms. Dispatch reviews it in two minutes, management approves. In the past, this case would have been a footnote over a beer after work.

Common objections from the field

"Our customers won't pay demurrage anyway." Some won't — but rejection is much harder when the telematics log and signed timestamps are in front of them. And even where you waive the claim, the documented standing times are your strongest argument in the next price round.

"Our drivers don't have time for extra documentation." The effort for the driver actually goes down: a photo of the document, a quick confirmation — telematics and the agent handle the rest. Today, drivers write notes on paper that nobody ever evaluates anyway.

"We don't want to annoy customers with small claims." That's why approval stays with you. Many businesses define thresholds: document small cases only, invoice larger ones. The point is that you can now decide — instead of having to decide to skip it for lack of evidence.

Self-check: are you giving away demurrage?

  • Your vehicles regularly stand more than an hour at loading docks
  • Waiting times get noted on paper or not at all
  • Demurrage claims fail due to missing evidence
  • You don't know which loading points cost you the most standing time
  • Preparing a claim takes longer than it's often worth

If three or more of these apply, there's real money sitting here — and a process that can be automated quickly.

The next step

We'll work out what time data your telematics already delivers today and how to turn it into solid demurrage cases in a free intro call. A pilot with selected routes follows. For more use cases, see our industry page AI in logistics.

Frequently asked questions

Why do demurrage claims fail so often?
Almost always due to evidence: arrival and departure times aren't documented cleanly, timestamped proof is missing or surfaces too late. Without a gapless chain of evidence, customers reject the claim — and the effort of compiling it discourages people further.
How does an AI agent document waiting time at the loading dock?
The agent combines telematics data, driver status messages, and photographed documents with timestamps. Once standing time exceeds the agreed free time, it automatically opens a case, gathers the evidence and logs everything against the shipment in an audit-proof way.
Does the agent calculate demurrage itself?
It applies your stored terms: free time, rate and required proof per customer or framework agreement. That produces a ready-to-send claim with all evidence attached. Whether it goes out is your decision — approval always stays with you.
What does the standing-time analysis bring beyond billing?
You see for the first time, systematically, which loading points and customers regularly cause standing time. These numbers are a strong argument in price negotiations and help decide which routes are genuinely worth running — independent of whether you claim every instance of demurrage.
Does this mean more work for our drivers?
No, actually less: a photo of the signed document and a short confirmation by message — telematics and the agent handle the timing and matching. The paperwork that today often nobody ever evaluates goes away.
Is capturing this data compliant with data protection and driver data rules?
Yes, if set up cleanly: operation on German servers or within your own environment, a data processing agreement, a clearly defined purpose and logging. Driver-related data is processed only within the agreed scope — this can also be structured to align with a works council.

Topics

  • logistics
  • demurrage
  • waiting-time
  • documentation
  • billing

Relevant for your industry