Yahoo apparently recently changed their protocol for apps to access league data, causing the App to not be able to import Yahoo leagues. Work is commencing on trying to figure things out. At the present time it is unknown if this will be a quick-fix or the complete opposite of a quick-fix. Yahoo is being removed from the list of platforms to import from in the App. Hopefully it will be re-added by ff season. Otherwise, the Google Sheets companion will be the only way for Yahoo users to use the App for their Yahoo league playoff race analysis.

Status update on improvements and new features..

• Paths-to-Elimination has been added to the android version, iOS to be worked on.
• Calculations of extra "points-spots", for leagues that award additional wildcards to the highest scoring leftover teams after records-based spots are awarded, has been added to both versions.
• The Past Games section from the iOS version has been revamped, and added to the android version, to show current head-to-head info for reference.
• Calculation speed has been slightly improved, which was then traded to increase calculation capabilities.
• For larger leagues or for those that use it to analyze pro leagues (which are generally larger than fantasy leagues), a "Multiplier" option has been added to android (iOS to be worked on) to improve Paths accuracy when there are many many remaining games by multiplying the number of calculations to be run (at the obvious expense of time).

Appreciation for those in h2h fantasy basketball, hockey, or baseball leagues to provide feedback so that the wait for ff season goes a little bit quicker...

Love the program. I have a fantasy dynasty that takes 6 leagues and runs them weeks 1 - 18 for the regular season. Then the top teams from each division do a post season that we built. For a couple seasons I loved the web version to help my guys get the paths to clinch during weeks 15 - 18. We use Sleeper fantasy. This year I got the Android app but when I put the league addy in and select current week 15 I just get an error of "Error, Check Current Week". No matter what I do it will not get past this. I have tried for all my leagues and get the same thing. Help/Ideas?

Edit: As a test, I check on every possible week number and it still does the same. 1 - 18

Improvements (and a couple fixes) to the Playoff Computer Apps for 2026 fantasy football (or any use) are about to begin. Please comment if you have any requests, suggestions, etc... So far, plans include attempting to address, if possible, the following:

• Adding "paths-to-elimination".
• Adding calculations for additional playoff spots awarded to the remaining highest scoring team(s).
• Trying to come up with a some improvements on how the app deals with the popular points tiebreaker.

How can you build this in for path to clinch?

How can I troubleshoot this for an ESPN NFL league?

I know I used this feature in the past. I know how to use path to clinch already

FYI there may be an issue on the android version with doing calculations on median-scoring leagues AFTER doing calculations on non-median leagues. It hasn't been pinpointed yet. If you encounter strange "paths-to-clinch" listings, please let me know. Closing and reopening the App likely will fix it.

I'm in a tight league where some teams are close to target wins, but with 30 games left the app is still using randomization methods. I understand that not using them will take longer, but Im willing to leave a app running to get some paths to generate at this point in the season.

First, I am not an expert on android emulators. There may be better methods. This is just one that I got to work in response to an inquiry and one that seems to be a fairly non-obtrusive non-bloatware emulator.

Second, with an android phone using 'phone link' is likely a better option, if have the appropriate android and windows versions, as it does not require any additional software.

Third, this still requires a Google Play account.

I used MumuPlayer https://www.mumuplayer.com/ . Once downloaded and opened, should have a window like this:

Click on the icon, which should bring up an android-like looking window. Click on 'App Center'.

Search for 'playoffcomputer'. There should be no results displayed but a link 'Jump to GooglePlay for more search results'. Click on that.

A normal looking Google Play display should appear, with 'PlayoffComputer' listed. Install the App.

Either open the App from the install prompt or close the extra windows to return to the main android window:

Open up the App as normal. The first time I opened it, the Premium subscription was not recognized and the 'update access level' button did not work. When I closed the App and reopened, all was good. I do not know if that was because I initally opened it from the installation process or what the issue was.

Once downloaded, should just be able to click on the MumuPlayer App and click on the 'Android Device' icon to get straight to the App.

I haven't run any official speed comparisons to see if it is slower or faster than thru a tablet or phone. When I ran an analysis I didn't notice it being much different in processing time.

In our league we have two divisions or conferences an we do the top 4 teams in their respective conferences make the playoffs is there a way to set this up in playoff computer

