Record Freight Waiting Time Without Assuming a Charge

1. Define the narrow record before opening a timer

This guide concerns one question only: what waiting-related events can a team factually record at a freight collection point? It does not decide whether anybody should pay, receive, waive, dispute or approve a commercial charge. It also does not reschedule a receiving window, describe a failed no-load pickup, cancel a job, prove delivery, invoice a customer, or give driving-hours or safety instruction.

Use one existing freight-job reference and create a linked waiting-interval record. Do not replace the job status with a broad label such as “delayed” when the facts are more specific. A useful record distinguishes the vehicle’s arrival, the collection point’s readiness confirmation, loading start, loading end, and departure. These events may occur in that order, but the record must allow an event to be unknown, absent, or reported later.

The supplied fleet workflow treats loading delays as execution information and distinguishes assignment from acceptance. It also says manual updates are not GPS tracking. Apply that limited idea here: preserve the reported operational event and its evidence reference; do not represent a manual note as a location feed.

Source: BossFlow Fleet workflow scope

2. Set the time basis and preserve uncertainty

Before entering the first timestamp, identify the collection-point location and the time zone used by the source. Store the local date and time with its time-zone label where known. If a message states only “arrived at 08:10” and the zone is not stated, record the supplied text, mark the zone as unknown, and avoid silently converting it.

Keep event time separate from record-entry time. Event time answers when the observation or communication says something happened. Record-entry time answers when the dispatcher entered or amended it. A late entry can still be useful if the source and uncertainty are visible.

Use controlled certainty labels as suggested internal practice: confirmed from named evidence; reported by named person; estimated from a stated basis; unknown; or not applicable. “Unknown” is not a zero-duration interval. “Not applicable” means that the event does not belong to this collection activity. Do not turn an unknown readiness time into an assumed readiness time merely to complete a worksheet.

3. Follow the field decision sequence

First, confirm that the record belongs to the correct freight job, collection point, vehicle movement, and date. Second, enter arrival only when there is an identifiable observation or report, preserving the source reference. Third, record readiness confirmation as its own event: it is not the same thing as vehicle arrival, and it is not automatically loading start.

Fourth, enter loading start and loading end independently. If loading paused, create a separate pause interval only when its boundaries are actually known; otherwise attach a note without manufacturing times. Fifth, record departure independently from loading end. A vehicle can remain on site after loading ends, and a departure report can be missing even where loading completion is known.

Sixth, calculate only the interval your team has explicitly named. Suggested labels include arrival-to-readiness, readiness-to-loading-start, loading duration, loading-end-to-departure, and total on-site presence. Seventh, attach evidence references and a named recorder. Eighth, mark the factual record ready for review without making a commercial conclusion. A reviewer may later decide what additional information is needed; this guide does not supply that decision.

4. Prevent overlapping time from being counted twice

Use intervals as spans between two distinct event boundaries. When showing a total on-site presence, use arrival-to-departure where both boundaries are known. Do not add arrival-to-readiness, readiness-to-loading-start, loading duration, and loading-end-to-departure to another total and describe the result as a second independent waiting total. Those component spans already sit inside the full presence span.

If two descriptions cover the same clock period, retain both labels only if they answer different factual questions. For example, a readiness-to-loading-start span may overlap a site-access pause mentioned in a note. Preserve the note and its evidence, but do not sum both spans unless the overlap has been resolved. Where boundaries are uncertain, state that the total cannot yet be derived rather than filling the gap with an assumption.

The following is a suggested internal decision table, not a carrier requirement, universal industry standard, Malaysia service rule, or legal obligation.

5. Suggested internal decision table

Apply the table to a single event or interval at a time. It helps a dispatcher choose a record treatment, not a financial or liability outcome.

6. Fictional example / 虚构示例

Fictional example / 虚构示例: Freight job FJ-ORCHID-17 concerns collection from the fictional Orchid Components yard. A dispatcher receives a gate message saying the vehicle arrived at 09:12 in the stated local time zone. A warehouse message at 09:46 says the load is ready. A signed loading sheet records loading from 10:03 to 10:31. No departure message is available when the worksheet is updated.

The dispatcher creates one linked waiting record. Arrival is entered as reported, with the gate-message reference. Readiness is entered as reported, with the warehouse-message reference. Loading start and end are entered from the loading-sheet reference. Departure remains unknown, not estimated. The arrival-to-readiness and readiness-to-loading-start intervals can be displayed as factual elapsed spans. Total on-site presence is not displayed because the departure boundary is unknown.

An original suggested internal worksheet for this example contains: job reference; collection-point name; vehicle reference; local time zone; event type; event time; certainty label; evidence reference; recorder; entry time; overlap note; and review state. This is an adaptable proposal for internal use, not a carrier-specific form or transport requirement. The example makes no statement about a charge, fee, entitlement, liability, fault, service availability, or outcome.

7. Review, acceptance and narrow differentiation

Use a short close check before handing the record to another dispatcher or reviewer. The supplied GOV.UK material describes acceptance criteria as observable outcomes that can be checked and linked to supporting evidence. Here, use that idea only as an internal review method: the record should make observable facts and missing facts easy to see. It does not prescribe transport procedure.

This guide is narrower than a dispatch-readiness guide because it does not decide whether a vehicle or driver may proceed. It is narrower than a freight plan because it does not assess documents, cargo or capacity. It is narrower than a cost review because it deliberately leaves commercial treatment undecided. Its output is a factual, evidence-linked interval record that keeps unknowns visible.

Reuse the existing AI conceptual fleet illustration labelled “Illustrative AI concept: freight readiness; not an actual customer fleet or event.” The image supports orientation only and does not evidence a timestamp, vehicle movement, loading condition, or commercial conclusion.

1. Five-item close check: the freight-job and collection-point references match the event evidence.
2. Each known event has a local time and stated or unknown time-zone basis.
3. Arrival, readiness, loading and departure have not been merged into one vague status.
4. Any overlap is labelled and not added twice to a displayed total.
5. Unknown boundaries, evidence references and the next reviewer are visible.

Source: GOV.UK: writing user stories