Give the exception a decision owner before departure
A contact list is useful only when the next person knows which decision they are authorised to make.
Most planning documents can name a sender and a receiver. Fewer explain who decides what happens when the shipment presented at a handover differs from the expected one. A missing package, unreadable reference or unavailable unloading slot creates a decision, not just a request for an update. If that decision has no owner, several people may be informed while the load remains unresolved.
Start by describing the event that needs a response. The receiving team can record a count difference, but may not be authorised to accept a substitute item or release a partial order. The carrier may report an access problem, but cannot decide whether the consignee should change an installation sequence. Keeping those responsibilities distinct makes an exception path more useful than a long undifferentiated contact list.
Write the decision beside the handover
For each transfer, identify what should be checked and what happens when it disagrees. A cargo receipt might compare packed-piece identifiers and external condition. A dispatch release might require a document owner to confirm the agreed scope. The plan should say who can approve the next action and how a real operation reaches that role, using its own appropriate communication arrangements.
Include the boundary of that authority. Someone authorised to record damage is not automatically authorised to dispose of cargo, approve a repair or change a destination. Those actions may have commercial, legal or safety consequences beyond the receiving task. The Relay & Quay examples retain such questions as unresolved rather than presenting a signature field as universal permission to proceed.
An expected response time can also be a planning question. If a receiving decision is needed outside the responsible team’s working hours, find that out before dispatch. The demo’s desk hours are fictional labels and provide no staffed service. In a real enquiry, a name and telephone number are insufficient if nobody has agreed when the person can make the required decision.
An update tells people what happened. A decision owner determines what may happen next.
Relay & Quay Planning Desk — fictional editorial note
Keep an exception from becoming a false completion
Use language that separates an observation from an outcome. “Eight pieces received; one reference under review” is more informative than “delivery complete” when the receiving scope remains unsettled. A record can be timely and accurate without closing the issue. The important thing is to preserve the unresolved item where the next team will see it, rather than hiding it in a comment detached from the cargo line.
The parts-receipt exercise applies this distinction to urgent stock. It records what arrived before a separate person decides what may be released for use. Priority can influence which inspection happens first; it does not answer a compatibility question. The case makes no claim about a real warehouse system or customer result. It demonstrates why two related decisions should not be compressed into a single status.
At the end of a planning review, trace one likely exception through the document. Ask who detects it, who decides, what information they need and which later handover depends on the answer. If the chain ends with “contact someone”, the brief is not yet specific enough. Resolve the role before the goods reach the point where waiting becomes the only available action.