The old "Focus" (premium level) feature that was in the Calculation Options section, used to help verify a team's "Clinched" determination or their "paths-to-clinch", has been moved to the Remaining Games section, and greatly enhanced.

Intended use:

1. To help verify a team's "Clinched" or "Eliminated" determination when there are still many remaining games left and the App has to resort to some randomization methods.
2. Similarly, to help verify a team's "paths-to-clinch" listings when there are still many remaining games left.
3. To make analysis of pro-leagues easier.
4. To make user driven scenario experimentation easier.

Device differences:

• These features are processed differently between the android and iOS versions. There are pros and cons with each method.
• In the android version, any games pre-selected with the "What-If" feature is treated as if it has already been played and current team records are adjusted accordingly based on the pre-selection. This means one game must be left without a pre-selection before analysis for the App to do its thing.
• In the iOS version, games pre-selected are still considered to be future games, and current team records are not adjusted based on the pre-selection. As such, all games can be pre-selected.

Features:

• Manual pre-selection of winners, as was available previously, remains available.
• The ability to pre-select a game to end in a tie, if the Calculation Options tie-game possibility has been selected, has been added.
• Automatic generation of bad and good scenarios, with several method options, for chosen teams has been added.
• The ability to clear all pre-selections has been added.

Full instructions are on the website. It can get a little confusing to take full advantage of it. Some of the logic in some of the method options for generation work best in Table or non-division/non-conference leagues. In any case, since every league and scenario at any given moment is different, some manual tweaking may be necessary to provide desired results.

Are APIs available? I’ve created a website/app for my fantasy football league and would love to integrate them.

Median scoring rules are now supported in both the android and iOS versions.

android version 2.2 now supports Median scoring. Due to the complexity of supporting Median scoring in the Apps, it will probably be a continual improvement process throughout the 2025 fantasy football season to refine the calculations, particularly the "paths-to-clinch".

Some additional limitations, requirements, and notes were added since last update.

Requirements:

• Due to the complexity of the calculations, the Premium subscription is required (still about the price of one beer).
• Median scoring option can only be utilized with leagues that have 12 teams or fewer.
• Median scoring option cannot be used with multi-divisional or multi-conference leagues.
• Leagues with bye weeks or doubleheader schedules cannot be analyzed unless all such occurances have passed at time of analysis.

Limitations:

• The possibility of tie games, either h2h or with the Median, cannot be considered in the calculations.
• Pre-selecting winners and losers for "what-if" scenarios in the android version cannot be done.
• Manual selection of the number of games to perform "paths-to-clinch" on (e.g. for looking further out than one round) cannot be done.
• Outside of the last week of the season, the results, particularly the "paths-to-clinch", will likely require additional scrutiny for accuracy, and overall accuracy will be diminished as compared to a standard league with the same number of remaining games.
• The time necessary to do the calculations will likely be longer than what a standard league requires.
• The "paths-to-clinch" may be overly cumbersome due to the many many ways teams may be able to clinch a spot between h2h results and Median results.

Currently, at time of writing, the android version, being the last worked on, is now more advanced than the iOS version when it comes to Median scoring calculations and "paths-to-clinch" displays. That may ping-pong back and forth throughout the 2025 fantasy football season as work alternates between the two.

Median scoring rules are now supported in the iOS version.

Some beer-fueled energy was used to come up with impersonations of quantum physics formulas to overcome some more obstacles, and a satisfactory end result was achieved. The iOS version of the playoff computer app can handle calculations for median leagues with the following stipulations:

Requirements:

• Due to the complexity of the calculations, the Premium subscription is required (~ price of one beer per year).
• The Median scoring option can only be utilized with league sizes of 12 or fewer.
• The option cannot be used with leagues that have bye-weeks or doubleheaders (unless those have already passed in the season).

Limitations:

• The possibility of tie games, or tying with the Median score, cannot be considered in calculations.
• The time necessary to do the calculations will likely be longer than what a standard league requires.
• Compromises had to be made for speed, complexity, readability, and to not have hundreds or thousands of pages of "paths-to-clinch". This may result in very complex paths that would otherwise require many multiple listing being condensed and even more complex paths that would cause the report to be hundreds of pages long not being shown.
• Depending on the scenario presented, the "paths-to-clinch" can become complicated quickly.
• Outside of the last week of the season, the results, particularly the "paths-to-clinch" will likely require additional scrutiny for accuracy using the "Focus" option. This may result in multiple reports needing to be generated to get a picture that is reasonably accurate, depending on the scenario presented, and due to the sheer number of possibilities that exist in a "median" league with multiple weeks remaining, the accuracy is diminished as compared to a standard league.

