7 Common Hockey League Scheduling Mistakes (And How to Avoid Them)

We've all been on a team that got stuck with the 10:30 PM slot every single week. Here's how commissioners screw up schedules—and how to not be that guy.

Alex Thompson
Staff Writer & Beer League Player
December 29, 202510 min read

Key Takeaways

  • Start scheduling 6 weeks out—not two weeks before puck drop when you're already panicking
  • Collect blackout dates before you build anything, or prepare for weeks of inbox chaos
  • Track time slot distribution or you'll hear about the 10:30 PM injustice all season long
  • Build makeup capacity in from day one—something always gets cancelled

I've made all of these mistakes. That's not a rhetorical opener—I mean I have personally, as a commissioner, made every single error on this list. Some of them more than once. The back-to-back game fiasco of my third season with the Lakeview Hockey Association in Minneapolis is still something I hear about when I run into certain captains. We had three teams play two games in less than 24 hours during Week 2, and two of those teams had their worst defensive performances of the season in the second games. Correlation? Sure. But try explaining that to a goalie who let in seven goals on a Sunday morning after playing Saturday night.

After 15 years as a commissioner and building scheduling tools for hundreds of other leagues, I've seen every version of these problems. Here's what they are, what they cost you, and how to avoid them.

Mistake 1: Starting Too Late

The most common mistake by far, and the one that cascades into every other problem. When you start building a schedule two or three weeks before the season, your ice slot options are already gone, teams can't plan childcare, and you're assigning referees on a timeline that means you're taking whoever's available rather than whoever's good.

The fix is simple but requires willingness to start when it feels early: begin the scheduling process six weeks before opening night. Confirm ice slots in week six, finalize team registrations in week five, generate the base schedule in week four, review for conflicts and fairness in week three, assign referees in week two, and publish with full communication in week one. This calendar feels aggressive until you've tried to compress it and realize the rink already gave your Friday slot to a figure skating club.

Week OutAction
6Confirm ice slots with rink in writing
5Finalize team registrations
4Generate base schedule
3Review for conflicts and fairness
2Assign referees
1Publish and communicate

Tip

Block your calendar for scheduling work during the six-week window. It's not something you fit in between other things. It takes concentrated time and interruptions create errors.

Mistake 2: Ignoring Time Slot Fairness

The 10:30 PM slot exists because every league has it and someone has to take it. The mistake is giving it to the same team repeatedly without noticing—or noticing but assuming nobody will care. They will care. The team that gets the last slot four times in a row will absolutely bring it up at the bar, then in the group chat, then to you directly.

Track your time slot distribution from the beginning. Build a simple matrix with teams as rows and weeks as columns, logging which slot each team plays each week. When you can see the numbers, the unfairness is obvious—and you can fix it before it becomes a complaint. Every team should finish the season with roughly equal distribution across all slots. If someone has to absorb more late ice, compensate with more early-prime slots elsewhere.

Team6pm7:30pm9pm10:30pm
Sharks4444
Eagles5434
Storm4354

This is what a fair distribution looks like. If one team has 7 games at 10:30, you have a problem—and you want to catch it in Week 4, not after they've already complained twice.

Mistake 3: Creating Back-to-Back Games

This is the Lakeview mistake. Two games in less than 24 hours—or worse, twice in one day at different rinks—is bad for players, bad for goalies, and generates forfeit requests at the worst possible times.

The fix requires building hard constraints into your schedule before you generate matchups, not as a patch after you notice a problem. No team plays twice in one day. Forty-eight hours is the minimum gap between games. If a back-to-back is truly unavoidable due to makeup scheduling, the second game should be the home game to minimize travel. Scheduling software flags these automatically. In spreadsheets, use conditional formatting to highlight same-team appearances within 48 hours.

Mistake 4: Not Collecting Blackout Dates

You build a beautiful schedule. Three days after publishing it, the captain of the Grizzlies emails you that they're missing six players for Week 4 because of a long weekend nobody told you about. Then the Eagles have a tournament conflict in Week 7. Then the Sharks' captain realizes his team always has Thanksgiving Eve games.

The fix is to collect blackout dates before you build anything. Send the request eight weeks before the season, set a firm deadline at six weeks out, and communicate clearly that the policy is no changes after the deadline except genuine emergencies. Collect specific dates teams cannot play, note when key players are unavailable for small-roster teams, and block league-wide holidays preemptively. Then hold the deadline—make exceptions and suddenly every team has an emergency.

Warning

If you send a blackout request and three teams don't respond, chase them down before you build the schedule. Silence is not agreement. The team that doesn't send blackout dates is almost always the team that surprises you with conflicts in Week 5.

Mistake 5: Unbalanced Home/Away Distribution

In single-rink leagues, home and away are often the same ice. But locker room assignment, "home" bench designation, and perceived home-ice status still matter to players and captains. In multi-rink leagues, it matters even more.

Aim for plus-or-minus one game of perfect balance across the season. In a 16-game season, target 8 home and 8 away; 7-9 or 9-7 is acceptable. If you're hitting 6-10 for any team, that's a real problem you need to fix before publishing. For odd-number game seasons, alternate who gets the extra home game from season to season so the imbalance doesn't compound.

Mistake 6: Scheduling Without Confirming Referee Availability

You've built a schedule that perfectly fits your ice slots. Then you check with your referee coordinator and discover that two-thirds of your referees aren't available on the nights you've scheduled the most games.

