The boat, run the same way every time.

Most of what keeps a vessel safe is not written down anywhere. It is in one person's head — the order they check things in, the thing they always look at twice, the step everyone forgets. That works until the person with the head is not aboard.

The knowledge problem

A relief captain takes her out for a week. A new mate joins mid-season. The owner runs her himself for the first time in a year. In every one of those cases the boat is the same and the procedure is not, because the procedure was never a document — it was a habit.

A boat should not run differently depending on who happens to be aboard.

Paper checklists solve this badly. They get photocopied, annotated, lost, and — worst of all — they get ticked. A completed paper checklist tells you a box was ticked. It does not tell you who ticked it, when, whether they actually did the thing, or what they found when they did.

A playbook is the procedure. A run is what happened.

theONE ships nine kinds: Pre-Departure, Underway, Anchoring, Refueling, Post-Trip, Maintenance, Emergency, Extreme Weather, and Custom for whatever your boat needs that nobody thought of. Each is a list of items, and each item is assigned to a crew position — so the engine-room round belongs to engineering and the lines belong to deck, whoever happens to be filling those roles this week.

Then you run it. And the run is where this stops being a checklist app:

• Every check is attributed. Who ticked it, and at what time. Not "someone did this" — a name and a timestamp.
• A check can carry a note and photos. "Port seacock stiff, freed it" is worth more than a tick, and the photo of the thing you were unsure about goes in the record.
• A skip has to say why. Steps get skipped legitimately all the time. theONE records that it was skipped and the reason, rather than letting it silently read as done.
• The run is pinned to the playbook's version. Playbooks get edited; versions are bumped. A run from March is auditable against the checklist as it existed in March, not as it reads today. That is the difference between a record and a claim.

Readiness: one number, and what's behind it

Runs roll up. Every open item assigned to a position feeds a departure readiness score for the trip — Engineering, Deck, Interior, Bridge, Electrical, Hull, Safety — and that score is on Mission Control before you leave the dock.

The number on its own would be useless, so it is a door. Tap a department and you get exactly what has been done and what is left, with the name against each finished item. A captain deciding whether to go does not want a percentage; he wants to know that engineering is clear and the deck has one thing outstanding, and who is doing it.

Playbooks are assigned by role — and to specific people where you need that. A mate sees the playbooks a mate runs.

Built once, reused

Items can be drawn from a shared library rather than retyped for every playbook, and playbooks can be scheduled and recommended against the phase of the leg you are on — a pre-departure list surfacing before you leave, not after.

A completed run exports as a PDF summary straight out of the share sheet. That is what you hand a relief captain, a surveyor, or an owner who wants to know how the boat is actually being run — and it is the difference between saying the checks were done and showing that they were.

Why it matters more than it sounds

Because "we always do it this way" is the single largest body of undocumented knowledge on any well-run boat, and it walks off the dock every time the crew changes. A playbook is that knowledge written down once, run the same way every time, and left behind as evidence that it was.