Services for Principals
Each service card includes rollover or tap details for deeper explanation without interrupting the page flow.
Convert principal, guest, or representative requests into operational tasks with accountable owners and completion notes.
Each request can carry vessel, trip, due date, priority, service type, approver, and evidence of completion.
Summarize itinerary, berth status, provisions, guest requirements, crew readiness, weather, and unresolved blockers.
The view favors decisions: green for ready, amber for watch items, and clear calls for approvals needed.
Keep vessel and principal preferences accessible to management teams, captains, and service coordinators.
Covers food, beverage, cabin setup, transport, communication style, vendor preferences, and special handling.
Review quotes, scope changes, service upgrades, high-value orders, or exception decisions before work proceeds.
Approvals are attached to the related request so decisions do not get separated from operational context.
Track arrivals, transfers, deliveries, hospitality, local arrangements, and special requests for guest movements.
Links timing, location, responsible party, vendor status, and fallback notes.
Receive concise summaries that explain completed work, upcoming needs, watch items, and costs requiring attention.
Designed to compress operational detail into a reliable executive summary.
See status across owned, managed, or family-use vessels without logging into every operational thread.
Helpful for principals and family-office staff supervising more than one vessel, location, or support team.
Maintain continuity across crew changes, management changes, yard periods, and recurring principal preferences.
The profile becomes a durable operating memory for each vessel.
Service matrix
Every service is structured as an intake, routing rule, operating workflow, and completion output.
The day-to-day reality
Most principals and family-office teams do not lack service — they lack a clean view of it. Requests travel by text, quotes arrive as forwarded email, and the state of the vessel lives in the head of whoever touched it last. When the principal asks a simple question — is the vessel ready, what did that visit cost, who signed off — assembling the answer becomes its own project.
This catalog exists to close that gap. Every service above is management-led: the management agency and crew run the operational detail, while the principal side keeps a durable record of what was requested, what it cost, who approved it, and how it was completed. Nothing here asks the principal to manage the dock — it asks the operation to report in a shape the principal can trust.
Example lifecycle
A concrete walkthrough: a principal visit is coming up, and the representative needs provisioning, cabin setup, and ground transport handled without chasing anyone.
The representative submits one request from the principal workspace: arrival date, guest count, and which standing preference profile applies.
MERIDIAN structures it into scoped tasks — provisioning, interior setup, transport — each with an accountable owner on the management side.
The provisioning quote crosses the standing threshold, so it waits in the approval queue attached to the visit, the scope, and the vendor quote.
Statuses roll up as green and amber. The representative watches readiness, not task chatter, and steps in only where a decision is needed.
Completion notes and costs land in the service history, and any new preference is saved to the profile for the next visit.
Questions
A principal representative or family-office staff member can be scoped to submit, approve, and review — the principal decides how much lands on their own desk.
No. MERIDIAN is the coordination and record layer. The management agency, crew, and the service network they engage perform the work — the services above define how that work is requested, tracked, and reported.
The operation sets thresholds by amount, category, or vessel. Anything under a threshold proceeds and is recorded; anything over waits in the approval queue with the quote and visit attached.
The operating team works the full task detail. The principal side sees readiness, approvals, watch items, costs, and the completion record — the summary shape, not the noise.
Requests are scoped per vessel so history stays clean, but the multi-vessel overview shows them side by side for family-office teams supervising several programs.
Next page
The workflow page shows how intake, review, assignment, execution, updates, and close-out should feel for principals.
Get started
See how these services would map onto your vessel or program, or request a walkthrough tailored to your operation. Access is reviewed and routed — guest workspaces are approved manually.
