# Understanding Classifications

In **RUFUS Race Manager (RRM)**, race classifications are generated **dynamically** each time they are requested. Unlike systems that “lock” results after initial processing, RRM continuously adapts to changes, ensuring results are always **accurate, up to date, and consistent** with the raw timing data.

## Dynamic Recalculation

Every time classifications are viewed or exported, RRM recalculates them in real time. This provides key benefits:

* **Modifications without reprocessing** → Edits to participants, passings, or race start times are immediately reflected in the results. No batch reprocessing is required.
* **Error correction** → Mistakes (like missing or duplicated passings) can be fixed on the fly, with classifications updating instantly.
* **Raw data preserved** → All passings are stored with their original timestamps. Adjustments never overwrite the source data.

## Role of Segments and Checkpoints

Classifications in RRM are built on the structure of **checkpoints** and **segments**:

* **Checkpoints** mark specific locations on the course (Start, intermediates, Finish). As participants cross checkpoints, passings are recorded.
* **Segments** are the timing intervals between checkpoints. At least one segment (Start → Finish or Gunshot → Finish) is required for ranking a **CLASSICAL** race. Additional segments (like Start → 10k or Swim → Bike) allow for splits and transition analysis.

By combining checkpoints and segments, RRM generates meaningful classifications that reflect both total race times and detailed performance insights.

The diagram shows how raw **Passings** flow into **Checkpoints**, combine into **Segments**, and ultimately generate **Classifications**.

<figure><img src="/files/URTgNiP9kpjn9gjPdN4v" alt=""><figcaption><p>Classification Flow Diagram</p></figcaption></figure>

## Why This Matters

This approach ensures that:

* Last-minute changes don’t break results.
* Manual passings or floating passings can be added confidently.
* Rankings are always based on the most accurate, current data.

Timers can adapt to real-world conditions (mass starts, late edits, hardware hiccups) without sacrificing the reliability of official results.

## Summary

Classifications in RRM are **live, dynamic, and resilient**. By recalculating on demand and preserving original data, the system guarantees that every result reflects the true state of the race—no matter when or how it’s reviewed.


---

# 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/classification-and-results-processing/understanding-classifications.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.