If you already run marina software
Waiting lists alongside your marina software
Most harbours already run something for dockage, billing and reservations. We do not replace it. We do the one part it is usually weakest at: the queue in front of it, and the record of why the queue looks the way it does.
What a marina management system does
Who is moored where, what they owe, meter readings, work orders, seasonal contracts, reservations for transient boats, and the accounting behind all of it. It is the system of record for the boats that are already in the water.
What a waiting list engine does
Who is next, and why. Seniority as its own field that survives an import, separate rules for who may join and who comes first, offers that go out with a deadline and record what came back, and a written reason attached to every movement in the order.
Where the line is
When somebody wins a place we hand over their contact details and stop. We do not write the agreement, we do not take the signature, and we never stand between a harbour and the person who is about to pay it. Money your applicants pay in fees goes to your own account, not through ours. If you were hoping for one system that does everything, this is the point to know it is not us.
How the two sit side by side
The queue is the source of truth for order
Who joined when, who moved, who was passed over and why. That history is the thing a harbourmaster cannot reconstruct from a spreadsheet after the fact, and it is what an angry applicant is actually asking for.
Your system stays the source of truth for berths
We never hold the mooring plan. When a place comes free you tell us, or your system does; when somebody accepts, you put them into the system you already run.
Nothing is locked in
Every list exports as a file, and the paid plans have an API. If you leave, you leave with the queue and its whole history, including the dates people joined.
What to ask any supplier, including us
These are the questions that separate a waiting list that holds up from one that does not. Ask them of whoever you are comparing. Ask them of us.
- 1
Is the date somebody joined stored as its own field, or is it the date their row was created? An import that resets seniority costs people years.
- 2
Can an applicant see their own position, and the reason it changed, without asking staff? If seeing your own place in a queue costs extra, the queue is being held to ransom.
- 3
When somebody is moved, is there a required reason attached to the movement? A log that records what changed but not why is not an answer to a complaint.
- 4
Is a decline told apart from no answer at all, and both from being passed over? Three different things that get recorded as one are three things you cannot defend later.
- 5
Can you export everything, today, without asking? And does the export include the history, or only the current order?
- 6
Who is the merchant of record for fees your applicants pay? If the money passes through the supplier's account, you are relying on them to pass it on.
The price is on the page. You do not have to sign up to see it.