ROV Best Practices for Offshore Inspection
A field-tested framework covering pre-dive planning, deployment protocols, data acquisition standards, and reporting — built for ROV supervisors, inspection engineers, and offshore asset managers.
Why Best Practices Matter
Remotely operated vehicles have transformed subsea inspection — but the quality of an ROV inspection is only as good as the processes behind it. Poor pre-dive planning, inconsistent data acquisition, and unstructured reporting lead to missed anomalies, rework, and costly re-mobilisations.
This guide consolidates field-tested protocols used across hull surveys, pipeline inspections, and offshore platform assessments. Whether you are an ROV supervisor preparing for a first deployment or an asset manager reviewing your inspection programme, these practices will help you get more from every dive.
Pre-Dive Planning
Thorough planning before the ROV enters the water is the single highest-leverage activity in any inspection programme. Rushed or incomplete planning is the root cause of most inspection failures.
Define the inspection scope in writing
A written scope document should specify the asset, inspection type (visual, CP, thickness, sonar), coverage requirements, and any anomaly thresholds that trigger immediate reporting. Verbal scopes lead to gaps and disputes.
Review as-built drawings and previous inspection records
Cross-reference the current inspection scope against as-built drawings and the anomaly register from the last inspection. Identify areas of known concern and ensure the dive plan addresses them explicitly.
Confirm equipment configuration against scope requirements
Match the ROV payload to the scope. A visual-only survey requires different tooling than a CP survey with thickness measurement. Confirm camera resolution, lighting configuration, and sensor calibration certificates before mobilisation.
Assess environmental conditions and operational limits
Review current and forecast metocean data. Establish go/no-go thresholds for current speed, visibility, and sea state. Document these thresholds in the dive plan — do not rely on on-the-day judgement calls.
Brief the full team before every dive
A pre-dive toolbox talk should cover scope, hazards, communication protocols, and emergency procedures. Every team member — pilot, supervisor, data logger, and deck crew — should be able to state the dive objectives.
Deployment Protocols
Consistent deployment procedures protect the ROV, the asset, and the data. Deviations from protocol during launch and recovery are a leading cause of equipment damage and data loss.
Complete a full pre-deployment systems check
Run through the manufacturer's pre-deployment checklist without shortcuts. Verify thruster response, camera feeds, sensor readings, tether integrity, and emergency recovery systems. Log the check with a timestamp.
Establish and test communications before launch
Confirm two-way communication between the ROV pilot, deck supervisor, and vessel bridge before the ROV leaves the deck. Test the emergency stop and recovery signal. Never launch without confirmed comms.
Control descent rate and approach speed
Rapid descent in poor visibility risks collision with the asset. Approach the structure at reduced speed, using sonar to confirm position before visual contact. Establish a reference point before beginning systematic coverage.
Maintain consistent standoff distance
For visual inspection, maintain a standoff distance that keeps the full inspection surface in frame without distortion. For CP surveys, follow the probe manufacturer's specified contact or proximity protocol precisely.
Data Acquisition Standards
Data quality determines the value of an inspection. High-resolution video and accurate sensor readings are worthless if they cannot be located, timestamped, or correlated with the asset geometry.
Record continuous, uninterrupted video for all inspection passes
Do not stop and restart recording between areas of interest. Continuous recording preserves context and allows reviewers to assess coverage completeness. Label recording files with dive number, date, and area before archiving.
Geo-reference all data to the asset coordinate system
Every video frame, sensor reading, and anomaly position should be referenced to a consistent coordinate system tied to the asset. Use the as-built drawing grid where available. Undated, unlocated data has no engineering value.
Log anomalies in real time during the dive
The data logger should record anomaly observations as they occur, not from memory after the dive. Each log entry should include timestamp, video timecode, position reference, anomaly type, and estimated dimensions.
Capture still images for all anomalies
For every anomaly logged, capture at least two still images: one contextual (showing the anomaly in relation to surrounding structure) and one close-up. Include a scale reference where possible.
Verify sensor calibration status before and after the dive
CP probes, thickness gauges, and sonar systems should be calibrated to a traceable standard before deployment. Record calibration certificate numbers in the dive log. Post-dive verification confirms data integrity.
Reporting & Deliverables
A well-structured report transforms raw inspection data into actionable engineering intelligence. Reports that are unclear, incomplete, or poorly organised delay decisions and erode client confidence.
Use a standardised report template
Consistent report structure allows clients and class surveyors to locate information quickly. At minimum, include: executive summary, scope confirmation, methodology, findings register, anomaly details with images, recommendations, and appendices.
Classify anomalies by severity and urgency
Every anomaly should be assigned a severity classification (e.g. Critical / Major / Minor / Observation) and an action recommendation (Immediate / Next Scheduled Maintenance / Monitor / No Action). Unclassified findings force clients to make engineering judgements without context.
Include a comparison with previous inspection findings
Where previous inspection records exist, compare current findings against the historical anomaly register. Highlight new anomalies, anomalies that have grown or changed, and anomalies that have been repaired. Trend data is more valuable than a single-point snapshot.
Deliver within the agreed timeline
Late reports delay maintenance planning, regulatory submissions, and insurance renewals. Agree a delivery timeline at the start of the project and flag any risks to that timeline as early as possible — not on the due date.
Interactive Checklist
Pre-Dive Checklist
A condensed field reference covering the critical checks before every ROV deployment.
Planning
Equipment
Communications
Data & Reporting
Need Expert ROV Inspection Support?
Coregent Robotics provides ROV inspection services across hull surveys, subsea pipelines, and offshore platforms. Our teams operate to the standards described in this guide.
Request an Inspection Quote