The platform

One operating file for the whole port call.

MERIDIAN is a controlled operating workspace for serious vessel calls — planning, agency execution, service requests, anchorage intelligence, vendor invoices, approvals, PDA/FDA closeout, and executive reporting, all in one file that travels port to port.

A blue-hour port-call operations desk near a marina window — a portable operating file, tablets, and abstract approval and vendor panels.
Port call · one operating file

What it does

Plan, coordinate, approve, close out.

Every port call runs the same four beats — MERIDIAN gives each one a shared, auditable home instead of a scattered email thread.

01

Plan the call

Vessel profile, port-call file, itinerary context, weather and anchorage intelligence, and the service scope for the visit.

02

Coordinate locally

Invite the local agent and vendors for that port; collect quotes, documents, and status updates in scoped threads.

03

Approve the spend

Quote comparisons, cost approvals, and invoice backup — routed to the right principal, manager, or purser.

04

Close out clean

PDA/FDA-ready closeout packets, exportable cost data, and a record that stays with the vessel for the next port.

Portable by design

Carry the operating file to the next port.

A yacht can license MERIDIAN directly and keep one continuous operating history across ports. At each port of call, the captain or management company invites only the people needed for that visit.

Invitees may include:

  • Local yacht agent
  • Ship agent
  • Marina or harbor contact
  • Fuel supplier
  • Provisioner
  • Transport provider
  • Aviation provider
  • Medical provider
  • Security provider
  • Contractor or technician
  • Principal representative
  • Management-company accountant

Each invitee receives scoped access only to the relevant visit, request, invoice, document, or task thread. The vessel or programme keeps the operating history after the port call closes.

Vessel retains the memory

Past port calls, invoices, supplier notes, authority documents, weather decisions, and closeout packets stay with the vessel.

Agents and vendors stay scoped

Local partners can contribute without seeing sensitive principal, itinerary, finance, or vessel-wide information.

Every port gets cleaner

The next agent does not start from zero. MERIDIAN carries the vessel's preferences, document standards, service history, and approval pattern forward.

Where MERIDIAN fits

What MERIDIAN replaces — and what it connects.

Replaces

Messy email chains

Service requests, quotes, approvals, invoice backup, and visit updates move into one operating file.

Complements

Yacht finance systems

MERIDIAN does not need to replace yacht accounting. It produces clean port-call backup, cost packets, and exportable data.

Complements

Onboard PMS

MERIDIAN does not compete with planned maintenance systems. It coordinates local service execution, vendors, documents, and closeout.

Extends

The local agent

MERIDIAN turns local knowledge, authority workflow, supplier coordination, and briefing production into a repeatable system.

Inside the workspace

The surfaces a call actually runs through.

Captured from the current build. Intake runs once per vessel; guides and the service desk run on every call.

Intake, once per vessel.

A ten-step intake captures particulars, insurance, the cruising programme, service requirements, provisioning, and operational particulars — and turns the answers into the required-document list for that vessel’s category.

It saves as you go, so an intake can be handed between the captain, the manager, and the office without restarting.

The MERIDIAN vessel-intake wizard on step 2, showing vessel particulars, hull and P&I insurance, and contact fields filled in for a sample vessel.
Vessel intake — step 2 of 10.

Anchorage guides, built from sources.

A guide is authored through a seven-step studio: sites and scope, an automatic gather of depths, tides, currents, buoys and regulatory extracts, swing geometry per vessel, exposure and climatology, then the written sections.

Publishing is gated on a lint pass, so a guide cannot go out with an unknown bottom type or a missing disclaimer.

A published MERIDIAN anchorage guide with the planning-grade disclaimer, a three-spot cruising and routing sequence, and the weather and seasonality section.
A published guide, with audience views for the principal and for vessel operations.

Service requests, quoted and approved in place.

Every request carries its own quotes, budget, approval tier, and decision. The desk shows the whole call at once — what is requested, quoted, awaiting a decision, running, and closed.

The decision line records who approved the spend and when, so the closeout packet does not have to be reconstructed from email.

The MERIDIAN service desk showing sample requests across requested, quoted, pending approval, approved, in progress, and completed states, each with quotes and an approval decision line.
The service desk, filtered by state.
A single MERIDIAN service request open, showing two vendor quotes, the budget awaiting a purser decision, and approve and decline controls.
One request: quotes, budget, and the approval decision.
The MERIDIAN guide studio on the geometry step, showing computed swing radius, scope, and set point for a vessel at one anchorage.
Swing geometry computed per vessel, per anchorage.

Screens are from the current build, populated with sample data. Vessels, organisations, people, vendors, and figures shown are illustrative and are not those of any client.

Ready

See the platform on your own vessel, agency, or destination.

Every production workspace begins with intake, review, scoped configuration, and a written proposal. Guest workspaces are approved manually.