WhatsApp, Messenger and Heja: The Aussie Rowing Shed Chaos Problem

Why every Aussie rowing shed ends up here

WhatsApp won the Aussie rowing scene because it was already on everyone's phone. No new account. No training session for the membership. No sign-up email going to the spam folder. You add ten people to a group, give it a sensible name, and replace phone calls and emails for a few cents a month. Messenger covers the parent side at the few schools where the parent cohort sits more on Facebook. Heja shows up where the school PE department already runs it for soccer or netball and the rowing coordinator inherits it without picking it. For announcements, every one of those tools is genuinely brilliant.

The problem starts when announcement-shaped tools get used for jobs that are not announcements. Coordinating a session takes a poll. Polling needs replies. Replies bury other messages. Other messages are about something else entirely. By Wednesday arvo the captain or director of rowing is scrolling back through 80 messages to find out who confirmed for Saturday's outing, and there are three people on the list who reacted with a thumbs up at 11pm Tuesday and never said yes in writing.

This is not a discipline problem with the membership. It is a tool problem. WhatsApp was not designed to track who said yes to a session next Saturday. It was designed to deliver messages in real time and move on. The data does not stick around in a useful shape. There is no separate field for an active confirmation. The poll feature exists, but you cannot retroactively edit a poll question if the session changes, and the results disappear into the chat history.

The seven specific failures

These are the moments where group chats visibly stop working for an Aussie rowing club or school programme. Most sheds have hit at least four of them.

1. The thumbs-up RSVP. Someone reacts with an emoji to the session announcement. Are they confirming? Acknowledging? Just lurking? Nobody knows. The captain or director of rowing has to message them privately to ask, which defeats the entire point of the broadcast.

2. The bury. A genuinely important message - boats are off the water on Sunday because of a heat-policy call or a Yarra flood warning - gets buried under chat about whose turn it is to bring sausages to the post-regatta BBQ. By Saturday night three people did not see it and arrive at the shed anyway.

3. The fragmented poll. The session organiser starts a poll. Some people vote. Some people reply with text. Some reply only on Messenger because the parent group lives there. A couple reply on Heja because that is where the school crew chat sits. The results are split across four message types and three apps and impossible to reconcile.

4. The orphan group. A group is set up for one specific regatta crew (Head of the Yarra, Australian Rowing Championships, Head of the Schoolboys or Schoolgirls). The regatta passes. The group keeps existing because nobody wants to leave first. Eight months later it has 47 unread messages of birthday emojis and one entirely different topic.

5. The new member problem. Someone joins the club or starts year 7 rowing. They are added to the senior squad WhatsApp, the women's WhatsApp, the cox group, the boat-maintenance group, the parent Messenger and the social Heja group over the course of three weeks. They miss the message about which group is actually for what. They post a question in the wrong group and get told off.

6. The committee handover (or change of director of rowing). A new captain or director of rowing takes over. They are not in the messaging history of the previous captain. They have to be added to every group across all three apps, asked who is in each, and then introduced as the new admin. By the time the handover finishes the previous captain has forgotten which groups they should leave.

7. The audit trail problem. Welfare, child safety and Rowing Australia compliance sometimes need a clear record of what was said and when. WhatsApp, Messenger and Heja messages are private to participants and not auditable in any meaningful way. For most things this does not matter. For the things where it does (school child safety, RA member protection cases, state child-safe scheme reporting), it matters a lot.

What to keep the chat apps for

The answer is not to ban WhatsApp, Messenger or Heja. The answer is to give each one the job it is good at. The chat apps are excellent for:

• Real-time announcements while people are at the shed or in transit. A flood warning. A boat repair. A change of plan in the next ten minutes.
• Quick coach-to-cox or coach-to-cox-box messages during a session.
• The committee group where five or six people who already know each other are discussing decisions in conversation form.
• Social arrangements that do not need to be tracked or recorded. BBQ after the regatta, dinner before the King's Cup race, lift to Penrith or Nagambie or West Lakes.

None of those are job-of-record activities. They are conversations that happen and then are over.

What to move out

Anything that creates data the club or school needs to refer back to should not live in WhatsApp, Messenger or Heja. That includes:

• Session RSVPs. Move to one-tap session confirmations. Members tap to confirm or decline once. The roster is visible to coaches without scrolling through three apps.
• Rack bookings. Move to a real rack booking system. The booking is the source of truth, not the message announcing it.
• Crew lineups. Move to coach tools with saved lineups. Members get notified once when the 1st VIII is finalised, not pinged six times as it changes.
• Regatta entries and travel logistics. Move to a structured form with deadlines. Australian Schools Championships entries, training camps at West Lakes or Lake Barrington, school exchange tours.
• Welfare, child safety and RA compliance records. Anything that may need to be referenced later belongs in an auditable system, not a chat group.

The transition the membership will accept

Members and parents do not want a fourth app. That is the realistic objection that defeats most attempts to clean up communications. The fix: pick one tool to handle the structured data, and let WhatsApp (plus Messenger or Heja where they already sit) keep doing the conversational job.

The pattern that works: structured stuff happens in a club or school management system. Members and parents get notified about it in the app when they log in, or by email if they prefer. They never have to open the system unless they want to confirm a session, book a rack slot, or update their details. Conversation continues in WhatsApp because that is where conversation belongs.

After about a month, something shifts. The senior squad WhatsApp group goes quieter because the operational chatter has moved to where the operational data lives. What remains is pre-session banter, post-regatta debriefs, the occasional cake debate. That is the right shape for WhatsApp.

A practical first step

If you want to test this with minimum disruption, start with one squad and one task. Pick the squad with the most active WhatsApp group (often the 1st VIII at a school, the senior squad at a club). Move session RSVPs for that squad into a structured tool for one month. Keep WhatsApp, Messenger and Heja for everything else.

At the end of the month, ask the squad two questions. Did session organisation get easier? Did anything important get missed? Almost every time the answer is yes to the first and no to the second. From there you can roll the same approach out to other squads, then move rack bookings, then crew lineups.

What this looks like with Row HQ

I built Row HQ partly because I got tired of this exact problem at my own club in England. The pattern translates straight across to Aussie clubs and rowing schools - the shed changes, the BBQ menu changes, the group-chat chaos does not. Row HQ is built around the assumption that a club or school programme already runs WhatsApp (plus a Messenger group or two and probably a Heja team for the schools cohort) and is not going to stop. It handles the structured data (sessions, RSVPs, bookings, lineups, members, regattas) and pushes notifications to the right people at the right time. The chat apps keep the social layer. They coexist deliberately - that was the design brief from day one.

For the broader case against keeping operations in spreadsheets and chat groups, see Row HQ vs spreadsheets. For a sister article on attendance tracking specifically, see the guide to training session management.