Keep Customer References Separate from the Dispatch Job

1. Make the dispatch job the stable operational anchor

At a freight desk, begin with the existing dispatch job, not with the newest customer message. The dispatch-job reference is the stable internal handle for the movement the team is already planning or monitoring. A customer may supply a purchase-order number, booking reference, receiving reference, consignee reference, or another label for that movement. Those values can be important to the customer, yet they do not replace the job reference and do not become universal identifiers merely because they appear in an email or chat.

Keep the two questions separate: “Which internal freight job is this?” and “Which customer-issued reference applies to which covered part of that job?” The first question uses the existing job record and its observable movement context. The second needs a crosswalk row with an issuer, the exact value supplied, a source item, a named checker, and the part of the job that the reference is said to denote. Do not generate a new code to make an unclear match look settled.

This distinction is especially useful where one freight job has several stops, several customer contacts, or more than one request covering different parts of the same movement. A single job can legitimately retain multiple verified customer references. Conversely, identical reference text from two issuers is not evidence that their requests describe one job. Preserve the identity of each issuer before deciding whether a row can be linked.

Source: BossFlow Fleet workflow scope

2. Capture a reference exactly before interpreting it

Copy the customer reference exactly as supplied, including visible punctuation, spacing, prefixes, and letter case where the source shows them. Record the issuer name as supplied or as already identified in the job context; record the reference type separately from the value. “Purchase order” and “booking reference” are meanings, while the character string is the value. Keeping them in separate fields prevents a later reader from guessing whether a label was added by the customer or by the dispatch desk.

Attach or point to the source evidence that supports the row: for example, an identified email, request attachment, portal extract supplied to the desk, or a clearly dated conversation record. State what the evidence actually supports. It may show that an issuer supplied a reference and named a destination or stop. It does not, by itself, establish cargo ownership, invoice ownership, contractual responsibility, or completion of a freight movement.

Use a suggested internal crosswalk worksheet with these fields: dispatch-job reference; issuer; reference type; exact value as supplied; source evidence; covered part of the job; checked owner; check status; unresolved collision; and next decision. This is original, adaptable internal practice. It is not a carrier requirement, a universal industry standard, a service rule, or a legal document.

3. Follow the decision sequence before linking a row

First, open the existing dispatch job and confirm that it is the job under review. Second, collect each supplied customer reference without changing the job reference or customer text. Third, record the issuer and evidence for each reference. Fourth, map the reference to a specific covered part of the same job: the full movement, a stated pickup, a named delivery stop, a stated consignment portion, or an explicitly unresolved scope. Fifth, compare any apparent collision using issuer, type, evidence, and covered part rather than matching characters alone.

If the evidence identifies the issuer and covered part consistently with the existing job, add a crosswalk row and mark it checked by the named owner. If the evidence is incomplete, retain the row as unresolved and ask the appropriate operational owner to clarify the mapping. If the same text comes from a different issuer, create a separate row even when the text looks identical. Do not merge jobs, overwrite either supplied value, or infer that two customers refer to the same goods.

A useful desk outcome is modest and visible: linked, awaiting clarification, or collision unresolved. “Linked” means the worksheet records what evidence supports the relation to one existing job and which part it covers. It does not mean the desk has decided commercial, document, cargo, or tracking questions that lie outside this guide.

1. Open the existing dispatch job before reviewing the incoming reference.
2. Record issuer, reference type, and exact supplied value separately.
3. Preserve the source evidence and identify what it actually says.
4. Map the reference to a precise covered part of the job.
5. Name the checker and leave uncertain collisions unresolved.

4. Use a five-row decision table at the dispatch desk

The table is a suggested internal prompt for choosing the next record action. It does not replace the team’s own escalation routes or decide facts not present in the evidence.

5. Fictional example / 虚构示例

Fictional example only: dispatch job DJ-ORCHID-17 already describes one planned freight movement with two named receiving stops. Issuer North Quay Stores supplies purchase-order text “PO-4821” in a request that identifies the first stop. Issuer Orchard Supply supplies booking text “PO-4821” in a separate request that identifies the second stop. The identical text is a collision in characters, not a basis for merging issuers, requests, or jobs.

The dispatcher creates two separate suggested internal worksheet rows. Row one records North Quay Stores, purchase order, exact value “PO-4821”, its identified request evidence, and “first receiving stop” as the covered part. Row two records Orchard Supply, booking reference, exact value “PO-4821”, its separate request evidence, and “second receiving stop” as the covered part. The job reference remains DJ-ORCHID-17 in both rows. Neither customer value is edited or replaced.

Later, North Quay Stores supplies a second reference for the same first stop. The dispatcher adds another row after checking its evidence and maps it to the same covered part. More than one verified customer reference can therefore sit beside one dispatch job without making them interchangeable. This fictional example does not describe a real customer, shipment, result, carrier process, or system integration.

6. Keep the boundary narrow when evidence is incomplete

This guide does not correct a carrier-issued or freight-document reference. It does not link an external carrier leg, create a return request, record an empty repositioning movement, or decide whether an invoice, cargo, or contract belongs to a party. Those are separate operational questions with different evidence and ownership. A customer reference crosswalk merely makes the relation between a supplied customer label and an existing freight job reviewable.

The supplied fleet workflow material supports the general operational idea that job, vehicle, driver, assignment, response, readiness, and completion are distinct states. It does not prescribe this worksheet or determine the meaning of a customer purchase order. The supplied GOV.UK material supports using observable acceptance criteria and linking them to evidence. Applied here, that supports a visible check such as “issuer, source, job part, and checker are recorded”; it does not make the crosswalk a regulatory or transport document.

Do not generalise parcel, air-freight, carrier, or platform conventions to this desk decision. Where an issuer, source, or covered part cannot be verified from available material, record the uncertainty and a next owner. The correct immediate action can be to preserve the separate row and wait for clarification.

7. Close the reference review, not unrelated freight work

Before ending the review, check that every row still points to the existing dispatch job; that each customer value remains exactly as supplied; and that each mapped reference names a covered part or is openly marked unresolved. Confirm that a named person performed the check and that a collision has not been silently converted into a merge. Keep the worksheet with the job’s operational material in the team’s chosen controlled location.

The reused fleet-yard illustration is labelled “AI concept imagery — illustrative only; not an actual customer fleet or reference record.” It may help readers recognise the dispatch setting, but it is not evidence for any customer reference, job, vehicle, or movement. The practical value of the guide is deliberately narrow: it helps a desk retain separate identities while making a justified job-reference relation visible.

Source: GOV.UK: writing user stories