# Creating Checkpoints

Checkpoints are a vital part of race management in **RUFUS Race Manager (RRM)**. Creating checkpoints accurately ensures participants are tracked correctly and the race flow is managed effectively.

### Accessing the New Checkpoint Dialog

To create a new checkpoint:

1. Navigate to the **Checkpoints Menu** using the left-hand navigation bar.
2. Click the **New Checkpoint** button.
3. The **New Checkpoint modal** will open, allowing you to configure all the details.

<figure><img src="/files/opErV0cAKR6onNBXJ6k3" alt=""><figcaption><p>Checkpoint Dialog</p></figcaption></figure>

### Adding a New Checkpoint

In the New Checkpoint modal, the following fields are available:

* **Name** → A descriptive name to identify the checkpoint, such as *Start Line*, *Checkpoint 1*, or *Finish Line*.
* **Bounce time** → The minimum time interval (in seconds) required between valid reads at this checkpoint.
  * Any passing that occurs within the bounce window after a valid passing receives the status **BOUNCED\_BY\_CHECKPOINT**.
  * This prevents duplicate detections when a participant lingers or steps multiple times on the mat.

<figure><img src="/files/wPNSYXOCOeVusmELJTXf" alt=""><figcaption><p>Bounce Time Diagram</p></figcaption></figure>

* **Latitude / Longitude (optional)** → Coordinates for precise mapping of the checkpoint. Useful for GPS-based planning and route visualization.
* **Show passings notifications** → Toggle notifications for this checkpoint.
  * When enabled, every passing generates a notification.
  * When disabled, passings are still recorded and processed, but without real-time pop-up notifications.

Once configured, click **Save** to create the checkpoint. If you decide not to proceed, click **Cancel** to close the modal without saving changes.

### Tips for Creating Checkpoints

* **Use descriptive names** → Clear labels (e.g., *Start Line*, *Finish*, *10k Split*) simplify event control, especially when managing multiple checkpoints.
* **Set bounce times carefully** → Adjust based on checkpoint type. For example:
  * Start/Finish mats may need a larger bounce window to avoid congestion duplicates.
  * Intermediate splits can often use shorter bounce windows.
* **Silence notifications when needed** → For very busy checkpoints (e.g., mass starts), disabling notifications helps operators focus without being overwhelmed.
* **Add location data if relevant** → GPS coordinates are optional but recommended for precise planning, mapping, and post-race review.


---

# 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/checkpoints/creating-checkpoints.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.