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

![](https://rufus-serverless-v1-shopmediabucket-yqa11v58uwom.s3.us-east-1.amazonaws.com/knowledge/assets/knowledge_asset_44c427d83e364a4e9cf4a57b6f78af3b/imported.png)
_Checkpoint Dialog_

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

![](https://rufus-serverless-v1-shopmediabucket-yqa11v58uwom.s3.us-east-1.amazonaws.com/knowledge/assets/knowledge_asset_a86bc18c73aa429d87a2f72003fd82bc/imported.png)
_Bounce Time Diagram_

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