Notices and tenant communicationProfile + request dataRole / vessel / location● Live queueReport / completion noteMarina Operators
Day to day
Built for the way a marina morning actually goes.
By opening time the desk already has a pedestal fault called in from the docks, a tenant email about a parking pass, a transient inquiry with vessel particulars attached, and a vendor waiting at the gate. None of it arrived in the same channel, and all of it is your team’s to route.
MERIDIAN gives each of those moments one intake and one owner. The pedestal fault becomes a utility ticket with a slip number. The parking request lands in the tenant desk with the tenant’s history attached. The transient inquiry opens a dockage intake with LOA, beam, draft, and power needs already structured. The vendor’s gate arrival checks against a scheduled work order and an access window. Nothing depends on whoever happened to answer the phone.
Why structure matters
Requests that arrive as calls, texts, and walk-ups get resolved from memory — and disputed from memory. Structured intake means every request carries its slip, category, priority, and completion evidence from the first minute.
The same desk serves resident tenants, transient visits, staff, and service vendors — each scoped to their own view.
Service request lifecycle
One pedestal fault, start to finish.
A worked example of how a single tenant request moves through the service desk — the same lifecycle every service on this page follows.
Report
A resident tenant reports a dead power pedestal at their slip from the tenant portal. The ticket opens with slip, category, priority, and a photo attached.
Route
The desk classifies it as a utility fault, links the affected pedestal and meter, and routes it to maintenance with a target response window.
Assign
Maintenance assigns an electrician from the vendor list, with scope, dock access notes, and an access window the tenant can see.
Execute
The vendor completes the repair, attaches completion photos, and records the meter state. The work order closes with evidence, not a verbal all-clear.
Close and report
The tenant gets the completion note automatically. The ticket, its response time, and the vendor record roll into manager reporting.
Next page
Translate these services into workflow states.
The workflow page shows how intake, review, assignment, execution, updates, and close-out should feel for marina operators.
Do tenants have to use the portal for every request?
No — walk-ups, calls, and radio requests still happen. Staff log them into the same desk in seconds, so every request is trackable regardless of how it arrived.
Can we limit which services each tenant can request?
Yes — the request catalog is scoped by role and tenancy. Resident tenants, transient visitors, and vendors each see only the categories that apply to them.
How do transient requests differ from resident tickets?
Transient dockage intake collects vessel particulars, stay duration, and services needed before assignment, then hands off to the same work-order and notice machinery once the vessel is alongside.
Do vendors work inside the same system?
Yes — service vendors receive scoped work orders with access windows and evidence requirements. They see their jobs, not your operation.
What does management get out of structured services?
Manager reporting summarizes request volume, response times, unresolved work orders, and occupancy — the picture a property team needs before staffing, pricing, or capital decisions.
Get started
Put every request on one desk.
See how these services map to your docks, tenants, and vendors. Access is reviewed and routed — guest workspaces are approved manually.