> For the complete documentation index, see [llms.txt](https://docs.wiclax.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wiclax.com/en/other-features/team-rankings.md).

# Team rankings

Wiclax can calculate many types of team rankings. You can access them from here:

<figure><img src="/files/2ZPiF95PLpd58SA5MGO2" alt="" width="256"><figcaption></figcaption></figure>

These rankings are displayed in a side tab:&#x20;

<figure><img src="/files/TDxhX6nfuaOrYlotXHMx" alt="" width="421"><figcaption></figcaption></figure>

There you will find the list of ranked teams with details of the teammates' performances, as well as the possibility of selecting the scope of the ranking, for example a race.

{% hint style="info" %}
In the case of a stage race, you can consult the team classification of the stage as well as the general team classification at the end of the stage.

If intermediate split points or segments are defined, one can also consult their own team ranking corresponding to this moment in the race.
{% endhint %}

## Ranking criteria

By clicking on `Ranking criteria` the ranking settings form opens.

<figure><img src="/files/dAqt4O2o3hlk2STZBglq" alt="" width="370"><figcaption></figcaption></figure>

It allows you to manage criteria either at the general level or at the more specific level of a race or a stage. From the moment more specific criteria are defined, these will be apply instead of the general criteria.

### Main criterion

The main criterion is to be selected from the possibilities: sum of times, sum of ranks, time of the last teammate, ...

### Filters and conditions

Adding a filter makes it possible to restrict the selection of competitors concerned by the ranking:&#x20;

<figure><img src="/files/6c5mNhDMHAD5b5LJHchJ" alt="" width="342"><figcaption></figcaption></figure>

Note the additional option that is important: when the calculation involves the ranks of the competitors, it determines whether these ranks must be relative to the filtered selection or not. That is to say, in this example, if the rank of a competitor comes from a ranking including TEAM XX or not.

Other conditions allow you to specify more complex rules for team formation:&#x20;

<figure><img src="/files/ropxppwFpJi4RRCmC8F3" alt="" width="217"><figcaption></figcaption></figure>

These rules are cumulative.

Without specifying a value for a data field, the condition simply relates to the number of teammates.

### Tie splitting rules&#x20;

The tie splitting rules block allows you to modulate their order of priority. That makes it possible to finely comply with the rules of the event.

<figure><img src="/files/U18IDMYME1aDjJMRTtnT" alt="" width="332"><figcaption></figcaption></figure>

### *Team* data

In the `Calculation Options` section, you can designate a data other than *Team* or *Club* to make out the ranking. For example, a *Company* field.

### Mixed teams

The Mixed Teams block allows you to specify what constitutes a mixed team.

For example, if we say that 2 female finishers are required, a team at the finish with only one female will still be considered a Men's team.

NB: this setting does not imply that we only want to classify mixed teams. If necessary, we should rather work with a [condition](#filters-and-conditions) of type `minimum 1 female`.

## Grouping

The Grouping button allows you to obtain a grouped ranking, either by gender or by categories. With 2 variants for the gender being either individual gender or team gender. Only the 2nd one will allow for mixed teams.

## Printing

From the print preview, you can choose a level of detail regarding the information of the different teammates:

<figure><img src="/files/DSefcYdJlP5SQXWoOu3g" alt="" width="311"><figcaption></figcaption></figure>

## Publishing

Team rankings are only published on the Internet (G-Live) if marked as such.

<figure><img src="/files/lzZr0T41pdMTtK7dvGsf" alt="" width="343"><figcaption></figcaption></figure>

Remember to repeat the operation for the different races concerned, if necessary.

## Other team rankings

If you need to manage a specific ranking, for example a company ranking, in parallel with the standard team ranking, you can create it here:&#x20;

<figure><img src="/files/7c9lm6fZWaM0zsctdmgp" alt="" width="204"><figcaption></figcaption></figure>

You can then edit its criteria independently.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.wiclax.com/en/other-features/team-rankings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.