> 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/additional-classifications.md).

# Additional classifications

The additional classification are rankings separate from the main ranking, typically based on a points system.

In cycling this will for example be the classification of the best climber, the classification by points, or even the combined classification.

2 types of additional classifications are possible:

* with subclassifications, where recipients of each subclassification are assigned manually
* made up of the main ranking, on which a filter is applied (for example the best young rider)

## Manage additional classifications

<figure><img src="https://1159484786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJRt17XpwpUQzKYPTGL7Z%2Fuploads%2FuMKLs3DSi0dQkGR8J9tS%2Fimage.png?alt=media&amp;token=187762d7-d65c-48b5-8f29-dc2e73f3c733" alt="" width="563"><figcaption></figcaption></figure>

On the ribbon, the `Additional classifications` group allows you to access predefined rankings, or create a new one.

Selecting a ranking displays it at the same level as the main grids and you will then find it as a tab:&#x20;

<figure><img src="https://1159484786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJRt17XpwpUQzKYPTGL7Z%2Fuploads%2FYBvIN5ILMhIxuhRtr1Pf%2Fimage.png?alt=media&amp;token=e06217c4-a1d6-4332-897f-c87338fad5bc" alt=""><figcaption></figcaption></figure>

## Main properties

The general properties of a ranking, in addition to its name, are:

* an optional filter to obtain the ranking directly from the main ranking (for example the best young rider)
* the tiebreaking rules, to be ordered if necessary to adapt to the rules of the event

## Sub-classifications

You can add sub-classifications within a stage. For example an intermediate sprint, a pass summit.

## Entering points and bonuses

The grid allows you to pre-fill the series of points to be assigned for a sub-classification. For example 5, 3, 2 respectively for the first 3 competitors.

Bonuses are entered in seconds, and will apply to the main ranking.

## Automatic filling

Recipients of a sub-classification can be entered manually, or automatically if you have an intermediate split point to attach to it:

<figure><img src="https://1159484786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJRt17XpwpUQzKYPTGL7Z%2Fuploads%2FjHScPQXenIKF4CASBHdV%2Fimage.png?alt=media&amp;token=b4bbccd9-8609-47a2-a8d2-5a76307dd831" alt="" width="211"><figcaption></figcaption></figure>

In the case of a lap race, this may be the intermediate ranking at a certain lap.

The finish case for the points classification is automatically linked to the finish line.

## General classifications

For each sub-classification Wiclax will calculate a summary total for the stage and a general classification at the end of the stage.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.wiclax.com/en/other-features/additional-classifications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
