Twenty to thirty members, one committee member
When the same person handles the rota, the membership list and the renewals, version control is not really a problem. One spreadsheet, one editor, no conflicts.
Support Area coming soon
Quick verdict
A spreadsheet can work for a small club with one careful owner and simple records.
It starts failing when several officers edit copies, members chase updates and duties sit elsewhere.
Move when version control, permissions and handovers cost more effort than the software would.
Keep an export and clear ownership even after moving.
Excel and Google Sheets work for small UK sailing clubs with one volunteer admin and a tight committee. They crack at around fifty members, the point where two people start editing the same workbook and member self-service becomes the bottleneck. SailHQ replaces the spreadsheet with a live system members use directly, with audit logs the committee can show if anyone asks. CSV import from your existing sheet is free.
When the same person handles the rota, the membership list and the renewals, version control is not really a problem. One spreadsheet, one editor, no conflicts.
One or two membership types, no households. A flat list with names, emails and a tick box for paid is all you really need.
If new members all join through word of mouth and a paper form at the AGM, you do not need a public registration funnel. A spreadsheet captures what arrives.
Six races a season, a couple of duty types, the same handful of volunteers. Pinning a printed rota on the noticeboard works fine and the committee can fix gaps in person.
If your club fits these patterns, the spreadsheet is doing what it should. The rest of this page is for clubs that have outgrown them.
The race secretary edits the rota on Sunday. The membership secretary edits the same workbook on Monday. Two versions exist by Tuesday. Two weeks later the membership secretary realises an edit got overwritten.
Cloud-shared sheets help, but they do not fix the underlying issue: a spreadsheet is not designed for several people to edit different parts of it at the same time.
Members do not have access to the live spreadsheet, so they ask the duty officer when their next slot is. Every time. Swap requests turn into WhatsApp threads with three people copied in and no record of who agreed what.
A spreadsheet is read-only as far as the membership is concerned. They cannot self-serve, so the committee becomes the help desk for every routine question.
A wide spreadsheet on a phone is a row of frozen panes, pinch zoom and tiny text. Members on the dock checking what they signed up for next Saturday give up and message the committee instead.
Most members run their lives from their phones. If your club admin only really works on a laptop, you are forcing a workflow that does not fit how people actually live.
Member data sitting in a spreadsheet on three committee members' laptops sits awkwardly with the ICO's security expectations under UK GDPR. There is no record of who viewed what, no record of who edited which row, and no clean process for a member who asks for their data to be deleted.
If a member ever raises a concern, "we have a spreadsheet" is not the answer the committee wants to give.
Leg 1
Leg 2
Leg 3
Leg 4
Leg 5
Scoring: 0-1 nos - spreadsheet is fine, no need to switch. 2-3 nos - the spreadsheet is starting to cost more time than it saves. 4-5 nos - the committee is already doing platform work by hand and is one resignation away from losing the institutional knowledge.
| Feature | Spreadsheets | SailHQ |
|---|---|---|
| Member directory | Yes - flat list | Searchable, with household links and roles |
| Online registration | Manual entry from a form | Public sign-up with admin approval queue |
| Duty rota | Static grid, manual edits | Live system, gaps highlighted, calendar view |
| Swap requests | Email or WhatsApp | In-platform request and approval |
| Qualification gating | Trust the admin to remember | Enforced - safety boat slots only fillable by qualified members |
| Household billing | Manual reconciliation | Households grouped, fees handled per family |
| Member self-service | None | Full member portal |
| Audit trail (who changed what) | Limited at best | Status change logs across membership |
| Mobile access | Painful | Mobile-first, add to home screen |
| Live weather | Not possible | Live wind from club coordinates |
| Public website integration | Separate | Public registration page tied to the platform |
| Data export | Native | CSV export at any time |
Spreadsheets do real work for member directories and data export. They cannot do member-facing self-service or qualification enforcement, because that's not what they're for.
Every member logs in, sees their next duties, their boats, their household, their renewal date. They update their own contact details. The committee stops being a help desk for "what's my email on file again".
Members sign up for vacant slots themselves, gated by their qualifications. Swap requests sit in an approval queue rather than buried in a group chat. The committee approves with one click and the rota updates everywhere at once.
Tiered membership types with proration for mid-season joins. Households grouped together. Public sign-ups land in an approval queue. The "who has actually paid this year" question stops being a guess.
Status changes on memberships are logged. Permission changes are logged. If a member raises a concern, the committee can show exactly what happened and when. UK GDPR stops being a yearly worry.
Send the spreadsheet, the SailHQ team maps the columns, members get invite links to log in and confirm their details. The history of who joined when stays intact, the boat list carries across, qualifications and expiry dates carry across.
Same series, same race days, same fleets, same handicap system. Your programme drives the platform, not the other way round.
Custom roles map to your existing committee titles. Treasurer, race secretary, membership secretary. Permissions match the job, not a generic template.
Club name, logo, colours and login background all your own. Members log into something that looks like the club, not a generic SaaS product.
Migration help is included at no extra cost. There is no expectation that the committee learns a CSV format or maps fields by hand. You send what you have, the team handles the rest.
Talk to the team about your spreadsheetTypical migration timeline
Leg 1
Leg 2
Leg 3
Leg 4
Free
In licence cost. The real cost is committee evenings spent on admin that should run itself.
From £0.65
Per member per month, dropping as your club grows. See the full pricing calculator.
For a fifty-member club that's around £390 a year. Whether that's worth it comes down to how many committee evenings you're currently spending on admin, and how comfortable you are leaving member data sitting in shared spreadsheets. For most clubs that have outgrown the spreadsheet, the maths is straightforward once the time saved is accounted for.
More questions? Read the full FAQ or contact the team.