What If? The 2017 NCAA Women's Hockey Tournament Pairwise Predictor

For years, USCHO has provided a fantastic tool allowing you to plug in theoretical results of the men's hockey conference semifinals and finals and see its results on the Pairwise rankings. Unfortunately, a similar tool was never available for women's hockey.

But as they say, necessity is the mother of invention. So here at BC Interruption, we built it ourselves. This is the third year of the BCI Pairwise Predictor, and version 3.0 has some new features:

First, the CHA now has its entire conference tournament in one weekend, so there are still two days left in the regular season for six teams. Our calculator allows you to select the results of those games.

Second, if you input results that are not possible (for example, if you select Wisconsin to win the WCHA, but then go back and make them lose in the semifinals), the Predictor will inform you of the error and highlight the field(s) you need to fix.

The interface is pretty self-explanatory — just follow the instructions on the sheet. Starting with the CHA regular season games on the bottom right, use the drop-down menus to select who you think will win each game, progressing next to the conference quarterfinals, then across to the "Finals" and "Champion" columns.

The "Semis" column will autopopulate with teams based on conference tournament re-seeding rules depending on the results of the quarterfinals.

Once all of the white drop down fields are filled, the box at the top right will update to show the resulting Pairwise Rankings, including the 4 autobids and 4 at-large bids. The first two teams out are provided as well, to see how close they were to making the field. This will not update until all results are entered.

Note: This is based on a pretty big file. The sheet will take a few seconds to load. Also, it can sometimes take a couple seconds for the quarterfinals/semifinals picks to carry over into the semifinals/finals picks. Be patient; it will update.

Feel free to ask questions or let us know of any bug reports, either in the comments or by email at grant dot salzano at gmail dot com.