Open movement or request
Start with ETA, berth need, service request, or crew/guest requirement.
Workflow path
How the captains & operators version moves work forward.
The process language changes by audience, but the underlying pattern is consistent: intake, route, execute, update, and close out.
Confirm resources
Attach berth, vendors, documents, weather context, and local contacts.
Track execution
Monitor vendor ETA, service progress, crew logistics, and blockers.
Prepare departure
Close out documents, utilities, waste, provisions, and final checks.
Hand off cleanly
Export a concise handover for management, owner reps, and next port.
Operational queues
Role-specific queues instead of generic product modules.
This keeps the site focused on what visitors need to accomplish: request service, assign work, resolve exceptions, and keep stakeholders informed.
- Fewer scattered channels — The captain-facing version organizes calls, messages, and service tasks into one queue.
- Arrival confidence — Berth, vendors, documents, weather, and supplies are aligned before arrival.
- Useful crew support — Crew logistics become visible, timed, and accountable.
- Clean departure state — Departure tasks and missing items are obvious before the window closes.
Queue preview
Example work in motion.
The same component set supports rollups for management, dock desks, tenants, and vendors.
Tasks open12
Vendors due5
Docs needed3
Next window18:30
Plan 02
Arrival windowETA 20:15 · berth fit confirmed
Weather watchSwell dropping after 18:30
Service 02
Fuel and waterTender at Dock B
Laundry pickupVendor delayed 25 min
Crew 02
Crew change2 arrivals tomorrow
TransportAirport pickup confirmed
Depart 02
Clearance packet1 missing item
Departure checklist8 of 11 complete
States, not messages
A message tells you what someone said. A state tells you where the work is. The desk holds every open item in a named state with one owner and one next action, so nothing rides in anyone’s head between watches.
If you can answer “what state is it in?”, you never have to scroll a thread to find out.
Why this shape
The port day is interruptions; the workflow is how they stay ordered.
Berth changes, vendor slips, a crew flight moved twice — the plan you wrote at 06:00 is rarely the day you get. Workflows absorb the changes: each disruption becomes an update to a tracked item instead of a fresh round of calls, and the people downstream re-brief themselves from the plan.
Example: one workflow, narrated
A berth shift, start to finish.
A generic mid-call disruption, run as one tracked workflow instead of a dozen messages.
07:10 — the ask arrives
The marina office asks you to shift one berth down the dock late morning so a crane barge can work. You open a movement instead of writing a sticky note.
07:25 — the plan absorbs it
The desk shows what the shift touches: the fuel window, a provisioning drop, shore-power disconnect, two crew ashore. Nothing has to be remembered.
08:00 — everyone re-briefed at once
Affected vendors see their updated access windows on their own scoped view. No group text, no “who told the laundry van?”
11:30 — the move itself
Lines, fenders, shore power down and back up — the checklist runs on the board, and each confirmation is logged as it happens.
12:15 — closed and recorded
The movement closes with confirmations attached. The daily report and the handover already reflect it; the afternoon continues on plan.
Questions
Frequently asked about workflows.
Is the workflow rigid?
The states are consistent — intake, route, execute, update, close — because that is what makes status legible at a glance. What happens inside each state adapts to your operation.
Who sees a workflow besides me?
Only the people you scope in. A vendor sees their job and access window. Principals and managers see readiness rollups. Nobody reads the whole desk by default.
What happens when something breaks mid-workflow?
The exception lives on the item — flagged, timestamped, and visible — instead of buried in a message thread. You resolve or reroute from the same place.
Can I run several workflows at once?
That is the normal state of a port call. The board groups live work by state, so a dozen open items read as a plan rather than a pile.
Where does a closed workflow go?
Into the call file and the vessel’s service history, and into the daily report and handover — closing the work and reporting the work are the same act.
Get started
Run your next port call as one workflow.
See how intake, routing, and close-out map onto the way your vessel already works, or request a walkthrough tailored to your operation. Access is reviewed and routed — guest workspaces are approved manually.