> 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/races/classical-race-dashboard.md).

# Classical Race Dashboard

The Classical Race Dashboard in RUFUS Race Manager (RRM) provides a real-time operational view for traditional point-to-point and split-based races (such as 5K, 10K, half marathon, or any race defined by sequential checkpoints rather than laps). It combines timing controls, checkpoint monitoring, and participant performance tracking into a single screen.

This dashboard is designed to help organizers verify split points, monitor finish arrivals, oversee race timing, and maintain the overall flow of the event.

<figure><img src="/files/pI8dzk2YFZkPfEHnNc53" alt=""><figcaption><p>Classical Race Dashboard View</p></figcaption></figure>

## Overview of the Classical Dashboard Layout

A Classical race dashboard includes:

* **Race header and processing controls**
* **Checkpoint progress overview**
* **Start time and floating passing tools**
* **A detailed participant table with all race splits**
* **Race progress statistics**
* **Race clock or elapsed time display**

Each component provides clarity on how the race is progressing and whether participants are moving through checkpoints as expected.

## Race Controls

### Process Passings

The **Process passings** switch determines if the race is actively processing detections:

* **Enabled** → Passings are validated, timed, and used for results
* **Disabled** → Passings are captured but marked as *RACE\_CLOSED* and do not contribute to results

This allows timers to prevent unwanted early detections or to close the race after all participants have finished.

### Race Reset

Races allow a **Reset race** action, clearing recorded passings and participants status.

## Checkpoint Progress

The dashboard displays all checkpoints defined for the course, in order:

* Start checkpoints
* Intermediate splits (e.g., km-5, km-10)
* Finish checkpoint

Each checkpoint shows:

* **Its name or label**
* **Its activation state** (green when actively processing passings)
* **crossed / not crossed** count

This provides an immediate visual confirmation that all checkpoints are functioning and open.

## Start Time Management

The Classical Race Dashboard includes tools to set or adjust the race start time:

* Enter a specific timestamp
* Use the **NOW** button at the moment the race begins
* Adjust the time after the start if necessary

RRM automatically recalculates all race times and results when the start time changes, keeping classifications accurate.

## Floating Passings

The "+" button allows adding manual passings when corrections are needed:

* Missing detections
* Recovered chip reads
* Manual adjustments

Timers can specify the exact timestamp or use the current system time.

## Race Progress Summary

A panel on the right side shows the overall race status:

* **Not Started** count
* **In Race** count
* **Finish** count
* **Gender leaders**
* **Excluded or invalid participants**
* **Completion percentage**

<figure><img src="/files/e4i7kJuXN2P7uF4yILZy" alt=""><figcaption><p>Classical Race Progress</p></figcaption></figure>

This helps organizers quickly assess how many participants remain on course and how many have finished.

## Race Clock

The race clock displays **elapsed gun-time**.\
Its behavior:

* If the start time is in the future → shows a **countdown**
* Once started → counts upward and timestamps passings accordingly

This clock ensures all split calculations match the official race timing.

## Participant Results Table

The central component of the Classical Dashboard is the participant table. Each row shows a participant’s progress throughout the race, updating in real time.

Common columns include:

* **Position**
* **BIB and Name**
* **Race Time**
* **Gun-time (official)**
* **Pace**
* **Gap to leader**
* **Each checkpoint split** (check-0, km-5, km-10, finish, etc.)
* **Time of day for each split**

Each checkpoint column typically includes:

* The participant’s split time
* Pace for that segment
* Position within that split (e.g., *(1)* marking the fastest split)

#### Sorting and Monitoring Tools

* Sort by finish time, pace, checkpoint, or gap
* Use the search bar to quickly locate a participant
* Enable **Last arrivals first** to track late-stage finishers

The table updates continuously as passings are processed.

## When to Use the Classical Race Dashboard

This dashboard is ideal for races defined by a sequence of checkpoints rather than repeated laps. Use it for:

* Road races (5K, 10K, half marathon, marathon)
* Trail races with defined split points
* Triathlon single-discipline run segments
* Cycling time checks when no lap structure exists

It is optimized for races where each participant completes the course only once.

## Conclusion

The Classical Race Dashboard offers a clear, complete view of all participant progress in traditional checkpoint-based races. With powerful monitoring, timing controls, and immediate access to split data, it enables race organizers to manage the event confidently from start to finish.