Shift Handover Guide

What every handover must cover: equipment status, active alarms, permits to work, safety isolations, and pending actions. Checklists for outgoing and incoming operators, quality score breakdown, and regulatory context.

A shift handover is the most safety-critical communication in a plant. This guide defines what every Capped AI handover must cover, what both operators must do before the shift changes hands, and how Capped AI's quality score is calculated. Reference this guide during operator onboarding and after any handover-related incident.

Why handovers fail

Industry incident data consistently points to three failure modes: missing context (the outgoing operator knew something but did not write it down), ignored detail (the incoming operator skimmed the handover under time pressure), and unsigned transfer (no formal acknowledgment that the incoming operator accepted the shift). Capped AI's structure and quality score are designed to close all three.

Anatomy of a Capped AI handover

Every signed Capped AI handover contains the following sections, generated from DCS data and your voice notes:

Section	Source	Required
Shift summary	AI from DCS + operator voice notes	Yes
Active alarms at handover	DCS historian (live snapshot)	Yes
Alarm events during shift	DCS historian (time-series)	Yes
Key process values (trend)	DCS historian (tag list)	Yes
Permits to work (PTW) status	Operator voice note or manual entry	If any open
Safety isolations (LOTO)	Operator voice note or manual entry	If any active
Pending actions for incoming shift	AI extraction + operator confirmation	If any
Equipment abnormalities	Alarm analysis + voice notes	If any
Operator narrative	Voice transcription	Recommended
Outgoing operator signature	Digital PIN	Yes
Incoming operator signature	Digital PIN	Yes

Outgoing operator checklist

Complete this before tapping Sign & Submit:

Start the session 20 minutes before shift end

Open Capped AI, select your unit and shift, and tap New Handover. Starting early gives you time to review the draft and add voice notes before your relief arrives.

Record your voice narrative

Walk through anything the DCS cannot tell the incoming shift: verbal instructions from the superintendent, intermittent issues that cleared before logging, contractor activities, and anything you personally observed. Speak for at least 60 seconds. A typical good handover narrative is 2–4 minutes.

Declare all open permits to work

For every active PTW, say the permit number, the job description, the area, and whether the job is ongoing or suspended. Example:

"PTW-2024-0118 — hot work on heat exchanger E-301, Unit 3.
Suspended at 22:00. Job resumes day shift. Scaffold still in place."

Declare all active safety isolations

List every Lock-Out / Tag-Out (LOTO) or valve isolation that is currently in place. State the equipment, the isolation point, and the lock owner. The incoming shift must not inadvertently reinstate isolated equipment.

List pending actions explicitly

Say “pending action:” before each item you are handing over. Capped AI will extract these into the Pending Actions section automatically. Example:

"Pending action: call instrument technician for flow transmitter FT-205 calibration check.
Pending action: chase maintenance for P-201 vibration report — due before next day shift."

Review the AI draft

Read every section. Pay particular attention to: the alarm event list (check for anything Capped AI may have de-prioritised that was actually significant), the pending actions list (make sure all items you mentioned are captured), and the key process values (check that the trend directions match what you saw during the shift).

Sign

Tap Sign & Submit and enter your PIN. Signing means you attest that the handover is accurate and complete to the best of your knowledge. You cannot edit it after signing.

Incoming operator checklist

Read the full handover before accepting the shift

Do not sign until you have read every section. Ask the outgoing operator to clarify anything that is unclear — while they are still physically present in the plant.

Check active alarms

Verify that the alarms shown in the “Active alarms at handover” section match what you see on the DCS screens. If there is a discrepancy, resolve it before signing.

Confirm open PTWs and LOTOs

Walk to the permit board (or check your plant's PTW system) and verify every isolation listed in the handover. Any isolated equipment is your responsibility from the moment you sign.

Accept the pending actions

Read each pending action. If you cannot action something in this shift, add a voice note on the same handover (using the Addendum feature) so it stays visible to the next relief.

Sign the incoming acknowledgment

Tap Sign as Incoming Operator and enter your PIN. This records your name, the timestamp, and your acknowledgment of the shift status. The shift transfer is now complete.

Face-to-face walkthrough

For high-hazard units (reactors, high-pressure systems, H₂S service, fired heaters), the incoming operator should physically walk the unit with the outgoing operator before signing. Capped AI does not replace this walkthrough — it gives both operators a shared, accurate reference to discuss during the walk.

After the walkthrough, add a brief voice addendum confirming the walk occurred and any additional observations:

"Handover walkthrough complete with Ahmed Al-Rashid at 06:05.
Unit 2 visually normal. Confirmed P-201 vibration — still running within limits.
No additional items beyond handover."

Quality score

Every signed handover receives a quality score (0–100) displayed in the handover list and on the manager dashboard. The score is calculated from:

Component	Weight	What it measures
Voice narrative length	25%	≥ 90 seconds of operator commentary
Pending actions declared	20%	At least one pending action if any alarms are unresolved
PTW / LOTO completeness	20%	All open permits declared if any are active in the PTW system
Incoming signature	20%	Incoming operator signed within 30 minutes of outgoing signature
Alarm coverage	15%	AI confirmed it addressed all HIGH and CRITICAL alarms in the narrative

A score below 60 triggers a yellow flag on the manager dashboard. A score below 40 triggers an amber alert and sends a notification to the shift supervisor. Quality scores are visible to your supervisor and plant manager — they are not punitive but are used to identify training gaps and systemic issues.

What must never be omitted

The following items are mandatory in every handover regardless of how quiet the shift was. A handover that omits any of these is incomplete and should not be signed by the incoming operator.

Any HIGH or CRITICAL alarm active at shift end — even if it has been acknowledged and is being monitored
All open permits to work — including suspended jobs
All active safety isolations — LOTO, blinded flanges, closed block valves for safety purposes
Any abnormal equipment condition — even if the decision was made to continue operating
Any deferred maintenance — equipment flagged for repair but not yet taken out of service
Safety override or bypass in effect — any SIS or safety instrument in manual or bypassed state

Adding an addendum after signing

If you need to add information after a handover is signed (for example, the incoming operator discovers something during the walkthrough), use the Addendum feature:

Open the signed handover from the handover list
Tap Add Addendum
Record a voice note or type the additional information
Sign the addendum with your PIN

Addenda are appended to the original handover and are visible to managers. The original signed handover is not modified.

Regulatory context

Shift handover procedures in the GCC petrochemical sector are governed by plant safety management systems aligned to IEC 61511 (functional safety for SIS), OSHA Process Safety Management (PSM) equivalents, and individual company HSE standards. Capped AI's handover structure is designed to meet the documentation requirements of these frameworks.

The tamper-proof audit log produced by Capped AI satisfies the record-keeping requirements for process safety management incident investigations. For regulatory queries, contact hello@capped.ai.

Back to Docs