> 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/participants-laps-segments.md).

# Participants Laps/Segments

From the **Edit Participant** tab in RUFUS Race Manager (RRM), users can access two detailed performance views depending on the event type: **Laps** (for Time-Trial/Laps-based races) and **Segments** (for Classical races). These grids provide an immediate breakdown of the participant’s progress throughout the course, allowing organizers to verify times, pacing, and intermediate performance with precision.

<div><figure><img src="/files/bRPu2NBvtdXSFBALcqNt" alt=""><figcaption><p>Participant Laps Grid</p></figcaption></figure> <figure><img src="/files/k14JBYYvMqayUnElaEF6" alt=""><figcaption><p>Participant Segments Grid</p></figcaption></figure></div>

## Laps View

The **Laps** grid displays a lap-by-lap summary for events structured around repeated circuits or timed laps. This view helps officials confirm that each passing has been correctly detected and properly associated with the corresponding lap.

#### What the Laps Grid Shows

* **Lap Number**\
  Indicates the lap index and total laps (e.g., *1/3*).
* **Lap Time**\
  The time taken to complete the lap. If the participant has a fastest lap, it is highlighted visually.
* **Accumulated Time**\
  Total race time up to that lap.
* **Gap**\
  Difference between this lap and the leading participant in the race up to that segment.
* **Interval**\
  Time difference compared to the previous lap.
* **Lap Rank**\
  The participant’s ranking for that specific lap compared to all competitors.
* **Pos. Δ (Position Change)**\
  Shows if the participant’s overall position improved, remained the same, or dropped after the lap.
* **Lap Pace**\
  Calculated pace for the lap, expressed in Km/h for cycling/TT formats.

#### How Organizers Use the Laps Grid

* Validate lap detection and ensure all expected laps were recorded.
* Identify performance trends, such as improving or declining lap times.
* Spot irregularities (missing laps, unexpected speed changes, etc.).
* Support protests or result inquiries by providing transparent lap-by-lap data.

## Segments View

For Classical races (running, triathlon splits, cycling point-to-point, etc.), the **Segments** grid shows performance across predefined course segments. This allows organizers to audit intermediate times and compare the participant’s pacing across the route.

#### What the Segments Grid Shows

* **Name**\
  The segment label (e.g., *km0–km5*, *km10–km15*, *chip-time*, etc.).
* **Start Time**\
  Timestamp of the participant’s first passing that marks the beginning of the segment.
* **End Time**\
  Timestamp of the passing that marks the completion of the segment.
* **Segment Time**\
  Total duration required to complete that segment.
* **Pace**\
  Running pace or cycling speed adapted to the race type (e.g., *5:30 min/Km*).
* **Segment Rank**\
  Participant’s ranking within that segment compared to all other participants who completed it.

#### How Organizers Use the Segments Grid

* Verify that all split points were registered correctly.
* Compare the participant’s speed/pacing evolution across the course.
* Detect unusual slowdowns or surges that may require further validation.
* Provide accurate split-based reporting to athletes and stakeholders.

## Understanding Laps and Segments Together

Both grids are directly driven by the validated passings of the participant. Any modification—adding, removing, or validating a passing—will immediately update these tables. This ensures that the participant’s intermediate data remains consistent with the final classification.

These views give officials a comprehensive understanding of the participant’s progress and allow for quick troubleshooting when discrepancies arise.