Single-team clubs have a communication problem. Multi-team clubs have twelve of them, plus a thirteenth: the club itself, which has to talk to everyone and is not sure how.
This post is for the sports club, the music school, the scout group with three sections or the swimming club with squads from age six to masters. Anywhere a club is really a club of clubs.
How it usually looks
Each team has a chat, made by whoever coached first. The club has a Facebook Page nobody under forty reads. The committee has an email thread. Somewhere there is a spreadsheet of members that was accurate in March.
When the club needs to tell everyone the hall is closed next week, the chair messages twelve coaches and hopes. Three coaches forward it the same evening, four the next day, and the rest assume someone else did. On Thursday, two teams turn up at a locked door.
When a coach leaves, their team's chat leaves with them. The new coach starts a fresh one and loses the history, the parents' numbers and the pinned message about kit.
The three layers every multi-team club has
It helps to name them, because most tools only give you one.
The club layer. Things everyone needs: facilities, the AGM, the summer party, the code of conduct. One-way, rare, important.
The team layer. Training times, match-day plans, who is driving. Two-way, frequent, only interesting to that team.
The organizer layer. Coaches, committee, volunteers. Conversations the members should not be in, about the members.
A single chat flattens all three into one column. A Facebook Group puts all three into one feed. Either way, the club-layer notice competes with "who has Oscar's shin pads?"
What a working setup looks like
One space for the club, one group per team. Members join the club once, then belong to the teams they are actually in. A parent with a child in U9 and another in U13 sees both, and nothing else. The club's own announcements reach everyone, in every team, without anyone forwarding anything.
Announcements separate from chat, at every layer. A channel where only the organizers post, next to one where everyone does. The locked-door message goes in the first; the shin pads go in the second.
Events belong to the team that runs them. U9 training is a recurring event in the U9 group, with its own yes-and-no RSVPs. The club tournament is an event at club level and appears for everyone. Nobody is asked about a session that is not theirs.
Roles per team, not per person. A coach is an admin of their team's group, and only that. The committee sees across the club. When a coach leaves, the group stays and the next coach is given the role; the history, the files and the parents come with it. That handover is where most clubs get caught out, and the guide to roles and permissions has the checklist.
One member list. Not twelve address books in twelve phones. Who is in the club, which teams they are on and who the parent contact is, in one place that survives a coach's phone being replaced.
The question of the under-tens
A multi-team club nearly always has children in it, and that changes who should be in which room. Parents belong in the team group; the children mostly do not. The coaches' channel should be invisible to both. If your tool cannot make a channel invisible to a member of the club, it is not a club tool. It is a chat.
Start with the club layer
If you only fix one thing, make the club-level announcement reach every member without a chain of forwards. That is the message that costs the most when it fails, and it is the easiest to move: one announcement channel, every member in it, organizers only posting.
Then move one team, ideally the one with the most engaged coach, and let the others ask why their team is not on it yet. A club that migrates team by team, with one weekly session set up properly in each, is done within a season. The mechanics of each move are in the afternoon-long migration plan.
Joyn is built around exactly this shape: a space for the club, and groups with their own channels, events and files inside it. The free plan covers up to 100 members and two groups, enough to pilot the club layer plus one team; a full multi-team club runs on Team or Community. Setting up the first group takes less time than finding the current spreadsheet.