Conf USA doing round robin/flex scheduling next year for Bball

Submitted by triguy616 on

Link

Conference USA will be moving to a conference schedule that is a round robin and then "podding" teams into categories, with teams in a pod playing each other again. This is very similar to Brian's proposed Big Ten schedule.

"We're going to play 13 games and your travel partner twice, which would be Western Kentucky for us," said D'Antoni. "Then they are going to seed the schools. If you finish in the top five, No. 1 through No. 5 will play each other for the next four games to get 18 games.

They are hoping that this will increase their chances to get a second team into the tournament.

bacon1431

May 27th, 2018 at 6:13 PM ^

I’d like to do it. Play everybody once. Then split it to into two halves, have everybody in the top half play each other and everybody in the bottom half play each other. Ideally, you’d do home and away for the second half, but 25 conference games might be too much. Would be much more feasible had we not expanded to 14 teams

Jfhskhx

May 27th, 2018 at 8:24 PM ^

How will seeding work for the conference tournament? Will the initial top pod have the higher seeds, or will it still be overall conference record?

DoubleB

May 28th, 2018 at 10:07 AM ^

your original pod once the last 4 games of the season are played. So if you're 1st after the first 14 games, you can't finish lower than 5th. If you're 10th after the first 14 games, you can't finish higher than 6th.

The last pod only has 4 teams so I don't know how they get to 18 games. Play another pod team a 3rd time during the season? Or save everyone the time and energy and only play 17 games.

Jon06

May 28th, 2018 at 7:06 AM ^

We’re sorry. This site is temporarily unavailable.

We recognise you are attempting to access this website from a country belonging to the European Economic Area (EEA) including the EU which enforces the General Data Protection Regulation (GDPR) and therefore cannot grant you access at this time.

For any issues, contact us.

(403 error.)