Spreadsheets vs evidence-based oversight: why the fleet's paper habits keep failing it

Walk into any technical office and ask to see the condition of a vessel — not the certificates, the condition. What usually appears is an Excel sheet somebody maintains by hand, a folder of PDF survey reports, a photo album on someone’s phone, and a chief engineer’s email from two weeks ago. Every one of those artefacts took real work to produce. Almost none of that work is still usable a month later.

I spent years producing those artefacts myself. The handover notes typed at midnight before a flight home. The defect list that lived in a notebook until it could be typed into a form nobody downstream ever queried. The survey report that arrived as a flat PDF, was read once, and went to rest in a shared drive. The work was real; the record it left behind was almost unusable. This article is a task-by-task comparison of that way of working against what has started replacing it — call it evidence-based oversight: the vessel’s own observations, photographs and reports captured in a structured form that can be searched, compared and acted on. It is one category inside a wider field — our guide to what maritime technology covers sets out the others.

The comparison, task by task

The task	The paper-and-spreadsheet way	The evidence-based way
A defect is spotted on rounds	Noted on a form; typed up later if time allows; the office learns of it only by email	Captured once as a structured observation — location, system, severity — dated and visible to everyone who should see it
A survey report arrives	A flat PDF in an inbox; findings retyped into a tracker by hand, or not at all	Findings sit alongside the vessel’s other evidence, comparable with what the crew reported before and after
Crew handover	Written under time pressure; covers what the outgoing officer remembered to write	The record does not leave with the person — the handover note points into a file that already exists
Preparing for vetting or PSC	A sprint through folders and inboxes in the weeks before the window	A review of a record that already exists; the gaps announce themselves early
The office’s view of vessel condition	Assembled on request from calls, emails and the freshest spreadsheet	A current, structured view per vessel; the fleet summary is a report, not a research task
A senior engineer retires	Their unwritten knowledge of the ship leaves at the gangway	The judgement leaves — the evidence trail of what they saw, flagged and fixed stays with the vessel

The pattern across every row is the same. The analog way does not lack information — ships generate observations all day long. It lacks retention and structure: each piece of evidence exists once, in one place, legible to one audience, and decays from the moment it is written. The office ends up managing the fleet through summaries of summaries, and risk is discovered at the moment it becomes expensive — the breakdown, the detention, the failed vetting — rather than at the moment it first became visible to someone on board.

What this costs, concretely

Three of the rows above deserve numbers-free honesty about their cost, because every operator pays them.

The handover. A ship’s continuity is rebuilt from scratch every time a senior officer changes, from whatever the outgoing one had the time and energy to write. Everything they knew but did not write is simply gone. No industry that depends this heavily on rotating personnel should accept the institutional memory of an inbox.

The inspection sprint. Vetting regimes have moved to continuous, evidence-backed readiness — we have covered what SIRE 2.0 changed for tanker operators and RightShip’s phased expansion of dry bulk inspections in detail. The two-week preparation sprint was built for regimes that no longer exist. When the questionnaire is compiled per inspection and the inspector expects the record to already exist, a fleet that assembles its evidence on demand is structurally late. The preparation walk still matters — our RISQ preparation checklist and its SIRE 2.0 counterpart exist exactly for that — but a walk works best when it reviews a living record instead of creating one.

The office view. When the current state of a vessel is a research task, it gets researched rarely. Decisions that should be routine — which vessel gets the next docking slot, where the superintendent flies first — are made on the freshest anecdote rather than the fullest record.

What “evidence-based” does and does not mean

It does not mean replacing the planned maintenance system, and it does not mean another reporting layer stacked on the crew. A PMS schedules maintenance and records its completion; it was never designed to hold the unstructured evidence a vessel produces — the observation on rounds, the photograph of a doubtful weld, the surveyor’s report, the handover note. That layer is precisely where the spreadsheet-and-inbox habit lives, and precisely what structured capture replaces.

It also does not mean trusting a black box. The point of evidence-based oversight is the opposite: every flag traces back to a dated, human-made observation you can open and read. Judgement stays with people; the system’s job is to make sure the evidence that judgement needs is still there, structured and findable, when it is needed — months later, by someone who was not on board.

This is the layer our own product work lives in: HullSnap exists to give a fleet one structured, evidence-linked view of each vessel. This article is the reasoning behind that category, not a manual for our product — the comparison above holds whichever vendor you evaluate.

The questions to ask before you move

Any operator considering the switch should put the same hard questions to every vendor. Does capture add effort on board, or remove it? Does the crew ever see value back? What exactly do you own, where does it live, and what happens when you leave? The due-diligence list we published as the ship-to-shore data security checklist covers the data questions in full — ownership, jurisdiction, OT/IT separation and exit terms — and we would rather you ask them of everyone, including us.

The fleet already pays for the evidence: the crew produces it every day. The only real question is whether it lands somewhere it can protect the ship, or keeps dying in the inbox it was mailed to. Look at the state of your fleet’s records and decide honestly which side of the table you are on — and if you want to see what the evidence side looks like against your own vessels, request a technical review.