What Is Shift Handover?

Back to Blog

What a Handover Communicates

A complete handover covers the state of the process and everything that departs from normal. That includes current operating conditions and rates; any alarms or abnormal conditions active or recently cleared; equipment out of service, bypassed, or on manual; maintenance and work permits open in the field; process changes or operations in progress, such as a tank being filled or a unit being started; and any safety concerns. The outgoing operator also flags things the incoming operator specifically needs to monitor - a level creeping up, a machine behaving oddly on the last round.

Good handover pairs a verbal briefing with written records. The shift log - and the event log and trends - give the incoming operator the objective history, while the face-to-face conversation conveys judgment and context that a log cannot: 'the compressor has been surging intermittently, keep an eye on suction pressure.' Both matter, because writing alone loses nuance and conversation alone loses detail.

Why Handover Is a Safety-Critical Task

Incident investigations across process industries repeatedly identify communication at shift change as a contributing cause. When information is dropped at handover - an isolation not communicated, a running job not mentioned, an abnormal condition glossed over - the incoming operator makes decisions on an incomplete picture. High-profile process safety events have been traced in part to inadequate shift communication, which is why regulators and standards bodies treat handover as a defined, auditable task.

To manage that risk, operations use structured handover: a standard checklist or form ensures the same topics are covered every time, an overlap period lets the two operators walk the plant state together, and the incoming operator is expected to read back and confirm understanding rather than passively receive. In oil and gas control rooms covering wide fields, the shift log, event log, and trends underpin the handover so the oncoming operator can quickly reconstruct what happened across many sites during the shift they missed.

A Handover Sequence That Works

Structure beats good intentions at shift change. A sequence many control rooms converge on:

1. The incoming operator arrives with enough margin to read before talking: shift log first, then the alarm summary and any standing alarms, then trends for the units that ran abnormal.
2. The outgoing operator gives the verbal brief against a fixed checklist, in the same order every time, so omissions show up as skipped lines rather than silent gaps.
3. The pair walk the displays together for anything abnormal - the trend tells the story better than the sentence about it.
4. The incoming operator reads back the critical items: what is out of service, what is bypassed, what must be watched, what is expected to happen next.
5. Responsibility transfers at an explicit, unambiguous moment, and the log records who has the plant.

The read-back step earns its place. Handover failures are rarely about information never spoken; they are about information spoken and not absorbed. Making the incoming operator restate the plant's condition in their own words exposes the difference immediately, while both people are still standing there to fix it.

Where Handover Breaks Down

The known failure patterns are worth naming, because every one of them feels reasonable in the moment. End-of-shift fatigue compresses the brief exactly when the shift was hardest and there is the most to say. Interruptions - a phone call, an alarm mid-brief - cut the checklist short, and nobody returns to the skipped items. A return from days off gets the same brief as a routine change, even though the incoming operator is missing several shifts of context rather than one. Abnormal plant states rush the handover precisely when it deserves double the time. And standing alarms that everyone has normalized never get mentioned at all, so the newcomer inherits them as invisible background.

Regulated pipeline control rooms treat these patterns formally: shift change and fatigue are addressed together in the PHMSA control room management rules on fatigue and shift handover, which makes a useful reference model even for operations not under that regulation. The common thread is that handover quality is something you design and audit, not a courtesy between colleagues.

Handover Without a Shared Control Room

In remote oil and gas operations the two operators often never stand at the same console. A field operator hands to the next by phone at the end of a hitch, or coverage passes from a day operator to an on-call rotation overnight. The same information still has to move; it just loses the walk-the-displays step and the body language that flags an unconvincing 'it's fine'. That raises the weight carried by the written record: a structured log the next person can read cold becomes the primary channel rather than a backup to conversation, which is the case for keeping it in a searchable system - see the electronic shift logbook - rather than a paper book at a site nobody is standing at.

On-call transitions deserve the same discipline as shift changes, because they are shift changes - the plant does not distinguish between an operator going home and a shift ending. Whoever picks up the phone at 02:00 needs the same picture the day operator had: what is down, what is bypassed, what was creeping. The mechanics of passing that baton cleanly are covered under on-call shift handoff.

Frequently Asked Questions