When a Kiwi Rowing Club Outgrows the Shared Google Sheet

How big is the spreadsheet problem in NZ rowing?

Nobody has published a count of Kiwi clubs still leaning on Google Sheets, so this article will not invent one. What is countable is the size of the affiliated population, plus the long-standing audit literature on what happens when a Sheet picks up its second and third editor.

EuSpRIG's 88% number is the most-cited spreadsheet error baseline in the audit literature. The point is not that your boat sign-out Sheet is throwing wrong totals today - the point is that the error pattern is structural. Multi-editor Google Sheets erode faster than the single-author Excel files Panko studied, so the real-world figure is probably worse.

Where spreadsheets actually break

Google Sheets and Excel are not bad software. They are extraordinary tools - for one editor, doing one job, with no real-time conflicts. Clubs ask them to do something else: handle scheduling that two coxes are trying to update on phones at the same time, hold member data five committee logins can see when only two should, and survive a committee changeover without losing the colour-coded knowledge baked into the previous treasurer's formatting. The failure happens in three predictable places.

The first place is the shared boat sign-out tab. You build a clean grid - quads, fours, doubles and singles down the side, half-hour slots across the top - and for three weeks it is a thing of beauty. Then someone signs out the Filippi eight on Saturday morning at 0600 without realising the captain pinned it for the school squad's Maadi trial, because the captain pinned it by colouring the cell yellow and the cox on the phone could not see the colour clearly. Then a member working in offline mode syncs back in and overwrites a booking that was already moved. By the end of the Karapiro block the Sheet has merged cells, a "DO NOT EDIT" row in red, and a note at the top reading if your name is in green please check with Tom before launching.

The second place is the member register. The treasurer keeps one list with subs status. The captain keeps another with rowing categories - novice, senior, masters. The welfare officer keeps a third with emergency contacts and medical conditions, in a Sheet only she should see but which is in fact accessible to everyone on the club Google account. Privacy Act 2020 IPP 5 - storage and security of personal information - covers that situation explicitly. A Sheet shared with five logins because nobody wanted to set up separate accounts is the failure mode IPP 5 was written for.

The third place is the committee handover, which lands harder now that ISA 2022 is in force. The incoming captain inherits a Drive folder full of files named fleet_status_v3_FINAL_use_this_one.xlsx alongside the live Google Sheets. The Incorporated Societies Act 2022 makes the new committee formally responsible for maintaining a register of members - name, contact, the date they joined, the date they ceased to be a member. A Drive folder of half-broken Sheets is not the evidence the Registrar would want to see if anything ever escalated.

None of this is laziness. The failures are baked into the format. A Sheet is built for one author. Asking it to serve a treasurer, a captain, three coaches and 40 rowers at once is asking a tool to do something it was never designed for. The specific incident that pushed Row HQ into existence was losing a coxed four lineup the morning of a regatta, because the lineup lived in a personal Drive and the person who owned the Drive was off the grid. Three rowers half-remembered the seating. None of the half-memories matched.

What to replace first

You do not need to migrate everything in one go. Most clubs get better outcomes by replacing the loudest pain point first, banking the win, showing the committee what changed, and moving on. The sequence is the same at most Kiwi clubs.

1. Boat booking. This is the row in the verdict that earns its place. Swap the shared boat sign-out Sheet for a system that holds availability in a real database, blocks double-bookings at the schema level, and shows the cox on the phone the same state the captain sees on the laptop. A purpose-built boat booking system removes the entire ghost-booking class of problem on day one, because there is one source of truth and the database refuses to write a conflict.

2. Session attendance. The standard NZ pattern is a WhatsApp poll on the Wednesday-night squad chat or a Google Form pinned in a thread. Replace it with one-tap confirmation tied to specific outings, so the coach can see who is in the boat before they leave home and rowers get an automatic reminder the night before. Training session management handles attendance, lineup and a coach's outing notes end to end.

3. Member contact details and emergency contacts. One member database, with permission tiers that let the welfare officer see medical notes the coaches cannot, gives you the ISA 2022 register and the Privacy Act 2020 IPP 5 controls at the same time. A member self-service portal moves the maintenance burden to the rower - they update their own phone number, their own emergency contact, their own medical notes - and the committee stops chasing renewal-time updates.

4. Crew lineups and saved configurations. Coaches who rebuild lineups from scratch every Tuesday and Thursday morning are spending twenty minutes per session on something that should be a two-minute task. Coach tools with saved crew configurations and skill-based pairing matter especially during Maadi trial blocks, when a school programme is rotating 30 rowers through seven boats and the trial seat order changes daily.

What to keep

Plenty of Sheets earn their place. The AGM budget model the treasurer rebuilds once a year, the RowIT entry tracker that gets used for two weeks before the South Island Champs, the boat repair log the equipment manager has been refining since 2021 - if a file has one editor and serves one annual task, leave it where it is. Replacing spreadsheets is a practical exercise, not a moral one. Replace the ones causing weekly grief. Leave the rest.

