# Chip to Bib Reference Table

The **Chip to Bib Reference Table** links chip identifiers, also called **EPC values**, with participant bib numbers.

This table is used by RUFUS Race Manager to resolve RFID passings when the detected chip does not directly match the participant’s primary chip field, or when the event requires an external chip-to-bib mapping.

## Purpose

The Reference Table allows RRM to identify which bib belongs to a detected chip/EPC.

This is useful when:

* Chips are assigned outside RRM.
* The chip code is different from the participant bib number.
* A timing provider receives a chip list from an external registration or chip encoding process.
* Chip values should be hidden from regular event views while still being used internally.

## Reference Table

The Reference Table panel in the Settings Tab shows the current table status:

* **Rows**: number of records loaded in the table.
* **Updated**: date and time of the last table update.
* **Matched count**: number of table rows that currently match participants in the event.

<figure><img src="/files/N9XSoyx44Cay3ZeNJYI7" alt=""><figcaption><p>Reference Table Panel in Settings Tab</p></figcaption></figure>

A table is considered useful when the chip/EPC values can be matched to existing bib numbers in the participant list.

### Managing the Table

Click **Manage Table** to open the Reference Table manager. Once a table is loaded, you can access the Reference Table manager from the Status Bar icon.

<figure><img src="/files/HkpyCVGKicXzk20B8bTE" alt=""><figcaption><p>chip/EPC to Bib Reference Table Manager.</p></figcaption></figure>

From this window, you can:

* Add rows manually.
* Upload a CSV file.
* Edit existing rows.
* Delete individual rows.
* Clear the full table.
* Search by chip/EPC or bib.

Each row contains:

* **Chip / EPC**: the RFID chip identifier.
* **Bib**: the participant bib number linked to that chip.
* **Updated**: the last update time for that row.

### Adding a Row Manually

To add a chip-to-bib relation manually:

1. Enter the **Chip / EPC** value.
2. Enter the corresponding **Bib**.
3. Click **Add Row**.

Use this option for small corrections or manual additions.

### Uploading a CSV File

Use **Upload CSV** to import multiple chip-to-bib relations at once.

The CSV file should contain one row per chip assignment, with the chip/EPC value and the bib number.

Recommended structure:

| Chip / EPC               | Bib |
| ------------------------ | --- |
| E28011606000020C8C00000A | 10  |
| E28011606000020C8C00000B | 11  |

Before uploading, check that:

* Bib numbers exist in the event participant list.
* Chip/EPC values are complete.
* There are no duplicate chip values unless intentionally replacing existing assignments.
* The file does not contain empty rows.

### Matched and Unmatched Rows

When a row is linked to an existing participant bib, RRM can use it to resolve passings correctly.

If a bib does not exist in the event, the row can still be stored in the table, but it will not be matched to a participant until a participant with that bib exists.

This makes it possible to upload the reference table before final participant checks, then verify the matched count afterward.

### Clearing the Table

Use **Clear Table** only when you need to remove the full chip-to-bib reference table from the event.

This action affects all stored chip/EPC mappings for the event. If the table was imported from a CSV file, keep a backup copy before clearing it.

## Hiding Chip Columns

The option **Hide chip columns across the event UI** controls whether chip-related columns are shown in the event interface.

When enabled, RRM hides chip values in supported event views while still using the Reference Table internally to resolve passings.

This is useful when operators should work mainly with bib numbers instead of raw EPC values.

## Recommended Workflow

1. Import or create the participant list.
2. Upload the chip-to-bib reference table.
3. Check the **Rows** and **Matched count** values.
4. Review unmatched or incorrect bib assignments.
5. Enable chip column hiding if operators should not work with EPC values.
6. Save or continue with event setup.

## Notes

The Reference Table belongs to the selected event only.

If you clone or export an event, review whether the chip-to-bib assignments should be reused, replaced, or cleared before using the event in production.


---

# 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/collecting-and-managing-timing-data/chip-to-bib-reference-table.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.