> 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/event-variables.md).
# Event variables
Event variables are data that you can declare freely, and then use:
* on a print template
* in a custom data export
* in a [calculation formula](/en/other-features/calculated-fields.md)
In the first two cases, it will be possible to define reusable printing or export models regardless of the event.
More generally, these variables allow you to define data at the race level that are not managed natively by Wiclax, for example the air temperature, the name of the assistant referee, etc.
To access the entry: Variables tab of the event options window or search for the command (`control + p`).
The `name` of a variable will also be its identifier when it is requested for an export/print/formula.
The same name can be replicated to provide different values to the same variable depending on the race. The grid can be grouped on the name column for ease when revisiting existing variables.
In the case of a stage race, each variable can similarly take on a new value for each of the stages, always by duplicating the rows.
{% hint style="info" %}
The `Copy` button allows you to duplicate a variable row for all races in the event.
{% endhint %}
---
# 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/event-variables.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.