How to run rowing club boat bookings without the spreadsheet

The Saturday morning problem

Most rowing clubs hit the same wall. Two crews turn up for the same eight. A single is out on the water when the person who booked it arrives. A coach spends Friday night texting nine people to find out who is coming, then rebuilds the crew at the landing stage because two of them were not.

None of this is a people problem. It is a records problem. The boat list lives in one place, the availability in another, the crew plan in a coach's head, and the response to "who's in tomorrow" scattered across a group chat that also carries the bake sale.

This guide covers what a rowing club needs from a boat booking setup, where the spreadsheet stops working, and what to check before you pick a system. It is written for the captain, the coach or the committee member who has ended up owning the problem.

Why the spreadsheet stops working

A shared spreadsheet handles bookings for a while. It is free and everyone knows how to open it. It fails at three predictable points.

The first is concurrency. Two people edit the same cell on a Thursday evening and one of them loses. Nobody notices until Saturday.

The second is that a spreadsheet only knows what someone typed into it. It cannot tell you that the pair you have just booked is already down for repair, or that the person you put at stroke has only ever rowed bow side. The knowledge exists at the club. It just does not exist in the sheet.

The third is that a booking is not the whole job. A club outing is a boat, a crew, a time and a plan. The sheet records one of those four. The rest is held together by messages.

When British Rowing published its list of online club management tools, it described FitClub in terms of boat booking, sign out and sign in, and repairs logging in the same breath. That pairing is the point. Bookings and boat condition belong together.

What a booking system has to do

Strip the marketing back and a rowing booking system needs to do six things.

Know the fleet. Every hull, its class, and whether it is available, booked or off the water for repair. Singles need this as much as the club eights, because singles are where private bookings and club bookings collide.

Stop double bookings. If one crew has the boat from 07:00 to 08:30, nobody else can. That sounds obvious. It is the one thing a spreadsheet cannot enforce.

Attach the crew to the booking. A boat with no named crew is a guess. The booking should carry who is rowing, and ideally what side they row and how experienced they are, so the coach can see the problem before the crew does.

Collect responses against a session. Publish the session, let members say yes or no, and let the coach work from that list. The alternative is a coach counting thumbs-up emojis.

Work on a phone at the boathouse. The moment a booking matters is the moment someone is standing in front of the rack. If the system only works on a laptop in the club office, people will go back to the whiteboard.

Keep a record afterwards. Outing logs, who took the boat out, and any damage reported on return. This is what a committee wants when a rigger comes back bent.

Start with the sessions, not the boats

Clubs often begin by loading the fleet and expect bookings to follow. In practice the better order is sessions first.

A session is the thing members respond to. Tuesday erg. Saturday 07:30 water session. Sunday juniors. Once responses come in, the coach can see who is available, build crews from the people who actually said yes, and only then allocate hulls. Booking the boat is the last step, not the first.

This order also means a member who cannot see a boat list still has a reason to open the system. They are answering "are you coming". The booking takes care of itself behind that.

Rowing side, experience and the crew list

Any general sports app can do attendance. Rowing has two extra fields that matter: which side someone rows and how experienced they are.

A coach putting a four together needs two bow side and two stroke side. If the system knows that, it can show it in the response list. If the system does not, the coach is back to memory or to asking in the chat. The same goes for experience. A novice in an outing planned for a senior crew is a safety question, not a preference.

Look for a system where these live on the member record and appear when you are building the crew, rather than in a profile page nobody opens.

Juniors and parents

If the club has a junior squad, the person responding to a session is often a parent, not the rower. The system needs to let a parent manage a junior's responses and hold the consent information the club asks for at the start of the season.

Without this, junior sessions run on a separate WhatsApp group and paper forms in a folder. That is where clubs end up with two systems again.

What the current UK options look like

British Rowing's list of club tools, which we read for this guide, describes FitClub as a website built for rowers with boat booking and repairs logging, and ClubHub as a free membership and finance tool for affiliated clubs run through JustGo. FitClub's own site claims 5,000 active users across 100 or more clubs. ROWter, formerly GIGRota, describes itself as boat sign out, availability, groups and notifications. Some clubs use a general team app for the messaging and keep a spreadsheet for the boats.

Each of those covers part of the job. What none of the pages we read explains is how the boat, the crew and the session connect. That gap is usually where a club feels the pain.

Where RowHQ fits

We built RowHQ around that connection. Sessions, on the water and on the erg, are published with a place for members to respond. Coaches build crews from those responses with rowing side and experience showing. Boat bookings sit alongside the crew plan and the club fleet, so you check the hull is free before you allocate it, and club boats and singles are both handled as named hulls rather than blank calendar slots.

Member profiles, membership records and club information sit in the same place, so the committee has one reference for the administration and parents can handle junior responses and consent. Outing logs and incident records support the club's own processes on the water. Regatta and event pages collect interest and hold deadlines.

RowHQ works in a browser, and there are apps for iPhone and Android for members who want one. Clubs can use their own logo, colours and a club subdomain. For current pricing, country coverage and how a club gets started, use the RowHQ website at rowhq.app.

A checklist before you commit to any system

Run these against whatever you are considering, including the free ones.

1. Can two people book the same boat for the same time? If yes, it is a calendar, not a booking system.
2. Does the member record hold rowing side and experience, and do they show when building a crew?
3. Can a parent respond for a junior?
4. Does it work on a phone at the rack, with the boat list loading in seconds?
5. Is there a place to log damage on return, and does that mark the boat unavailable?
6. Can a session be published once and responses collected against it?
7. Can the committee get member data out as an export if the club moves on later?
8. What does it cost per year for your member count, and what happens to the price as the club grows?

Ask the last one directly. A per-member price that looks small at 40 members reads differently at 200.

Moving off the spreadsheet

Do not try to move everything in one weekend. A workable order is:

1. Load the fleet with honest availability. Mark the boats that are actually off the water.
2. Add members, with side and experience for the active rowers first.
3. Publish next week's sessions and ask people to respond in the system instead of the chat.
4. Book boats against those sessions for one week.
5. Keep the spreadsheet open, read only, for two weeks as a fallback. Then close it.

The step most clubs skip is the third. If responses keep arriving in the chat, the coach keeps rebuilding crews by hand and the booking system becomes a second job. Ask for responses in one place, and be boring about repeating that request for a month.

When a spreadsheet is still fine

A club with one boat class, a dozen members and a single outing a week does not need any of this. A shared sheet and a group chat will do. The point at which it stops being fine is usually the first season with a junior squad, a second coach, or a private single that someone else keeps taking out.

If you are at that point, the club has already outgrown the sheet. The question is only which system replaces it, and whether it treats the boat, the crew and the session as one thing or three.

The full SportsHQ collection, with guides for sailing and paddling clubs, is under sports clubs.