> 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/collecting-and-managing-timing-data/adding-manual-passings.md).

# Manual Passings

In **RUFUS Race Manager (RRM)**, manual passings allow operators to add a participant’s passing when it was not automatically recorded by the system. Manual passings can be created in two different ways, depending on the context of the correction or adjustment.

In addition to manual passings, RRM also supports **Floating Passings**, which are manual passings without a checkpoint. These are covered in detail in the [Floating Passings article](/rufus-race-manager/collecting-and-managing-timing-data/floating-passings.md).

### Adding Passings via Checkpoint-Race View

When a manual passing is added in the **Checkpoint-Race View**, it is processed through the full **timing data collection logic**.

This means the system applies all normal checks before accepting the passing, including:

* Race association (does the participant belong to this race?)
* Checkpoint matching (is the passing in the correct place of the plan?)
* Bounce time compliance (too soon after the last read at this checkpoint/device?)
* Status evaluation (VALID, BLOCKED, PROMOTED, etc.)

This method ensures the manual passing behaves exactly like an automatic passing, maintaining full consistency with the race’s timing rules.

### Adding Passings via Participant Edit

A manual passing can also be added directly when **editing a participant**.

In this case, the passing is inserted straight into the participant’s data and is automatically validated for the specified checkpoint. Unlike the Checkpoint-Race View, this method does not pass through the broader timing collection process.

This is especially useful for:

* Adding a missing passing confirmed by officials
* Correcting a single participant’s data without affecting the main event workflow
* Handling post-race adjustments

### Comparison of Methods

| Method                   | Scope                                       | Processing Logic                                                | Typical Use Case                                                                              |
| ------------------------ | ------------------------------------------- | --------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| **Checkpoint-Race View** | Tied to a specific checkpoint               | Full timing logic (race plan, bounce, status precedence)        | Adding a missing passing during the live event, ensuring it behaves like an automatic passing |
| **Participant Edit**     | Tied directly to a participant + checkpoint | Direct assignment and validation (skips full timing logic)      | Post-race correction or targeted fix for one participant                                      |
| **Floating Passing**     | No checkpoint (full race plan scope)        | System infers the next expected checkpoint using full race plan | Quick “catch-all” entry when the operator wants the system to decide placement                |

### Related Articles

* [**Participant Passings**](/rufus-race-manager/participant-management/participant-passings.md)
* [**Checkpoint-Race View**](/rufus-race-manager/checkpoints/checkpoint-race-view.md)
* [Floating Passings](/rufus-race-manager/collecting-and-managing-timing-data/floating-passings.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://help.runonrufus.com/rufus-race-manager/collecting-and-managing-timing-data/adding-manual-passings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.