How to Make a Golf League Schedule (Round Robin)

To make a golf league schedule, list your teams, then use a round robin so every team plays every other team once. Add a bye if you have an odd number of teams, then add makeup weeks and holidays off before you publish it.

The round robin sounds like math homework, but it is one trick repeated. This guide teaches that trick step by step, shows a full 8-team schedule you can copy, and covers the parts the math ignores: tee times, front and back nines, byes, holidays and rain. If you would rather skip the building, the free golf league schedule generator makes a printable schedule for 4 to 32 teams in a few seconds.

What a golf league schedule needs to do

A schedule is a promise to every team about where they will be and who they will play. A good one does five things:

1. Every team plays every other team once before anyone plays a team twice.
2. Every team plays every week, except for planned byes.
3. Tee times rotate, so the same team is not stuck with the 5:00 slot all season.
4. Nines are fair. Everybody plays the same number of fronts and backs.
5. The calendar has slack: holiday weeks marked, one or two makeup dates, and a finale.

A round robin gives you the first two. You add the other three by hand. If you are still setting up the league itself, start with how to start a golf league and come back here when you have a team count.

The round robin circle method, step by step

The circle method is the oldest trick for building a round robin, and you can do it with a pencil. It works because one team stays put while everyone else rotates around it. Take 8 teams.

1. Number the teams 1 to 8. If you have an odd number, add a "Bye" team to make it even (more on that below).

2. Write two rows. Put teams 1 to 4 on top and teams 8 to 5 on the bottom, so each team sits across from its opponent:

   Top:     1  2  3  4
   Bottom:  8  7  6  5
   

3. Read week 1 straight down the columns: 1 v 8, 2 v 7, 3 v 6, 4 v 5.

4. Rotate. Keep team 1 fixed. Move every other team one seat clockwise. The last team on the top row drops to the end of the bottom row, and the first team on the bottom row climbs to the second seat on top:

   Top:     1  8  2  3
   Bottom:  7  6  5  4
   

5. Read week 2: 1 v 7, 8 v 6, 2 v 5, 3 v 4.

6. Keep rotating until you have done it 7 times. After 7 weeks the circle has gone almost all the way around, and every team has faced every other team exactly once.

For N teams (N even), you rotate N - 1 times and play N - 1 weeks, with N / 2 matches each week. That is the whole algorithm. The only way to get it wrong is to move team 1 by accident, or to skip a seat while rotating.

A complete 8-team schedule

Here is the circle method run all the way out for 8 teams: 7 weeks, 4 matches a week. The columns are tee times, and I have placed the matches so that no team gets stuck in one slot (more on that in the next section).

Check it: all 28 pairs

Never trust a schedule you have not checked. With 8 teams there are 8 x 7 / 2 = 28 possible pairs, and 7 weeks x 4 matches = 28 matches. If those 28 matches are all different, every pair appears exactly once. Here is each team's opponent list, grouped by the lower-numbered team, with the week in brackets:

The pair count is 7 + 6 + 5 + 4 + 3 + 2 + 1 = 28. Every pair shows up once, and no team appears twice in the same week. You can run the same check on any schedule you are handed, including ones from a spreadsheet or an app.

A shortcut on size pages: if you have 8 teams, the printable version is on the 8-team schedule page. For 12 teams, use the 12-team page. Pages for the other sizes sit under the same schedule generator.

How many weeks does a full cycle take?

A full cycle is one pass where every team plays every other team once. For an even number of teams that takes N - 1 weeks. For an odd number it takes N weeks, because one team sits out each week. The arithmetic matches the standard round-robin tournament formula.

Look at that table next to your season length. A 16-team league needs 15 weeks for one cycle. That fits a typical 16-week spring and summer season with one week to spare. An 8-team league finishes a cycle in 7 weeks, so it can play two cycles in a 14-week season.

Odd number of teams: how to build in a bye

Nine teams, 11 teams, 13 teams: it happens all the time. The fix is to add a dummy team called "Bye." You schedule it like any other team, and whoever draws it sits out that week.

Here is 5 teams, which is the smallest useful example. Five real teams plus Bye makes six, so you run the circle method for 6 teams and get 5 weeks:

Check it. Five teams give 5 x 4 / 2 = 10 pairs. Five weeks x 2 matches is 10 matches. The pairs are 2-5, 3-4, 1-5, 2-3, 1-4, 3-5, 1-3, 2-4, 1-2 and 4-5, and all ten are different. Each team gets exactly one bye: 1, 4, 2, 5 and 3 in order.

What a bye is worth is your call, and you need to write it down before week 1. Three common rules:

• Average points. The team gets the average of its points from the weeks it played.
• Fixed points. The team gets a set number, such as a half-win equivalent.
• Make-up round. The team plays its own score against the field and takes points based on a target.

Averages are the fairest and the hardest to do by hand. If you run a bye rule on points, say so in your rules template, so nobody argues about it in week 6.

If the bye bothers you, ask whether a team can play the sub list instead, or whether you can recruit one more team to get an even count. For more on this case, the subs guide has ideas.

Rotate tee times fairly

A tee sheet is not neutral. The 5:00 group plays in the best light with the freshest greens, and the last group finishes in the dusk. If a team gets the late slot six weeks out of seven, someone will notice.

With 4 matches a week you have 4 slots, and a team plays 7 times in a full cycle. 7 does not divide evenly by 4, so perfect fairness is impossible. The best you can do is have every team in each slot once or twice: 2 + 2 + 2 + 1 = 7. The 8-team table above does exactly that. Here is the slot count for each team:

