Job dispatch queue
Receive assigned jobs with vessel, slip, scope, priority, due window, contact, and access details.
Dispatch detail
Vendors get enough context to show up prepared and reduce clarification calls.
Services for Service Vendors
Actual service delivery, written for the way this audience works.
Each service card includes rollover or tap details for deeper explanation without interrupting the page flow.
Scope and photo notes
Use request photos, job descriptions, attached documents, measurements, and special instructions before arrival.
Scope evidence
Helpful for maintenance, repairs, provisioning, cleaning, inspections, and specialty trades.
Site access coordination
Confirm arrival windows, marina access, dock location, escorts, parking, delivery routes, and vessel contact.
Access workflow
Designed to prevent vendors arriving without the right gate, berth, person, or permission context.
Quote and approval routing
Respond to quote requests, recommended extras, scope changes, and approval thresholds in context.
Quote context
Quote discussion remains linked to the job, vessel, location, and requester.
Check-in and check-out
Mark on-site status, timing, delays, and completion so operations teams know what is happening.
Status tracking
Useful for busy docks where vendor presence affects security, access, berth operations, and tenant expectations.
Completion evidence
Attach photos, notes, receipts, part numbers, meter readings, and next-step recommendations.
Completion record
A stronger handoff for operators, tenants, captains, and management agencies.
Recurring vendor programs
Support repeat services such as fuel, waste, cleaning, laundry, inspections, supplies, and scheduled maintenance.
Recurring pattern
Jobs can be grouped by vessel, dock, contract, route, or weekly service cadence.
Vendor performance visibility
Track response, completion notes, exceptions, missed windows, and service quality for operational review.
Performance view
Not a public ranking; an internal coordination record that helps service teams improve.
Service matrix
From intake to operational output.
Every service is structured as an intake, routing rule, operating workflow, and completion output.
Service layerIntakeRoutingStatusOutputPortal
Job dispatch queueProfile + request dataRole / vessel / location● Live queueReport / completion noteService Vendors
Scope and photo notesProfile + request dataRole / vessel / location● Live queueReport / completion noteService Vendors
Site access coordinationProfile + request dataRole / vessel / location● Live queueReport / completion noteService Vendors
Quote and approval routingProfile + request dataRole / vessel / location● Live queueReport / completion noteService Vendors
Check-in and check-outProfile + request dataRole / vessel / location● Live queueReport / completion noteService Vendors
Completion evidenceProfile + request dataRole / vessel / location● Live queueReport / completion noteService Vendors
The vendor’s day
Built for the hours between the first call and the signed-off job.
A working vendor day rarely fails at the workmanship — it fails around it. The scope arrives as a voicemail, the gate code changes, the deckhand who requested the work is off rotation, and the photo that proves the job was done right lives in a text thread nobody can find a month later.
Each service in this catalog exists to remove one of those failure points. Dispatch carries the full scope so crews arrive with the right parts on the truck. Access coordination puts the gate, berth, escort, and contact in the work order itself. Quotes and scope changes route to the person who can actually say yes. Completion evidence closes the job against the visit — not against someone’s memory of it.
Read this page as a toolkit
Start with the dispatch queue — that alone replaces the phone-and-text shuffle. Add quote routing, recurring programs, and performance visibility as the management agencies, marinas, and fleets you serve run more of their port calls through MERIDIAN.
Every service card expands with rollover or tap detail; the matrix above shows how each one moves from intake to output.
Example lifecycle
One service request, start to sign-off.
A typical run, kept generic on purpose: a raw-water pump on a visiting motor yacht starts weeping two days before departure.
1 · Request raised
The captain flags the pump to the management agency. The agency turns it into a scoped work order — photos of the pump, engine-room access notes, and the departure deadline attached.
2 · Dispatch received
The job lands in your queue with vessel, berth, priority, due window, and the engineer’s contact. You accept it, and the agency sees the acceptance immediately.
3 · Quote in context
You quote the reseal and flag a replacement impeller as a recommended extra. The quote routes to the right approver with the photos beside it — no forwarded email chains.
4 · Access confirmed
The marina’s access window, delivery route, and gate contact are on the work order. You check in on arrival, and the dock desk sees your crew on site.
5 · Work with evidence
Reseal done, impeller swapped. You attach before-and-after photos, the part numbers, and a note on the belt you’d watch at the next haul-out.
6 · Close the loop
Your completion record closes against the visit. The engineer confirms, the agency releases the job, and the whole trail stays on the vessel’s file for next time.
Questions
Frequently asked about services.
Do I have to use the whole catalog?
No. Most vendors start with the dispatch queue and completion evidence, then add quote routing, recurring programs, and performance visibility as more of their work arrives through MERIDIAN.
Can I decline a dispatched job?
Yes. Accept or decline from the queue; a decline goes straight back to the dispatcher so the work can be re-routed without a phone chase.
How do scope changes and extras work?
Raise them on the job itself. A scope change or recommended extra routes to the requester as a quote item, and the approval threshold is visible before you start the additional work.
What counts as completion evidence?
Photos, notes, receipts, part numbers, meter readings, and next-step recommendations — whatever your trade uses to prove the work. It attaches to the visit and stays on the record.
Does this replace my invoicing or accounting?
No. MERIDIAN carries the quote, approval, and completion trail; your invoicing stays yours. Accounting and calendar integrations are part of the upper vendor tiers on the plans page.
Who sees my performance record?
The operations you work with — it is an internal coordination record, not a public ranking. It reflects response, completion notes, and exceptions on jobs you were dispatched to.
Next page
Translate these services into workflow states.
The workflow page shows how intake, review, assignment, execution, updates, and close-out should feel for service vendors.
Get started
Put these services to work on your next dispatch.
Join free when a subscribing operation invites you, or ask about the vendor workspace tiers. Access is reviewed and routed — guest workspaces are approved manually.