The Shift Change Handoff

Every agency has a moment where responsibility changes hands. A crew comes off duty and another crew takes over. A unit goes back in service and a different unit picks up the district. A watch ends and the next one starts. In that moment, everything the outgoing crew knows has to become everything the incoming crew knows, and it has to happen fast, usually in the middle of other work.
That moment is the handoff. It is one of the highest-risk points in public safety operations, and most agencies handle it the same informal way they handle everything else: verbally, from memory, whenever there happens to be time.
I have seen out-of-service equipment get missed at shift change because the person who wrote it on a whiteboard three days earlier was not the person working the handoff, and nobody carried it forward. I have seen a hospital diversion notice sit unmentioned because the outgoing crew assumed the incoming crew already knew. None of that is a training failure. It is a structure failure. The information existed. It simply did not survive the handoff.
Why the Handoff Is Where Information Dies
The handoff fails for a boring reason: it depends entirely on a person remembering to say something, at the exact moment they are also getting off shift, packing up, and thinking about going home. Fatigue, timing and distraction all work against it.
It also fails because nobody has agreed on what a complete handoff actually includes. Ask five members what belongs in a shift change report and you will get five different answers. One mentions apparatus status. Another mentions open issues with a piece of equipment. A third assumes personnel notes are covered somewhere else. When the content of a handoff depends on who happens to be doing it, some of it will always be missing, and nobody will know which part until it matters.
And the handoff usually happens once, verbally, with no record. If the incoming crew forgets something they were told twenty minutes into their shift, there is nothing to check it against.
Build a Handoff That Does Not Depend on Memory
A reliable handoff has a fixed shape. It covers the same categories every time, in the same order, regardless of who is running it or how busy the day has been.
At minimum, that means:
- Unit and apparatus status. What is in service, what is out of service, and why.
- Equipment and inventory issues. Anything damaged, missing, low on supply or flagged for repair.
- Operational notices. Hospital diversions, road closures, active hazards, anything affecting how the next crew will respond.
- Open issues. Anything unresolved from the outgoing shift that the incoming shift needs to pick up, whether that is a maintenance request, a pending call-back or an unfinished report.
- Personnel notes. Who is on light duty, who is out, who is new and needs extra attention during their first weeks.
The specific categories matter less than the fact that they are fixed. A handoff built around a checklist, whether that checklist lives on paper, in a log, or in a shared system, does not rely on anyone's memory of what to mention. It relies on the list.
Write It Down Somewhere Both Crews Can See
Verbal handoffs disappear the moment the conversation ends. A written record, even a short one, gives the incoming crew something to check against later in the shift, and it gives the next outgoing crew a starting point instead of a blank page.
This does not need to be elaborate. A shared log that both crews can see, whether it is a physical binder at the desk or a digital log accessible from a phone, is enough. What matters is that it persists past the conversation and that someone did not have to be standing there to receive it.
It also creates something a whiteboard cannot: a record you can go back to. If a piece of equipment turns out to have been out of service for three shifts running, a written handoff log shows exactly when it was first reported and by whom. A verbal handoff gives you nothing to check.
Make the Handoff Itself Non-Negotiable
A structure only works if it happens every time, not just when the shift is quiet enough to allow it. Busy shift changes, where a crew is coming off a run or dealing with an incident at the exact moment the next crew arrives, are exactly when handoffs get skipped, and exactly when skipping one is most dangerous.
Build the handoff into the actual routine of the shift, not as an optional courtesy at the end of a busy day. That might mean a standing time it happens regardless of call volume, or a rule that the outgoing crew is not off duty until the handoff is complete. The point is to remove the decision of whether to do it fully, since that decision, made under time pressure, will not go your department's way often enough.
How This Looks in Your World
Volunteer fire departments. The handoff here is less about a fixed shift and more about duty crew turnover, where members rotating on and off standby need to know what changed since their last time on duty. Because volunteers are not there daily, the gap between handoffs can be days, not hours, which makes a written log even more important than a verbal one.
EMS agencies. Handoffs happen unit to unit, often mid-shift, and often under time pressure between calls. Diversion status, equipment restocking and vehicle issues need to move cleanly between crews who may only overlap for a few minutes at the ambulance bay.
Career fire departments. The classic 24 or 48-hour shift change is the highest-stakes version of this problem, because a full day or two of activity has to be compressed into a single handoff. Apparatus status, open maintenance issues and personnel notes accumulate over the full cycle and need a structured pass, not a hallway conversation.
Law enforcement. Watch change and roll call carry the same burden with an added layer: active investigations, be-on-the-lookout notices and officer safety information have to move forward accurately, since an incomplete pass-down here can mean the next watch is operating without information that directly affects their safety.
The Handoff Deserves the Same Discipline as the Rest of the Job
Agencies train relentlessly on tactics, protocols and procedures, then leave the moment when responsibility changes hands to whatever gets said in passing. That is backwards. The handoff is not an administrative footnote. It is the point where the next crew inherits everything the last one knew, and everything they did not pass along becomes a gap the new crew is operating with, whether they know it or not.
Fix the handoff and you fix one of the quietest, most common sources of missed information in the whole organization.
Tools for this topic
Free interactive tools to put this into practice.
AssessmentInternal Communications Health Check
BuilderDashboard Content Planner
BuilderCommunication Channel Mapper
Part of the seriesInternal CommunicationsExplore the series Recent posts
All posts →
