Shift handover records: who owns an unresolved operating exception?
For Refinery, gas-processing, terminal or upstream operator
TL;DR — what you’ll learn
- **Narrative shift logs drop unresolved exceptions across multi-shift boundaries:** When an abnormal operating condition—such as an inhibited safety alarm, a bypassed custody meter run, a temporary manual control loop override, or an open confined-space isolation—is typed into a free-text shift note on Shift A, it frequently disappears from Shift B's narrative summary if nothing changed during Shift B, leaving Shift C unaware that the exception is still active.
- **Separate persistent exception registers from narrative shift commentary:** Effective shift handover governance treats an unresolved operating exception as a **stateful, carried-forward object** with a unique ID, risk category, named accountable role, explicit incoming-shift acknowledgement, and expiry/escalation timer—never as a one-time diary paragraph.
- **Handover records track ownership and status; they never replace operating procedures:** A shift handover log records *what* abnormal state exists, *who* owns the next verification or restoration step, and *which* approved Permit-to-Work (`PTW`), Management of Change (`MOC`), or Standard Operating Procedure (`SOP`) governs it. The log itself is never a substitute for formal bypass authorisation or operating instructions.
- **Quantify carry-forward leakage across three 8-hour shifts:** In an illustrative `24-hour` (`3 × 8-hour shift`) gas-processing plant scenario tracking `14` active operating exceptions (`6` temporary instrument overrides/inhibits, `4` equipment standby/degraded states, `3` extended isolation permits, and `1` pending off-spec condensate lab re-test), a persistent carry-forward register enforces `100%` incoming shift-lead acknowledgement across all `3` handovers, resolves `9` exceptions with linked verification evidence, escalates `2` overrides breaching the `16-hour` two-shift threshold to the Operations Superintendent, and carries forward `5` open exceptions (`including the 2 escalated items`) into Day 2 with zero silent drop-offs.

