# Creating a Fixed Laps Race

Fixed Laps races in RUFUS Race Manager (RRM) are designed for events where participants must complete a **specific number of laps** to finish the race. These formats are common in motor sports, running track events, cycle criteriums, obstacle course circuits, and many loop-based competitions where all participants cover the same total distance.

A Fixed Laps race ends when participants reach the configured lap count, and rankings are determined by the fastest total race time.

<figure><img src="/files/tLxbZ5diC8QGljNSApJW" alt=""><figcaption><p>TT/Laps Race Dialog</p></figcaption></figure>

## Fixed Laps Race Overview

In this race format:

* The goal is to complete a **target number of laps**.
* The participant’s **total time** to reach that number determines their result.
* Lap counting is controlled by a designated **Lap Gate** checkpoint.
* Intermediate **Sector checkpoints** can be added to collect split times or sector performance.

RRM manages lap validation, timing, rankings, and finish logic automatically based on the race configuration.

## Configuring a Fixed Laps Race

The New TT/Laps Race dialog includes the settings needed to define the lap count, lap structure, and sector checkpoints.

### Race Information

#### **Race Name**

Enter the name of the race (e.g., *3 Laps*, *12-Lap Circuit*, *10-Lap Run*).

#### **Sport Type**

Select the discipline appropriate for the event.

#### **Lap Length (meters)**

Specify the length of a single lap.\
This value is used to calculate pacing, speed, and distance-based statistics.

## Race Objective

Select **TARGET LAPS** as the race type.\
This enables the Fixed Laps configuration panel.

#### **Target Laps**

Enter the total number of laps participants must complete.

Examples:

* 3 laps on a 2.5 km circuit
* 12 laps on a 400m track
* 6 laps on a mountain-bike trail loop

#### Optional: Checkered Flag Display

* **Show checkered flag when the winner finishes target laps**\
  When enabled, the race interface displays a checkered flag icon once the first participant completes the required number of laps. **When the first one finishes, everyone finish the current lap only.**

## Adding Sectors and Checkpoints

Fixed Laps races use:

* **A single Lap Gate** → Required for counting laps
* **Optional Sector checkpoints** → Used for split times and intermediate monitoring

#### Adding a Checkpoint

Use the **Pick a checkpoint and role…** dropdown to assign a role to any existing event checkpoint.

Available roles:

**SECTOR**

Captures intermediate passings but does not close a lap.

**LAP\_GATE**

Defines the point where each lap is completed.\
A passing at the Lap Gate increments a participant’s lap count.

Each checkpoint is listed in the grid with:

* **Checkpoint Name**
* **Type** (Sector or Lap Gate)
* **Sector Number**
* **Closes Lap** indicator (displayed only for Lap Gate)

The Lap Gate must always be the final sector in the sequence.

## Saving the Race

Once all fields and checkpoints are configured, click **Save** to add the Fixed Laps race to the event.

From this point, you can:

* Assign participants to the race
* Monitor race progress via the **Race Dashboard View** or the **Checkpoints** / **Event Control View**
* View per-participant lap performance in the **Edit Participant View**
* Generate rankings based on total race time after completing the target laps

All lap timing logic is handled automatically by RRM as passings are processed.

## Conclusion

Fixed Laps races in RRM provide a structured and accurate framework for competitions where all participants must complete the same number of laps. With simple lap setup, optional sector checkpoints, and automated timing logic, organizers can configure and manage loop-based events with confidence.


---

# 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-a-fixed-laps-race.md?ask=<question>
```

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.