# Team Standings RulesΒΆ

In Tabbycat, you can choose how teams are ranked in the team standings. For
example, at Australs, teams are ranked first on the number of wins, and second
on their total speaker score. The setting that specifies how teams are ranked is
called the *team standings precedence*. The team standings precedence is used

- when displaying the team tab,
- whenever a power-paired draw is generated, and
- when computing which teams are in the break.

When you choose the team standings precedence, you choose from a list of
*metrics*. Then, in the standings, teams will be sorted first by the first
metric, then by the second metric, and so on. You must choose at least one
metric, and you can choose up to eight. Teams tied on all metrics will have the
same rank.

Metric | Description |
---|---|

Wins |
How many debates the team has won. |

Points |
How many points the team has. Currently, this is just a synonym for wins, and differs only in column labelling. |

Points (2/1/0) |
How many points the team has, where teams earn 2 points for a win, 1 point for a loss and 0 points for a forfeit. |

Total speaker
score |
The sum of all speaker scores attained in all debates. |

Average speaker
score |
The average total speaker score over all debates the team has had, not counting debates where they or their opponents forfeited. |

Sum of margins |
The sum of all margins. Wins are positive, losses are negative. |

Average margin |
The average margin over all debates the team has had, not counting debates where they or their opponents forfeited. |

Draw strength |
The sum of the number of wins of every team this team has faced so far. This is also known in some circuits as |

Votes/ballots
carried |
The number of adjudicators that gave this team a win
across all of their debates. Also known as the number
of In cases where the panel is smaller or larger than 3, this number is normalised to be out of 3. For example, if a panel of five splits 3–2, then the winning team is recorded as gaining 1.8 votes, and the losing team is recorded as gaining 1.2. This also means that solo adjudicators are always worth three votes. |

Who-beat-whom |
If there are exactly two teams tied on all metrics earlier in the precedence than this one, then check if the teams have faced each other. If they have, the team that won their encounter is ranked higher. If they have seen each other more than once, the team that has won more of their encounters is ranked higher. If there are more than two teams tied, this metric is not applied. This metric can be specified multiple times. Each time who-beat-whom occurs, it applies to all the metrics earlier in the precedence than the occurrence in question. |

Who-beat-whom
(in divisions) |
As for who-beat-whom, but only compares for teams in the same division. That is, the metric applies whenever there are exactly two teams from the same division exactly tied. |

Note

Some debugging information is printed to the logs when some of these metrics are invoked.