# Creating a Classical Race Creating races in **RUFUS Race Manager (RRM)** is a key step in configuring an event. A race defines the checkpoints, rules, and timing policies used to calculate results and track participants. ### Race Types RRM currently supports two race formats:
Race TypeDescription
CLASSICALTraditional race format with an optional START checkpoint and a required FINISH checkpoint. Intermediate checkpoints can be added along the course.
LAPSLap-based races such as circuits or multi-loop formats.
This article focuses on creating a **CLASSICAL race**. ## Accessing the New CLASSICAL Race Dialog To create a new race: 1. Open the **Races** section from the left navigation bar. 2. Click **Add races**. 3. Select **CLASSICAL**. The **Add Race dialog** will open, where you can configure the race structure and timing policies.

Classical Race Dialog

## Filling Out Race Details In the **New Race modal**, complete the following fields: * **Race name** → Enter a descriptive name (e.g., *5K Run*, *Mountain Bike Challenge*). * **Sport** → Select the sport type (e.g., RUN, BIKE, TRIATHLON, TRAIL\_RUN, OBSTACLE\_COURSE, etc.). This helps with classification and participant management. ## Assigning Checkpoints A race is built from **checkpoints**, which represent timing points along the course. To add checkpoints: 1. Select a checkpoint from the list. 2. Choose its **type**. 3. Click **Add to Race**. Checkpoint types include: | Type | Description | | ---------------- | --------------------------------------------- | | **START** | The race start checkpoint. | | **INTERMEDIATE** | A checkpoint placed between start and finish. | | **FINISH** | The race finish checkpoint. |

Race Structure Diagram

### Lap IDs Each checkpoint receives an automatic **Lap ID**. | Checkpoint | Lap ID | | ------------ | ----------------- | | Start | 0 | | Intermediate | Sequential values | | Finish | 9999 | #### Rules * Each race must contain **at least one FINISH checkpoint**. * A race can only contain **one START** checkpoint. * Intermediate checkpoints can be added freely. ## Start Policies Start policies define how the system behaves when start passings are missing or ambiguous. ### Auto-create lap 0 If no valid start passing is detected, the system automatically generates a **synthetic start passing** at: ``` Race start time + 1 millisecond ``` This is useful when participants stand on the start mat before the gun and the system does not record a clean start passing. ### Allow finish without start If enabled, participants who cross the **Finish checkpoint without a recorded Start** will still receive a valid finish time. If disabled, finish passings without a valid start will be ignored. ### Auto-select last start time When multiple start passings are detected for a participant, this policy determines which start time will be used. If enabled: * The system will use the **last detected start passing** as the official start. This helps handle situations where participants cross the start mat multiple times before leaving the start area. ## Auto-Generate Race Segments RRM can automatically generate all possible timing segments for the race based on the configured checkpoints. When this option is enabled, RRM creates a proposed segment set before saving the race. This may include: * Gun-time segments * Chip-time segments * Intermediate checkpoint splits * Checkpoint-to-checkpoint segments Before the race is created, RRM opens a **Review generated segments** screen where you can check and adjust the proposed segments.

Review Generated Segments Dialog

In this review step, you can: * Rename segments. * Remove segments that are not needed. * Select the race order segment. * Set the discipline for each segment. * Set the length of each segment to enable pace calculations. These segments are used for participant results, rankings, race order, and pace calculations. This option helps build a complete segment structure from the race checkpoints while still allowing operator review before the race is saved. ## Race Aliases Race aliases allow RRM to recognize race names from **imported participant files**. This is useful when importing data from **registration platforms or CSV files** that may use slightly different race names. Example: Race name: ``` 21k ``` Aliases: ``` 21 K 21 21 km ``` When importing participants, if the CSV file contains any of these values in the **Race column**, RRM will automatically assign the participant to the correct race. This improves compatibility with external registration systems. ## Saving the Race Once the details, checkpoints, and policies are configured: * Click **Save** to create the race. * The race will appear in the **Races Menu**, ready for dashboard access and live timing. --- # Agent Instructions: 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: ``` GET https://help.runonrufus.com/rufus-race-manager/races/creating-races.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.