Submit or approve
A request, approval, or trip requirement enters the principal-facing workspace.
Workflow path
How the principals version moves work forward.
The process language changes by audience, but the underlying pattern is consistent: intake, route, execute, update, and close out.
Translate to operations
MERIDIAN structures the request into service tasks, vendors, timing, and principal-specific details.
Monitor readiness
Principal reps see clear status, blockers, and decisions needed rather than raw task clutter.
Receive confirmation
Completed items are confirmed with concise notes, dates, and supporting evidence.
Retain history
Preferences, service outcomes, and notes are retained for the next visit or trip.
Operational queues
Role-specific queues instead of generic product modules.
This keeps the site focused on what visitors need to accomplish: request service, assign work, resolve exceptions, and keep stakeholders informed.
- Less operational noise — Principals see what matters: readiness, approvals, watch items, and completion.
- Better preference continuity — Service teams stop relearning principal requirements on each visit.
- Cleaner approvals — Approvals stay attached to scope, quote, vessel, and operational deadline.
- Executive confidence — The principal-side view creates a disciplined record of care and coordination.
Queue preview
Example work in motion.
The same component set supports rollups for management, dock desks, tenants, and vendors.
Open requests11
Approvals4
Trips planned2
Reports ready6
Requested 02
Principal arrivalGround transport and provisions
Guest preferenceCabin setup update
Awaiting Approval 02
Interior serviceQuote review
Fuel top-offBudget threshold reached
In Progress 02
Trip readinessCrew, berth, stores aligned
Concierge requestRestaurant confirmation pending
Complete 02
Status reportDelivered to representative
Preference updateSaved to profile
Why the shape matters
A workflow the principal side can see is a workflow nobody has to narrate by phone. The structure does the reporting: each step leaves a record, so the story of the trip is written as it happens rather than reconstructed afterwards.
The management agency runs the steps. The principal side reads the state.
Grounded in the week
What this replaces.
For most family-office teams, “the workflow” today is a group text, a forwarded quote, and a call to the captain to find out where things stand. Each trip re-invents the process, and each new crew member relearns it. The principals version replaces that with one repeatable path — the same intake, the same approval shape, the same close-out — so the second trip of the season runs like the tenth.
Worked example
One trip, narrated end to end.
A representative books a ten-day trip with guests aboard. Here is how that single workflow moves through the principals version.
1 — The trip is opened
The representative enters the trip window, guest count, and which preference profile applies. That single entry becomes the spine every task attaches to.
2 — Readiness assembles
Berth confirmation, provisioning, interior preparation, crew status, and transport each become tracked items against the trip, with accountable owners on the management side.
3 — A decision surfaces
An interior service quote crosses the approval threshold. It arrives in the queue with the scope, the vendor quote, and the trip it belongs to — a two-minute decision instead of a phone chase.
4 — A watch item appears
A delivery slips. The item turns amber on the readiness view with a note and a revised date, so the representative sees it before it becomes a departure-day surprise.
5 — Departure and close-out
The trip goes green. After departure, completion notes, approved costs, and any new preferences are retained on the record — the starting point for the next trip.
Questions
Workflows, frequently asked.
Does the principal have to run this workflow?
No. The management agency and crew run the steps. The principal side sees state, approves where thresholds require it, and reads the close-out.
What happens when something goes off-plan mid-trip?
The affected item turns amber with a note and a revised date, and anything needing a decision moves to the approval queue. Exceptions surface — they do not hide in a thread.
Can approvals be delegated or capped?
Yes. Thresholds and delegation are set per operation: a representative can hold day-to-day approvals while larger decisions route to the principal or family office.
How much detail reaches the principal at each step?
As much or as little as the operation configures. The default is the summary shape — readiness, decisions needed, watch items, and completion — with detail one level down when wanted.
Is the workflow the same across vessels?
The pattern is the same — intake, route, execute, update, close out — while thresholds, preference profiles, and accountable owners are set per vessel.
Get started
Run the next trip on one repeatable path.
See how this workflow adapts to your vessel or program, or request a walkthrough tailored to your operation. Access is reviewed and routed — guest workspaces are approved manually.