principal visibility
A MERIDIAN site version for principals, principal representatives, and family-office teams that need clear service status, trip readiness, approvals, preferences, financial handoffs, and concierge-level coordination across one or more vessels.
Tailored service story
This version keeps the navigation functional and service-led, while adapting language, metrics, tasks, and operating examples to principals.
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.
Common pain points
The updates that reach you are either too much detail or not enough.
What the vessel and crew know about the principal is not written down anywhere durable.
You approve a number without the visit behind it.
Your command deck
MERIDIAN is permissioned by role. You see your operation, and only your operation.
Working together
They run the detail; you see the picture.
Preferences and readiness stay connected across the season.
Scoped to the job — never to your wider affairs.
Example workflow
Trip and vessel readiness at a glance.
The visit and cost behind each approval.
Recorded once, carried forward.
A clean, current picture on request.
Principal, itinerary, and finance context stays private and is never exposed to local partners unless you share it.
Guest and invited access is approval-gated and scoped — never open public signup.
Discretion
Everyone invited into your operation sees only what their role needs. The operating file stays yours.
Questions
No. The point is the opposite — you see readiness, approvals, and cost without the operational noise.
Yes — a principal representative or family-office staff can be scoped to act on your behalf.
Access is role-based; sensitive principal, itinerary, and finance context is not exposed to agents or vendors.
Yes — recorded once, carried forward.
Get started
See how MERIDIAN adapts to your workflows, or request a walkthrough tailored to your operation. Access is reviewed and routed — guest workspaces are approved manually.