A reasonable rule of thumb: if a Sheet has one author, lives in one person's Drive, and nobody outside the committee needs to read it in real time, it is doing fine. Leave it alone.

How to evaluate the alternatives

There are three categories of replacement and most NZ clubs pick the wrong one because they search for the obvious AU/NZ generic first.

Generic club management software. Hello Club, Friendly Manager and similar AU/NZ-familiar platforms cover everything from netball to pottery clubs. They are perfectly capable products. The problem is that boat booking is not the same workflow as court booking, and a coxless four does not behave like a yoga mat reservation. You can configure these tools for rowing, but the hours you spend doing that - building a custom "asset" type for boats, working out how to express the cox seat, hacking the membership categories to cover novice, senior and masters - usually add up to more than a year of the difference in monthly cost. Worth pricing both options, but price the configuration hours too.

Rowing-specific platforms. Built around the actual concepts: boats, crews, seat orders, RowIT regatta entries, Maadi-style multi-day trials. Row HQ is in this category. The fair price comparison is the generic platform's monthly fee plus whatever an hour of committee-volunteer time is worth, multiplied by the configuration hours.

Custom-built solutions. The pattern: a coding-capable member offers to build something for the club, usually in their spare time, usually for free. These can work brilliantly for one or two seasons. The single point of failure is the volunteer. The day they move to Wellington for a job, take on a new baby, or get a contract that uses their evenings, the system stops being maintained. If your member-data future depends on one person's ongoing goodwill, plan for the day that goodwill ends.

Migrating without losing the past

The objection that lands hardest in the committee room is losing historical data. Years of attendance logs, race results, race numbers, training notes - they sit in old Sheets and feel important even when nobody has opened them in two seasons. The reality: Google Sheets is the easiest source format to migrate from. File > Download > Comma-separated values gives you a clean export per tab. Every modern club platform accepts those CSVs.

Step one is audit. Open every Sheet in the club Drive, name the contents, sort each tab into current data, historical archive, or duplicate. Most clubs find half their files are stale copies of other stale copies, kept because nobody wanted to be the one to press delete.

Step two is cleaning the current data. Standardise the column headings so every Sheet calls the same field the same thing. Strip the conditional-formatting colour codes that only made sense to the 2024 treasurer. Normalise phone numbers to a consistent format - +64 or 0 prefix, not a mix. This is where the long-running data-quality problems surface.

Step three is staged import. Members and emergency contacts first, because everything else hangs off the member ID. Boats next. Session templates after that. Historical attendance last, and only if the club has decided to keep it. A platform worth paying for will do most of the actual import work for you.

Step four is two weeks of parallel running. This is the step every club skips and every club regrets skipping. Keep the old Sheets open and visible but make them read-only. New bookings, new attendance, new member updates go in the new system only. After a fortnight of nothing breaking, lock the Sheets to view-only and stop maintaining them.

The committee meeting where this gets decided

The other reason clubs stay on Google Sheets longer than they should is the committee meeting dynamic. Someone raises the idea of switching. Someone asks what it costs in NZD per month. The room does fast mental arithmetic against the membership-fee income, decides the answer is "a lot", and the meeting ends with let's look at it again at the next AGM.

A better frame: what is the current setup already costing in volunteer time? If the captain spends two hours every week sorting boat conflicts and chasing attendance, that is over 100 hours across the year. Cost that out at any reasonable value for the time of a skilled volunteer who could otherwise be coaching, coxing or recruiting new juniors, and the comparison stops being software versus free. It becomes software versus a hundred hours of committee attention. Most Kiwi clubs underestimate the volunteer cost because nobody invoices for it - until the captain burns out and there is nobody to replace them.

A short checklist before you switch

• Find the one Sheet causing the most weekly arguments. That is the one that moves first.
• Get the people who will actually use the new system on board - the captain, the head coach, the equipment manager. Not just the chair signing off the budget.
• Audit the Google Drive. Sort every file into current, historical or duplicate. Delete the duplicates and stop pretending you might need them again.
• Choose a rowing-specific platform over a generic AU/NZ tool. Price the configuration hours, not just the monthly fee.
• Run the new system and the Sheets in parallel for two to four weeks. Read-only on the Sheets after week one.
• Document the migration so the next committee inherits a working register, not a Drive folder and a mystery.

If you are ready to look at what replacement actually looks like

Row HQ replaces the shared boat sign-out tab, the WhatsApp attendance polls, the master member list and the saved-lineup document with one platform every committee member sees with the right permissions for their role. The member database gives you the register ISA 2022 expects of an incorporated club, and the role-based access keeps welfare-officer-only data away from the coaches and the treasurer - which is the practical answer to Privacy Act 2020 IPP 5. Because Row HQ is free for clubs up to 20 active members, a Kiwi club can run it alongside the existing Google Sheets through a full pre-Karapiro or pre-Ruataniwha training block before committing.

For the long-form comparison against Sheets, see Row HQ vs spreadsheets. For a worked case study of a club that switched, see Oundle Town Rowing Club. For who else is rowing in your part of Aotearoa, browse the New Zealand rowing clubs directory.