By: Mike Davis
In the last couple of weeks, the ACC has been very vocal in their desire to scrap the current system of conference divisions. Since the SEC, ACC, and Big Ten all expanded to 14 team divisions, many have proposed a solution:
“Why not set up the schedules so that every conference member a team doesn’t play in their current year, they must play them the next year?”
I have seen something along those lines posted countless times on various forums for the better part of two years now and the idea is rapidly gaining steam. Syracuse Athletic Director Daryl Gross proposed the idea with no fixed rivals to the ACC earlier in the year. The website Southern Pigskin proposed the idea for the ACC/SEC in late January.
This is much easier said than done. Making this proposal a reality is a lot harder than it seems. There are a number of factors that need to be taken into account such as:
Keeping home/away consistent between programs - For example, making sure a matchup like Ohio State and Penn State continue to rotate evenly between Columbus and Happy Valley.
Keeping the amount of conference home games consistent - For eight game conference schedules, each team should have an equal amount of home/away. For a nine game conference schedule, some teams will have five home games whereas others will have only four. To keep the balance of a nine game conference schedule equal, all schools should be guaranteed nine conference home games every two years.
Keeping rivalry games – This should be pretty self explanatory. Matchups like Ohio State-Michigan or Auburn-Alabama not playing every season would cause quite a bit of backlash.
So far, I have yet to see a scheduling proposal that takes into account all three of these problems. This article is where I do just that, showing exactly how a “no divisions” scheduling scenario can play out.
Some Things to Note:
I will provide full schedules for both eight game and nine game schedules for the Big Ten, SEC, and ACC. I did not include the Big 12 because they already play a true round robin schedule.
I did not do a Pac-12 scenario because that conference has other scheduling factors to consider not seen in the other Power-Five conferences. For example, every Pac-12 member currently gets to play three California schools each year. This gives each non California member an equal “California presence” and allows all four California schools to play each other every year. The new members (Utah/Colorado) are placed in a division where most of their out of state alumni living in the Pac-12 footprint are located. This goes a long way to help them maximize the benefit of new Pac-12 affiliation in terms of recruitment, donations, and attracting prospective students. For the Pac-12, eliminating the divisions causes more problems than it solves.
A 14-team conference is quite literally the hardest conference size to schedule. You can not do any sort of pod setup with this number. I also struggled to find a way to make a multi year round robin format because there were not enough teams. This project has taken me months and countless failed Excel sheets. I tried a number of different schedule styles and the only real option was an 8 game conference schedule with 3 fixed rivals.
Step #1 Assign Rivals
Due to the size of these pictures, I could only include them in trimmed down sizes. Click on any of them for a full view. These are the three rivals I assigned per each team. If you want further information about why I chose these rivals, click here.
Step #2 Making the Schedule Sheet
This picture is a basic rundown on how the schedule sheet works. On the far left, you have all the teams in bold. Their 13 fellow Big Ten teams all appear as you move to the right horizontally. The first team (Michigan) has the eight teams they play in 2015 in red and the five teams they don’t play in yellow.
I tried to make the orange/blue pods as fair as possible. I accomplished this by splitting the four strongest Big Ten programs (UM, PSU, OSU, & UNL*) and did my best to make other programs play only two of them each year rather than four of them one year and none of them the next year. I also split up schools from the same state. For example I tried to prevent schools from playing IU/Purdue or UM/MSU in the same year. This was particularly important with the ACC where there are huge recruiting differences between the northern and southern states.
I did things like this whenever possible for every conference when I made their schedule sheets.
*I refer to Nebraska as UNL as explained in the “Explaining the Rivalries post“.
Step #3 Determining a Rotation
This picture is a breakdown of how the teams rotate. The yellow represents each program’s fixed rivals. In other words, the schools they play every year. The orange and blue represent the two pods that rotate back and forth. Schools will play either all teams in the blue pod or all teams in the orange pod plus their fixed rivals. While I call them pods, they do not reflect any pod/divisional split in the conference.
This is what the following year (2016) will look like. You will notice the only difference in this picture from the last picture is the year. This is because the pattern of the blue/orange rotation goes blue, blue, orange, orange, and repeats. This means that a team plays the exact same schedule two years in a row.
As you can see, the following year (2017) the teams will play the orange pod.
And the year after (2018).
The reason why I set it up like this was to balance home/away between programs. The reasoning behind using this tactic is quite complicated and hard to explain. The best way to state it is that if you don’t use it, you will have one of the following happen:
Using PSU & Michigan as an example.
– Penn State has to play at the Big House in Michigan in both 2017 and 2018
– Penn State plays at the Big House in Michigan in 2017, and Michigan visits Happy Valley in 2018. However, PSU gets only three Big Ten home games and five away games for 2018.
Neither situation is ideal and for a schedule to work, you cannot have either happen. The reason why this happens is that if you did this on an orange, blue, orange, blue rotation, then you have some teams who will fulfill their home/away requirements with some opponents in two years other in three years. That is where things start to get screwed up and causes scheduling imbalances. The fix is to have every program fulfill their home/away requirements with every opponent at the same time. So having a “repeat year” allows for the exact same schedule to occur, only the home/aways are the opposite of the previous year thus eliminating the problem.
This concept is not new. The Big Ten used a method similar to this for the exact same reason back when they were an 11 team conference.
Step #4 Determining Home/Away
Now that the rotation has already been determined, the next step is to decide home/away. I accomplished this by filling in the home matchups dark green and the away matchups in light green.
As you can see every team has four home games and four away games.
In this picture, you will observe that the only differences from the last picture (besides the year) is that all the dark greens have been turned to light greens and vice versa.
The above examples show a completed Big Ten schedule for the 2015 and 2016 seasons would look like. I have provided a 2015 below for the SEC and ACC.
One important thing to note that this is simply a spreadsheet that shows who each team plays and the location of the game. This does not mean these teams must play in this specific order. They can move games around however they please.
For a full Excel spreadsheet of an eight game schedule on Google Docs, all three conferences are provided below:
One thing you will notice is every team has exactly four home games and four away games each. You will also notice that it takes only four years before the cycle repeats.
Step #5 Adding a 9th Conference Game
The Big 12 and Pac-12 both play nine game conference schedules. The Big Ten also uses a nine game conference schedule and the ACC is making a serious attempt to do the same. So of course I am not going to present to you with only an eight game schedule.
The way I set up a nine game schedule was to keep the eight game schedule plan that I have already shown and add a 9th game. It is basically an 8+1 model using all the rules of the eight game model with an added 9th game. The team that a program plays as part of their extra game is taken from the “Does Not Play” column.
So this is what the schedule looks like so far. As you can see, it looks just like an eight game schedule with an added 9th game. You can see that the orange/blue pod setup is the same and I have placed the 9th game (I call it the slot game) under game #1 in the far left in bright green. If the Color concept is confusing anyone, sorry for having so many different shades of green.
Here I have filled in the empty game #1 using the first column of the “Does Not Play” section. I will use this column for the next four years before moving on to the 2nd column of the “Does Not Play” list. I have done this because it takes the other eight games four years to fully repeat. This means it takes a nine game conference schedule 24 years to go through a complete cycle before repeating.
Example of what the schedule will look like in after 5 years (2019) when the 2nd cycle starts. I used a shade of blue to identify the “slot game” on the right under “Does Not Play.”
Example of what the schedule will look like in after 17 years (2031) when the 5th and final cycle starts.
Example of what the schedule will look like after 21 years (2035) when the cycle fully repeats and goes back to the 1st cycle. The schedule is exactly the same as 2015.
Step #6 Adding Home/Away for a 9th Conference Game
This is how I assigned the home/away. Some teams have five Big Ten home games while others have only four home games.
As you can see the home/aways have been switched, meaning all the teams that had only four conference home games last year have five conference home games this year and vice versa.
The problem is that it is not this simple every year. In some years, you will have teams play consecutive seasons of having 4 conference home games. It is an unavoidable problem.
For the Big Ten and SEC, I could have set it up where it happens only once every 20 years for 7 of the members in each conference. However, in the interest of fairness, I didn’t want to do that so I attempted to make it happen only once for every school every 20 years. That was too problematic so I took the easy way made it happen 2x times for every school every 20 years. It might be possible to make it happen just once a year per school, however these schedules are incredibly time consuming and I did not want to spend the time to redo those schedules with the hope of accomplishing that.
With the ACC, I was successful in making the consecutive four home games a year event happen just once every 20 years. Part of this was because I configured the ACC schedule last and learned from my mistakes with the Big Ten/SEC schedules. This allowed me to build the ACC in a way that was much easier to work with. Another reason was because the ACC fixed rivalries had a different setup using a semi pod system that also made working with the schedule easier. If you are confused about what I mean by the ACC rivalry setup, I explained it in my “Explaining the Rivalries” post.
This is a graph I designed to display which years Big Ten teams have 4 or 5 conference home games. The graph shows how often the consecutive 4 conference home games event occurs for each Big Ten member and is represented in yellow. The same graph also shows that every 20 years (not counting 2015), each member has the same amount (10) of white and orange boxes. This means that the number of home/away games each team has is balanced throughout the full cycle. The graph can also be used as an example to show in which years the 5-cycles run through.
Here is the same graph for the SEC.
As well as the ACC.
I have provided longer versions of this graph all the way to the year 2054:
And of course, who would I be if I didn’t provide full excel sheets for 9 conference games? Each spreadsheet shows a full cycle (20 years).
How do you determine who plays in the conference championship game?
The two teams with the highest BCS ranking will be paired up. Since OSU-UM will be paired up in the final week before the conference championship game, one of them has to lose and thus drop in the BCS rankings. This minimizes the potential for back-to-back rematch games between any two opponents.
At first, I was strongly against giving each team three fixed rivals. But I had to do it because doing it made the eight game schedule work so smoothly. After awhile, the concept grew on me as several schools have three major conference rivals and it meant more rivalries could be saved.
While this scheduling style is a major upgrade over the current divisions setup, some of the problems the divisions setup creates are still present in this system. Teams still miss other teams for two straight years, which allows the potential for “conference dodging” between the strongest teams to exist.
Another reason I was against the divisions setup is because teams go too many years without playing at certain locations. An example of this is Syracuse not playing Georgia Tech in Atlanta until 2027. This system prevents teams from skipping games at another team’s stadium for more than four years, which is still quite a long time.
An eight or nine game schedule without divisions is entirely possible as I have shown and can be implemented without causing any major problems. Now if only Delany, Slive, or Swofford read this and decide to use it.
Follow me on Twitter: @sportspolitico or email me: firstname.lastname@example.org