A logistics shift handover is the controlled transfer of unfinished operational state from the outgoing team to the incoming team so that open shipments, holds, deadlines, exceptions, risks and next actions remain owned when the people on duty change.
Warehouses, ports, airports, transport control rooms and distribution centres do not reset when a shift ends. Vehicles are still approaching. Orders are still open. A pallet may be waiting for release. A refrigerated shipment may be inside a tolerance window. A customer may be waiting for an answer promised after the next team arrives.
The outgoing shift should not hand over a story. It should hand over a usable current state.
This is Article 107 in the extended How Logistics Works series. Logistics Handoffs remains the general owner for custody and responsibility across organisations. This page owns one narrower boundary: continuity across people and time inside a live operation.
The Shift Boundary Is a Logistics Handoff
A handover changes who is actively watching the work. That makes it a real control boundary even when the goods do not move.
The outgoing team may know:
- which vehicle is late;
- which order is waiting for approval;
- which pallet is physically in an unusual place;
- which customer accepted a revised delivery;
- which system status is stale;
- which temporary workaround is keeping flow alive.
If that knowledge does not cross the shift boundary, the next team can inherit the objects without inheriting the meaning.
A Handover Should Answer Six Questions
- What is open?
- What is its current verified state?
- What is the next action?
- Who owns that action?
- By when must it happen?
- What constraint or uncertainty could change the action?
Everything else is supporting context.
Do Not Hand Over Completed Noise
A handover that lists every shipment from the shift creates information overload. The incoming team needs what remains operationally relevant.
Good candidates include:
- open exceptions;
- unfinished high-priority orders;
- holds and quarantines;
- vehicles due soon or materially late;
- expiring cut-offs;
- capacity constraints expected next shift;
- system outages or manual fallbacks;
- temporary authorisations;
- condition-sensitive cargo needing observation;
- work whose next owner has not yet accepted it.
The handover is a filter, not a warehouse diary.
Status Words Need Operational Meaning
“Pending”, “urgent” and “follow up” are weak unless the next team knows what they imply.
A practical state set can distinguish:
- in progress — work is actively moving;
- awaiting external action — another party must act;
- held — movement is intentionally prevented;
- blocked — movement cannot proceed because a dependency is unavailable;
- watch — no action yet, but a threshold or deadline is approaching;
- ready for next action — evidence exists and a named action can proceed.
The exact vocabulary can differ. Its purpose is to reduce the amount of meaning buried in free text.
The Next Action Matters More Than the Last Discussion
A handover note saying “spoke to carrier twice” describes effort. The incoming operator still needs to know what to do.
A stronger entry might say:
Shipment S-240: carrier has not accepted revised collection; next action is call dispatch control by 22:15; if no vehicle confirmed by 22:30, escalate to approved recovery carrier.
The history remains available. The working handover points at the decision that is still alive.
Keep Fact, Inference and Unknown Separate
The outgoing shift may believe a pallet was moved because a forklift driver said so. The physical location may not have been verified.
Handover should make that uncertainty explicit:
- observed: system shows Location B;
- reported: operator says pallet moved to Overflow 2;
- unknown: no confirming scan or physical check yet.
The incoming shift can now choose a discriminating next action instead of inheriting a rumour as fact.
Shift Handover Has a Strong Precedent in Other High-Consequence Operations
The FAA’s human-factors guidance for aircraft maintenance describes formal shift turnover because some tasks extend across shifts and important status information must pass between workers. Its guidance highlights the risk of errors when information passes from one person to another.
That is not a warehouse regulation. It is a useful cross-domain control principle: unfinished technical work becomes safer when its current state and special problems are deliberately transferred rather than rediscovered.
IATA’s current Cargo Operations programme likewise stresses common operating processes across the cargo chain and a Master Operating Plan for seamless handling. The logistics lesson is continuity of agreed process across changing actors.
Handover Needs Positive Acceptance
Sending the handover does not prove the incoming team received and understood it.
For critical open work, require an acceptance state:
- received;
- understood;
- clarification requested;
- accepted with named owner.
This can be conversational and efficient. The point is to prevent an open case from becoming ownerless during the few minutes in which both teams assume the other has it.
Some Work Deserves Verbal Handover Even When the System Record Is Complete
Structured data is excellent for normal state. Unusual context can still benefit from direct explanation.
Examples include:
- a customer who has accepted a narrow exception;
- a recurring scanner fault affecting one lane;
- a physically unstable pallet awaiting specialist attention;
- a complex recovery sequence involving several providers.
The spoken handover should point back to the recorded case. Conversation adds context; it should not become the only record.
A Physical Walk Can Be Part of Handover
For abnormal physical states, the cleanest handover can be to walk to the object.
“This damaged pallet is the one on hold” removes ambiguity that a written note may not. The incoming operator can see the actual location, condition and containment.
This is especially useful when:
- inventory is in a temporary location;
- physical segregation matters;
- signage is imperfect;
- the object is unusual enough that its identity could be confused.
Cut-Offs Should Be Sorted by Time-to-Decision
The incoming team should not discover a critical cut-off by reading chronologically through the previous shift’s notes.
Prioritise open work by remaining decision time:
- next 15 minutes;
- next hour;
- this shift;
- watch later.
The same shipment can move between bands as time passes. The handover board should represent the current clock rather than remain a static document written thirty minutes earlier.
High-Consequence Cargo Needs Condition State, Not Only Location
A refrigerated shipment can be physically safe at the moment of handover and still require action because battery duration, coolant margin or receiving availability is narrowing.
A useful handover can include:
- current observed condition;
- required range;
- remaining margin or next monitoring point;
- next qualified storage state;
- what threshold triggers escalation.
The product-specific decision remains with the proper specialist owner. The shift handover preserves the operational state required to reach that owner in time.
Holds Need a Release Condition
“Do not move” can survive indefinitely across shifts if nobody knows what must happen next.
A hold entry should state:
- what is held;
- why the hold exists;
- who owns assessment;
- what evidence is awaited;
- who may release;
- where the item physically sits.
The incoming shift then preserves the hold without converting it into abandoned inventory.
Pending Approval Is Not a Next Action Unless Someone Is Responsible for Chasing It
An outgoing team writes “awaiting manager approval”. The manager assumes operations will call if the issue remains urgent. The next shift assumes the request is already being handled.
Assign a watcher:
approval owner = manager; chase owner = incoming transport lead; response deadline = 23:00; escalation = deputy manager at 23:05.
Authority and follow-up are different roles.
System Outages Make Handover More Important
During a WMS, TMS or network outage, temporary records may live on paper, spreadsheets or local devices. The shift boundary becomes a risk point because the incoming team can inherit only part of that shadow process.
Handover should identify:
- which systems are unavailable;
- which manual records are authoritative temporarily;
- which work has already moved physically;
- what data must later be reconciled;
- which activities remain prohibited without the normal system.
Cyber Disruption in Logistics owns the wider fallback and reconciliation problem.
Do Not Let the Handover Spreadsheet Become a Second Permanent System
Teams often create a local sheet because the official system does not show the exact information needed at shift change. The sheet can be useful. It becomes risky when important state exists only there and never returns to the system of record.
For each handover field, ask:
- is this temporary context?
- is this a missing field that belongs in the operating system?
- is it duplicated from another source?
- who clears it when the case closes?
The handover tool should make continuity easier, not create permanent parallel truth.
Handover Length Has an Optimum
Too short, and critical context disappears. Too long, and the incoming team cannot distinguish what matters now.
Compress routine work into the systems that already track it. Use the handover for:
- exceptions;
- decisions;
- deadlines;
- temporary states;
- unresolved uncertainty.
A long operation may need multiple views rather than one long list: immediate actions, open holds, inbound risks and watch items.
Shift Overlap Is Capacity for Information Transfer
If the outgoing shift leaves at exactly the moment the incoming shift begins, every clarification becomes asynchronous. A modest overlap can allow discussion of the few complex cases that structured records do not fully explain.
The required overlap depends on the operation. More overlap is not automatically better; it has a labour cost. The useful principle is to allocate enough transfer capacity for the number and consequence of open cases.
Night Shift Should Not Inherit Only What Day Shift Could Not Finish
A weak operating culture treats later shifts as a residual queue. Complex decisions accumulate until the people with more authority return the next day.
That can create predictable overnight drift:
- holds age;
- cut-offs expire;
- customers wait;
- manual workarounds expand;
- night operators avoid decisions because authority is unclear.
Shift design should include deputies and decision rights appropriate to the work that continues at night.
Worked Example: The Late Reefer and the Midnight Shift
The following is a hypothetical operational example.
A temperature-sensitive shipment is due to arrive at 23:40. The receiving cold room has capacity. At 22:50, the carrier advises a revised arrival of 00:35. The day/evening team ends at 23:00; the night team begins at 22:45.
A weak handover says: “Reefer delayed, watch arrival.”
A stronger handover records:
- shipment identity and current last trusted event;
- required temperature range from the authorised shipment record;
- revised ETA and confidence;
- cold-room receiving location and confirmed capacity;
- transport contact;
- next monitoring point at 23:45;
- what condition or further delay requires specialist escalation;
- night-shift owner who accepted the case.
At 23:50 the night team receives another delay update. Because the trigger and owner are explicit, it contacts the proper specialist decision-maker rather than merely updating the ETA. The shipment remains controlled across the shift change.
The example does not prescribe pharmaceutical disposition. It shows that the information needed to reach the correct decision survived the people change.
A Shift Handover Should Have a Closing Reconciliation
At the end of the incoming shift, check whether inherited cases were:
- closed;
- transferred onward;
- still open with a reason;
- lost from the active view.
An inherited case that vanishes from every active list without a completion event is an orphaned task. That is one of the most important handover failure modes to measure.
Useful Handover Metrics
- open cases handed over;
- percentage accepted by a named incoming owner;
- orphaned open cases;
- missed cut-offs within a defined period after shift change;
- cases reopened because critical context was missing;
- temporary holds whose release condition is unknown;
- handover items with no next-action deadline;
- manual shadow records not reconciled to the normal system.
Do not turn these into a bureaucracy contest. The measure should reveal continuity gaps, not reward longer notes.
Handover Quality Should Be Tested With the Incoming Team
The outgoing team can believe a note is clear because it remembers the whole story.
Ask the incoming operator to state:
- what is happening;
- what happens next;
- who owns it;
- what would change the plan.
If the answers differ, the handover is incomplete even if every field was filled.
Shift Handover at Three Zoom Levels
One shipment
Can the incoming operator identify the verified current state, next action, owner and clock without reconstructing the entire case?
One facility
Do open holds, late vehicles, high-priority orders and system fallbacks cross every shift boundary without becoming orphaned work?
One network
Can 24/7 operations preserve the same service meaning and decision rights even when different sites and time zones take turns controlling the journey?
A Singapore Lens
Singapore’s port, airport, express, warehouse and regional control operations often function across extended or continuous operating windows. Short physical distances do not reduce the need for temporal handover; they can make the next decision arrive faster.
A late vessel connection, midnight air-cargo arrival or overnight parcel sort can cross several staff changes before the final receiver sees the result. Continuity is therefore part of the hub’s invisible operating quality.
Hostile Test: “Everything Is in the System”
Can the incoming shift identify which of 300 open records matter in the next hour? Does the system show the temporary physical location? Does it show which approval is being chased? Does it distinguish a stale status from a verified state? Who owns the next action?
Information storage is not the same as operational handover.
Logistics Shift-Handover Audit
- Which open work must cross this shift boundary?
- What is each item’s verified current state?
- What is the next action?
- Who owns it on the incoming shift?
- What is the deadline or next check time?
- Which items are held, blocked, awaiting or watch-only?
- Are observed facts separated from reports and unknowns?
- Do high-consequence items include condition state as well as location?
- Do holds have release conditions?
- Do pending approvals have a chase owner and deputy?
- Are manual fallback records visible during outages?
- Will temporary shadow records be reconciled later?
- Does the incoming team positively accept critical cases?
- Which abnormal physical states need a walk-through?
- Is the handover ordered by time and consequence rather than chronology?
- Can inherited cases be reconciled at the next shift?
- Are orphaned tasks measured?
Evidence and Further Reading
The FAA’s Human Factors Guide for Aviation Maintenance treats shift turnover as a formal transfer of status and special problems because maintenance work often continues beyond one shift. IATA’s Cargo Operations programme and 2026 Cargo Handling Manual emphasise consistent operating processes across the cargo chain. These sources support the general need for continuity and common process; the logistics handover structure in this article is an original operational synthesis.
Return to the Logistics Hub
Shift handover protects logistics state when the people responsible for watching it change. Return to How Logistics Works for the full mechanism. Continue next to Logistics Reason Codes | How Exception Labels Become Evidence Instead of Noise.
Final compression: a shift handover succeeds when unfinished work changes people without losing its state. The incoming team should inherit the object, the evidence, the next action, the clock and the authority needed to act. A strong 24-hour logistics system is not one in which every operator knows everything. It is one in which the right unresolved information crosses the time boundary before the previous keeper of that information leaves.