RECIPIENT DESK / SIBU

Plan the receiving conversation before the handover.

Turn user-supplied cargo facts, two contact windows, access questions and a named acknowledgement owner into one private preparation memo. Unknowns stay visible.

Open the receiving desk →Ask about Sibu receiving planning

2: contact windows
5: confirmation edges
0: invented schedules

Recipient and coordinator reviewing a blank contact plan at a generic covered counter — 00ILLUSTRATIVE RECIPIENT PREPARATION

01 / BEFORE CONTACT

Four facts make the first conversation usable.

Cargo facts

Plain-language description and user-supplied package form/count.

Named recipient

One reachable recipient and a fallback contact owner.

Contact windows

A preferred and fallback window—not an appointment or ETA.

Handover question

A user preference carried to the responsible provider for confirmation.

Two people arranging blank preferred and fallback contact cards

02 / CONTACT WINDOWS

Preferred. Fallback. Still waiting for confirmation.

A window is a coordination preference supplied by the user. It is not a sailing, ETA, appointment, delivery promise or evidence that anyone was reached.

APreferred contact windowBFallback contact windowRESPONSIBLE PROVIDER CONFIRMS

Prepare the contact memo →

03 / HANDOVER QUESTION

Carry one preference without advertising a service.

User-supplied address

Ask whether delivery to the supplied location is actually available and accepted.

Covered collection

Ask for the actual point, access rules, timing and responsible handover contact.

Neither option is offered or confirmed by this website. An “other” option remains open until the provider names it.

Frame the handover question →

04 / ACCESS EDGE

The last few metres need named answers.

01Vehicle approach or receiving path
02Covered staging before handover
03Steps, lift and doorway questions
04Handling help or equipment owner
05Controlled or dangerous-goods confirmation

This page cannot inspect a path, choose lifting equipment or classify goods. Carry concerns to the people responsible for the real site, cargo and handover.

Open the access questions →

Two people reviewing a generic receiving entrance before cargo movement

Recipient and coordinator comparing a blank count sheet with unbranded cartons

05 / ACKNOWLEDGEMENT

Record an exception. Do not manufacture proof.

Package count suppliedCondition reportedOwner namedException carried

A typed summary is not a signature, receipt, inspection, custody record or proof of delivery.

IMO · DOSH · CUSTOMS

Authoritative context, deliberately narrow claims.

The CTU Code includes people who receive and unpack units; DOSH publishes workplace manual-handling guidance; Customs requires current restriction checks. CargoSibu turns those boundaries into questions—it does not inspect, classify or approve.

06 / PRIVATE MEMO

Carry facts, unknowns and stop items together.

The receiving desk stores one local result in this browser tab until you reset it. Nothing is submitted or emailed.

Build my receiving summary →