The Havoc Amateur Hockey League runs four divisions today — Bronze, Steel, Silver, and Iron — plus a board and a registered spare pool. The thing that keeps all of these populations on the same page is not a single tool or a single channel. It is a three-layer communication structure: the league talks to everyone, the league talks to captains separately, and captains talk to their teams. Each layer has a different audience, a different frequency, and a different tone. When leagues struggle with communication, it is usually because they have collapsed those three layers into one and are flooding the wrong people with the wrong messages.
This guide is HAHL's communication playbook — the parts that work, the parts that took years of getting wrong to settle on, and the silent failure modes that quietly cost leagues their renewal rate.
The Three Layers
Most leagues have one mailing list — the whole league — and try to communicate everything through it. That produces the predictable failure mode: important messages drown in operational ones, captains stop reading because half of every email does not apply to them, and players opt out of league email entirely.
The HAHL structure splits communication into three distinct channels:
Layer 1: League → everyone
Weekly recap (standings, top scorers, upcoming games), registration windows, board decisions that affect everyone, end-of-season events. Audience: all rostered players, all spares. Frequency: weekly during the season, monthly in off-season. Tone: short, scannable, links to detail rather than detail in the email.
Layer 2: League → captains
Operational coordination — schedule changes, roster freeze reminders, policy updates, what to expect at playoff dress. Audience: team captains and assistant captains only. Frequency: as needed; typically every week or two during the season. Tone: assumes context, gives operational detail. This is the layer most leagues miss.
Layer 3: Captains → teams
Game-specific stuff — who is dressing Tuesday, who needs a sub, line assignments. Audience: the team. Frequency: every game. Tone: whatever works for that team — text thread, group chat, whatever. The league should not dictate this layer; it should just make sure captains have the tools to do it without burning out.
The discipline of keeping these layers separate matters more than any specific tool. A league with three sloppy channels still outperforms a league trying to do everything through one channel.
The Weekly Recap (Layer 1 in Detail)
HAHL's weekly recap goes out on a fixed day of the week during the season. Same day, same format, same general length. Predictability matters more than perfection — players come to expect it, and that expectation is half the reason they keep paying attention.
What goes in the recap:
- Last week's results. Game scores by division, with links to box scores for players who care about their stat line.
- Current standings. Each of the four divisions as a separate table. People want to see where they sit.
- This week's games. Schedule for the upcoming week with times, opponent, and ice slot. Captains will repeat this to their teams; the league still publishes it because it sets the rhythm of the week.
- One league announcement (or none). If the board has something to communicate to everyone, this is where it goes. If not, no filler. An email with one real message is read; an email with seven announcements is scanned and discarded.
- Spotlight or feature (occasionally). A new player intro, a recap of a notable game, a community item. Not every week, but enough that the recap is more than a results dump.
What does NOT go in the recap: registration deadlines (those get their own messages with their own urgency), playoff bracket announcements (separate dedicated message), conduct issues (handled privately, not communicated to the league). Keeping the recap focused makes the rare urgent message land when it shows up.
The Captain Layer
Captains are the operating layer of a beer league. They handle RSVPs, sub coordination, line cards, occasional dispute mediation, and the unglamorous work of telling someone they are not dressing this week because they did not respond in time. (For the wider role, see the beer league management guide.)
League-to-captain communication needs to do two things: give captains the operational information they need without burying it in the all-league recap, and protect captain attention so they have bandwidth for the actual work of running their team.
Things that belong in the captain channel and nowhere else:
- Schedule changes affecting their team specifically
- Roster freeze date reminders with the specific roster the captain needs to confirm
- Playoff dress eligibility lists (which players on their team are eligible)
- Policy clarifications when a captain asks a question — answer publicly to all captains so the next one does not have to ask the same thing
- Board decisions that affect captain operations (sub rules, conduct enforcement, dispute process changes)
What burns captains out is operational work the system should do. Chasing RSVPs in a group text. Building line cards from a roster spreadsheet. Negotiating sub coverage across three text chains. Modern league software handles all of that, and a captain spending two hours a week on logistics is a captain who is about to quit.
The Player-to-Board Channel
The single most under-built piece of communication infrastructure in most beer leagues is the channel a player uses when they have a problem with the league itself. Issues that fit here: a scheduling complaint that crosses captains, a conduct concern about another player, a refund question, a placement appeal, a captain complaint, an injury-related concern.
Leagues that get this wrong tend to do one of two things. They direct everyone to a generic info@ inbox that nobody owns, where messages disappear for weeks. Or they make the captain the catch-all, which means captains end up mediating issues that are really board-level decisions.
HAHL's approach is a board-owned channel with a real human attached to it, a published response window in the 48-hour range, and a clear escalation path when an issue cannot be resolved at the first level. Board members rotate primary monitoring responsibility across seasons, but the channel itself is stable so players do not have to guess where to send a question.
Why this matters more than it looks: Players who feel heard renew. Players who feel ignored quit, and they do it quietly — they just do not register next season. The single biggest predictor of HAHL's renewal rate is whether players feel the league is reachable, not whether their team won.
Step-by-Step: Setting Up the Cadence
If you are starting a league or rebuilding your communication structure, this is the order HAHL would do it again given a clean slate.
Define the three communication layers explicitly
League to everyone (announcements, registration, schedule), league to captains (operational coordination, board decisions, policy changes), captains to teams (RSVPs, line cards, sub coordination). Each layer has different audience, frequency, and tone. Mixing them up is how leagues end up flooding everyone with messages meant for one captain.
Set the weekly cadence and stick to it
A predictable weekly recap during the season — standings, top scorers, upcoming games, anything operational the league needs everyone to know. Same day of the week, same format. Players who know it is coming wait for it; players who do not know it exists complain about being out of the loop.
Make the league-to-board channel actually reachable
A real email address, monitored by a real person, with a response window in the 48-hour range. A generic info@ inbox that nobody owns is how leagues lose players quietly. At HAHL, board members rotate primary responsibility but everyone knows who is on this season.
Push operational coordination off the captain
Captains should be doing relational work — knowing players, calling the right people, mediating issues. They should not be running a sub-finder text chain at 9 PM Tuesday. Automated RSVP reminders, automated sub callouts, automated game-day notifications handle the operational layer.
Communicate decisions, not just deadlines
When the board decides something, the announcement should say what was decided, why, and what that means for players going forward. The leagues that struggle most are the ones where rules change without explanation and players are left to infer.
Survey at the end of every season
Mid-season is too late to fix anything for the current players; end-of-season tells you what to do differently for renewals. Keep it short. Act on what you hear. Tell the league what changed because of their feedback.
The Silent Failure Modes
Communication failures rarely show up as a single bad email. They show up as patterns the league does not notice until renewal numbers come in below expectation.
The unowned inbox
Players email a generic league address. Nobody owns it. Messages get marked as read by whoever happens to log in, but never responded to. Players assume the league does not care. Renewal drops. Fix: a single named owner per season, with a backup, and a published response window. If the owner is overloaded, fix the staffing — do not let the inbox decay.
The captain bottleneck
Everything routes through the captain, including issues that are not theirs to solve. Captain gets burned out and quits mid-season. Now the team is also a communication black hole. Fix: clear escalation paths for issues bigger than a captain's authority, written down somewhere players can find them.
The off-season disappearance
The league communicates weekly during the season, then goes silent for three months between seasons. By the time registration opens, players have forgotten they were going to play again. Fix: one or two off-season touchpoints — a brief midsummer note, a registration-open announcement with the date already on people's calendars.
The unexplained policy change
Board changes a rule. The announcement says what changed but not why. Players speculate; the speculation is worse than the actual reason. Fix: every policy announcement says what changed, why, and what it means for players going forward. Two extra paragraphs of context prevent two weeks of locker-room rumor.