> 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/participant-management/participant-passings.md).

# Participant Passings

From the **Edit Participant** tab in **RUFUS Race Manager (RRM)**, users can view and manage participant passings during the race. Passings represent the recorded instances of a participant passing a checkpoint, providing essential data for race analysis and classification. This article will cover how to manage passings, including adding new passings, deleting, and changing their status.

<figure><img src="/files/WyAH2VdNx1Qv74sk5ZSo" alt=""><figcaption><p>Participant Passings</p></figcaption></figure>

## Viewing Passings

In the **Edit Participant** tab, the **Passings** section displays all recorded passings for the selected participant. Each passing includes the following details:

* **Checkpoint**: The checkpoint where the passing was recorded.
* **Lap**: The lap number associated with the passing.
* **Racetime**: The elapsed race time when the passing occurred.
* **Time of the Day**: The exact timestamp when the passing was recorded.
* **Status**: The current status of the passing (e.g., **VALID**, **EOTR**).
* **Device**: The device that recorded the passing.

## Managing Passings

### 1. Deleting a Passing

Passings cannot be edited in terms of their recorded date, time, or checkpoint; this data is immutable once captured by the system to maintain integrity. However, users can **delete** a passing if necessary.

To delete a passing:

* **Select the Passing**: Click the checkbox next to the passing you wish to delete.
* **Delete**: From the grid menu, select **Delete** to remove the selected passing.

### 2. Changing Passing Status

The status of a passing can also be modified. There are two main statuses that a user can assign:

* **VALIDATED\_BY\_USER**: If a previously invalid passing is deemed correct, the user can mark it as valid, and it will be included in the classification analysis.
* **INVALIDATED\_BY\_USER**: If a passing is considered incorrect or irrelevant, the user can mark it as invalid, excluding it from the classification analysis.

To change the status of a passing:

* **Select the Passing**: Click the checkbox next to the passing whose status you wish to change.
* **Change Status**: From the grid menu, select **Change Status** and choose either **VALIDATED\_BY\_USER** or **INVALIDATED\_BY\_USER**.

## Adding a New Passing

Users can manually add a new passing if required, such as when a timing issue occurs, and additional data needs to be captured for accuracy.

<div><figure><img src="/files/e0U6hq3L9em0bL8KTcVG" alt=""><figcaption><p>Add New Passing Modal for Laps races</p></figcaption></figure> <figure><img src="/files/aY8b8tmKu6kpKdeLd2oX" alt=""><figcaption><p>Add New Passing Modal for Classical races</p></figcaption></figure></div>

To add a new passing:

* **Click Add Passing**: In the **Passings** section, click the **Plus icon** to open the **Add New Passing** modal. Or within the context menu in any Participants Grid.
* **Enter Details**:
  * **Date**: Specify the date of the new passing.
  * **Time or Race time**: Specify the time of the day or the race time of the new passing. Press the NOW button to input the current date/time in the fields.
  * **Lap number:** Specify the lap number of the new passing (for Laps races only)
  * **Checkpoint & Lap**: Select the corresponding checkpoint and lap for the passing.
* **Save**: Click **Save** to add the new passing. All manually added passings are assigned the **VALIDATED\_BY\_USER** status by default.

## Important Notes on Passings

* **Immutable Data**: The date, time, and checkpoint of a passing are immutable once captured. This ensures that the recorded data maintains its integrity for race classification purposes.
* **Deleting vs. Invalidating**: Deleting a passing removes it entirely, while invalidating a passing allows the data to be retained but ignored for classification.

## Conclusion

The **Passings** section in the **Edit Participant** tab provides a comprehensive toolset for managing the recorded checkpoints of participants in **RUFUS Race Manager**. Whether you need to delete, invalidate, or manually add passings, understanding how to manage these records ensures accurate race tracking and classification. Properly handling passings allows for a seamless race experience and reliable results.