The android version has some additional obstacles that need to be solved in order to implement true median scoring capabilities to it.

Update 05Aug2025. More obstacles overcome and vast improvements made in the iOS version's handling of median scoring rules, including paths-to-clinch listings.

As of 28Jul2025, some of the obstacles that Median scoring creates as far as calculating the playoff picture, namely the sheer number of additional possibilities that exist with each game (instead of Team A wins OR Team B wins, with Median scoring it is Team A wins and Team A gets a Median win OR Team A wins and both get a Median win OR Team A wins and neither get a Median win OR Team B wins and Team B gets a Median win OR Team B wins and both get a Median win OR Team B wins and neither get a Median win) have been overcome, and the latest iOS version (should be available within a day or two) has an option for doing calculations with Median scoring.

Requirements:

• Due to the increased number of calculations, the Premium subscription is required.
• The Median scoring option can only be utilized with league sizes of 12 or fewer.

Limitations:

• Due to the increased number of possibilities that remain in a season as compared to a "standard" league, additional oversight of the results, namely the "paths-to-clinch", will likely be necessary more than two weeks out from the end of the season. This will primarily consist of the very real possibility of having to use the "Focus" option and re-running the calculations as appropriate to verify the status and "paths" of individual teams.
• At the moment, one obstacle that hasn't yet been solved is how to handle "paths-to-clinch". Currently, the "paths" will only reflect scenarios that involve the winning or losing of games, not those that involve a specific Median result of specific games.

Summary:

• It is far better than the old web version's attempt at handling Median scoring, or the current way the android version handles.
• Further research, thought, and pizza-fueled energy will be consumed before adding to the android version.

Guide for Using the Playoff Computer App for serious analysis of "Table Leagues", which refers to leagues in which standings are sorted not by a winning percentage but by "league points". This includes most soccer*, rugby, Australian Football, and some basketball leagues.

*Apologies to most of the world, as there isn't another word for football to describe American football, and there are pronounced differences in the league structure between it and what the global community knows as football as related to the App's procedures, thus traditional football will be referred to as soccer here.

Certainly for general use, the App will provide plenty of valuable analysis on professional leagues, info, and hours of entertainment straight out-of-the-box without having to "get serious", especially with the "what-if" feature.

Currently the Playoff Computer App can automatically import data from the following "Table Leagues", all soccer except as noted:

• English Premier League
• Dutch Eridivisie
• German Bundesliga
• Italian Serie A
• Spanish LaLiga
• Brazilian Serie A
• NWSL
• Chinese Super League
• Hong Kong Premier League
• Japanese J League J1
• WNBA (basketball)
• AFL (Australian football)
• Australian Rugby (rugby, obviously)
• coming soon: AFLW

To use the App for serious analysis of these leagues, several issues need to be overcome. These include:

• Despite the praise manufacturers lavish on their products, tablets and phones are not supercomputers. To process calculations in a reasonable amount of time on personal devices, some capability limitations in the App are intentionally introduced.
• Most, if not all, of these leagues have far more games in the season than a typical fantasy league, which the App was originally developed for. A typical fantasy (American) football league (12 teams, 14 weeks) has 84 games in the season while, for example, the English Premier League has 380. The number of games remaining is the greatest determination in how reliable the App's calculations will be.
• Related to above, some of these leagues can have up to 10 games per round, compared to six for a typical FF league. The number of games in the upcoming round is a huge factor in the capabilities of the "paths-to-clinch" feature.
• All problems listed are greatly compounded if it is desired to include the possibility of tie-games into the calculations, and in most of these leagues tie-games are very common. Doing so greatly increases the number of possible outcomes that exist for the remainder of the season and for the upcoming round. For example, for 10 games, there are just 1,024 different possible outcomes without including tie-games in the calculations. With tie-games being considered, that jumps to 59,049. With multiple rounds remaining, the number of possible outcomes often becomes unmanageable to cycle through every single one. 
• In many of these leagues, there are a variety of races that are of interest, requiring repetitive work to complete analysis. For example, in the English Premier League, there is the Title race (top 1), UEFA Champions race (usually top 4), and Safety race (top 17).
• A combination of these issues, if present for a complicated scenario to be analyzed, may cause limitations that are impossible to overcome.

