> 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/penalties-and-bonuses.md).
# Penalties and bonuses
Bonuses and penalties affect a competitor's performance, either positively or negatively.
In addition to a dedicated entry space, bonuses can also come from [additional classifications](/en/other-features/additional-classifications.md).
## Entry
Bonuses and penalties are managed in a similar form. The scope of it is only the current stage in the case of a stage race.
2 distinct lists of bonuses/penalties: one for individual participants, the other one for teams.
Entering a reason is optional.
The bonus or penalty may be expressed in time or in points. The case of points will apply to the points classification (as a [secondary classification](/en/other-features/additional-classifications.md)) or to the main individual ranking in the case where it is based on points.
{% hint style="info" %}
It is possible to copy and paste a list to fill the grid. The origin of the data can be the grid itself (for a duplication) or external. A control + V on the grid will launch the operation, triggering the import wizard if necessary.
{% endhint %}
## Target
In the case of a stage race, it will be necessary to ensure that this parameter of the event is positioned appropriately. The choice of the general classification is more specifically suited to cycling races.
On the Timekeeping tab in the Event options
On a general classification, a red or green circle indicates the presence of bonuses or penalties which affect the result:
---
# 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/penalties-and-bonuses.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.