Every row adds to 7, and no team has fewer than one or more than two of any slot. A simple "shift everything down one tee time each week" rule does not give you this. Try it with the 8-team grid and you will see a team stuck in the same slot five times. The slots need to be assigned on purpose.

Two more tips for fairness:

• In the second cycle, flip the order. Whoever had the early slots in cycle one takes the late ones.
• Be honest about daylight. In September, the last tee time on a 5:30 start may be a flashlight round. Rotate the pain.

Front nine, back nine

Most nine-hole leagues play one nine per night, and the whole league plays the same nine. That keeps it fair on its own: everyone plays the same holes. The simple pattern is to alternate by week, front on odd weeks and back on even weeks. Over 14 weeks, that is 7 fronts and 7 backs for every team.

If your course sends some groups to the front and some to the back (to speed up a long tee sheet), then the nine becomes part of the schedule and you have the same fairness problem as tee times. Try these rules:

• Each team plays the same count of fronts and backs, within one.
• A team never plays the same nine more than twice in a row.
• In the second cycle, flip every team's nine from the first cycle.

Nine-hole rounds count toward an official handicap too, per Golf Canada. For handicaps on the nine you play, our 9-hole league handicap guide covers the stroke index.

When the season is longer than one cycle

An 8-team league has a 7-week cycle. A 12-week season means five weeks are left over. You have four sensible ways to fill them:

1. Run a second cycle, in the same order. Easy to publish. The downside is that rivals meet in the same week of the second round.
2. Run a second cycle, reversed. Replay the weeks from 7 back to 1. Teams that met in the early weeks meet again late. This is the most popular fix.
3. Run a second cycle with a new rotation. Number the teams a new way so the matchups land in a different order.
4. Use the extra weeks for position rounds. More on this next.

Here is a sample for 8 teams and a 16-week calendar:

That adds up: 7 + 1 + 7 + 1 = 16 weeks. In that plan, every team plays every other team twice, plus the position round.

Position rounds: finishing by standings

A position round (also called a seeding round or a finale) pairs teams by where they stand. With 8 teams:

• 1st plays 2nd
• 3rd plays 4th
• 5th plays 6th
• 7th plays 8th

It works because after a full cycle, every team has already played every other team, so the position round does not repeat a pairing that hurts. It also makes the last night matter: the first-versus-second match decides the title, and every team knows exactly who it is playing. One or two position rounds is plenty. Beyond that, the leader keeps playing the runner-up, and lower teams keep meeting each other, which kills the variety.

Decide your tie-breaker for the table before the final week. A common order is total points, then head-to-head result, then net strokes. For ideas on formats, see two-person team match play and stroke play.

Holidays, makeup weeks and rain

Your calendar matters as much as your matchups. Here is a short list.

1. Pick the weeks you will not play. Memorial Day, July 4 and Labor Day weeks lose golfers. Put them on the calendar now.
2. Schedule the cycle around them. If the 4th of July falls on your night, week 11 does not exist. Number the playing weeks 1 to 15 and keep a separate column for calendar dates.
3. Add one or two makeup dates. A spare week near the middle and another near the end covers most seasons.
4. Write a rain-out rule. Does the missed round get played, or is it dropped? A short note in the schedule is enough, and the rain-out policy guide has a full sample.
5. Protect the finale. Do not let a makeup week crowd the position round. If you have to cancel a week, cancel a mid-season one, not the finale.

Here is a 12-team example. A cycle takes 11 weeks. Add 1 makeup week and 2 position rounds and you need 14 playing weeks. If two of your Tuesdays are holidays, the calendar needs 16 Tuesdays. Plan for the count of calendar weeks, not the count of playing weeks. The 12-team schedule page has the full grid.

Publishing and printing your schedule

A schedule nobody can find is no schedule. Before week 1:

1. Make one master copy. One place, one version. Date it.
2. Show team numbers and names together. Golfers will not remember that they are "Team 6."
3. Include the date, the opponent, the tee time and the nine. A one-line row per team per week.
4. Print it. A one-page printout stuck on the pro shop corkboard and the clubhouse door beats an email that nobody reads. A printed copy also helps the starter.
5. Send it to the whole league with a note on how to report changes.
6. Keep a change log. If you swap a week, put the date next to the change and re-send.

The schedule generator outputs a printable grid, one page per team count. The scorecard generator and the league spreadsheet can pair with it if you run the league by hand.

Template, maker, or by hand?

You have three ways to get the schedule built:

The free golf league schedule generator is a schedule maker for 4 to 32 teams. It handles byes and prints cleanly. If you already use Gimme for scoring, the same schedule feeds weekly pairings and standings, and the first 3 league rounds are free with no card. If you run it all yourself, the circle method above is the same thing, with a pencil.

Commissioner checklist

1. Count your teams. If odd, add a Bye.
2. Work out the weeks per cycle from the table.
3. Build week 1 with two rows, then rotate 7 times (or N - 1).
4. Check it: count your pairs and confirm no team plays twice in a week.
5. Assign tee times so every team gets each slot once or twice.
6. Decide the nine for each night.
7. Fill extra weeks with a reversed second cycle, then position rounds.
8. Mark holidays and add one or two makeup dates.
9. Write the bye rule and the rain-out rule.
10. Publish, print and re-send when anything changes.