> 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](https://docs.wiclax.com/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`).

<figure><img src="https://1159484786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJRt17XpwpUQzKYPTGL7Z%2Fuploads%2FdiuJBlQ4Gh5kRx0V7g0V%2Fimage.png?alt=media&amp;token=87af806a-6fdd-4a3f-a2e4-db3677db4d7f" alt=""><figcaption></figcaption></figure>

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 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/event-variables.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.