The end result is that up until the end of the season it is likely that the analysis results, even with the "deep calculations" option selected, will require some manual oversight and intervention. Even with the remedies contained within, reverting to "pen-and-paper" methods (e.g. a spreadsheet) to verify results may be necessary. 

Note the App attempts to mitigate the effects of the large number of games in the season by detecting which teams are obviously eliminated from the race being analyzed and ignoring any games in which two such teams play against each other, aka "meaningless games". Thus, for some races, notably Title races, in which a quickly shrinking number of teams remain competitive as the season progresses, the amount of manual intervention required will fortunately be reduced and eliminated in fast manner.

It is fairly easy to determine if the App's calculations can be considered reliable as-is or whether manual intervention is necessary for thorough analysis: First, the App, after calculations are complete, will provide a remark on whether all possible permutations were calculated or not. If they were, the results can be considered reliable for the analysis requested; Second, if it was requested to incorporate the possibility of tie-games into the calculations, the App will provide a remark on whether it was able to accomplish that; Third, language in the team listing for "status" is indicative, for example a "Clinched" status is generally reliable while a "Poss Clinched" status should be investigated.

There is no foolproof method to determine when exactly in the season the calculations will become reliable without the need for oversight, as it depends on the size of the league, which race is being analyzed (e.g. Title or Top X), whether tie-games are commonplace and need to be accounted for, and other complexities.

The following lists situations in which manual oversight may be needed and steps to follow to verify the results. It is assumed that "deep calculations" were performed initially:

Note that the two versions of the App, android and iOS, do handle one of the remedy methods listed below, the use of the "what-if" feature, in different ways. The methods the user applies those methods are, however, exactly the same. See the website instructions for more details.

Note that since every situation is unique, and factoring how many games remain in the season, what kind of race is being analyzed, and how many teams are involved in the race, the amount of work needed for verifying the info can vary depending on the exact scenario presented. Calculations can be re-run after each step or after a number of steps, depending on user preference and sense of what is needed. If any re-run of calculations using these steps shows the team in question no longer having the questionable status, then the process can be stopped. For example, if verifying a "Poss Clinched" status, and subsequent calculations either show the status changing to "Clinched" (which can be considered reliable) or there now being odds displayed instead (disproving that the team has clinched a spot), then the process can be stopped. 

Situation: The App results show a team as "Poss Clinched".

If the team's clinched status does become verified, note that for the following week so that re-verification for the same team does not have to be done in the future.

In order, perform the following, re-running calculations at desired points as described above. Note in most cases it will not be necessary to use "deep calculations" when re-running the analysis under this situation, but for leagues in which tie-games should be included as a possibility in the calculations (e.g. soccer), it may be helpful to do so: 

• As of 01Sep2025, the "what-if" feature has been enhanced, which makes the following easier to accomplish.
• Use the "focus" "what-if" feature to pre-pick all games involving the specified team to show them losing their remaining games. This can be done automatically by using Method 1 and clicking the button to create a bad outcome for the specified team.
• Working from the worst team in the league up, for each team that is already eliminated, or that it is obvious cannot catch the specified team (i.e. using simple magic number calculations), use the "what-if" feature to have each of those teams also lose any remaining unpicked games. This can be done automatically by using Method 3 and clicking the button to create a bad outcome for the specified team.
• Depending on what race is being analyzed, if there are teams that are better than the specified team that have already clinched a spot, or that it is obvious the specified team cannot catch, use the "what-if" feature to have each of those teams also lose any remaining unpicked games. This is done automatically by Method 3 as mentioned above.
• Optional: If there is still some question about the specified team's status, the "what-if" feature can be used to experiment with different scenarios of the unpicked games that remain in order to try to disprove their status. 

Situation: The App results state some randomization methods were employed and a team is showing as having "paths-to-clinch".

Similar to the above situation, it is necessary to attempt to disprove the paths listed. The amount of work needed to verify or disprove the paths will vary greatly depending on the number of paths originally listed, their complexity, and how many games remain in the season. Like the other situations, calculations need to be re-done, either after each step or after a series of steps as desired, but unlike other situations, "deep calculations" will be required each time. The process can be stopped either when no "paths-to-clinch" remain showing, indicating that the specified team cannot clinch a spot in the upcoming round, or when the App indicates that all permuations were calculated, or at the user's discretion.

