# Event Structure

In **RUFUS Race Manager (RRM)**, every event is built on a clear and flexible structure that defines how timing data is collected, organized, and used to calculate results. Understanding this hierarchy is essential for setting up and managing races effectively.

<figure><img src="/files/ZGgw2AfUZjVDyCV029lw" alt=""><figcaption><p>Event Structure Diagram</p></figcaption></figure>

## Event

The **Event** is the top-level container. It represents the entire competition and may include one or multiple races.

* Example: An event called *Run to the Hills 2025* may contain a *21k race* and a *3k fun run*.

## Races

Each **Race** defines a competitive unit within the event. Races have their own:

* Start time
* Checkpoints
* Segments
* Participants

This allows multiple races to coexist within a single event while keeping timing data separate.

## Checkpoints

A **Checkpoint** is a physical or logical location where passings are captured.

* **Start** → Marks the beginning of the race (lap 0).
* **Finish** → Marks the end of the race (lap 9999).
* **Intermediate checkpoints** → Provide splits, pacing information, and course validation.

Checkpoints can be **shared** (e.g., Start and Finish on the same mat) or **separate** for finer control (e.g., Start closed independently, Finish kept open).

## Segments

A **Segment** represents the section of the course between two checkpoints. Segments are used for splits, rankings, and analysis.

Types of segments include:

* **Standard Segments** → Defined between consecutive checkpoints (e.g., *Start → 10k*, *10k → Finish*).
* **Full-Course Segments** → Defined across the entire race (e.g., *Start → Finish*).
* **Race Order Segment** → A special segment (e.g., *Gunshot → Finish*) used to determine the official order of finishers for the race.

Every race must have at least one **Race Order Segment** to establish rankings.

## Summary

The event structure in RRM follows a logical hierarchy:

* **Event** → contains multiple **Races**
* **Races** → built from **Checkpoints**
* **Checkpoints** → connected by **Segments**

This structure ensures that timing data is always consistent, flexible, and ready for classification. By carefully setting up checkpoints and segments, timers can manage everything from simple fun runs to complex multi-split races with confidence.


---

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