In short: Marina management software has moved from the office PC to the cloud and onto the berthing master's tablet, so it now depends on a live connection at the visitor pontoon, the fuel berth and the boatyard. Most UK marinas were never wired for that, and the gaps show up as late check-ins, missed overstays and invoices raised from memory.
Key Takeaways
- The software moved to the water's edge — Cloud platforms such as Harbour Assist are sold for use "in the office, or on the water", so the berthing master's tablet now needs a live connection at the visitor berth, not just at reception.
- Signal gaps turn into overstays and debt — When a tablet drops out mid-arrival, the boat is logged later from memory, and the unpaid-and-overstay list the software exists to produce quietly drifts out of date.
- Plan coverage around the workflow — Map where arrivals, inspections, fuel sales and lifts are actually recorded, then build one managed network that covers those points before signing the software contract.
In a nutshell

Why does marina management software struggle on the pontoon?
Marina management software struggles on the pontoon because it was designed as a cloud service, and the pontoon is usually the part of the estate with the worst connection. The weak point is the radio path between the tablet in the berthing master's hand and the internet.
Ten years ago, most UK marinas ran berthing on a desktop package in the office, a wall chart and a clipboard. The clipboard went down the pontoon, the desktop stayed in the warm, and someone reconciled the two at the end of the day. The current generation of platforms works differently. Harbour Assist, which lists Port of Ramsgate, Boatfolk, Beaulieu River, Tarbert Harbour and Aquavista among its clients, describes itself as a cloud-based system that gives the team the tools "in the office, or on the water". Moored Solutions, Metarina, MarinaOffice and DockMaster offer similar mixes of interactive berth maps, online booking with live availability, boater apps and mobile check-in. SoftwareAdvice lists Harbour Assist from £400 a month, which prices it as the core operating system of the business.
All of these products assume that the person allocating a berth, departing a boat or raising a fuel charge can reach the server at the moment they do it. In the office that assumption holds. On a visitor pontoon 300 metres from the clubhouse, behind a breakwater, with a few hundred masts and hulls between the tablet and the nearest access point, it frequently does not. Ofcom's Connected Nations reports have shown coastal and estuary locations near the bottom of the outdoor coverage tables for years, and a marina's own geometry (long, narrow, over water, a long way from the building with the broadband line) makes the local picture worse than the postcode average suggests.
What does the berthing master actually need from the network?
The berthing master needs a connection that works at every point where a booking, a payment or an inspection is recorded, at the moment it is recorded, on the busiest day of the season. That is a modest amount of data and a demanding amount of coverage.
By way of example, a typical summer Saturday at a 400-berth south coast marina involves a sequence of small, time-sensitive transactions spread across the whole site:
- Visitor arrivals at the reception pontoon, where the berth is allocated by length, beam and draught against the live map and the boat is marked as arrived.
- Fuel sales at the fuel berth, usually the most exposed point on the estate, where the charge is raised against the berth holder's account or taken by card.
- Departures and overstays, logged as boats leave, so the unpaid and overstay lists are correct before the evening walk-round.
- Yard work such as lifts, pressure washing and hard-standing moves, recorded against work orders in the boatyard, often in or beside a steel shed.
- Inspections and tasks, from pontoon defects to shore power faults, photographed and logged on the spot.
None of these needs much bandwidth. A berth allocation is a few kilobytes; a photograph of a cracked pontoon cleat is a couple of megabytes. What they need is consistency: the same dependable connection at the reception pontoon, the hammerhead, the fuel berth and the yard, with enough capacity left over when two thousand visitors' phones are on the same public cells. In practice many marinas have a tablet that works in some places, hangs in others, and needs a walk back towards the office to sync.
What happens to the data when the tablet drops out?
When the tablet drops out, the transaction is either queued, abandoned or written down to be entered later, and each of those options costs the marina something. The software's value lies in a single, current picture of who is on which berth and who has paid; every gap in coverage puts a delay into that picture.
Some apps cache work offline and sync when the connection returns, which helps, but caching has its own failure modes. Two staff can allocate the same empty berth from two offline tablets; the system resolves the conflict hours later, after both boats have tied up. A visitor marked as arrived on a tablet that has not synced does not appear on the office's occupancy view, so the next caller is told the marina has space it does not have. More commonly, staff give up on the tablet altogether in the dead zones and fall back to a notebook, which reintroduces the end-of-day reconciliation the software was bought to remove.
The commercial consequences are easy to underestimate because they are small per boat. A visitor who leaves at 06:00 before the overnight fee is collected, a fuel charge entered against the wrong account, a lift that never makes it onto the invoice: each is a few tens or hundreds of pounds. Across a season, at a marina handling several thousand visitor nights, they become a material line in the accounts, and they are precisely the leakage that features such as Harbour Assist's "highlight unpaid and overstay boats" are meant to catch. Those features only work if the arrival and departure records reach the server when they happen.
There is a customer side too. Online booking with live availability, which most platforms now offer, sets an expectation that the marina knows its occupancy in real time. A boater who books a visitor berth on an app and arrives to find it occupied, because the previous departure was never synced, is unlikely to blame the radio coverage.
Can marina Wi-Fi or a 4G dongle fix it?
Marina Wi-Fi and 4G dongles can patch individual dead spots, but neither tends to give consistent operational coverage across a whole marina estate. We see three common approaches, each with genuine strengths and clear limits.
Firstly, extending the berth-holder Wi-Fi to the staff tablets. This is the cheapest option because the access points are already on the pontoons. However, those networks are usually built for browsing in the cockpit, run on consumer-grade hardware exposed to salt spray, and are shared with every berth holder streaming in the evening. Staff traffic competes with Netflix, and a tablet roaming between access points along a long pontoon drops its session at each handover. Our earlier piece on Wi-Fi for boats covers why marina Wi-Fi so often disappoints even for its intended users.
Secondly, a SIM card in each tablet on a public mobile network. This works well where outdoor coverage is good and fails where it is not, which at many marinas means it works in the car park and fails on the outer pontoons. It also leaves the marina with no control over capacity on a busy weekend and a growing drawer of SIMs, contracts and data bundles.
Thirdly, a mobile signal booster on the clubhouse roof. Boosters can help inside a building, but Ofcom rules restrict which repeaters may be used on licensed mobile spectrum, and an indoor-focused unit does little for a tablet half a kilometre away on a floating pontoon.
Each of these is a reasonable answer to a single problem at a single spot. The difficulty is that marina management software turns connectivity into a requirement for the whole operational footprint, and that calls for a network planned as a whole.
What does a private network across the marina look like?
A private network across a marina is a small set of radio units, owned or managed on the operator's behalf, that covers the pontoons, fuel berth, boatyard and car parks with one consistent signal for staff devices and marina systems. Private 4G or 5G is the usual technology, using shared-access spectrum licensed from Ofcom for the site.
The practical difference from Wi-Fi is range and control. A single private 5G or 4G radio mounted on a mast or the clubhouse roof can typically cover several hundred metres of open water and pontoon, so a medium-sized marina may need two or three units rather than the dozens of access points a full Wi-Fi build would require. Tablets, handhelds and card readers use a SIM issued by the marina, so the operator decides which devices get on the network and how much capacity the berthing team reserves on a busy Saturday. The same network then carries other traffic the marina already wants to connect: pontoon CCTV and security, card payments at the fuel berth, smart shore-power pedestals and man overboard alarms that need to reach the night patrol.
There are trade-offs. A private network is a capital project, with radio planning, a spectrum licence and a backhaul link to budget for, and it suits marinas where the operational footprint is large enough to justify it. For a 60-berth inland site with the office beside the moorings, a well-placed Wi-Fi access point may be all that is needed. Equally, a private network covers marina staff and systems; berth holders will still want public mobile and Wi-Fi for their own phones, although the same infrastructure can carry a separate berth-holder service if the marina chooses.
How should a marina plan connectivity before changing software?
A marina should plan connectivity alongside the software procurement, because the coverage requirement follows directly from how the new system will be used. We suggest a short sequence that most operators can complete in a few weeks.
- Walk the workflow. List every place where staff will record something in the new system: reception pontoon, each visitor finger, fuel berth, lift dock, yard, dry stack, car park barrier. Note when each is busiest.
- Measure what is there. Take a tablet or handheld to each point on a busy afternoon and record whether the software loads, how long a berth allocation takes, and whether the public mobile signal holds. A simple spreadsheet of locations and results is enough.
- Ask the vendor about offline behaviour. Find out what the app does without a connection, how conflicts are resolved, and whether payments can be taken offline. The answers tell you how much a coverage gap will hurt.
- Cost the options against the footprint. Compare extending Wi-Fi, per-device SIMs and a site-wide private network against the list from step one, including the other systems (CCTV, payments, pedestals) that could share the same network.
- Phase it with the season. Install and test over the winter, so the berthing team has had a full shakedown before the first busy weekend of spring.
At time of writing, the vendors' own materials say a great deal about berth maps and boater apps and very little about the signal those features need on the water. Spending a winter afternoon walking the pontoons with a tablet and a notepad, recording where the berth map loads and where it hangs, is the cheapest first step, and it gives both the software vendor and any network supplier a concrete brief to quote against.