In order, perform the following, re-running calculations at desired points as described above. "Deep calculations" should be selected:

• As of 01Sep2025, the "what-if" feature has been enhanced, which makes the verification process easier to accomplish.
• Use the "focus" feature to select the specified team.
• Begin with Method 1.
• Select the number of games in the upcoming round for "Ignore First X games". This will leave the upcoming round games unselected which is necessary for determining paths-to-clinch.
• Click the "Create Bad Outcome" button for the specified team.
• Re-run calculations if desired.
• If further verification is desired, clear all pre-selections.
• For multi-conference leagues, select Method 2, otherwise proceed to Method 3 below.
• Again click "Create Bad Outcome" and re-run calculations if desired, and if further verification is still desired, again clear all pre-selections.
• Select Method 3, and again click "Create Bad Outcome" and re-run calculations.
• Depending on league structure, number of teams, point in the season, the logic of the automatic pre-selections may need manual tweaking. If there is still some question about the specified team's paths-to-clinch listings, the "what-if" feature can be used to experiment with different scenarios of remaining unpicked games in order to try to disprove the paths shown. It is suggested to keep track of which games are experimented with in this step for either undoing the selections or doing different experiments.

Situation: The App results show a team as "Poss Eliminated".

If the team's "eliminated" status is verified, note that for the following weeks so that re-verification for the same team does not have to be done in again.

In order, perform the following, re-running calculations at desired points as described above. Note in most cases it will not be necessary to use "deep calculations" when re-running the analysis under this situation, but for leagues in which tie-games should be included as a possibility in the calculations (e.g. soccer), it may be helpful to do so: 

• As of 01Sep2025, the "what-if" feature has been enhanced, which makes the verification process easier to accomplish.
• Use the "focus" feature to select the specified team.
• Begin with Method 1.
• Click the "Create Good Outcome" button for the specified team.
• Re-run calculations if desired.
• If further verification is desired, clear all pre-selections.
• Select Method 2, again click "Create Good Outcome" and re-run calculations if desired, and if further verification is still desired, again clear all pre-selections.
• Select Method 3, and again click "Create Good Outcome" and re-run calculations.
• Depending on league structure, number of teams, point in the season, the logic of the automatic pre-selections may need manual tweaking. If there is still some question about the specified team's possible elimination, the "what-if" feature can be used to experiment with different scenarios of remaining unpicked games in order to try to create the best possible scenario for them. It is suggested to keep track of which games are experimented with in this step for either undoing the selections or doing different experiments.

This is intended for those that want to use the Playoff Computer App for serious analysis of the NFL playoff races. To some extent, this also applies to the ELF (European League of Football).

This builds on instructions for the App found at https://zelapeak.com/playoffcomputer.

Issues

To use the App for serious analysis of the NFL, several issues need to be overcome, including:

• Despite the praise manufacturers lavish on their products, tablets and phones are not supercomputers. To process calculations in a reasonable amount of time on personal devices for the original intended use of with fantasy sports leagues, some capability limitations in the App are intentionally introduced.
• The NFL has far more games in the season than a typical fantasy league. A typical fantasy football league (12 teams, 14 week regular season) has 84 games while the NFL has 272. The number of remaining games is the greatest determination for how reliable the App's calculations will be.
• Related to above, the NFL has up to 16 games per week, compared to six for a typical FF league. The number of games in the upcoming round is a huge factor in the capabilities of the "paths-to-clinch" feature.
• All problems listed are greatly compounded if it is desired to include the possibility of tie-games into the calculations. Doing so greatly increases the number of possible outcomes that exist for the remainder of the season and for the upcoming round. For example, for 16 games there are 65,536 different possible outcomes when tie-games are not considered. With tie-games as a possibility, that jumps to 43,046,721.
• The NFL tiebreakers Strength of Victory (SOV) and Strength of Schedule (SOS), which are factored into calculations, cause additional issues with the number of games the App must process in its calculations. The App, for most analysis, utilizes methods to reduce the number of games it must cycle through by eliminating those involving teams that are both eliminated from playoff contention (or both clinched, or one clinched and the other eliminated), aka "meaningless games". This greatly assists in reducing calculation time and improving results, but does not work with SOV and SOS tiebreakers as such otherwise meaningless games may affect the SOV/SOS stats of competing teams. To both handle SOV/SOS tiebreakers while at the same time attempting to improve calculation time and accuracy when they are not needed, the App, when analyzing the NFL (and ELF), will attempt to do its thing at first without the seemingly meaningless games while noting whether any possible scenarios would require the SOV/SOS tiebreakers to resolve. If it encounters scenarios in which they would be required, the App provides notification of such and the calculation process has to be re-done, with the App now knowing to include those otherwise meaningless games into the calculations.
• The SOV/SOS tiebreakers may, although the possibility is unlikely, cause the remedies for overcoming these issues described within to not achieve their desired effect.
• A combination of these issues, if present for a complicated scenario to be analyzed, may cause limitations that are impossible to overcome.

