Shift safety handovers: tell the next team what has changed

A shift log can contain many entries and still fail to answer the next supervisor's first question: what needs my attention now? Routine activity, unresolved concerns and historical updates often appear in the same long list. A useful safety handover makes changes, current restrictions and outstanding decisions easy to find while preserving access to the underlying records.

The aim is a shared understanding of the current position. Reading a message is not always the same as understanding its consequence for the next shift. Build a handover that supports a brief conversation, especially where work is incomplete or the incoming team will encounter conditions different from those at the start of the previous shift.

Begin with the current situation

Describe what changed, where it applies and when the information was checked. Avoid opening with a chronology of everything that happened unless the sequence matters to the immediate decision. A note that equipment is awaiting review tells the next team more when it identifies the exact item, its location and the person coordinating the review.

Use the site's established arrangements for restrictions, authorisations and urgent response. A handover note should point to those decisions accurately; it should not create an informal substitute. If the position is uncertain, say which question remains open and who must resolve it. The incoming supervisor should not have to infer permission from silence.

Shift discussion context photographed by Tiger Lily on Pexels.

Separate information from a request for action

Some entries tell the next team about a completed event. Others ask someone to do something. Mark the distinction in the wording. “Supplier attended at 14:00” is an update. “Contact the supplier because the report is still missing” is a task that needs an owner and a next step. Combining both in one vague note makes it easy to miss the request.

For each task, identify the person or role accepting responsibility on the incoming shift. If the action already exists elsewhere, reference it rather than creating a second competing record. The handover can explain what the next shift needs to know while the action record remains the authoritative place for progress and evidence.

Make temporary arrangements visible

Temporary changes are vulnerable to being forgotten precisely because they are intended to be short lived. Record their scope, the decision that established them and the next review point. Explain any dependency that the incoming team must follow, such as a pending technical assessment or a planned access window. Do not assume the next supervisor attended the earlier conversation.

Consider a fictional situation where a delivery route has been changed while maintenance is unfinished. The handover should identify the applicable route arrangement and who controls further changes. It should also tell the next team whether the planned completion time is confirmed or estimated. A guessed time can spread quickly when each shift repeats it as fact.

Give unusual work enough context

Contractors, late deliveries and nonroutine maintenance may cross a shift boundary. Include the responsible contact, what remains unfinished and the process for resolving changes. A note saying “contractor on site” does not tell the next team whether the job has started, paused or reached a point requiring a site decision.

If supporting information is held elsewhere, test that the incoming team can access it. A link to a private mailbox is not a dependable handover route. Where access must be restricted, identify an authorised contact who can provide the necessary operational information. Keep personal details out of a general shift log unless they are required and handled under approved arrangements.

Handover record context photographed by Monstera Production on Pexels.

Check understanding through a short exchange

Ask the incoming colleague to identify the entries that require a decision or action during their shift. This is a practical check on the handover's clarity, not a memory test. If they interpret a restriction differently, resolve the ambiguity before the outgoing team leaves where possible. Record important clarifications so later readers do not inherit the original uncertainty.

Design the exchange around available time and the work environment. A lengthy form completed in a noisy doorway may be less useful than a concise written summary followed by a focused conversation in a suitable place. The record and conversation should support each other. Neither should depend on everyone having identical knowledge of the site.

Keep old items from becoming background noise

Repeatedly copying every unresolved entry can make the log unreadable. Keep a current summary that points to the main record and highlights what has changed since the last handover. If nothing changed, identify the next expected decision instead of pasting the whole history. This preserves continuity without asking each supervisor to reread weeks of narrative.

Remove an item from the active handover only when the relevant need has ended or responsibility has clearly moved elsewhere. Record that transition. An action disappearing from the shift log can otherwise be mistaken for completion. Conversely, retaining a resolved issue indefinitely can lead people to distrust the log and rely on verbal updates instead.

Make a late update recognisable

Information can change after the formal handover. Agree how an important late update reaches the incoming team and how receipt is established under your process. A note added silently to yesterday's log may never be read. Identify the actual change and its relevance instead of sending the entire handover again with no indication of what is new.

For example, a supplier may revise its expected arrival or explain that a report covers a narrower scope than anticipated. The incoming supervisor needs the changed fact, its source and any resulting decision required. Keep estimates labelled as estimates. If the update affects another team, identify who will pass it on rather than assuming everyone receives the same message.

After a suitable trial, ask the incoming team which entries were useful during their shift. Remove unnecessary detail from the active summary while preserving the underlying record. This keeps the handover focused without losing history. The test is whether a colleague can find and understand the information when it becomes relevant, including after the original sender has gone home.

Review one boundary, not the entire system

Choose a recent shift boundary and trace an unresolved issue across it. Can you see what the outgoing team knew, what the incoming team accepted and what happened next? Ask both sides where information was missing. One detailed example can reveal a weak link more clearly than a broad statement that communication needs improvement.

HSE's Great Britain management guidance provides a general reference for organising and reviewing safety arrangements. The specific handover design here is practical advice to adapt to your operation. Any technical controls, formal permissions or statutory records still need their own appropriate process.

Use Incident Management for connected incident context and Reporting for the wider review. For work spanning several shifts, read Why corrective actions become overdue. The best handover gives the incoming team a clear starting position and a reliable route to the details behind it.