Cross-border Trade
A shared inbox is not a shipment handover
For an independent freight forwarder, a colleague’s absence should not leave a shipment hidden in email. Use a short handover record that connects the job, its source documents, the next action and the person allowed to take it.
Find the next action without reading the whole inbox
A shared mailbox can make messages visible, but visibility is not the same as an operating handover. One person may know which booking changed, another may hold the latest rate, and the customer may be waiting on a reply that exists only as an unfinished draft. The test is simple: could a covering operator identify the next safe action on a shipment without asking its usual owner to reconstruct the history? If not, add a handover record before adding another notification.
Start with one job reference and the customer’s agreed movement requirement. Record the current milestone, the next deadline and the timezone attached to it. Link the latest booking confirmation, transport document and relevant instruction rather than copying fragments into a fresh message. The WCO Data Model describes structured, harmonised and reusable data definitions for cross-border exchange. [1] A forwarder’s internal handover need not implement that whole model, but the underlying discipline is useful: keep meanings consistent and avoid retyping the same shipment facts into competing records.
Give every exception an owner and a boundary
Separate an established fact from an action still awaiting confirmation. “Carrier booking received” is different from “space requested”, and a customer’s preferred delivery date is not a carrier commitment. Include the evidence link, who checked it and when it was checked. If a message contradicts the current job record, flag the discrepancy rather than silently replacing the old value. The covering operator needs to know what is reliable and what still needs an answer.
For each open exception, state the next action, its owner and the point at which approval is required. An operator may prepare an amended quote without having authority to accept a higher supplier cost. A document can be ready for review without being cleared for release. Customs, dangerous-goods and other regulated matters must remain with the appropriately authorised person for the shipment and jurisdiction. This is a recommended desk procedure, not a claim that a generic handover record satisfies every regulatory obligation.
Keep customer updates apart from internal detail
The customer-facing update should contain the information that customer is entitled to receive: an approved milestone, a document request, a confirmed change or a decision needed from them. Internal supplier pricing, other customers’ documents and unreviewed compliance notes should not travel with the update merely because they sit in the same mailbox. Make the distinction explicit in the handover so the covering colleague is not forced to guess under time pressure.
Account security matters here because the mailbox is often a gateway to other business activity. CISA’s guidance illustrates how a compromised email account can lead to further account compromise and recommends multi-factor authentication. [2] Use individual access to shared resources where your system supports it, rather than passing around a common password. Check unexpected access or payment-related requests using a known contact route. These are baseline precautions; multi-factor authentication does not prove that every message in an account is genuine or that every proposed action is authorised.
Rehearse an absence before it becomes an outage
Pick one ordinary shipment and ask a colleague who is not its usual owner to work from the handover record. Have them identify the next action, find the latest supporting document and prepare a customer update without releasing it. Note what they could not establish. Missing cut-off timezones, stale document versions and unnamed approvals are concrete faults you can correct. Do not use a live payment, booking commitment or regulated filing as the test event.
Then consider what happens if the mailbox itself is unavailable. The NCSC’s small-organisations guidance covers backups, account protection and scam awareness and emphasises that security is a team responsibility. [3] Keep an access-controlled continuity contact list and an agreed way to reach the current handover information. Decide how temporary notes will be reconciled when normal access returns. Avoid exporting a full customer inbox to an unmanaged personal device as an improvised fallback; convenience does not remove confidentiality obligations.
Use a five-field check at the end of the shift
For each shipment that needs another person’s attention, check five fields: job reference, verified current position, next action, owner and deadline. Attach the source document or message to the position and include any approval boundary with the action. If a field is unknown, say what is missing and who will obtain it. A clear unknown is more useful than a confident but unverified status. Keep the format short enough that the team will maintain it during a busy afternoon.
Start with the exceptions due before the next staffed shift, not an attempt to rewrite every historic job. Review the first handovers with the people who actually cover the desk and remove fields that do not help them decide or act. The objective is continuity without exposing internal information or widening authority: another operator can pick up the work, understand its limits and keep the customer informed from the same checked shipment record.
Sources
- WCO Data Model — World Customs Organization
- Turn On MFA — CISA
- Small organisations guide to cyber security — NCSC
General operational guidance. Apply the approval and regulatory requirements relevant to your business and shipment.