The Survey Is Not the Bottleneck
Offshore inspection programmes are often discussed in terms of vessel day rates, weather windows, and mobilisation costs. These are real constraints, and they dominate the pre-survey planning conversation. But the vessel returns to port within the planned campaign window. The footage is captured. That part of the project, for all its logistical complexity, closes on schedule.
The reporting phase does not close on schedule. From working with operators in our early-access programme, we consistently see a gap of six to twelve weeks between footage receipt and final report delivery. The survey took days. The report takes months.
We spent time mapping this delay in detail across several North Sea operator programmes, talking to the inspection engineers, asset managers, and contractors involved. The time does not disappear in any single dramatic bottleneck. It drains away across a series of small handoffs, queuing events, and sequential dependencies that compound into a months-long delay.
Step 1: Data Transfer and Queuing
Footage arrives on hard drives or via managed file transfer. For a 20-foundation campaign generating 200 hours of footage, data volume is typically 8 to 15 terabytes depending on recording format and resolution. Transfer from the vessel operator to the inspection contractor, and then from the contractor to the reviewing engineer, takes time. In practice, this step often introduces a one-week delay before any review work begins, and sometimes longer when transfer logistics or connectivity issues intervene.
More significantly, the footage sits in a queue. Inspection contractors manage multiple active programmes simultaneously. An engineer who finished their previous review last Wednesday may not begin the new programme until a Monday scheduling slot opens. The footage is ready; the reviewer is occupied elsewhere. This queuing delay is invisible in the project timeline unless someone is explicitly tracking it. In our experience, it accounts for one to two weeks of elapsed time on average.
Step 2: Manual Video Review
Once review begins, the pace is determined by the footage volume and the reviewer's available hours per week. A diligent reviewer covering 200 hours of footage, working on it between other project commitments, typically completes the review over two to three weeks of calendar time even if the active review hours would fit into a single work week. Review is rarely the sole assignment.
The output of manual review is an anomaly log: a spreadsheet or document listing each finding with foundation reference, zone code, defect type, severity assessment, and frame reference. The quality of this log varies considerably based on the reviewer's systematic practice and the time pressure they are under. When review is rushed, frame references become approximate, zone codes are less precise, and borderline findings are either omitted or logged without the detail needed for downstream classification.
Log quality problems compound at the report assembly stage. A vague anomaly log entry requires the report writer to go back to the footage for clarification. That back-and-forth is one of the underappreciated hidden delays in the reporting chain: it creates unplanned rework cycles that extend the elapsed time well beyond what the nominal review duration would suggest.
Step 3: Report Assembly
Report assembly is structurally distinct from footage review, and in many programmes it is performed by a different person. The reviewing engineer produces the anomaly log; a senior engineer or project manager assembles the compliance report from that log. This handoff introduces its own delay, often a week or more, as the report writer is scheduled into the project at a point determined by the reviewing engineer completing their work.
The assembly step involves: converting anomaly log entries into structured finding records with the correct condition codes for the applicable classification society or regulatory framework, organising findings by foundation and zone, cross-referencing against prior survey records where they are available, drafting condition summaries, assembling the photographic evidence log, and writing the overall compliance statement. For a 25-foundation programme, this is two to three days of focused work from an experienced engineer, assuming the anomaly log is clean and well-referenced. When the log requires clarification, the assembly step can stretch considerably longer.
Draft reports go through internal quality review before submission. In most contractor workflows, this means a senior reviewer checking the report for consistency, completeness, and appropriate condition classifications. If revisions are required, the report returns to the assembler. A single revision cycle adds three to five business days to elapsed time. Two revision cycles are not unusual on a complex programme.
Step 4: Client Review and Acceptance
The client, typically the offshore operator's asset integrity team, reviews the delivered report and accepts it or requests clarifications. On straightforward programmes with a clean findings profile, this step closes in a week. On programmes with significant findings or condition ratings that require additional supporting evidence, the clarification exchange can extend for several weeks.
The operator's asset integrity engineer reviewing the report may be encountering the programme data for the first time at this stage. If they have questions about specific findings that require referring back to the original footage, that creates another rework loop: the inspection contractor retrieves the relevant footage, the relevant frame, and provides the supporting clarification. By the time this cycle completes, the elapsed time since vessel return is well past six weeks.
Why the Total Exceeds the Sum of the Parts
Each individual step in this chain is not unreasonably long. A one-week transfer period, a two-week review period, a one-week assembly period, a one-week QA period, a one-week client review period: that is already six weeks, without any rework cycles or queuing delays. Add the queuing delay between steps and a single revision cycle and the total reaches eight to twelve weeks without anyone being particularly slow or negligent.
The problem is structural, not individual. Sequential handoffs with queuing between each step create elapsed time that is much longer than the sum of active working hours. The active working hours for a 200-hour footage programme might be 15 to 20 engineering days total. Spread across a sequential multi-handoff chain, those days translate into six to twelve weeks of calendar time.
What changes this is reducing both the number of handoff steps and the time required for each one. When footage review produces a structured machine-readable anomaly record rather than a variable-quality human log, the assembly step becomes faster and requires fewer rework cycles. When the assembly step can be substantially automated from a structured detection record, the sequential bottleneck shortens. The survey-to-report gap compresses from months to days, not because anyone worked faster, but because the chain has fewer steps and the steps that remain are better supported.
This is not a hypothetical. In the programmes we processed through our early-access pilot, the time from footage receipt to draft report delivery was under 24 hours for the detection and initial draft assembly. The remaining engineering time was in the review, judgement, and sign-off steps that remain appropriately human. Those steps have their own cadence, but they are not extended by the documentation assembly queue. The six-week default becomes a one-to-two-week exception.
