# Event Dashboard View

The **Event Control View** in **RUFUS Race Manager (RRM)** provides a complete and centralized workspace for monitoring, validating, and managing all passings of an event. It consolidates every captured passing—regardless of device, file, or source—into a single operational dashboard focused purely on raw timing data. This makes it the primary environment for real-time supervision during a race.

<figure><img src="/files/gHlIDdD6O6bNUT84NuFY" alt=""><figcaption><p>Event Control View</p></figcaption></figure>

## Main Features

#### Centralized passings management

All passings generated during the event—whether from CloudBox devices, backup files, manual inputs, or floating passings—are displayed and managed in one place.

#### Real-time visibility

Passings appear instantly as they are received from any source. The grid updates live without needing to refresh.

#### Flexible and powerful data grid

The data grid supports:

* Searching and instant filtering
* Sorting and grouping
* Column arrangement and customization
* Fast scrolling for large-scale events
* Exporting data to CSV

#### Floating passings

Floating passings let operators manually insert a passing anywhere in the race timeline. They are ideal for:

* Correcting missed reads
* Handling uncommon race situations
* Reconciling handwritten notes or manual observations

Floating passings are clearly marked to differentiate them from device-generated passings.

## Race Control Widgets

#### Race-level control

Each race includes a dedicated control widget showing:

* **Elapsed time** since the race start
* A **Process passings** toggle
* Visual indicators of the race’s processing state

These widgets allow operators to pause or resume passing processing per race, and to quickly understand the timing state of each race.

## Checkpoint Control Widgets

#### Checkpoint-level management

Each checkpoint appears with its own widget containing:

* A processing toggle
* Status and activity indicators

These controls allow operators to enable or disable the processing of individual checkpoints and to focus on specific segments of the course when needed.

## Global Start Time Widget

#### Multi-race start synchronization

When an event contains two or more races, the Global Start Time widget allows setting or adjusting the start time for multiple races simultaneously. This is especially useful for:

* Mass-start events
* Synchronizing multiple races sharing the same start line

## Grid Columns

| Column              | Description                                                        |
| ------------------- | ------------------------------------------------------------------ |
| **BIB**             | Participant’s bib number                                           |
| **Chip**            | RFID chip code assigned to the participant                         |
| **Name**            | Participant’s name                                                 |
| **Age Group**       | Participant’s age group, if defined                                |
| **Lap**             | Lap number associated with the passing                             |
| **Race**            | Race in which the participant competes                             |
| **Checkpoint**      | Checkpoint where the passing was recorded                          |
| **Virtual**         | Indicates if the passing belongs to a virtual lap, when applicable |
| **Sector**          | Sector number, when applicable                                     |
| **Racetime**        | Time elapsed since the race start                                  |
| **Time of the Day** | Exact timestamp of the passing                                     |
| **Status**          | Passing status (VALID, ORPHAN, INVALIDATED, EOTR, etc.)            |
| **Type**            | Type of passing (Local, Manual, Floating, Backup File, Cloud)      |
| **Device**          | Device or file source that generated the passing                   |

## **Context Actions**

Right-clicking a passing opens a contextual menu allowing you to:

* **Delete passing**
* **Reprocess passing**
* **Set passing as invalidated by user**

These tools are essential when resolving timing conflicts or adjusting data integrity.

## **Tips**

* Use the **search bar** to quickly isolate passings by bib, chip, or name.
* Combine **status filtering** with checkpoint widgets to resolve timing issues faster.
* Utilize **floating passings** for edge cases or manual corrections.


---

# 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/event-management/event-control-view.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.