What's open, what's running, who's on watch — changed by whoever changed it, seen by everyone else the moment they look.
Built aboard a working yacht. Shaped around yours.
A whiteboard by the galley. A crew WhatsApp group. A spreadsheet one person maintains and nobody else opens. Somebody's memory of what they did at 0400.
It mostly works, because your crew are good at their jobs. It stops working on crew change, in the second week of a charter, and at every handover where the person who knew is asleep. Then somebody walks a guest past an open hatch, or the passerelle light stays on all night, or two people each think the other one closed it.
VesselOverview is one screen that holds that state, and every phone aboard can see it.
I'm an ETO. Nineteen years working on yachts, standing the watches and being woken at 0300 because something tripped.
A contractor sees a boat for a week. They fix what they were called for, hand over a folder, and leave before the crew change that undoes it. I've been on the other side of that one: still aboard in week three, working out what the last person meant.
That's the difference in this product. It isn't a tidy model of how a vessel ought to run. It's built around how they actually do, by someone who has to live with the result.
Every change writes a log entry in the same breath as the change itself. Not a separate step somebody forgets. The same action. You can see who shut the tender garage and at what time, six weeks later.
Plain forms, no clever client-side state. On a boat the link drops constantly, and a form that either goes through or plainly refuses beats an interface that pretends it saved.
A log entry can be corrected for an hour after it's written, by the person who wrote it or by an administrator at any time. The original stays. Nothing quietly disappears.
Every yacht runs differently, and software that insists otherwise gets abandoned by week three.
Your administrator sets up the panels the boat actually needs, in the words the boat actually uses. If your crew say lazarette and not aft store, the screen says lazarette. If you care about six hull openings and one passerelle, that's what's on the board, not a fixed list somebody else decided was standard.
Hull openings, tenders, watch, guests aboard, anchor. Add what you need, archive what you don't. Archived, never deleted, so the history survives.
Item names, states and labels are yours. Nobody has to translate the screen into how the boat actually talks.
Per panel, decide whether any crew member can add an item or only an administrator. A guest manifest turns over every charter; the hull opening list does not.
You want to know the state of the boat without asking three people, and you want the handover to survive whoever was awake for it.
Cabins, crew, rotas and who's aboard, in one place instead of four spreadsheets that disagree with each other by Thursday.
One view across every boat you run, without ringing each captain to ask. Each vessel is billed and configured on its own.
Worth saying plainly, so you don't waste a call finding out.
If you need a planned maintenance system, buy one. This is the layer underneath it that the whole crew touches every day.
Per vessel, per year, unlimited crew. No per-seat billing, ever.
The daily picture everyone aboard shares.
£1,200per vessel, per year
Most vessels start here
Adds the department heads’ tools.
£2,400per vessel, per year
The demo is the real product with an invented boat and invented crew. No form, no call, no request-access gate.