Truck detention charges: build the timeline before approving the claim

A truck reaches the gate before its appointment, waits for a bay and leaves after the warehouse finishes its paperwork. The carrier submits a detention claim covering the whole visit. The warehouse accepts that the visit was long but disputes the charge.

Reconstruct the timeline first, then apply the agreed commercial rule. Gate-to-gate duration explains the operation. Payable detention depends on which events start and end the contractual clock, what time is free and which exclusions are supported. One number cannot safely answer both questions.

Establish the clock before calculating the amount

Create a claim record linking the carrier, vehicle visit, shipment references, site, appointment version and invoice line. One vehicle may carry several consignments. Decide whether the contract charges per visit, vehicle, consignment or another unit before allocating the amount.

Read the clause for the triggering event. It might use scheduled arrival, acknowledged reporting, readiness for unloading or another defined point. Check whether free time includes unloading and whether an hour means sixty elapsed minutes or each started billing hour. Record the document version and the person who resolved an ambiguous clause.

Site events can come from a gate register, a dock system, signed unloading records and release documents. Axestrack advertises stage-based yard turnaround analysis, illustrating a source of operational timestamps. The contract still determines their commercial meaning. Connected plant logistics

Keep the event time, capture time, timezone and source together. A gate operator entering yesterday's release today has created a late record, not a visit that ended today. Preserve the original entry and its correction history.

An illustrative visit with two different charge calculations

The following is an invented contract and visit, not a carrier tariff. All events occur on 15 October 2026 in Asia/Kolkata. The agreed clock begins at the later of actual reporting and the confirmed appointment, ends at release, includes unloading and allows three free hours. Chargeable time is billed per started hour at ₹800. There are no approved exclusions, taxes or other charges in this example.

The contractual elapsed period is 10:00–14:30, or 270 minutes. Subtracting 180 free minutes leaves 90 minutes. Two started hours at ₹800 produce ₹1,600.

Starting at the 08:10 reporting event instead would produce 380 elapsed minutes, 200 chargeable minutes and four started hours: ₹3,200. The ₹1,600 difference comes from the start rule, not from arithmetic. The early arrival remains in the operational timeline even though this illustrative contract excludes it from the charge clock.

Boundary cases matter. Exactly 180 elapsed minutes produces no charge. At 181 elapsed minutes, one started hour is chargeable. Do not round the total visit to hours before subtracting the free period; that can change the result.

Suppose a supported thirty-minute carrier-caused interruption is subsequently accepted as an exclusion under an applicable clause. If that clause deducts the interruption before rounding, chargeable time becomes sixty minutes and the charge becomes ₹800. Keep this as a revised assessment with an approved reason. A vague note saying “driver delay” is insufficient to remove time.

Turn conflicting records into a reviewable decision

A useful workflow has separate responsibility for event evidence and commercial approval.

A missing release does not justify choosing the last scanner event as a convenient endpoint. That scan may precede paperwork or occur after the truck leaves. Keep the calculation provisional and state the unresolved event.

Overlapping exclusions need interval arithmetic. Two departments may describe the same thirty-minute stoppage; subtracting both records would remove an hour. Retain the original intervals, identify overlaps and apply only the approved union of excluded time.

Choose a control that can explain a disputed bill

For occasional claims, a protected worksheet with linked source records may be sufficient. Lock the formulas, separate inputs from assessment and retain the approved version. A shared sheet that silently changes after approval is a weak payment record.

At higher volume, a visit ledger can assemble events and propose charges. It should retain unknown timestamps, conflicting appointment versions and the exact contract used. Replacing missing events with averages might help capacity planning; it should not manufacture evidence for a specific payable claim.

Before relying on the workflow, ask finance and operations to reproduce one normal visit, one early arrival, one overnight visit, one missing release and one revised claim. Check both the assessed amount and why the invoice was held. Measure unresolved claims by reason and age, including claims rejected or awaiting evidence. Faster approval alone can reward accepting unsupported charges.

Keep detention approval separate from invoice settlement. If an invoice contains other accepted services, finance follows its approved partial-payment or dispute process. The assessment tool should not infer authority to deduct an amount or send payment.

A defensible charge starts with a defensible interval

The useful result is a claim whose events, contractual interpretation and amount can be reconstructed. That also exposes operational delay without forcing every delay into a payable category.

Next actions

1. Select one disputed visit and gather the appointment, reporting, unloading and release records.
2. Write the clock, free-time, exclusion and rounding rules beside those events.
3. Recalculate the accepted and claimed amounts, retaining any unresolved evidence.
4. Have the contract owner approve the assessment before finance acts on it.