Services for Captains & Operators
Each service card includes rollover or tap details for deeper explanation without interrupting the page flow.
Coordinate ETA, berth readiness, local contacts, dock instructions, weather, and departure checklist items.
Attach route notes, harbor constraints, dockage, clearance status, and requested services to each movement.
Manage crew arrivals, ground transport, shore access, deliveries, hotel needs, and crew communications.
Each item can include person count, pickup time, vendor, contact, status, and notes.
Request, schedule, and track core vessel services with time windows and completion status.
Designed for high-friction dock services where timing, access, and confirmation matter.
Organize provisions, stores, laundry, catering, parts, flowers, and delivery instructions by vessel and deadline.
Requests can include drop point, crew contact, temperature handling, vendor, and photo confirmation.
Track crew lists, insurance, permits, certificates, customs/immigration packets, and local forms.
Shows what is requested, submitted, accepted, or blocking a movement.
Create practical work requests with photos, scope notes, vendor assignment, quotes, and completion evidence.
Useful for repairs, cleaning, inspections, dive service, electronics, engine room, and deck needs.
Tie weather windows, swell, wind, notices, and route advisories to the actual service or movement plan.
Weather is shown as an operational input, not a detached forecast screen.
Package what happened, what is pending, who owns it, and what is needed before departure.
Supports captain-to-manager, crew-change, and next-port handoffs.
Service matrix
Every service is structured as an intake, routing rule, operating workflow, and completion output.
Every card in this catalog began as a thing that interrupts a port day: the fuel tender asking to move up an hour, provisions on the dock with no one to meet them, an engineer waiting on a part, the office asking where things stand.
Structure turns an interruption into a request with an owner, a window, and a status.
The day this is written for
In port, your day is a queue of small negotiations — timing, access, quantities, who meets whom at which dock. This catalog is the intake surface for that day: each service is a structured request that carries enough detail to be executed without a second phone call, and enough status to keep managers and principals informed without a written update.
Example: one request, end to end
Every service on this page follows the same lifecycle. Here is what it looks like for one of the most common.
The evening before departure, you open a fuel-and-water request from the movement plan: quantities, preferred window, dock-side constraints, and who meets the vendor.
The request carries the vessel profile with it, so the fulfilling vendor or agent sees berth, access notes, and contacts without a phone briefing.
The vendor accepts a time window. It lands on your board next to the weather window and the rest of the departure plan — not in a separate thread.
ETA updates and on-station status roll in as they happen. If the tender slips, the delay is visible to everyone who depends on it, not just whoever took the call.
Quantities, completion notes, and photos close the request into the call file — ready for the daily report, the handover, and the vessel’s service history.
Next page
The workflow page shows how intake, review, assignment, execution, updates, and close-out should feel for captains & operators.
Questions
As specific as the dock requires. Requests carry quantities, time windows, drop points, crew contacts, access notes, temperature handling, and photos — so the vendor arrives briefed instead of calling the bridge twice.
Whoever your operation trusts: vendors you invite directly, an agency’s network, or a management company’s preferred providers. Routing follows how the vessel is set up — MERIDIAN structures the request; it does not force a supplier on you.
The delay shows as a status on the ticket with the updated ETA. You reschedule from the request itself, and everyone who depends on that window sees the change — no new thread, no relay calls.
That is a permission you set. Many operations let heads of department raise requests in their own area while the captain approves scope and anything spend-sensitive.
Yes. Completion notes, evidence, and vendor track record stay with the vessel profile, so the next port — and the next captain — starts from a record, not from memory.
It is context attached to movements and time-sensitive services rather than a separate forecast screen. It is planning-grade input; the decision stays with you.
Get started
See how the catalog adapts to your vessel and your vendors, or request a walkthrough tailored to your operation. Access is reviewed and routed — guest workspaces are approved manually.
