Keep Each Stop Outcome Separate on a Multi-Stop Freight Job

1. Define the record boundary before entering a stop outcome

Use one parent freight-job reference for the planned multi-stop work, then create a separate stop outcome for every named receiving location. The parent job answers: “What remains across all planned stops?” A stop outcome answers: “What happened at this receiving location, for goods assigned there, on the stated unit basis?” The records are connected, but they answer different operational questions.

Before anyone writes “completed”, identify the original job reference, stop reference, receiving location, and allocation for that stop. State the unit basis beside the allocation: cartons, pallets, cases, or another clearly named operational unit. Do not add unlike units into one total. If the allocation cannot yet be determined, record it as unresolved rather than guessing, and name the person expected to clarify it.

This is an original, adaptable suggested internal worksheet. It is not a carrier requirement, a universal industry standard, a Malaysia service rule, or a legal obligation. The supplied fleet-workflow reference offers only limited context: it presents assignment, response, execution updates, and completion review as distinct operational states. It does not prescribe this worksheet for multi-stop freight work.

Source: BossFlow Fleet workflow scope

2. Follow the same field decision sequence at every receiving stop

First, open the parent job and confirm the stop being handled. Second, identify goods assigned to that stop on the stated unit basis. Third, preserve available arrival evidence without treating arrival as acceptance. Fourth, record the unloading or receiving outcome for that stop only. Fifth, compare that outcome with the stop allocation. Sixth, state any unresolved quantity and its next owner. Finally, return to the parent-job reconciliation before changing the parent status.

Use neutral outcome wording. “Received as recorded”, “partly received”, “receiving outcome unknown”, and “unresolved quantity” describe the current operating position without deciding a dispute or assigning fault. Arrival evidence might be a time-stamped message, site-entry note, acknowledgement from a receiving contact, or another available record. State what the evidence shows, not conclusions it does not support.

A stop may be marked complete when the team’s stated stop-level evidence and reconciliation support that label. The parent job stays open if another planned stop is pending, a stop quantity is unresolved, or the overall reconciliation has not been completed. Parent status should describe the whole freight job, rather than repeat the latest stop update.

3. Use the suggested internal stop-outcome worksheet

Keep the worksheet short enough for a dispatcher, driver, or operations colleague to use during an active job. Suggested fields are: original job reference; stop reference; receiving location; assigned goods and unit basis; arrival evidence; unloading or acceptance outcome; unresolved quantity; next owner; and parent-job reconciliation note. Where relevant, record event time separately from entry time.

The worksheet does not determine whether goods were acceptable, who is responsible, whether a charge applies, or what a later commercial decision should be. A custody or receiving entry alone does not establish those matters. Its narrow purpose is to preserve the visible result at one stop and the next operational action without overwriting the history of the parent job.

If a field is unknown, state that plainly. Do not replace an unknown allocation with zero, and do not enter “delivered” solely because a vehicle arrived at a location. A visible unknown gives the next owner a specific question to resolve. It also helps a later reviewer see the difference between an observed event and an unconfirmed result.

4. Make the parent-job decision from all stop outcomes

After every stop update, compare the parent job with every planned receiving stop. The question is not “Did the vehicle finish its latest activity?” It is “Can each planned stop outcome be reconciled, and is any work or quantity still unresolved?” Keep the parent job open whenever the answer is no.

The table below is suggested internal practice for a desk-side decision. It is deliberately limited to record handling: it does not decide a commercial, contractual, liability, or service-availability question. A complete first stop can be reconciled and retained while the overall freight job remains open for a later unresolved stop.

Suggested parent-job decision table

Use this table with the stated unit basis and the actual records available for the specific job. It is not a universal freight standard.

5. Fictional example / 虚构示例

Fictional example / 虚构示例: North Quay Foods creates parent job FJ-204 for one vehicle and two receiving stops. Stop S1, Cedar Stores, is assigned 18 labelled cartons. Stop S2, Murni Depot, is assigned 12 labelled cartons. Cartons are the stated unit basis for both allocations. The names, references, locations, quantities, and events in this example are fictional.

At S1, the team records arrival evidence and an unloading outcome of 18 cartons received as recorded. The stop reconciliation is complete, so S1 is marked complete. The parent job is not marked complete because S2 remains a planned stop with no receiving outcome. The result at S1 stays attached to S1; it is not used as a shortcut to describe the entire job.

At S2, arrival evidence is recorded, but the receiving outcome records 9 cartons received as recorded and 3 cartons unresolved. The suggested worksheet names an operations coordinator as the next owner to clarify the unresolved quantity and keeps S2 unresolved. The parent reconciliation note reads: “S1 reconciled; S2 has 3 cartons unresolved; parent job remains open.” No result is invented for those cartons, and the job is not closed merely because the vehicle visited both locations.

6. Five-item close check

Use this suggested internal review before considering closure of the parent job. It does not replace any organisation-specific process or external requirement.

1. Each planned receiving stop has its own stop reference and recorded outcome.
2. Each stop quantity has a stated unit basis and is reconciled to its allocation or explicitly marked unresolved.
3. Arrival evidence is recorded separately from unloading or receiving outcome.
4. Every unresolved quantity has a named next owner and a visible next action.
5. The parent-job status reflects all stop outcomes and remains open until remaining reconciliation is resolved.

7. Narrow differentiation and illustrative image

This guide addresses only separate receiving-stop outcomes within one multi-stop freight job. It is not partial-pickup guidance, which concerns collected and remaining goods at one origin. It is not carrier-leg guidance, which links an externally handled movement. It is not delivery-proof discrepancy guidance, which examines a mismatch between evidence and acknowledgement. It also does not advise on driver reassignment, waiting intervals, route optimisation, loading, charging, legal liability, or service availability.

Reuse the existing AI conceptual fleet-yard illustration only with this label: “Illustrative AI concept: fleet yard and dispatch activity; not an actual customer fleet or operational result.” The illustration provides orientation only. It is not evidence of a real vehicle movement, receiving event, customer outcome, or fleet capability.

No carrier-specific example is treated as a universal rule in this guide. The cited fleet-workflow material is used only for the limited claim that its own workflow separates operational states and says manual updates are not GPS tracking. The suggested worksheet, decision sequence, fields, and reconciliation approach remain original internal-practice proposals, adaptable to a team’s own records.

Source: GOV.UK: writing user stories