Smeaton is designed to give fleet managers and marine insurers a concise view of vessel performance while keeping the detailed operational evidence available underneath when something requires investigation.
Fleet management needs to know where operational attention is required. Marine insurance needs a clear, defensible view of how onboard controls are actually being performed. Smeaton keeps both connected to the same verified evidence.
Compare performance across managed yachts, identify deteriorating behaviour and focus management time on the vessels or routines that are creating exceptions.
The insurer-facing concept is intentionally concise: surface the key vessel assurance indicators first, then allow the reviewer to investigate the underlying rounds, checkpoint history and exceptions only where needed.
Feedback from insurance discussions has shaped the Smeaton presentation strategy: do not make a risk reviewer interpret every individual round or checkpoint scan on the first screen.
The proposed insurer-facing framework begins with a headline Smeaton Index and the 5 Assurance Signals. If one of those indicators is deteriorating, the reviewer can move into the supporting evidence beneath it.
A fleet-level view can make it immediately obvious which vessel is operating consistently and which vessel deserves management attention, without forcing the user to open every yacht individually.
| Vessel | Smeaton Index | Round Adherence | Surveillance Gap | Current exception |
|---|---|---|---|---|
| M/Y VesselA | 93 | 94 | 96 | No material exception |
| M/Y VesselB | 90 | 92 | 91 | Hardware follow-up |
| M/Y VesselC | 78 | 81 | 69 | Repeated missed night round |
| M/Y VesselD | 74 | 76 | 72 | Round consistency deterioration |
Illustrative data shown to demonstrate the intended fleet presentation.
Smeaton does not simply show that a procedure existed. It can retain evidence of whether the scheduled round happened, who performed it, when it began, which physical checkpoints were reached and what was reported during the round.
This gives marine insurers another source of operational information when reviewing vessel risk, without implying that the technology itself determines underwriting outcomes or premium.
The assurance layer should never become a black box. A fleet manager or risk reviewer should be able to move from an elevated signal into the operational events that caused it.
Review completed, partial and missed rounds alongside the assigned user and expected start time.
Inspect the checkpoints reached during the round and the timestamps associated with that attendance.
Review reported issues, written observations and photographic evidence linked to the relevant checkpoint.
See whether the event appears isolated or forms part of a broader pattern in completion, timing or coverage.
That is the core design principle for fleet and insurance users. The operational platform may collect thousands of individual events, but the decision-maker should first see only the information required to understand vessel assurance.
Detailed round, checkpoint and issue evidence remains available when a score, trend or exception needs further investigation.
“Insurance does not need another dashboard full of operational noise. It needs a small number of meaningful signals backed by evidence that can stand up to scrutiny.”
Josh Newman, FounderFor yacht managers, brokers and marine insurance teams, the most useful conversation begins with the evidence and assurance information you actually need rather than another generic software demonstration.