- Who is this for?
- Transport operations, billing, sales administration and management teams
- Question addressed
- Connect observed waiting time, the applicable rule and any amount that may require review.
Key takeaways
- Observed vehicle detention and potentially billable waiting time are different measures.
- Every timestamp needs a source, a time reference and a validation status.
- The contract, its amendments and the terms accepted for the shipment determine the rule to review.
- A structured waiting-event record makes the calculation reproducible and exposes missing inputs.
- A detected amount is not confirmed until the facts, rule and supporting documents have been validated.
Observed time is not the same as billable time
A vehicle may be recorded on site from arrival to departure. That interval describes an operational fact, provided the timestamps are reliable. On its own, it does not determine which part of the interval may qualify as a dock waiting charge.
The start point depends on the terms actually accepted: the booked slot, gate check-in, arrival at the dock, notice to a named contact or another defined event. The rule may also include a grace period, billing increments, exclusions, caps or a notice procedure. None of these parameters is universal; each must be read from the source governing the shipment under review.
| Status | What it establishes | What it does not establish |
|---|---|---|
| Observed wait | A period between named, timestamped and sourced events. | That the billing conditions have been met. |
| Qualified wait | The start, end, cause and shipment link have been checked. | That a pricing clause necessarily applies. |
| Potentially billable wait | The facts appear to meet an identified contractual rule. | That the amount is approved, accepted or collected. |
| Prepared or reviewed line item | The calculation follows a verified rule version and cites its evidence. | That the other party will accept it without review. |
Establish the facts before looking for an amount
Start by reconstructing the timeline without selecting whichever timestamp produces the largest interval. GPS data, a site portal and a driver message may each describe a different event. Conflicts between sources should remain visible until they are resolved.
| Item | Possible sources | Useful control |
|---|---|---|
| Shipment and site | Order, customer reference, appointment, TMS. | Link the event to the correct record and stop. |
| Agreed time slot | Booking confirmation, portal, accepted exchange. | Keep the applicable version and any amendments. |
| Arrival on site | Portal, gate record, authorised location data, timestamped message. | Identify the event actually measured and compare clock references. |
| Start and end of operations | Site system, transport document, driver report. | Separate docking, loading or unloading, and completion. |
| Departure | Gate-out record, operations status, authorised location data. | Confirm that the time belongs to the same vehicle and visit. |
| Cause and communications | Reservations, emails, messages, logged call, site incident. | Separate a reported fact from its validation by an authorised party. |
| Supporting documents | Transport document, receipt, authorised screenshot or log. | Preserve the original, author, date and link to the record. |
A technical source may corroborate vehicle presence without proving that a charge was accepted. Conversely, a pricing clause does not prove that the event occurred. A reviewable case connects evidence of performance with the applicable rule while keeping them distinct.
Create a structured waiting-event record
The following record can sit inside the transport file. Any unresolved field remains explicitly marked “to be confirmed”; it should not be filled from memory or inferred from another customer or site.
| Record field | Value to capture | Control status |
|---|---|---|
| Identity | Shipment, stop, vehicle, site and relevant party. | Linked / ambiguous / unlinked. |
| Observed start | Date, time, event type and source. | Raw / corroborated / validated. |
| Observed end | Date, time, event type and source. | Raw / corroborated / validated. |
| Observed duration | Difference between clearly named events. | Calculated / recalculate. |
| Cause | Reported fact, author and any confirmation. | Reported / disputed / confirmed. |
| Applicable rule | Contract, amendment, agreement or accepted terms, version and scope. | Found / confirm / missing. |
| Contractual parameters | Start point, grace period, unit, rounding, exclusions and required evidence. | Verified / incomplete. |
| Calculation to review | Inputs, formula taken from the rule and intermediate result. | Prepared / validated / rejected. |
| Decision and follow-up | Authorised owner, decision, rationale, action and outcome. | Pending / closed. |
Apply the contractual source governing the shipment
Begin with the contract that applies to the customer and service, followed by its amendments and accepted special terms. Check their effective dates, order of precedence and relevance to the site, operation type and shipment. A standalone rate card or past practice is not enough if its applicability has not been established.
The selected clause must answer specific questions. Which event starts the clock? Is any period excluded from the calculation? How is time converted into chargeable units and rounded? Which exclusions or notice conditions apply? Which evidence must accompany the claim? If an answer is missing or two documents conflict, suspend the calculation and refer the case for validation.
- 01Identify
Name the contract, amendment or accepted agreement and its version.
- 02Qualify
Compare established facts with its conditions without extending the clause to a neighbouring case.
- 03Calculate
Reproduce only the formula, units, rounding rules and boundaries found in that source.
- 04Validate
Send any new rule or interpretation to the authorised owner.
- 05Trace
Retain the inputs, rule version, decision and observed action outcome.
Fictional example: a recorded wait with a blocked calculation
Fictional example — A transport record contains a confirmed time slot, gate check-in, docking time, unloading completion and gate-out. Driver and site times agree for some events, but the docking time appears only in a message. Total time on site can be calculated; the contractual start of chargeable time cannot yet be established.
The event record links every time to its source, marks the docking time “to be corroborated” and references the contract that was found. The rate appendix mentioned by the contract is missing. Without the applicable version, any grace period, billing unit and rate, no reliable amount can be prepared. The correct status is therefore “observed wait, incomplete rule, calculation suspended” — not “charge due”.
Once the applicable appendix has been obtained and validated, the review can resume using its exact parameters. The detail retains the selected duration, every calculation step and the required evidence. An authorised person can then confirm the line, request another document or reject the rule’s application. That decision remains separate from later acceptance or payment.
- proven fact: events supported by matching sources;
- fact to confirm: a time recorded by one unvalidated source;
- missing source: the applicable contractual appendix;
- calculation: deliberately withheld until its inputs are established;
- next action: obtain the source and have its application to the record validated.
Frequently asked questions
Direct answers
Is a GPS record enough to invoice dock waiting time?
Not necessarily. Depending on its accuracy and collection conditions, it may document that a vehicle was near or on a site. The applicable rule may require a different start event, a validation or additional evidence.
After how long does dock waiting time become billable?
This article sets no universal threshold. The duration, start point, any grace period and exclusions must be checked in the contract and its amendments and, if a legal rule is invoked, in the applicable primary source.
What if the timestamps conflict?
Keep both sources, state which event each one measures and seek authorised corroboration. If the conflict changes the rule’s application or the calculation, the case remains pending and must be reviewed.
Sources and methodology
This resource describes Axonovia's product approach based on transport workflows. The examples are illustrative and do not constitute a performance commitment or a universally applicable contractual rule.
Product review: Axonovia team · next review recommended before 31 August 2027 or following a material change in scope.