> 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/all-competition-types/team-race.md).
# Team race
## Definition
A race is said to be a team race when:
* Each participant is registered individually and bound to his team,
* The race ranking is calculated based on individual results, for example the finishing time of the 3rd runner of each team,
* The race ranking is a team ranking, with individual results being secondary on displays.
{% hint style="info" %}
This framework for team races does not include [relay races](/en/all-competition-types/relay-races.md), which are handled differently by the software.
{% endhint %}
## Settings
A team event can be created by choosing a type of team event in the event creation wizard, or by checking the Team Race option among the event properties.
A team time trial is naturally considered a team race.
In the context of a stage race, the activation of the *Team Race* option is valid for the event as a whole, that is to say for all stages.
## Team data
Some properties applicable at the team level are available by clicking the button that appears when the mouse hovers over a cell in the team column. These include, for example, the team category, which will be used for ranking, a bib/team number, or the nationality.
### Team categories
Team categories are derived from a list independent of individual categories. Automatic allocation rules can be defined, based on the number of teammates, the number of men or women, or the categories of each teammate.
An additional option allows you to simply transfer individual categories as team categories, in case these have already been assigned upstream before import (e.g. category of type 'Mixed Duo' on each bib).
## Team list
The `Teams` tab, located to the right of the `Participants` tab, displays a grid of teams. This grid can be sorted and filtered (for example, by race). The multi-edit tool (context menu) allows you to assign the same value to a series of selected teams.
## Mixing team races with individual races
If your event consists of both individual and team races, you can manage them in the same file by:
* declaring the event itself as a team race, at the general level
* declaring one or more races as individual - after indicating those races have some specific settings
## Managing rankings
The main difference with an individual event is that it is the [team ranking](/en/other-features/team-rankings.md) that will be published.
This ranking can be configured with criteria specific to the competition - calculation method, tie-breaking rules, ... and these criteria can be specific to each race of the event if necessary.
When printing or exporting the team ranking, it is possible to select which data is present. Among these data we find the results for intermediate split points and for segments, which will display the times and places of the team calculated according to the same criteria of the team ranking.
### Podiums
The podiums presented correspond to the team ranking of the event, and are calculated on the basis of the categories assigned to the teams where applicable.
### G-Live
On the G-Live application, the results naturally present the team rankings.
---
# 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/all-competition-types/team-race.md?ask=&goal=
```
`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.