One portfolio view
Portfolio visibility across yachts, workboats, tenders, support craft, and transient client vessels.
Coverage model
Service coverage shaped around the selected operating profile.
Coverage is presented as practical service reach: who can request, who fulfills, which locations are active, and what outputs are available to management agency.
Hawaii-ready operations
Regional service network, adapted by audience.
MERIDIAN coordinates service across Hawaii’s harbors, marinas, anchorages, and vessel programs — adapted to how your operation actually works.
- Audience-specific service categories and response paths.
- Location-aware intake for slip, berth, anchorage, harbor, or vessel.
- Reusable service network visual language across every version.
What coverage means
Coverage is where your desk can act, not a map graphic.
For a management agency, coverage is a practical question asked one voyage at a time: when a managed vessel moves, can the desk still take requests, route them to people who can fulfill them, and keep the principal’s picture continuous? MERIDIAN treats coverage as exactly that — location-aware intake, a fulfillment set attached to each active location, and outputs that follow the vessel rather than the harbor.
- Intake is location-aware: a request carries its slip, berth, anchorage, or harbor context from the start.
- Each active location carries its own fulfillment set — vendors, access rules, and service response paths.
- The vessel’s operating file is the constant; locations change around it.
The desk stays in one place
Vessels move; the agency does not. Coverage means the desk keeps working from the same portfolio board while the location context under each vessel changes — no separate tool, thread, or process per harbor.
New locations join as your operation’s season and programs require them.
Deployment layers
What coverage means for management agency.
These cards can become future market modules, service-area pages, or CRM routing rules.
Repeatable service playbooks
Standardize the service delivery model without losing vessel-specific preferences.
Cleaner handoffs
Fewer phone calls and message chains because each job has an assignee, due time, status, and next action.
Better client confidence
Management teams can show what happened, what is blocked, and what is complete.
Worked itinerary
Coverage on a multi-stop run.
A managed vessel runs a three-stop itinerary: its home-port harbor, a neighbor-island marina, and an anchorage call before returning. Here is how coverage carries it.
Stop one — home port
The visit plan opens against the home harbor’s fulfillment set: familiar vendors, standing access notes, and the vessel’s usual service preferences.
Underway — next stop opens early
While the vessel is in transit, the desk opens the marina stop: berth request, document requirements, and provisioning orders queued before arrival.
Stop two — neighbor-island marina
Same operating file, different fulfillment set. Requests route to the vendors attached to that marina, with its own access rules and delivery points.
Stop three — anchorage call
Location-aware intake shifts to anchorage logistics: tender runs, delivery timing, and a shore-side pickup — still logged on the same file.
Return — one continuous record
The itinerary closes as a single history: every stop’s services, costs, and evidence feed one principal update instead of three disconnected reports.
Profile routing
Keep this visitor in the management agency site version.
Because the profile is persisted, return visits continue to this role-specific structure until the visitor switches profile.
Questions
Frequently asked about coverage.
Does each stop on an itinerary need separate setup?
No. A stop is a location context on the same operating file. The desk opens the next stop from the portfolio board, and the vessel’s profile, preferences, and history carry forward automatically.
What if a location is not in an active service area yet?
The visit plan, documents, and approvals still run the same way. Fulfillment at that stop depends on the vendor set available — and you can attach your own vendors to any location your programs use.
Do vendor pools differ by location?
Yes. Each active location carries its own fulfillment set, so a request at one marina routes differently than the same request in the home harbor — without the desk re-briefing anyone.
Do principals see stops separately or one itinerary?
One itinerary. Principal updates compose across stops from the continuous record, so the picture a principal’s representative sees is the voyage, not a stack of per-harbor reports.
Can coverage follow a seasonal program?
Yes. Locations activate as your fleet’s season and programs require them, and quiet locations simply carry their history until the next visit.
Get started
Map your fleet’s real operating footprint.
Talk through the harbors, marinas, and anchorages your programs actually use, and how a season of movement stays one record. Access is reviewed and routed — guest workspaces are approved manually.