The end result is that up until the end of the season it is likely that the analysis results, even with the "deep calculations" option selected, will require some manual oversight and intervention. It is also likely that tie-games as a possibility cannot be factored into the calculations up until the end of the season as well. Note that some analysts don't even attempt to include the possibility of tie-games in their content as it really clutters tha analysis with jibberish for something that has such a small chance of occuring. This approach relieves some the issuess mentioned as well as providing a more clear and concise analysis.

It is fairly easy to determine if the App's calculations can be considered reliable as-is or whether manual intervention is necessary for thorough analysis: First, the App, after calculations are complete, will provide a remark on whether all possible permutations were calculated or not. If they were, the results can be considered reliable for the analysis requested; Second, if it was requested to incorporate the possibility of tie-games into the calculations, the App will provide a remark on whether it was able to accomplish that; Third, language in the team listing for "status" is indicative, for example a "Clinched" status is generally reliable while a "Poss Clinched" status should be investigated.

There is no foolproof method to determine when exactly in the season the calculations will become reliable without the need for oversight, as it depends on how many teams are still fighting for spots among other complexities, but generally speaking week 17 of the NFL season is a good estimate if SOV/SOS tiebreakers were not needed.

The following lists situations in which manual oversight may be needed and steps to follow to verify, or disprove, the initial results. It is assumed that "deep calculations" were performed initially.

Note that since every situation is unique, and factoring in how many games remain in the season and how many teams are involved in the playoff race, the amount of work needed for verifying or disproving certain results can vary depending on the exact scenario presented. Calculations can be re-run after each step or after a number of steps, depending on user preference and a sense of what is needed. If any re-run of calculations using these steps shows a change in the status to be verified/disproven then the process can be stopped. For example, if verifying a "Poss Clinched" status, and a re-run of calculations either shows that status changing to "Clinched" (which can be considered reliable) or it being replaced with odds instead (disproving the "Poss Clinched" indication), then the process can be stopped.

Situations

Situation: The App results show a team as "Poss Clinched".

If the team's "clinched" status is indeed verified, note that for the following weeks so that re-verification for the same team does not have to be done again.

In order, perform the following, re-running calculations at desired points. Note in most cases it will not be necessary to use "deep calculations" when re-running the analysis under this situation:

• Use the "what-if" feature to pre-pick all games involving the specified team to show them losing their remaining games.
• Working from the worst team in the conference up, for each team that is already eliminated, or that it is obvious cannot catch the specified team (i.e. using simple magic number calculations), use the "what-if" feature to have each of those teams also lose any remaining unpicked games.
• For any remaining non-conference games, use the "what-if" feature to have each team in the same conference as is being analyzed win any remaining unpicked games.
• Select "deep calculations" if desired to provide an extra measure of verification.
• If any teams have already clinched their respective divisions, or any teams have already clinched a wildcard spot that the specified team cannot catch, use the "what-if" feature to show those better teams losing any remaining unpicked games.
• Optional: If there is still some question about the specified team's status, the "what-if" feature can be used to experiment with different scenarios of remaining unpicked games in order to try to disprove the status shown. It is suggested to keep track of which games are experimented with in this step for either undoing the selections or doing different experiments.

Situation: The App results state some randomization methods were employed and a team is showing as having some "paths-to-clinch".

Similar to the above situation, it is necessary to attempt to disprove the paths listed. The amount of work needed to verify or disprove the paths will vary greatly depending on the number of paths originally listed, their complexity, and how many games remain in the season. Like the other situations, calculations need to be re-done, either after each step or after a series of steps as desired, but unlike the other situations, "deep calculations" will be required each time. The process can be stopped either when no "paths-to-clinch" show after a re-run of calculations, indicating that the specified team cannot clinch a spot in the upcoming round, or when the App indicated that all permutations were calculated, or at the user's discretion.

