ROV Shift Handover Guide: What New Pilots Need to Know About Offshore Crew Changes

Most offshore incidents that involve ROV operations don't happen at the start of a project. They happen during crew handovers — when information doesn't transfer cleanly, when the incoming team inherits an equipment issue they didn't know about, or when an ongoing anomaly gets lost in the shift change.

Why Handovers Fail

A shift handover fails when it relies entirely on verbal communication. Verbal transfers are fast and feel complete, but they depend on both parties being alert, unrushed, and focused — conditions that rarely exist at the end of a 12-hour shift offshore. Critical details get compressed, omitted, or simply forgotten.

What a Complete Handover Must Cover

• Operational status: what was completed, what's in progress, what's deferred
• Equipment status: any faults, ongoing anomalies, or components that need monitoring
• Outstanding maintenance: anything flagged during the shift that needs follow-up
• Environmental and weather conditions and how they affected operations
• Client communication: any instructions, change requests, or issues raised
• Safety observations: near misses, hazards identified, anything the incoming team needs to be aware of
• Next planned dives: objectives, sequence, any preparation required

Written Notes Are Non-Negotiable

Every handover point should be written down before the verbal handover happens, not instead of it. The written note is the record — it's what exists when memories differ about what was communicated. It's also the audit trail if something goes wrong.

The Anomaly Flag System

Any situation that isn't normal should be explicitly flagged as an anomaly in the shift note. Not buried in narrative text — flagged, so it appears at the top of the incoming supervisor's attention. This includes:

• Equipment behaving differently than expected, even if still within operational limits
• Near-miss events or safety observations
• Any deviation from the planned dive program
• Client or project manager concerns raised during the shift
• Environmental conditions that caused operational limitations

Running the Handover Meeting

A good handover meeting follows a consistent structure — the same order every time, so nothing gets skipped:

• Outgoing supervisor presents written shift note to incoming supervisor
• Walk through each section: operations, equipment, maintenance, client, safety
• Incoming supervisor asks questions — any ambiguity resolved before outgoing leaves
• Incoming supervisor signs the shift note to acknowledge receipt
• Outgoing supervisor remains contactable for a defined period after handover

Digital Shift Notes

A structured digital shift note — like those in ThrusterLog — solves the blank-page problem. The fields guide what information needs to be included. Anomaly flags are a dedicated field, not an afterthought. The incoming supervisor can review the note before the verbal handover, arriving at the conversation informed rather than starting from zero.