“Release requested” is a useful update, but it does not tell a buyer that a container is ready for collection. Identify the document and responsible party, obtain the issuer’s processing status, then check the destination requirements separately. A forwarded email should lead to a clear next action, not an assumed pickup promise.
Create a shipment status record
This guide helps buyers, export teams and logistics contacts record the status of a particular shipment. It does not select a legal document, decide title or authorise release. Use the shipping-document checklist for pre-departure data and the final-payment checklist for the separate internal payment review.
1. Identify the shipment and the actual document
Record the transport reference, container if relevant, issuer, carrier, consignee and current document revision. Where a forwarder is involved, ask which document and processing layer the update concerns. Do not carry a status from another reference across to this one. A draft is not evidence that the final document has been issued.
Confirm the document type and release arrangement with the issuing party. Do not change an original B/L, sea waybill or release instruction merely because someone uses a different term in an email.
2. Separate the document from the processing step
| Information received | What to confirm | What not to infer |
|---|---|---|
| Original B/L arrangement | Document holder/receiver, issuance and the carrier’s accepted surrender or processing route | A scanned copy completes surrender |
| Sea waybill | Named consignee and the actual destination delivery requirements | Identity, customs and other checks disappear |
| Telex/electronic release requested | Authorised requester, relevant conditions, acknowledgement and processing result | It is a sea waybill or an immediate pickup approval |
Maersk’s document explainer distinguishes the transport documents. Its surrender FAQ describes an online service for original/negotiable B/Ls rather than waybills, with document-receiver and Web BL agreement prerequisites. This is a carrier-specific example, not a universal route for every shipment.
3. Verify authority before relying on the request
Have the relevant authorised people confirm the agreed instructions, contract and payment position. If a bank or another rights holder is involved, route the question through the actual responsible contact. A chat screenshot is not a substitute for required authority. This guide does not bypass conditions, submit release instructions or sign indemnities.
Ask the handling party: Which document does the request concern? Who may submit it? Which condition is outstanding, and who must resolve it? Share only the necessary references and authorised records; this page does not collect customer documents.
4. Keep five status lines with their own evidence
Use the actual service’s terminology. Give every line a source, confirming person, time and next action rather than allowing one completed line to stand for all five.
| Status question | Where to obtain the current evidence | What to retain if unresolved |
|---|---|---|
| Was the request submitted? | Actual requester’s acknowledgement and reference | Missing input and submission owner |
| Has the issuer/carrier processed it? | Corresponding system status or official reply | Outstanding condition and next confirmation |
| What is the destination customs status? | Importer and its customs contact | Shipment-specific customs question |
| Are relevant charges and delivery documents resolved? | Carrier/agent; delivery order or instruction where required | Open items and responsible people |
| Is pickup actually arranged? | Consignee, destination operations and transport contacts | Appointment, availability and other restrictions |
Fictional example: a forwarder confirms that the request was sent but provides no carrier processing result. Mark submission confirmed and processing unresolved. Ask what remains missing instead of marking every line “released.” Even a completed document step leaves the destination parties to confirm the other collection conditions.
5. Send a supported update with the next owner
The logistics owner compiles the record; the export and receiving contacts review it. Inputs are the current document, authorised instructions, processing acknowledgement and destination replies. The output lists supported statuses, unresolved items, owners, next feedback time and evidence locations. Unknown is not complete or not applicable, and file completeness does not establish cargo clearance.
Review after a changed document, consignee, destination condition, charge or official reply, keeping earlier records. Document amendments or guarantees need the appropriate authority. Track the shipment’s free time and related charges while questions are open; this article sets no universal free days, fee or processing time.
Sources and operating limits
Maersk’s official FAQ, document explainer and cargo-release overview were checked on 19 October 2026. Their conditions depend on the service, document and destination. We use the workflow distinctions, not example prices or turnaround times as a quote or pickup decision. We did not access a customer account or perform a release.
The five checks and fictional example are CZ Overseas methods. Buyers can obtain an evidence-based handoff without treating a document copy, carrier processing and destination pickup readiness as the same status.
Frequently asked questions
Does a submitted telex-release request mean I can collect the cargo?
Obtain the carrier or issuing party’s processing status, then confirm destination customs, charges, required delivery documents and pickup arrangements. Submission alone does not complete every condition.
Is a sea waybill the same thing as telex release?
No. A sea waybill is a transport document; telex or electronic release is a processing arrangement to confirm under the actual carrier’s rules.
Does receiving a B/L PDF prove cargo release is complete?
Not by itself. Confirm the document type, issuance and processing status, and the relevant carrier and destination conditions. A copy or screenshot does not resolve those questions.