Topics: oil and gas shift handover, plant handover log, operating exception ownership, shift log software
Why Unresolved Exceptions Vanish Between Shift A and Shift C
When an abnormal operating condition cannot be restored within the shift that discovered or initiated it, who owns the unresolved exception across subsequent shift handovers, and how should the plant record keep it visible until formal closure?
Direct Answer: Dual ownership applies at every shift boundary: the Incoming Panel / Area Operator and Shift Charge Engineer assume immediate operational custody and monitoring responsibility for the active condition during their tour of duty through explicit line-item acknowledgement, while a designated Technical / Maintenance Action Owner retains resolution accountability when restoration depends on day-shift engineering, maintenance, or laboratory clearance. To prevent silent drop-offs, the handover system must automatically carry forward every unresolved exception as an active, pinned state object across every subsequent shift handover until verified restoration evidence is recorded.
In continuous 24/7 refinery units, gas-processing trains, tank terminals, and offshore production platforms, shift handovers are among the highest-risk operational transitions. Oil Industry Safety Directorate (OISD) safety standards and the Directorate General of Mines Safety (DGMS) Oil Mines Regulations, 2017 emphasise structured communication of abnormal plant conditions, safety-system bypasses, and ongoing maintenance isolations during shift relief (OISD Standards; DGMS Oil Mines Regulations 2017). Furthermore, where operational technology (OT) operator consoles, alarm management historians, and electronic shift logbooks interact, NIST SP 800-82 Rev. 3 highlights the importance of role-authenticated logging, audit trails, and clear boundary separation between supervisory control actions and enterprise administrative records (NIST SP 800-82 Rev. 3).
The classic failure mode in paper logbooks, Word documents, and basic electronic diary forms is second-handover decay:
- Shift A (
06:00–14:00): A wet-gas compressor suction scrubber level transmitter (LT-2104A) exhibits erratic readings during instrument calibration. Under an approved bypass permit (BYP-2026-118), Shift A places the loop on manual monitoring via sight-glass every2 hoursand writes in the Shift A narrative log: "LT-2104A placed on manual bypass under BYP-2026-118; instrument tech awaiting replacement diaphragm." - Shift B (
14:00–22:00): The incoming Shift B operator reads Shift A's note, checks the sight-glass, and focuses their own shift narrative on a separate amine regenerator foaming upset. Because nothing new happened toLT-2104Aduring Shift B, the Shift B operator does not re-type theLT-2104Anote at22:00. - Shift C (
22:00–06:00): The incoming Shift C crew reads only the Shift B summary (14:00–22:00). The active bypass onLT-2104Ais no longer mentioned in the current shift handover text, and the mandatory2-hourmanual sight-glass check is missed on the night shift.
Narrative Shift Diaries vs Stateful Exception Handover Registers
Scroll horizontally to see all columns.
| Handover Attribute | Free-Text Narrative Shift Diary | Stateful Carry-Forward Exception Register |
|---|---|---|
| Persistence Across Shifts | Ephemeral; disappears on Shift B or Shift C unless manually copy-pasted by every outgoing operator | Automatically pinned to the active handover workspace across every shift until formally closed with verification evidence |
| Ownership Model | Ambiguous ("Maintenance informed" or "Next shift to check") | Dual-tagged: (1) Active Shift Custody Owner (incoming operator/shift lead) + (2) Resolution Action Owner (named engineering/maintenance/lab role) |
| Incoming Relief Sign-Off | Single bulk signature at the bottom of a multi-page shift summary | Explicit item-by-item acknowledgement required for high-consequence exceptions (inhibits, overrides, temporary isolations) |
Relationship to PTW / MOC / Bypass Authority |
Informal notes sometimes misused as operating instructions ("Run pump with trip jumpered") | Strict cross-reference to authorised PTW, MOC, or Bypass Certificate ID; blocks creation of an override exception without a valid authority reference |
| Ageing & Escalation | No ageing counter; temporary workarounds silently become permanent plant norms | Automated shift-count timer (Shift 1, Shift 2, Shift 3+) triggering Shift Superintendent / Operations Manager review when threshold is exceeded |
Arithmetic check: Every exception across CAT-OVD Overrides/Inhibits (6), CAT-EQP Degraded Standby Equipment (4), CAT-PTW Extended Isolations (3), and CAT-QLT Pending Lab Holds (1) is conserved across all three relief boundaries.
Governance Boundary: What a Shift Handover Log Must Never Do
Before designing or configuring a shift handover exception workflow, operating companies must enforce a strict safety and regulatory boundary:
Operational Safety Boundary: A shift handover log records the existence, current status, monitoring cadence, and ownership of an operating exception. It is never an authorisation mechanism. Entering a note in a shift handover log does not authorise a safety instrumented system (
SIS) bypass, an alarm inhibit, a mechanical isolation, or a deviation from safe operating envelopes. Every safety-critical exception recorded in the handover log must reference an active, independently approved Permit-to-Work (PTW), Bypass/Override Certificate, Temporary Management of Change (TMOC), or approved Standard Operating Procedure (SOP).
Three-Shift Exception Lifecycle and Escalation Workflow
- 1. Log structured exception in active shift registerRecord inhibited alarms, temporary bypasses, degraded equipment loops, and open permits with tag ID, hazard control, and expiry timer rather than free-text diary prose.
- 2. Conduct joint outgoing-incoming relief walkthroughOutgoing and incoming operators verify each open exception on the console and field panel; incoming operator explicitly accepts or flags disputed items at handover sign-off.
- 3. Auto-carry unresolved exceptions into incoming shift queueAny exception not backed by a verified restoration record automatically persists on the incoming shift active board and escalates when approaching its governance limit.
- 4. Close only on verified field restoration evidenceRemove an exception from the carry-forward register only when normal tag state, de-isolation confirmation, or CMMS completion reference is recorded.
Safety boundary: A shift handover log tracks operational continuity and exception ownership; it never substitutes for a Permit to Work, LOTO certificate, or formal MOC approval ([O066](O066-permit-record-system-requirements.md), [O065](O065-management-of-change-evidence.md)).
Four Exception Categories Requiring Mandatory Carry-Forward
- Inhibited Alarms, Defeated Interlocks, and Manual Loop Overrides (
CAT-OVD): Any control valve on manual, suppressed nuisance alarm flood, or authorised process bypass. Requires reference to the active Bypass Register ID and intra-shift manual monitoring log. - Degraded or Unavailable Standby Equipment (
CAT-EQP): A critical2 × 100%pump where Pump A is running and standby Pump B is racked out under LOTO (Lockout/Tagout) for seal replacement, leaving the unit with zero auto-start redundancy. - Extended / Suspended Permits and Isolations (
CAT-PTW): Mechanical blinds, electrical isolations, or temporary hoses left in place across shift changes under a suspended or multi-shiftPTW(OISD Standards). - Pending Quality / Custody-Transfer Verification (
CAT-QLT): Off-spec rundown tank holds, bypassed fiscal meter runs operating on check-meter fallback, or pending laboratory re-sample confirmations.
Worked Example: 24-Hour (3-Shift) Exception Handover Reconciliation at a Gas Plant
Illustrative Scenario Scope: The following worked example models a
24-houroperating day (Gas Day 2026-10-18, divided intoShift A: 06:00–14:00,Shift B: 14:00–22:00, andShift C: 22:00–06:00) at an illustrative onshore gas-processing facility (Unit-GPP-Train-2). All exception counts, timestamps, and escalation thresholds (16 hours / 2 shiftsfor temporary overrides) are illustrative configuration parameters; actual bypass limits and shift-relief procedures must follow site-specificOISD/DGMSsafety management manuals.
Scenario Inputs Across the Three Shifts
Across the 24-hour cycle, Unit-GPP-Train-2 manages 14 total operating exceptions:
- Carried in at
06:00(Start of Shift A):5active exceptions from the prior night shift. - Newly opened during Shift A (
06:00–14:00):5new exceptions (total active pool during Shift A =10). - Newly opened during Shift B (
14:00–22:00):3new exceptions. - Newly opened during Shift C (
22:00–06:00):1new exception. - Total Distinct Exceptions Tracked Over 24 Hours:
5 + 5 + 3 + 1 = 14 exceptions.
Category Breakdown of the 14 Exceptions
CAT-OVD(Temporary Instrument Overrides / Alarm Inhibits):6 exceptions(configured escalation threshold: max2 consecutive shifts / 16 hourswithout Operations Superintendent re-authorisation).CAT-EQP(Standby Equipment Out-of-Service / Degraded Redundancy):4 exceptions(configured escalation threshold:3 shifts / 24 hours).CAT-PTW(Multi-Shift Mechanical / Electrical Isolations):3 exceptions(governed by physical LOTO register andPTWvalidity window).CAT-QLT(Pending Off-Spec Condensate Rundown Lab Re-Test):1 exception(configured escalation threshold:1 shift / 8 hours).
Shift-by-Shift Carry-Forward and Resolution Arithmetic
Shift A (
06:00–14:00):- Opening Carried-In:
5exceptions. - New Opened on Shift A:
5exceptions. - Gross Active on Shift A:
5 + 5 = 10exceptions. - Verified & Closed on Shift A:
4exceptions (day-shift instrument technicians restore2CAT-OVDtransmitters; maintenance returns1standby glycol pumpCAT-EQPto auto-standby; lab clears1CAT-QLTcondensate tank rundown after re-test). - Carried Forward at
14:00Handover (Shift A → Shift B):Shift A Carry-Forward = 10 − 4 = 6 exceptions - Acknowledgement Check at
14:00: Incoming Shift B Charge Engineer and Panel Operator individually acknowledge all6carried-forward items (6 / 6 = 100.0%).
- Opening Carried-In:
Shift B (
14:00–22:00):- Opening Carried-In from Shift A:
6exceptions. - New Opened on Shift B:
3exceptions (2CAT-OVDmanual valve overrides +1CAT-EQPfin-fan cooler vibration trip). - Gross Active on Shift B:
6 + 3 = 9exceptions. - Verified & Closed on Shift B:
3exceptions (1CAT-OVDoverride restored +2CAT-PTWisolation permits de-isolated and box-up signed). - Carried Forward at
22:00Handover (Shift B → Shift C):Shift B Carry-Forward = 9 − 3 = 6 exceptions - Ageing & Escalation Check at
22:00: Among the6items carried into Shift C,2CAT-OVDexceptions (EX-2026-104on wet-gas scrubber levelLT-2104AandEX-2026-107on flare knockout drum high-level alarm suppress) have now remained open across two full 8-hour shifts (16.0 hours). The register automatically flags both items asESCALATED — >16h Override Thresholdand routes a mandatory re-validation alert to the Operations Superintendent while keeping custody pinned to the Shift C Panel Operator.
- Opening Carried-In from Shift A:
Shift C (
22:00–06:00):- Opening Carried-In from Shift B:
6exceptions (including 2 escalated CAT-OVD items). - New Opened on Shift C:
1exception (1CAT-EQPinstrument air dryer switching valve fault). - Gross Active on Shift C:
6 + 1 = 7exceptions. - Verified & Closed on Shift C:
2exceptions (1CAT-OVDmanual loop restored after midnight process stabilisation +1CAT-EQPfin-fan reset verified). - Carried Forward at
06:00Next-Day Handover (Shift C → Day 2 Shift A):Shift C Carry-Forward to Day 2 = 7 − 2 = 5 exceptions
- Opening Carried-In from Shift B:
24-Hour Exception Reconciliation Ledger (Unit-GPP-Train-2)
Scroll horizontally to see all columns.
| Shift Window | Opening Carried-In | Newly Opened in Shift | Gross Active in Shift | Closed with Verified Evidence | Carried Forward at Handover | Escalated (>16h Override Rule) |
Unacknowledged / Dropped Items |
|---|---|---|---|---|---|---|---|
Shift A (06:00–14:00) |
5 |
5 |
10 |
4 |
6 |
0 |
0 |
Shift B (14:00–22:00) |
6 |
3 |
9 |
3 |
6 |
2 (EX-2026-104, EX-2026-107) |
0 |
Shift C (22:00–06:00) |
6 |
1 |
7 |
2 |
5 |
2 (Active escalated into Day 2) |
0 |
| 24-Hour Cumulative Summary | 5 (Start) |
9 (New) |
14 (Total Distinct) |
9 (64.29% Closed) |
5 (35.71% Open End) |
2 Escalated Overrides |
0 Silent Drop-Offs |
Verification Check:
Opening Pool (5) + Total New Opened (5 + 3 + 1 = 9) − Total Verified Closed (4 + 3 + 2 = 9) = Closing Carried Forward (5)
Ownership Matrix and Exception Closure Rules
Scroll horizontally to see all columns.
| Exception State | Shift Custody Owner (24/7 Operational Control) | Resolution Action Owner (Technical / Support) | Mandatory Evidence to Close Exception |
|---|---|---|---|
Open — Standard (< 16h / < 2 Shifts) |
Active Area / Panel Operator (acknowledged at shift relief) | Assigned Instrument, Mechanical, Electrical, or Lab Lead | Linked Work Order completion, PTW de-isolation signature, or DCS tag return-to-AUTO timestamp |
Open — Escalated (>= 16h Override / Inhibit) |
Incoming Shift Charge Engineer + Panel Operator | Area Maintenance Lead + Operations Superintendent (Risk Re-validation) | Superintendent extension sign-off + verified intra-shift manual check readings; closed only upon loop/interlock restoration test |
| Disputed / Unclear Status at Handover | Outgoing & Incoming Shift Charge Engineers jointly | Operations Superintendent | Joint control-room/field walkdown verification before outgoing shift lead departs site |
Observable Acceptance Tests for Shift Handover Systems
To verify that an electronic shift handover module or structured control-room register prevents exception drop-offs, execute these three acceptance tests:
- Test
ACT-O023-01(Zero Copy-Paste Persistence Test): Create an active operating exception (CAT-OVD) during Shift A, complete the Shift A → Shift B handover without editing the exception text during Shift B, and generate the Shift B → Shift C handover pack. Pass Criteria: The unresolved exception automatically appears at the top of the Shift B → Shift C handover screen with an updated elapsed-time counter (16h / 2 Shifts) even though the Shift B operator added zero free-text narrative notes. - Test
ACT-O023-02(Unauthorised Override Entry Block): Attempt to log aCAT-OVDsafety alarm inhibit or interlock bypass exception in the handover register while leaving theAuthorised Bypass / PTW Reference IDfield blank. Pass Criteria: The workflow rejects the entry or flags it immediately as anUnauthorised Control Exceptionrequiring immediate Shift Charge Engineer intervention, preventing the handover log from acting as an informal bypass permit. - Test
ACT-O023-03(Verification-Gated Closure Audit): Attempt to change an openCAT-EQPorCAT-PTWexception status toClosed / Normalwithout recording the restoration timestamp, de-isolation certificate reference, or incoming operator verification sign-off. Pass Criteria: The system blocks closure and retains the item inOpen — Carry Forwardstatus until the mandatory restoration evidence fields are populated.
Summary and next actions
To eliminate silent drop-offs of unresolved operating exceptions across shift changes, execute these four numbered actions:
- Separate the Exception Register from Narrative Shift Notes (Days 1–10): Redesign the control-room handover template so that unresolved overrides, standby equipment outages, multi-shift isolations, and pending quality holds live in a persistent, structured Carried-Forward Exception Table above the general shift diary commentary.
- Assign Dual Ownership to Every Carried-Forward Line (Days 11–20): Require every open exception to display both the Active Shift Custody Role (the incoming panel or field operator monitoring the condition during the shift) and the Resolution Action Owner (the maintenance, instrument, or engineering role responsible for permanent restoration).
- Enforce Mandatory Authority References and Ageing Escalation Timers (Days 21–35): Configure hard validation linking every
CAT-OVDandCAT-PTWexception to an active Bypass Certificate orPTWnumber, and set automated shift-count escalation rules (such as> 2 shifts / 16 hoursfor temporary overrides) that notify the Operations Superintendent. - Audit Three Consecutive 24-Hour Handover Cycles (Days 36–45): Sample
3 consecutive days(9 shift handovers) across one process unit, reconcile every opened exception against verified restoration evidence (Opening + New − Closed = Closing), and confirm zero exceptions vanished between Shift A and Shift C without documented closure.
Evaluate the next handover
Production accounting reconciliation: keep corrections traceable
References
Sources checked 15 October 2026. Vendor examples retain their stated release scope. Catalogue entries do not replace the full applicable standards.
- Oil Industry Safety Directorate (OISD) — OISD Safety Standards for Process Operations, Work Permit Systems, and Shift Handover Practices, Ministry of Petroleum and Natural Gas, Government of India (
S03): https://oisd.gov.in/oisd-standards - Directorate General of Mines Safety (DGMS) — The Oil Mines Regulations, 2017 (statutory shift charge and operational record obligations) (
S10): https://www.dgms.gov.in/writereaddata/UploadFile/The_Oil_Mines_Regulation_2017.pdf - National Institute of Standards and Technology (NIST) — NIST Special Publication 800-82 Rev. 3: Guide to Operational Technology (OT) Security (access control, audit logging, and operational boundary integrity) (
S23): https://csrc.nist.gov/pubs/sp/800/82/r3/final
