Choosing marina management software is a five-to-ten year decision made on the basis of a forty-minute demonstration. Every system in the market looks capable in that forty minutes, because the demonstration runs on clean data, full signal and a salesperson who knows exactly which button not to press. The differences show up in the first winter. This is the framework we use when we assess systems on behalf of Australian marinas, and it is deliberately weighted toward the things that fail on a wet Thursday rather than the things that photograph well.
Does it work where the work happens
Marina work happens on the arms, not at the office desk. The single most predictive question in a software assessment is whether the dockmaster application keeps functioning at the far end of the longest arm when the signal drops, and syncs cleanly when it returns.
Ask the vendor to put the device into flight mode during the demonstration and complete a dock walk, log a fire asset defect and take a booking. If the answer is that connectivity is fine at their reference site, you have your answer.
Can it answer 'does this boat fit'
The most frequent operational question in any marina is whether an incoming vessel fits an available pen. Answering it needs berth length, usable length, beam at the widest point, depth at low water, service capacity and whether the neighbouring vessel overhangs.
Many systems store berths as a list of names and lengths, which cannot answer the question. Ask to see a casual enquiry for an over-beam catamaran assessed against the actual marina plan, and watch whether the system checks fit or simply records the booking.
Compliance evidence, not compliance checkboxes
A tick in a box is not evidence. What survives an insurance or lease audit is a timestamped record with the operator's identity, a photograph, a location and an exportable trail that cannot be edited after the fact.
- Dock walks with photographs, zones and timestamps.
- Fire asset register with service dates, defects and rectification history.
- Contractor permits with insurances, SWMS and inductions captured before arrival.
- Environmental and wildlife incident logging with a one-click export.
- An audit trail that shows who changed what and when, and cannot be quietly amended.
Money in, money out
The office should not key anything twice. Test the accounting path end to end: a casual booking taken on the arm, a contracted fee apportioned across the period, metered power and water charged, GST separated correctly, and the whole lot landing in MYOB or Xero without manual re-entry.
Then test the reporting: daily takings by category, revenue per metre, arrears ageing and a rolling forecast. If a report requires the vendor to build it for you, you will be waiting for it every time the question changes.
The pricing model matters more than the price
Per-seat pricing is the trap in this category. A marina that pays per user will ration logins, the dockmaster will share an account with the yard hand, and the audit trail — the thing you bought the system for — becomes worthless because every entry is attributed to the same login.
Look for pricing based on the size of the facility rather than the number of people using it, quoted in Australian dollars, with the implementation cost stated up front and no lock-in that outlasts your confidence in the vendor.
- Is the price in AUD, GST inclusive or exclusive, and fixed for how long?
- What does implementation, data migration and training cost, specifically?
- Are there per-transaction fees on payments, and at what rate?
- What is the exit path — can you export your full data set, in a usable format, on demand?
- Where is the support desk, and what happens at 6am Sydney time on a Saturday?
Migration risk is the real project risk
Systems rarely fail on features. They fail on the changeover — a berth register imported with the wrong usable lengths, contracted periods that do not reconcile, a hardstand diary that never made it across, and three months of staff working two systems in parallel until everyone gives up.
Ask for the migration plan in writing before you sign: what data comes across, who validates it, what the parallel period looks like, and who is accountable if the register is wrong on go-live day.
Where BerthPoint sits
We built BerthPoint because we run marina operations and could not find a system that answered the questions above. It is Australian built and hosted, priced in AUD by facility size rather than per seat, works offline on the dockmaster's iPad, checks fit against your actual marina plan, captures compliance evidence as a by-product of the work rather than as extra admin, and syncs to MYOB and Xero.
We are equally comfortable telling a marina that its current system is fine. The framework above is worth applying whichever way that lands.
Book a walkthrough of BerthPoint on your own marina plan, or send us your shortlist and we will assess it against this framework independently.
Category tags