How to run a successful water polo league.

A tournament is a weekend with a bracket, and play ends in a winner. A league is many weeks where the same teams meet repeatedly and standings accumulate. Both have their place. Pick wrong and you will be patching the format all season.

• You have a fixed weekend (Saturday and Sunday, or a holiday) and teams travel in
• Bracket play is the point: the goal is to crown a winner from this specific field
• You are hosting visiting clubs from far away who cannot commit to a recurring weekly slot
• Sponsors, referees and venues are committed for one event, not a recurring slate

• Teams play each other repeatedly over weeks or months
• Standings, not bracket placement, are the measure of success
• You want regular-season games that feed into a playoff, not one elimination weekend
• Visiting clubs are local enough to come back regularly over a season, week after week
• Player development matters as much as crowning a champion, and you want a season judged on the whole body of work

• Round-robin. Every team plays every other team once. For N teams, that is N×(N−1)/2 games. Best for 4 to 12 teams. Predictable, fair, and easy to explain.
• Double round-robin. Every team plays every other team twice (home and away, or simply twice). Doubles the games and improves the sample size. Use for 4 to 6 teams and longer seasons.
• Single elimination. A bracket of 4, 8 or 16. Losers are out. Best as a playoff at the end of a regular season, not as the whole league.
• Double elimination. A losers’ bracket gives a team a second life. Teams must lose twice before they are out. About 2N−1 games. Use when you want a forgiving playoff with 4 to 12 teams.
• Swiss. Fluid: teams are paired against opponents with similar records. No team is eliminated. Best for fields of 12 or more teams where you want competitive games each round without strict scheduling.
• Weekly pods. Teams split into rotating small groups (pods) each week, often 3 teams playing a mini round-robin. Great for casual rec leagues with rotating availability.

Three questions get you there fast:

1. How many teams do you have? 5 to 10: round-robin. 12 or more: Swiss or pods. Fewer than 5: reconsider whether this is a league at all.
2. How many weeks of play? Round-robin needs N−1 weeks (one game per team per week). Swiss can run any number of rounds. Pods rotate weekly. Match the format to the calendar.
3. Is there a playoff? Most leagues finish with single or double elimination. If so, your regular season’s job is only to seed the bracket fairly.

• Minimum rest between same-team games. Do not schedule a team back-to-back unless you absolutely must. Aim for 90 minutes or more between games for the same team, and longer if your athletes are younger.
• Court and pool rotation. Over the season, every team should play roughly the same number of games at every venue. Pacific Waves should not play 80% of their games at one pool while everyone else rotates.
• Day-of-week consistency. If your league plays Saturdays, every team should expect a Saturday slot. Do not make one team play Sunday mornings every other week while everyone else plays Saturday.
• Spread, not bunching. Do not schedule three games against the same opponent in three consecutive weeks. Use a scheduler that mixes up each team’s slate so every week feels fresh.

The cleanest way to schedule a league is to define one weekly preset and let it fill every week. The preset includes:

• Day of the week (for example Saturday)
• Start time for the first game (for example 9:00 AM)
• Number of courts or pools available
• Buffer between games (for example 5 minutes for warm-up)

Use 3 points for a win, 1 for a tie, 0 for a loss. This system has become the global default across soccer and water polo for good reason: it rewards winning over “playing not to lose” without punishing draws as harshly as some older systems do.

When two teams end the season with the same number of points, you need a defined chain to break the tie. The most widely accepted chain:

1. Points. Tied here? Continue down the chain.
2. Wins. More wins is better. (A team at 10W-0L-0T tops one at 9W-0L-3T on equal points.)
3. Head-to-head. The result of games strictly between the tied teams. Only applies when exactly two teams are tied.
4. Goals against. Fewer goals allowed wins. Rewards defense.
5. Goals for. More goals scored wins. Rewards offense.
6. Goal differential (capped at ±10). Capping prevents a 20-2 blowout from skewing the table.
7. Alphabetical. The final fallback. Predictable, never decisive in practice.

For late-start leagues, consider hiding public standings until enough games are played. Two policies work well:

• Hide until week N. Standings open after week N, for example. Prevents week-one panic when one win or loss looks decisive.
• Hide until X games played. Standings open after every team has played at least 3 games. Adjusts for uneven scheduling at the start of the season.

