Start before the season, not during it
The worst moment to change tools is the week before a big tournament. The best moment is the quiet period before the season: there are no live schedules to protect, referees are renewing anyway, and the people who will use the new system have time to try it.
Plan the season in four phases: prepare, pilot, roll out, review. Each phase has a clear end point, and you only move on when it is reached. If the pilot goes badly, you have lost one tournament's worth of extra work, not a season.
Phase 1: prepare (four to six weeks before the first tournament)
Clean the referee list first. Every federation's spreadsheet has duplicates, people who stopped two seasons ago and email addresses that bounce. Decide who is active this season, and give each referee one level. If levels have drifted over the years, fix that now with the head of referees, not inside the new tool.
Write down the rules you actually use. How many games in a row before a referee must rest? Can a lower-level referee ever take a higher-level game? How many referees per game? These rules live in coordinators' heads today. A scheduling tool needs them written down, and so does the next coordinator you hire.
Pick one owner. Migration fails when it belongs to everyone. One person, usually the national coordinator, decides on settings, answers referee questions and signs off each phase.
Phase 2: pilot one tournament
Choose a mid-sized tournament with an experienced coordinator, not the national final. Run it in the new system, and keep the old spreadsheet next to it as a fallback for that one day.
In RefManager 3x3, the tournament schedule is imported from the Excel file most organisers already have: rounds, courts, categories, teams and breaks come in from the sheet. Referees are invited in bulk by pasting a list of email addresses, and the import marks anyone already invited, so you do not send duplicates. Referees then see their games on their phone, can subscribe to them in their own calendar, and get notified when something changes.
Success for the pilot is simple: the schedule was published on time, the day ran from the system, and the coordinator would use it again. Write down every friction point, however small. Those notes become the instructions for everyone else.
Phase 3: roll out by region or tier
After the pilot, do not switch everything at once. Move one region or one tournament tier at a time, and pair each new coordinator with the one who ran the pilot for their first tournament.
Referees adapt faster than coordinators expect. For them the change is mostly good news: schedules arrive in one place instead of in a group chat, and late changes reach them directly. The real work is with coordinators, who need to trust the automatic schedule before they stop rebuilding it by hand. Let them compare: build the schedule automatically, then show them the fairness score and the out-of-level report. Most stop second-guessing after two tournaments.
Set a cut-off date after which the spreadsheet is no longer the official schedule. Without it, you run two systems for the whole season, and that is worse than either one alone.
Phase 4: review at the end of the season
The first season produces something the spreadsheet never did: data. How many games each referee worked, at which level, with which colleagues, and how often a planned schedule changed on the day. Use it in the end-of-season review with the referee committee.
Look for three things. Referees who consistently worked far fewer games than their availability allowed. Levels that were a bottleneck at almost every tournament. And tournaments where many changes happened on the day, which usually points to a planning problem, not bad luck. Each of these is a decision for next season that used to be made on gut feeling.
What not to migrate
Do not import years of old spreadsheet history. It is inconsistent, nobody will trust it, and it slows the start. Begin with this season's active referees and this season's tournaments. Keep the old files archived if you need to look something up.
Do not rebuild your old process in the new tool either. If your spreadsheet needed a manual check for consecutive games, that check is now a rule the system enforces. The point of switching is to stop doing the work the tool does for you.
The short version
Clean the list, write down the rules, pick an owner. Pilot one tournament with a fallback. Roll out region by region with a hard cut-off. Review with real data at the end. One season is enough, as long as you start before it begins.
Your turn
Plan your switch with us
We will walk through your season, your rules and your first pilot tournament.
Book a demo