Choose request type
Tenant selects maintenance, utility, access, delivery, document, or general support.
Workflow path
How the marina tenants version moves work forward.
The process language changes by audience, but the underlying pattern is consistent: intake, route, execute, update, and close out.
Why a workflow at all
For a tenant, “workflow” means one thing: never wondering where a request stands.
Coordinating with a busy marina usually runs on calls to the office, notes at the dock desk, and texts to whoever answered last time. Each thread works until it drops. The tenant workflow replaces those threads with a single visible path — the same path every time, whether it is a leaking hose bib, a package at the gate, or a contractor visit — so the office and the tenant are always looking at the same state of the same request.
Add location and detail
Slip, vessel, photo, urgency, contact preference, and availability are captured.
Marina routes it
The office assigns staff or vendor and sets a target window.
Tenant gets updates
Status changes, questions, schedule windows, and completion notes are visible.
History remains available
Past requests and notices stay attached to the tenant profile.
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 phone-tag — Tenants can request, track, and confirm work without repeated desk calls.
- Faster routing — The right team receives enough detail at submission.
- Better transparency — Tenants see whether the item is queued, scheduled, in progress, or complete.
- Useful history — Recurring issues and service records are easier to reference.
Queue preview
Example work in motion.
The same component set supports rollups for management, dock desks, tenants, and vendors.
Open requests5
Scheduled2
Notices3
Docs due1
New 02
Pedestal issuePhoto attached
Package deliveryGate code requested
Scheduled 02
Vendor accessFriday 10:00
Pump-outWindow confirmed
In Progress 02
Dock maintenanceCrew assigned
Parking passOffice review
Complete 02
Water hose repairClosed with photo
Vessel doc updateAccepted
Worked example
One workflow, end to end: a vendor visit.
A generic contractor-visit example, narrated step by step — the same intake, route, execute, update, close-out pattern applied to a real coordination job.
1 — Request
Your vessel needs work you have arranged with an outside contractor. You submit a vendor access request: company, technician name, requested day, arrival window, and which dock they need to reach.
2 — Review
The marina office reviews the visit against its dock rules and the paperwork it already holds, then clears it — or asks a clarifying question in the same request thread instead of a phone chase.
3 — Scheduled
The visit appears on your board as Scheduled with the confirmed window, and the dock desk and gate know it is coming. No surprises at the gate, no vouching in person.
4 — On site
The vendor checks in on arrival day and the request moves to In Progress. Any notes from the visit attach to the thread you started, where you can see them as they land.
5 — Close-out
The visit closes with a completion note. You, the office, and the vendor worked from one record the whole way — and it stays in your history for the next visit.
Workflow questions
What tenants ask about the workflow.
Straight answers about who moves a request, how updates arrive, and what happens when plans change.
Who moves my request through the statuses?
The marina team does, as they work it. You watch the request move from received to scheduled to in progress to complete — you are never responsible for updating the board.
Will I be asked for the same details twice?
No. Your slip, vessel profile, and documents travel with every request, so intake starts from what is already known instead of a blank form.
What if a scheduled window slips?
The window is updated on the request itself, so the change reaches you the same way the original schedule did — in the thread, not in a missed call.
Can a representative handle this for me?
Yes. Tenant representatives can be invited into the same scoped workspace, submitting and tracking requests on your behalf with the same visibility.
Is there anything to learn?
Only two ideas: request types and statuses. If you can send a tracked message, you can run this workflow.
What happens after close-out?
The finished request joins your history with its notes and photos — a running service record for your slip and vessel instead of a stack of receipts.
Get started
One visible path for every request.
If your marina runs MERIDIAN, ask them to invite you — tenant workspaces are private, permissioned, and invitation-based. Or reach out and we will point you to the right operating team.