Arrival and departure queue
See expected arrivals, ETAs, vessel class, LOA/draft, requested services, and readiness blockers.
Designed for review, triage, assignment, and communication before the vessel is physically on approach.
Services for Harbor Master
Each service card includes rollover or tap details for deeper explanation without interrupting the page flow.
See expected arrivals, ETAs, vessel class, LOA/draft, requested services, and readiness blockers.
Designed for review, triage, assignment, and communication before the vessel is physically on approach.
Match vessel requirements to availability, restrictions, service needs, and local operating constraints.
Supports berth suitability notes, power/water needs, draft, LOA, duration, and conflict flags.
Track transient applications, commercial permits, insurance, certificates, crew/guest documents, and missing items.
Queues can separate submitted, incomplete, under review, approved, and declined items.
Publish operational notices, restriction zones, dock closures, weather impacts, maintenance work, and safety updates.
Send notices to affected vessel classes, tenants, staff, vendors, or berth zones.
Record blocked berths, vessel issues, weather impacts, service conflicts, complaints, and response actions.
Each item has responsible party, status, location, urgency, and follow-up record.
Keep resident tenants, transient visitors, operators, and service vendors informed through status updates and notices.
Designed to reduce front-desk phone traffic and repetitive manual status updates.
Coordinate fuel, waste, maintenance, utilities, closures, crew access, and vendor activity that affects harbor operations.
Services can be tied to berth zones, docks, active vessels, and scheduled restrictions.
Summarize movements, open exceptions, permits, berth status, notices, incidents, and next-shift priorities.
A consistent record for operations teams and leadership review.
The desk behind the catalog
A port-office morning rarely starts with a dashboard. It starts with a radio call about an early arrival, an insurance certificate that still has not landed, a berth blocked by overnight maintenance, and a charter operator asking when the fuel dock reopens.
Each service above maps to one of those interruptions. The queue absorbs the radio call, the review list holds the missing document, the exception desk owns the blocked berth, and the notice engine answers the fuel-dock question once — for every tenant asking it. The catalog is not a feature list; it is the desk’s actual workload, given structure.
Requests arrive from management agencies coordinating a visit, captains and crews on approach, resident tenants, commercial and charter operators, and your own dock staff — each through an intake scoped to their role.
The harbor office stays the deciding seat: intake is structured, but assignment, review, and notices remain yours.
Service matrix
Every service is structured as an intake, routing rule, operating workflow, and completion output.
Example lifecycle
A visiting motor yacht requests a multi-night berth with shore power — here is how that single request moves through the services above.
The vessel’s management agency submits the stay: LOA, draft, power need, duration, and requested services, with the permit packet attached.
The desk checks the packet against requirements. The insurance certificate is missing, so the item is flagged incomplete and the requester sees exactly what is outstanding.
Once complete, the request is matched to an available berth. A power constraint on the finger pier is recorded on the assignment, so the crew arrives informed.
The assignment triggers scoped updates: the agency and captain get the berth and window, adjacent tenants get a movement notice, and the fuel vendor sees its confirmed service slot.
On departure the record closes with services delivered, exceptions logged, and a completion note that flows into the daily harbor report for the next shift.
Next page
The workflow page shows how intake, review, assignment, execution, updates, and close-out should feel for harbor master.
Questions
Management agencies, captains and crews, resident tenants, commercial and charter operators, and your own staff — each through an intake scoped to their role. The desk decides what gets assigned.
The desk logs them into the same queue, so a called-in request is tracked exactly like a submitted one — nothing lives only in a notepad.
Yes. A request can be declined with a recorded reason, sent back as incomplete, or redirected to a vendor or another queue — and the requester sees the status either way.
Yes — the review queue separates submitted, incomplete, under review, approved, and declined items, so a missing certificate blocks assignment visibly instead of surfacing at the dock.
Every completed, declined, or still-open item carries into the daily report, so the shift closes with a record instead of a reconstruction.
Get started
See how these services map onto your harbor’s actual queues, or request a walkthrough tailored to your operation. Access is reviewed and routed — guest workspaces are approved manually.