Receive dispatch
Vendor receives scope, location, contacts, timing, and access instructions.
Workflow path
How the service vendors version moves work forward.
The process language changes by audience, but the underlying pattern is consistent: intake, route, execute, update, and close out.
Clarify or quote
Questions, quote requests, and scope changes stay attached to the job.
Check in on site
Operations can see vendor status and expected completion window.
Complete with evidence
Photos, notes, receipts, parts, readings, and next steps are captured.
Close the loop
Tenant, vessel operator, or management agency receives confirmation.
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.
- Clearer scopes — Vendors get better job information before arriving.
- Fewer access failures — Arrival instructions and contacts are attached to the work order.
- Faster completion records — Photos and notes are captured at the point of work.
- Better operations handoff — The requestor sees what happened and what remains.
Queue preview
Example work in motion.
The same component set supports rollups for management, dock desks, tenants, and vendors.
Jobs today14
Quote asks6
Access windows9
Review4
Assigned 02
M/Y AuroraInterior detail scope
Slip B-18Pedestal inspection
Quote 02
Pump repairPhotos attached
Parts runApproval threshold flagged
On Site 02
Fuel truckChecked in Dock C
Dive serviceETA 15 min
Complete 02
Provisioning deliveryPhoto confirmation
Laundry returnAwaiting tenant sign-off
Where vendor workflows break today
Not on the dock — in the handoffs. The scope that lived in a phone call, the access window that moved without anyone telling the truck, the approval that sat in an inbox while the crew stood by, the completion photo that never made it out of a text thread.
Each state above exists to make one of those handoffs explicit, visible, and attached to the job.
Ground truth
A workflow is only as good as its worst handoff.
The five states above are deliberately plain: receive, clarify, check in, complete, close. What changes with MERIDIAN is that every transition is recorded on the work order itself — so the dispatcher, the dock desk, the captain, and the management agency are reading the same job, not four versions of it.
Narrated example
One job, walked through every state.
A charter turnaround interior detail — dispatched the evening before, closed out by mid-afternoon.
Dispatch lands
The management agency dispatches the detail with berth, guest-departure timing, crew contact, and a photo set of the interior condition. Your team accepts from the queue that evening.
Clarify in-thread
Your supervisor asks whether product should be staged aboard or carried on. The answer arrives attached to the job — the next crew member to open it sees the same thread.
Check in on site
The gate, dock, and escort details are already on the order. You check in on arrival; the dock desk and the agency both see your team on site and the expected completion window.
Scope changes on site
Mid-job, the crew asks to add the crew mess. That is a scope change, not a favor: it routes as a quote item, gets its yes, and the extra hours are on the record before the work starts.
Complete with evidence
Before-and-after photos, product notes, and a flag on a worn carpet runner the crew should see. You check out; the job moves to completion review.
Close the loop
The interior lead confirms, the agency releases the job, and the record — thread, change, evidence, sign-off — stays on the vessel’s file for the next turnaround.
Questions
Frequently asked about workflows.
What happens when scope changes mid-job?
Raise the change on the work order. It routes to the requester as a quote item with the approval threshold visible, so your crew is never doing unpriced work on a handshake.
What if we miss an access window?
Update the job with the delay. The dock desk and the dispatcher see the new arrival estimate against the same window — a reschedule becomes a state change, not a round of phone calls.
Can several crews work one job?
Yes. Multi-crew dispatch is part of the vendor workspace tiers — each crew checks in and out against the same work order, and the evidence rolls up to one completion record. See the plans page.
Who sees my status updates?
The parties on the job: the dispatcher, the site controlling access, and the requester. Your updates never broadcast beyond the operations that invited you.
What if the requester goes quiet?
The job holds its state visibly — awaiting quote approval, awaiting sign-off — so the delay is on the record and the follow-up lands with the right person rather than in a group text.
Get started
Run your next job through a workflow that keeps its receipts.
See the dispatch-to-close-out flow with your own service categories, or request a walkthrough tailored to your operation. Access is reviewed and routed — guest workspaces are approved manually.