> 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/best-practices-and-tips/optimizing-race-timing-workflow.md).

# Optimizing Race Timing Workflow

To ensure a smooth race timing experience using RUFUS Race Manager (RRM), follow these best practices for different stages of the event: pre-race, during the race, and post-race.

## Pre-Race Preparations

1. **Setup and Testing**: Connect all timing devices, including RFID readers and CloudBoxes, and test each one to ensure proper data collection.
2. **Create Event and Assign Checkpoints**: Set up the event, races, checkpoints, and segments. Assign timing devices to checkpoints to ensure correct data capture.
3. **Participant Management**: Import participant data or enter manually, including bib numbers and participant information. Ensure the data is accurate to avoid discrepancies.
4. **Verify Network Connectivity**: Confirm local and cloud devices are connected. Verify internet access for cloud devices if needed.
5. **Setup Backup Devices**: If possible, have backup timing devices configured in case of primary device failure.

## During Race Monitoring

1. **Live Monitoring**: Use the **Race Dashboard** and the **Checkpoint-Race Views** to monitor incoming timing data in real time. Keep an eye on each checkpoint's data and device status to detect any connectivity or data issues.
2. **Activate or Deactivate Checkpoints**: Control which checkpoints are active. For example, once all participants have passed a checkpoint, deactivate it to prevent unwanted readings.
3. **Managing Passings**: Add manual passings as necessary, for instance, when a participant passes a checkpoint without being detected automatically. Assign these using the Checkpoint-Race View or during participant editing.
4. **Data Accuracy**: Continuously check for discrepancies in passings, and adjust statuses as needed (mark as validated or invalidated).
5. **Offline Capabilities**: If working offline, ensure all devices are synced correctly. Any discrepancies can be handled once reconnected to the internet.

## Post-Race Procedures

1. **Final Data Review**: Go through the Event Control View to review all passings, ensuring every participant has valid data for classification purposes. Delete incorrect or duplicate passings if necessary.
2. **Generate Classifications**: Request classifications using the Race-Result View. Segments and race order segments will help in accurate classifications.
3. **Export Results**: Use the Export feature to generate CSV or PDF reports of race results and classifications. This can be shared directly with event stakeholders.
4. **Synchronize Data**: Sync the local data with cloud data to ensure consistency across all platforms. Confirm that all the data is properly backed up.
5. **Remove Devices**: Disconnect timing devices from the event and remove any unnecessary devices.

By following these steps, race organizers can streamline the timing process from setup to post-race analysis, ensuring accurate results and efficient race management.