I watched this happen at a league in Ohio where the commissioner built the entire schedule optimized around ice availability without once asking the referee assignor about capacity. Week 1 went fine with the refs who were available. By Week 3 they were running single-ref games and calling in favors from retired officials. By Week 5, one game had no referee show up at all and they played self-reffed. It got ugly in ways that required formal apologies.

The fix is to get referee availability before you finalize the schedule—not after. Build the schedule around both ice capacity and referee capacity. Maintain backup referees for every slot. If refs are genuinely scarce, reduce your game count to match real capacity, consider one-ref formats for recreational play, or invest in developing a referee training pipeline.

Mistake 7: No Buffer for Weather and Emergencies

Every season has at least one cancellation. Usually more. An ice rink HVAC emergency. A blizzard. A facility double-booking. A key rink employee who forgot to unlock the building. If your schedule is packed with games from opening night through the last weekend before playoffs, you have no room to absorb any of these cancellations without games never getting made up.

Build makeup capacity into your schedule from the start. The cleanest approach is two designated "open weeks" spread through the season with no scheduled games—these become makeup slots when needed and either stay open or become practice dates when not. The second option is a buffer period of two weeks between the end of the regular season and the start of playoffs, specifically for makeup games. A third approach is reserving one or two ice slots per week specifically for makeup use, releasing them to the rink if unused three or four days out.

When weather is threatening, cancel early. A planned cancellation with 24 hours notice is a logistical problem you can manage. A same-day cancellation when players are already driving is a chaos event that generates anger and injury risk.

The Bonus Mistake: Over-Complicating Everything

The schedule that tries to satisfy every constraint simultaneously—custom time preferences for each team, complex cross-division matchup formulas, intricate tiebreaker scenarios—almost always ends up satisfying nobody, takes weeks to build, and falls apart completely when you need to make one change mid-season.

Simplicity wins. Same ice times each week creates predictability. Round-robin format when possible creates fairness that players can understand and verify. Clear, published rules mean you're not making decisions under pressure. And "no" is an acceptable answer to special requests—especially from the team captain who wants Thursday nights off because of his hockey fantasy league draft.

When players ask about your scheduling philosophy, "we rotate time slots fairly so no team gets stuck with bad ice all season" is a complete and satisfying answer. You don't need a 12-page document to explain a fair schedule.

Pre-Publish Verification Checklist

Before you hit send on any schedule, check these specifically:

  • All teams have equal games played
  • Home/away within one game of perfect balance
  • Time slots distributed fairly across all teams
  • No back-to-back games for any team
  • All collected blackout dates avoided
  • Referees confirmed for all games
  • Makeup capacity exists in the calendar
  • Published at least two weeks before opening night

Frequently Asked Questions

What do you do when teams complain about a published schedule? Hear them out, explain how you built it, and then hold the line. The moment you move one game for one team you've opened a door you cannot close—everyone has a reason their situation is special.

How do you handle a team that misses the blackout deadline and then complains about conflicts? Policy is policy. You set the deadline, you sent the reminder. Make an exception once and you've established that deadlines are negotiable.

Should you accommodate individual player conflicts? No. You're scheduling teams, not 200 people with different lives. If a player can't make a game, that's what the bench is for. Goalies and captains are the only exception worth considering, and only for truly exceptional circumstances.

How do you handle referee no-shows on game night? Have a call-list of backup officials ready before the season starts. Know in advance whether your league will play with one ref or postpone if the second doesn't show. Players need to know the policy before it happens, not when they're standing on the ice at 10:30 PM waiting for an answer.

Your Schedule Is Defensible When It's Fair

Most scheduling headaches are preventable. Start early, collect blackout dates before you build anything, track time slot distribution, and build with referee availability baked in. Your schedule will not make everyone happy—but it can be fair, functional, and something you can defend when Dave from the Sharks starts chirping.

For more guidance, check out our complete scheduling guide or league management resources.

Alex Thompson's Insight

After building schedules for 50+ team leagues and helping hundreds of commissioners through RocketHockey, I've personally made most of these mistakes before figuring out how to avoid them. The good news: they're all preventable—you just have to start earlier than feels necessary.

Frequently Asked Questions

What do I do if teams complain about a published schedule?

Hear them out, explain how you built it, then hold the line. The moment you move one game for one team, you've opened a door you can't close—everyone's got a reason their situation is special.

How do I handle teams that miss the blackout deadline?

Policy is policy. Make exceptions and suddenly every team has an emergency. You set the deadline, you sent the reminder—that's on them.

Should I accommodate individual player conflicts?

Nope. You're scheduling teams, not 200 individuals with different lives. If a guy can't make a game, that's what the bench is for. Goalies and captains are the only exception worth considering.

How far in advance should I start scheduling?

Begin 6 weeks before the season starts. Confirm ice 6 weeks out, finalize teams 5 weeks out, build schedule 4 weeks out.

schedulingleague managementmistakesbest practices
Share this article:

Sources & References

  1. RocketHockey Scheduling Survey 2024
  2. USA Hockey League Administrator Guide

Alex Thompson

Staff Writer & Beer League Player

Beer league hockey player for 10+ years and former league commissioner who's managed scheduling for leagues with 30+ teams. Alex spent years building schedules in spreadsheets before discovering there had to be a better way. Now he writes about the real challenges of running hockey leagues at every level.

Want to learn more about League Management?

Read Our Complete Guide