A shift logbook on a 24/7 site isn't a diary, it's the only continuous record of what's actually happening to the plant. Nobody sees the whole operating history in one sitting — each operator only sees their own shift, plus whatever the log tells them about the ones before it. On COMAH sites, CDOIF guidance treats that log as a safety-critical document in its own right, not an administrative nicety. Handwritten, inconsistent, or half-completed entries don't just look untidy, they break the chain of information that keeps a continuous process safe. A digital shift logbook like OxMaint keeps that chain unbroken, shift after shift.
Give Every Shift a Complete, Continuous Record
Structured shift logs with safety-critical status, sign-off accountability, and a retained history built for continuous 24/7 operations.
What CDOIF Expects From a Shift Log
CDOIF guidance on shift handover for high-hazard sites sets a clear bar, and it applies just as much to a control room log as to a face-to-face handover.
Continuity of Information
Every incoming shift should be able to reconstruct the plant's status without relying on memory or a hallway conversation.
Safety-Critical Status
Isolations, overrides, and abnormal conditions need to be unmistakable in the log, not buried in general notes.
Sign-Off Accountability
A named handover, confirmed by both parties, establishes who held responsibility for the plant at every moment.
Legible & Retained
Entries need to be readable and kept for long enough to support any later investigation or COMAH audit.
Core Fields Every Shift Log Needs
| Field | Purpose | Frequency |
|---|---|---|
| Process status & abnormal conditions | Baseline for the incoming shift | Every entry |
| Active isolations & overrides | Prevents duplicate or missed permits | Every entry |
| Open work & follow-up actions | Keeps tasks moving across shifts | As they occur |
| Handover sign-off | Confirms accountability transfer | End of shift |
Where Logbooks Fail COMAH Sites
Free-Text Only
Entries are written in prose with no structure, making safety-critical information easy to miss under pressure.
Illegible or Incomplete
Handwritten logs get abbreviated, rushed, or skipped entirely during a busy or high-pressure shift.
No Central History
Paper logbooks are physically tied to one location, making trend review or audit retrieval slow and manual.
Unconfirmed Handovers
A shift ends without a clear, timestamped confirmation that the incoming operator actually read the log.
Logbook Maturity Levels
Paper & Prose
A handwritten book gets passed along, with content and detail varying heavily by who's writing it.
Digital But Unstructured
Entries move to a digital log, but the format is still free text, so key details can still be missed.
Structured & Continuous
Fixed fields, confirmed sign-offs, and a searchable history give every shift the same complete picture.
The Numbers Behind Shift Continuity
On a continuous process, the shift log is the plant's memory — if it isn't complete, the next shift is effectively starting blind. Sign up free to set up a structured digital shift log for your site, or book a demo to see it working across a live shift change.
Build a Shift Log That Meets COMAH Expectations
Structured fields, safety-critical flags, and confirmed sign-offs — a continuous record built for 24/7, high-hazard operations.
Setting Up a Digital Shift Log
Define the Fixed Fields
Agree the structured fields every entry must include, based on what CDOIF-aligned handovers expect.
Flag Safety-Critical Items
Give isolations, overrides, and abnormal conditions their own visible flag, separate from routine notes.
Require Confirmed Sign-Off
Both outgoing and incoming operators confirm the handover digitally, with a timestamp recorded automatically.
Retain and Make Searchable
Keep the full history centrally, so any shift, incident, or audit review can be pulled up in seconds.
Frequently Asked Questions
What does CDOIF guidance say about shift handover?
CDOIF guidance for high-hazard sites treats shift handover as a safety-critical activity, expecting continuity of information, clear communication of abnormal conditions, and confirmed accountability between shifts.
Do COMAH sites need to retain shift logs for a set period?
Shift logs on COMAH sites are generally expected to be retained and available for regulatory review, though specific retention periods should be confirmed against your site's safety report and internal policy.
Can a digital shift log replace the control room logbook entirely?
Yes, and it typically improves on a paper logbook by making entries structured, searchable, and centrally retained rather than tied to a single physical location.
What's the biggest risk of an unstructured shift log?
Safety-critical information can get lost in free-text notes, meaning the incoming shift may miss an active isolation, override, or abnormal condition that a structured field would have made obvious.
How is a shift logbook different from a handover checklist?
A checklist confirms specific items at the moment of handover, while a shift logbook is the continuous, ongoing record of everything that happened during the shift, which the checklist draws from.
