> For the complete documentation index, see [llms.txt](https://help.runonrufus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.runonrufus.com/rufus-race-manager/races/races-menu.md).

# Races Menu

The **Races Menu** in **RUFUS Race Manager (RRM)** is where you view and manage all races defined for an event. From here, you can open race dashboards, edit race settings, and create new races.

<figure><img src="/files/ZrCHYqfGhUFkjiWz2BgD" alt=""><figcaption><p>Races Menu List</p></figcaption></figure>

## Viewing Defined Races

* All races already created for the event are listed in this menu.
* Each race is shown by **name**, making it easy to identify.
* Next to the race name, you can also see the number of checkpoints associated with that race.

#### Opening a Race

Clicking on a race name opens the **Race Dashboard**, where you can find detailed information and tools to manage that race.

#### Editing a Race

Hover over a race name and click the **pen icon** to open the **Edit Race modal**, where you can adjust race details such as name, distance, and other configurations.

## Creating a New Race

At the bottom of the Races Menu, you’ll find the **Add races** section.

* **Classical (V2)** → Create a traditional mass-start race. This is the standard format for most running, cycling, and triathlon events.
* **Laps/Time-Trial** → Create lap based races. This is the standard format for most motor sports events.

## Creating a Race Course

Operators can design a race course directly on an interactive map with the **Course Designer**, either by drawing it manually or importing it from **GPX/KML**. Event checkpoints can be placed as shared physical locations and reused across multiple races, making setup cleaner and faster.


---

# 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://help.runonrufus.com/rufus-race-manager/races/races-menu.md?ask=<question>&goal=<endgoal>
```

`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.