In a multi-club league, one club is the host. The host publishes the league, defines the schedule, owns the standings, and manages day-of issues. Other clubs are visitors. Visitors manage their own rosters, make sure their players show up, and submit any disputes.

Each visiting club uploads its own roster. The host should not be the one chasing 12 visiting clubs for player rosters. In Eggbeater, the host publishes a share code. Each visiting club imports the code into its own admin and uploads its roster. The host’s standings page resolves the visiting players automatically when scores are entered.

The biggest source of friction in multi-club leagues: visiting spectators want to follow their players’ games, but the spectator app belongs to the host club. The solution:

• Free public spectator page. Under Eggbeater’s Multi-Club League plan, every spectator from every visiting club gets free spectator access under the host’s umbrella. They open the league page and see everything, with no separate subscription required.
• Spectator pages per club. If your platform does not support that, expect visiting spectators to ask for one. Plan accordingly: print the public link and hand it to every visiting team’s spectators on day one.

If you can rotate the host venue evenly (Week 1 at Club A, Week 2 at Club B and so on), do it. The travel burden is shared, and every club’s spectators get a home game eventually. Coordinate court availability up front. Locking in venues for a 10-week season is harder than locking in for one weekend.

Some game-day fundamentals that hold whatever your format:

• Pre-game checklist. Thirty minutes before the first game: venue setup confirmed (clock, scoreboard, lane lines). Volunteer scorer assigned and briefed on the scoring app. Both teams’ rosters confirmed and caps matching the roster. Referees present and verified. Scoring password and device handed to the desk.
• Volunteer scorers. The scorer is the most important volunteer at the desk. They control the live scoreboard, the player stats, the kickout counter, and the game clock. Recruit early, train once, and stick with the same person across multiple weekends if possible. Eggbeater’s scorer view runs on a single phone (tap the action, tap the player, done) and the scoreboard updates everywhere in under five seconds.
• Referee sign-off (optional). Having the referee verify the final score before it goes to standings heads off Monday-morning disputes from coaches who saw a different score. In Eggbeater this is an optional step an admin enables (off by default): turn it on from the Leagues tab, Scorer Display card, and ending a game then asks the scorer for the referee’s name to finalize.
• Dispute handling. Publish a dispute policy before each season and do not deviate. Common shapes: scoring disputes (submitted within 24 hours of game end, by email to the league director), eligibility disputes (submitted before the game starts), conduct issues (handled by the referees on the deck). Most leagues never see disputes. Without a policy, you will get twenty.

Plan the awards before week one. The classic set: division champion (top of standings), runner-up, top scorer, best goalkeeper, sportsmanship. Pick what you can afford and announce the categories ahead of time so coaches can nominate.

• Archiving the season. When the playoffs end, archive the entire season. Every game, every box score, every roster. Then mint a fresh code for next year. Do not keep the same code: last year’s spectators (push subscribers, calendar feeds, bookmarked links) would get next year’s data. And do not simply delete it. That loses your historical record. Archive properly so MVP-of-the-decade conversations have a source of truth.
• Planning next year. Three things to review before next season. Format fit: did round-robin take too many weeks? Did Swiss feel arbitrary by week 3? Format complaints rarely show up in the standings. They show up in unsolicited messages from coaches, so listen. Venue economics: did one club host 80% of the games? Either pay them or rotate next year. Tiebreakers: if a tiebreaker felt unfair this season, change it before next season, never in the middle of one. Changes in the middle of a season destroy trust.

Most water polo leagues run on spreadsheets. You may have noticed: most water polo leagues are organized in Google Sheets with a team group chat for announcements. This works, until it does not. The four classic spreadsheet problems:

• Standings drift. Someone forgets to update the table after a Saturday game. Coaches see different versions on Sunday.
• Communication overload. “When is our next game?” asked 12 times a week. The information is in the sheet, but spectators do not open spreadsheets.
• Live games are invisible. Spectators at home have no idea what is happening at the pool. A goal scored at 11:42 reaches them the next day, if at all.
• The end-of-season report is a Word document. Done from scratch. Every year.