The last hour of a passage is not one job. It is berth, fuel, provisions, tender, customs and a crew change, all competing for the same attention the captain still needs on the approach.
The approach is a stack of departments
On a well-run yacht the bridge is not short of procedure. Passage plan, under-keel clearance, VHF, lines, fenders, passerelle: that work has a home. The problem is everything around it that is not navigation, and still has to finish before the gangway goes down.
A typical Mediterranean arrival looks like this. Stern-to. Shore power on the quay. A bunker barge at first light. A provision run before the shops close. The starboard tender due a service. Two crew joining at 0900, two signing off. Crew list, guest list and stores list to the agent before the yacht is alongside. Guests or the owner later the same day.
None of those jobs is unusual. The unusual part is that they all land in the same window, on a vessel where the person holding the whole picture is also on the con. Most of it still lives in WhatsApp.
A checklist, by department
Treat this as a prompt, not a form. Every harbour is different. The point is to see the stack in one place.
Berth and harbour. Confirm the berth in writing: alongside or stern-to, LOA, beam, draught, air draught, which side to the quay. Linesmen, fenders, passerelle, shore power, freshwater. Agent, marina VHF, ISPS if it applies. Tender dock if needed. Waste: garbage, sewage, sludge, and whether that window clashes with bunkering.
Fuel. Quantity against ullage, not a round number from memory. Grade for the next leg. Barge versus quay, timed away from guest arrival. Sample bottles, bunker delivery note, MARPOL entries. Who is on deck for the hose, and who is still on rest.
Provisions. Chef's list against what is already in freezers and dry stores. Dietary restrictions from the guest or owner sheet. Bonded stores. Last-mile: van to the quay, or a tender run if there is no alongside access. Par levels for the next passage, not only tonight's dinner.
Tender and deck. Launch plan, weather limits, which hull, which crew. Any service slot already booked. Toys guests will ask for in the first hour, checked, not discovered missing on the passerelle.
Customs and clearance. Crew list, guest list, stores list. Passports and visas in a pack the purser can hand over. Firearms, bonded stores, any declaration this port actually requires. FAL forms via the agent if that is how the harbour works. One joiner changes the pack; yesterday's version is not current.
Crew change. Joiners: flights, taxis, cabins, safety brief. STCW, ENG1, flag endorsements in hand before they take a watch. Leavers: sign-off, repatriation, cabin strip, notes someone else can still find tomorrow. If both watches are changing, rest hours still have to close.
Guests or owner. ETA, cars, luggage, cabin allocation, first meal, allergies. Cabin allocation is not interior trivia. It drives provisioning, laundry, air conditioning and which cabin the engineer must not enter with a toolbox.
A captain reading that list already does most of it. The failure is not ignorance. It is that the list is split across six people and four threads, and the only person who sees all of it is busy.
What still lives in WhatsApp
On most yachts the live operational picture is a set of group chats. Agent and captain. Captain and chief engineer. Interior and chef. A port-call group created in May and never cleaned. A photo of a fuel quote. A voice note about a dietary change. A flight delay sitting in a personal chat with the crew agent.
WhatsApp is good at a fast message to a person who has a phone. It is a poor operational record. There is no single list of open jobs. The berth time exists in three places. The fuel figure is a screenshot that may not be the latest offer. The chef is in a group the engineer is not in. When a crew member signs off, they leave the group, and whatever they knew leaves with them.
Why that fails on approach
The last hour is the worst possible time for a chat log to be the system of record. The captain's attention belongs on the approach. A phone buzzing with a revised fuel quantity is a second job at the moment the first cannot be delayed.
Version control collapses. The agent advances the berth by forty minutes; interior still has guest cars at the original time; the engineer is still expecting the barge at 0600. Nobody is wrong. They are reading different messages.
Rest hours take a quiet beating. MLC 2006 cares about hours of rest, not about whether the message was "just a quick one". If a steward or an engineer is answering port-call threads during a rest period, that time is work. Reconstructing it later from a phone is a bad morning with a surveyor.
STCW sits in the same pile when the crew change is the same morning as the arrival. A joiner's certificates are either in a folder the captain can see, or they are a PDF on someone's phone in a taxi. That is the difference between standing a watch after the safety brief and being short until the paperwork is found.
What belongs in a record, and what stays a phone call
Not everything should be software. The call to the harbour master, the visual on the quay, the judgement about whether the wind is still acceptable for stern-to: those stay with the people on deck.
What should not live only in a thread is the fact that other departments need to read. Confirmed berth, fuel order, provision list, tender work order, crew list, joiner certificates, guest dietary restrictions. Each of those is entered once, in one place, then read by whoever needs it. That is the difference between a chat and a shared record: not more features, one home for the arrival.
What this means on board
Write the arrival as departments, not as a single task. Give each fact one home. Keep the phone for conversations that need a conversation. Protect rest hours as if a surveyor will ask. Do not run a crew change, a bunker and a guest arrival off the same unread thread.
YachtOS treats this as a live operational problem. Command is a spoken workflow for berth, fuel, provisions and work orders. The captain stays in command of what actually goes out. The apps are live. Try them against a real arrival, or request a demo built around your own harbour.