Record a Failed Pickup Before Sending Another Vehicle

1. Keep one freight job and add one attempted-pickup event

A vehicle reaching the collection point is an operational fact even if no goods enter the vehicle. Do not overwrite that fact by marking the original job cancelled merely because another attempt may be considered. Equally, do not mark the job collected because the driver arrived. Keep the freight job open where its collection requirement remains unfulfilled, and add a distinct attempted-pickup event underneath it.

Suggested internal practice: give the event a unique event ID linked to the job ID, vehicle, driver, collection-point reference, arrival time, departure time, and plain no-load outcome. Record what was observed or reported, not an assumed cause. “No pallets were presented at the named bay when the driver checked” is clearer than “site issue.”

This separation allows the dispatcher to see two true statements at once: the vehicle attended, and the goods remain uncollected. It avoids creating a replacement job that hides the original instruction, the first movement, and the remaining work. The worksheet proposed here is a dispatch aid; it does not decide fault, charges, liability, entitlement, or commercial outcome.

Source: FedEx US: air-freight pickup details

2. Record the factual attempt before assigning a reason

Start the event record while details remain available. Capture arrival and departure as observed or reported, and identify the source where that matters. Separate a driver’s direct observation from a later phone call or message. State the no-load result plainly: no goods were loaded, the goods were not released, or no collection acknowledgement was obtained. A no-load outcome alone does not establish that the job is cancelled.

Then record the stated reason in the speaker’s terms and identify its source. A consignor contact may say packing is incomplete, access is unavailable, documents are pending, or the vehicle arrived before the goods were ready. Each is a reported explanation unless independently evidenced. Link an available message, call note, bay note, photo, or gate record using the team’s normal record method.

The supplied carrier sources are limited, carrier-specific US examples. They show that pickup information can be recorded and that an attempted pickup can be distinguished from whether packages were collected. They do not create a rule for this fleet, Malaysian operations, another carrier, parcel work, air freight, or other freight services. All fields in this guide remain suggested internal practice.

3. Follow a concrete decision sequence

Use this sequence before another vehicle is instructed: first, identify the continuing job and the completed no-load attempt. Second, record arrival, departure, the no-load outcome, and the source of each reported reason. Third, name the exact prerequisite said to block collection. Fourth, ask the consignor or authorised job contact whether that prerequisite is met, pending, or unknown. Fifth, preserve the confirmation and time. Sixth, name the internal decision owner. Seventh, decide whether to hold, clarify, arrange a later attempt, or close only the event while keeping the job open. Eighth, communicate the current instruction to the relevant person.

The decision is not simply “send another vehicle?” It is: “What evidence supports a further collection attempt for this still-open job, and who made that decision?” If the prerequisite is unclear, record uncertainty and assign a next action. Do not convert a vague statement into readiness. If goods are said to be ready, record who said so, when, and the specific readiness point confirmed.

When redispatch is selected, create a new instruction linked to both the continuing job and the earlier event. It should identify the current vehicle or driver instruction without altering the history of the first attempt. Use operational labels your own team can apply consistently; this guide does not prescribe a transport-management status model.

4. Use the suggested dispatch-desk decision table

This table is an adaptable internal prompt, not a carrier requirement, universal industry standard, Malaysian service rule, legal obligation, or instruction to any consignor. Its purpose is to make the known facts, reported information, and unresolved prerequisite visible before another movement is considered.

5. Obtain confirmation and prerequisite evidence

A stated reason becomes useful for dispatch only after the team can name the question that must be answered before redispatch. Replace “not ready” with a bounded question such as: “Are all goods for this job presented and available at the stated collection point?” If access, documents, loading equipment, or a contact is mentioned, ask which exact item remains unresolved and whether it is now available.

Suggested internal practice is a short confirmation record containing the job reference, confirming person and organisation, channel, time, concise wording or paraphrase, prerequisite addressed, evidence reference where supplied, and remaining uncertainty. A statement that goods are ready is not a vehicle allocation, arrival-time confirmation, or successful collection. Keep those decisions separate.

A request for confirmation must not erase the first attempt. The event may show that a vehicle attended and left empty; the confirmation only informs whether a later action may be considered. If no confirmation arrives, leave the job open with a named owner and a next follow-up rather than inventing a reason or silently redispatching.

6. Fictional example / 虚构示例

Fictional example / 虚构示例: Job FL-204 concerns boxed components at Cedar Quay Stores. Vehicle T-18 reaches the named bay and later leaves with no goods loaded. The driver records arrival, departure, and the bay contact, then reports that the contact said cartons were still being counted. The dispatcher records this as a consignor-reported explanation rather than a verified cause.

The dispatcher leaves FL-204 open and adds event AP-204-01 with a no-load outcome. A later message from the consignor contact says cartons for FL-204 are now at the bay. The dispatcher attaches the message reference and time, records the stated prerequisite as “cartons presented at named bay,” and assigns the redispatch decision to the shift dispatcher.

The shift dispatcher issues a later collection instruction linked to FL-204 and AP-204-01. It names the currently assigned vehicle, repeats the collection point, and states that collection remains unfulfilled until goods are loaded. This example is fictional and reports no real customer, address, operational result, commercial result, or service promise.

7. Close the event carefully and retain the remaining job

Close the attempted-pickup event when its factual record is complete: attendance, no-load outcome, reported reason, evidence references, contact response, decision owner, and next instruction or follow-up are recorded. Closing the event means that attempt has been documented. It does not mean the goods were collected or that the wider job is complete.

Before redispatch, use the following five-item suggested internal checklist. It is designed to make missing facts visible, not to imply that every situation has the same operational answer.

1. The continuing job ID and no-load attempt ID are linked.
2. Arrival, departure, and the no-load outcome are recorded without invented facts.
3. The reported reason is labelled with its source and evidence reference where available.
4. The consignor or authorised contact’s confirmation, pending position, or lack of response is recorded.
5. One named decision owner has issued or deferred the next collection instruction.

8. Illustrative image and narrow differentiation

Reuse the existing AI conceptual fleet illustration and label it “Illustrative / 示意图”. It may orient the reader to a freight setting, but it is not evidence of an actual vehicle, collection, site condition, or job status.

The narrow differentiation is practical: this guide preserves the boundary between a failed physical collection attempt and the still-unfulfilled freight instruction before another vehicle is sent. It deliberately excludes departure checks, receiver-side changes, delivery-proof disputes, reassignment workflows, booking, pricing, penalties, and liability analysis.

Source: FedEx US: pickup notifications and attempted-pickup outcome