Keep Load Custody Clear During an Unplanned Vehicle Transfer

1. Define the narrow desk decision

Use this guide when an already loaded freight movement is interrupted and the desk is considering whether the identified load may move from its current vehicle to a proposed receiving vehicle. The question is not simply “who can continue?” It is: “what record and authorised decision are needed before a proposed custody change is recorded?”

Keep the original dispatch job as the anchor. Add a stopped-movement event rather than changing history. Create a proposed transfer record linked to both. A transfer can later be authorised, declined, or held pending evidence; none of those outcomes alters a later delivery record.

This is record planning only. It does not direct roadside activity, unloading, repair, or emergency response. Use the organisation’s existing authorised procedures for those matters. A custody entry alone does not establish liability, condition, or later delivery completion.

Source: BossFlow Fleet workflow scope

2. Preserve facts before deciding

Capture what is observed and where it came from before interpreting the interruption. Record the job reference, original vehicle and custodian, last verified goods position, event time or stated time basis, and the reason as reported rather than as a conclusion. Keep the source of each item, such as a driver update, dispatch note, photo reference, sealed document reference, or receiving record.

Then separate proposed facts from confirmed facts. The receiving vehicle and proposed custodian are proposals until identified and accepted in the record. An observed quantity basis may be a count, a sealed-unit reference, a document reference, or an explicit unknown. Do not convert an unknown into a zero, a full quantity, or a presumed handover.

BossFlow Fleet’s workflow scope distinguishes assignment from acceptance and keeps vehicle, driver and job connected. Here, apply that same visible-state discipline to the exceptional transfer: an available vehicle is not yet an accepted custodian, and a proposed transfer is not a completed movement.

3. Follow the decision sequence

Work in this order so an urgent message does not overwrite the job history.

1. Open the original dispatch job and record the stopped-movement event with its last verified position and evidence source.
2. Create one proposed transfer sheet; link it to the original job and stopped movement instead of opening a replacement delivery job.
3. Identify the proposed receiving vehicle and custodian, or mark either item unknown. Record the observed quantity basis and every discrepancy separately.
4. Name the decision owner and request an explicit authorise, decline, or hold outcome. Do not treat a forwarded message as authority.
5. After evidence is confirmed, record the authorised transfer as its own event. Create any next movement separately; record later delivery evidence only against that later movement.

4. Suggested internal transfer worksheet

The following is an original, adaptable internal worksheet. It is not a carrier requirement, universal industry standard, Malaysia service rule, or legal obligation. It is deliberately smaller than a general fleet system: its purpose is to make one exceptional custody decision reviewable.

Suggested fields are: transfer-sheet reference; linked job and stopped-movement references; original vehicle and custodian; last verified goods or custody position; proposed receiving vehicle and custodian; observed quantity basis with its unit; discrepancy or unknown; evidence references; authorising owner; decision status; decision time basis; and the separately linked next-movement reference.

For each field, distinguish “reported”, “observed”, “confirmed”, and “unknown”. That vocabulary stops a helpful-looking completion mark from claiming more than the desk can support. GOV.UK guidance on user stories describes acceptance criteria as observable outcomes; use that idea internally by making each required field or unresolved exception visible to the named decision owner.

5. Decide from the evidence available

Use this desk-side table as suggested internal practice. It does not decide physical handling or replace any authorised procedure.

1. See the decision table below before changing a status.

6. Fictional example / 虚构示例

Fictional example: Dispatch job FJ-208 is linked to vehicle L-17 and custodian Sam. A desk update says the loaded movement stopped at “North gate lay-by”; the exact goods position is not yet independently verified. The desk creates transfer sheet TX-208-A, preserving L-17 as the original loaded vehicle and recording the location as reported.

Vehicle L-23 and custodian Mei are proposed. The only available quantity basis is “twelve labelled units” from the pre-movement load record; no handover observation is yet attached. One unit’s label reference is reported unclear. The sheet therefore records twelve as the pre-movement reference, the actual transfer quantity as unknown, and the label issue as an open discrepancy.

The authorised owner places the proposal on hold pending evidence. Later, an evidence reference identifies the receiving vehicle, accepting custodian, and observed quantity basis. The desk records a separate authorised-transfer event and opens a separate next-movement record. It does not mark FJ-208 delivered merely because a transfer was recorded.

7. Close the transfer question, not the whole job

Before closing the transfer review, use the five-item check below. If one item is missing, leave the specific transfer decision open or record the known limitation. A later movement, proof of delivery, customer communication, charge, repair outcome, or liability assessment remains outside this narrow record.

The narrow differentiation matters: this guide protects the chain between an interrupted loaded vehicle and a potential successor vehicle. It is not a planned carrier-leg process, a driver reassignment guide, a partial collection record, a pallet-return workflow, or a consumer transport page. The existing AI conceptual fleet-yard illustration may be reused only with the label “Illustrative AI concept; not an actual customer fleet.”

1. Original job and stopped-movement references remain visible and unchanged.
2. Last verified goods or custody position has a source and a clear time basis.
3. Proposed and confirmed vehicle or custodian values are not mixed.
4. Quantity basis, unit, discrepancy, and unknowns are recorded separately.
5. A named owner’s decision and the evidence references are linked to the separate transfer event.

Source: GOV.UK: writing user stories