# Publishing Race Progress

Race Progress publication allows the RUFUS Events App to show the live state of a race before final results are available.

Instead of showing only leaderboards, the event page can display who has started, who is currently in race, who has finished, checkpoint or lap advancement, leaders, gaps, and the current race state.

## Where Race Progress Appears

Race Progress is displayed in the published event page in the **RUFUS Events App**.

When available, the event page can show a **Live Progress** view next to the regular leaderboard view.

This view is designed for spectators, teams, organizers, and operators who need to understand what is happening during the race while timing is still active.

<figure><img src="/files/HcTvyqZW7MOpfKThncXu" alt=""><figcaption><p>Race Progress Desktop View in the Events App</p></figcaption></figure>

## When Race Progress Is Visible

Race Progress is shown in the Events App when the event and race conditions indicate that the race is active.

The main conditions are:

* The event is published.
* The current date is within the configured event dates.
* Race Progress has been published manually or automatically.

This means that the public event page responds to the real configuration and operational status of the event.

### Operator Responsibility

The Events App reflects the information published from RUFUS Race Manager.

For this reason, the RRM operator is responsible for keeping the event status accurate during the race.

Before and during the event, check that:

* Event dates are correct.
* Races that should be live are processing passings.
* Races that are not active are not processing passings.
* Race Progress is published when the public page should show live race status.
* Race Progress is not left active after timing is finished.

When timing is complete, close the race or disable **Process Passings** so the published event reflects the real race condition.

## Supported Race Types

Race Progress publication is available for:

* **Classical races**
* **Time Trial / Laps races**

The information shown in the Events App depends on the race configuration, checkpoints, laps, timing data, and publication status.

## Publishing Race Progress with Predictive Tracking

For Classical races with a valid race course configured for predictive tracking, the RUFUS Events App can also display predictive participant positions in the **Map View** of the Live Progress view.

When predictive tracking is available, the Events App estimates the participant position between checkpoints based on the configured race course and the latest timing information received from the race.

This allows spectators, organizers, and teams to visualize the live race flow on the course map, even when participants are between physical timing points.

<figure><img src="/files/mewEgf2tcnwW7zUYltk0" alt=""><figcaption><p>Predictive Tracking Desktop View in the Events App</p></figcaption></figure>

The Map View can display:

* Predicted participant positions along the course
* Live leader movement
* Participant progression between checkpoints
* Relative race distribution across the route
* Estimated race flow in real time

Predictive tracking depends on:

* A valid Classical race configuration
* A properly configured race course
* Predictive tracking support enabled through the race course data
* Available timing passings from checkpoints or intermediate timing points

The accuracy of predictive positions depends on the quality of the race course configuration and the availability of timing data during the event.

If no valid predictive race course is available, the Events App will continue showing the standard Live Progress information without predictive map positioning.

## Manual Publication

Race Progress can be published manually from the race dashboard.

Use the **Publish** button when you want to send the current race progress state to the Events App at a specific moment.

Manual publication is useful when:

* You want full control over when live progress is refreshed.
* The event does not require continuous updates.
* You want to verify timing data before updating the public page.

## Automatic Publication

Race Progress can also be published automatically using **Automatic Publication Updates**.

When enabled, RRM can refresh Race Progress without requiring the operator to repeatedly press **Publish**.

Automatic publication is useful for live events where the public page should stay close to the current race state during timing operations.

For more details, see the **Automatic Publication Updates** help article.

## What the Events App Can Show

Depending on the race configuration and available timing data, the Live Progress view can include:

* Race clock
* Current leaders
* Participants not started
* Participants in race
* Finished participants
* Checkpoint or lap counters
* Current participant position
* Last known checkpoint
* Race time
* Time gaps
* Participant race state

This gives the public event page a live race view, even before final classifications are complete.

## Recommended Workflow

1. Configure the event dates correctly.
2. Publish the event in RUFUS Cloud.
3. Confirm that the race configuration, checkpoints, and participants are ready.
4. Enable **Process Passings** only for races that are actively being timed.
5. Publish Race Progress manually or enable automatic Race Progress publication.
6. Monitor the Events App during the race.
7. When timing is finished, close the race or disable **Process Passings**.
8. Publish final results when classifications are ready.

## Notes

Race Progress is not a replacement for final results.

It represents the live operational state of the race based on the current timing data and race configuration. Final leaderboards and classifications should still be reviewed and published according to the event timing workflow.


---

# 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/publishing-in-the-rufus-event-app/publishing-race-progress.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.