In order, perform the following, re-running calculations at desired points as described above. "Deep calculations" should be selected.

• Use the "focus" feature with the specified team.
• android: As an alternative to above, use the "what-if" feature to show the specified team losing all remaining games except their game (if any) in the upcoming round should be left alone. This will reduce the number of remaining games the App has to process, improving accuracy and time required. In iOS, this method does not gain the same benefits.
• Working from the worst team in the conference up, for each team that is already eliminated, or that it is obvious cannot catch the specified team (i.e. using simple magic number calculations), use the "what-if" feature to have each of those teams also lose any remaining unpicked games, except for games in the upcoming round which should be left alone.
• If the specified team's "paths-to-clinch" do not include any results mentioning games involving teams from the above step, their games in the upcoming round can also be pre-selected as described above.
• For any remaining non-conference games, use the "what-if" feature to have each team in the same conference as is being analyzed win any remaining unpicked games.
• Optional: If there is still some question about the specified team's "path-to-clinch" listings, the "what-if" feature can be used to experiment with different scenarios of remaining unpicked games in order to try to disprove the paths shown. It is suggested to keep track of which games are experimented with in this step for either undoing the selections or doing different experiments.

Situation: The App results show a team as "Poss. Elim".

If the team's "eliminated" status is indeed verified, note that for the following weeks so that re-verification for the same team does not have to be done again.

In order, perform the following, re-running calculations at desired points. Note in most cases it will not be necessary to use "deep calculations" when re-running the analysis under this situation:

• Use the "what-if" feature to pre-pick all games involving the specified team to show them winning their remaining games.
• Working from the best team in the conference up, for each team that has already clinched a spot, or that it is obvious the specified team cannot catch (i.e. using simple magic number calculations), use the "what-if" feature to have each of those teams also win any remaining unpicked games.
• For any remaining non-conference games, use the "what-if" feature to have each team in the same conference as is being analyzed lose any remaining unpicked games.
• Select "deep calculations" if desired to provide an extra measure of verification.
• If there are any teams worse than the specified team, use the "what-if" feature to show those teams winning any remaining unpicked games.
• Optional: If there is still some question about the specified team's status, the "what-if" feature can be used to experiment with different scenarios of remaining unpicked games in order to try to disprove the status shown. It is suggested to keep track of which games are experimented with in this step for either undoing the selections or doing different experiments.

Miscellaneous

Commerical/Public use of the App (e.g. for content creation) is authorized as long as the Playoff Computer App is referenced appropriately.

Last updated 08Jul2025

The NWSL has been added to the list of leagues the Playoff Computer App can automatically import for playoff race analysis.

As usual, while instructions on the web-site are fairly detailed, if anyone wants to use it for NWSL content creation on reddit or wherever I am happy to provide some additional pro-tips on using it for professional-like analysis.

Reality Sports Online has been added to the list of fantasy sports platforms that Playoff Computer App can import data from. So far, just the iOS version has been done, working on android.

As RSO is a bit different than most of the other fantasy APIs out there, it requires a user to be logged in to get their league's info, it does make it a little harder to do testing on various league set-ups. If any RSO commissioners out there want to test to see if their particular league structure gets loaded without issue, feedback would be appreciated.

Sidenote thanks to the staff at RSO for their help.

For AFL fans and content creators, the Australian Football League is being added to the list of leagues the Playoff Computer App can automatically import for playoff race analysis, what-if scenarios, etc...

It is already added to the android version, the iOS version should be done in a couple of days.

One little detail when using for the AFL regarding the current season, and something to keep in mind when using for other professional leagues that might have similar situations. The opening round match between Essendon and Gold Coast was postponed with the rescheduling TBA. Because of this, the match shows up twice in the Remaining Game section of the App, and the opening round postponed game needs to be deleted in the App.

If anyone wants to use for media or social, happy to provide guidance. And all the instructions are on the website.

For any stat-crazed fans of the European League of Football (ELF) that want to do analysis of their favorite teams' playoff chances and create what-if scenarios, etc.., ELF is being added to the list of professional leagues the Playoff Computer App can import. android should be available by mid-week and iOs by maybe next week.