The ROV Inspection Data Package — What Belongs in It

Raw data, findings report and reproducibility memo: the three building blocks of a complete ROV inspection handover

Published on 15 Jan 2026 · Updated on 9 Apr 2026

A ROV underwater inspection is only as valuable as its handover. A client who receives a data package after the mission that can be used in an inspection file, an expert report or a maintenance plan without rework gains defensible value. A client who receives only video recordings and a verbal summary has an inspection — but no documentation.

This news entry summarises the three building blocks that every ScanSustain mission delivers as standard.

Block 1: Sorted raw data

The core of every handover is the raw data from the mission. It is chronologically ordered, annotated with timestamp and position reference, and stored in archive-capable standard formats. The raw data package specifically includes:

• HD video of the full inspection route (unedited)
• Targeted stills at damage, finding and reference locations
• Sonar datasets where used (multibeam, side-scan or profile sonar)
• Route and telemetry file with position and time data
• Metadata on sensors, settings and boundary conditions

The client receives the raw data immediately after the mission — before the processed documentation is even prepared. This ensures no information gap if time-critical decisions are needed.

Block 2: Structured findings report

The findings report is the processed layer on top of the raw data. It is structured so it can flow directly into an inspection file, expert report or maintenance plan:

• Assignment and method context (who, when, where, with what)
• Tabular findings overview with position and time reference
• Detail findings per damage or find location with image reference
• Damage classification by agreed schema
• Summary and factual action recommendation

Format and structure are agreed in the briefing with the reviewing body or expert witness — ScanSustain delivers the format the file demands, not its own.

Block 3: Reproducibility memo

The often-overlooked third block is the reproducibility memo. It documents the methodology in enough detail that a follow-up inspection — years later, by different personnel — can traverse the exact same path. It contains:

• Route with reference points, branches and key markers
• Sensor setup and relevant settings
• Documented deviations from the mission plan and their reasons
• Recommended frequency for follow-up surveys

Without this memo, no defensible time series is possible. With it, every single inspection becomes the first data point of a long-term monitoring programme.

Why the three blocks belong together

Each block serves a distinct function: raw data secures evidential value, the findings report secures day-to-day usability, the reproducibility memo secures comparability over years. If any one element is missing, the documentation becomes contestable — or ends as a one-off result without follow-up.

Related content in the knowledge hub

• Documentation Standards for Authorities — guideline
• ROV vs. Diver — why third-party usability matters
• ROV Inspection (service)
• Monitoring & recurring inspection