Module 4: Reviewing Reads

This module teaches you how to view and interpret timing reads in RaceDay Scoring. Understanding this helps you verify the system is working and spot potential issues.

Viewing Reads by Timing Location

Each Timing Location captures reads from participants crossing that point.

Accessing the Location View

  1. From the Dashboard, select your timing location

  2. Choose the view type: Raw Reads or Scored Reads

  3. Review the list of captured reads

Understanding the Read List

Each read entry typically shows:

Field Description

Bib Number

Participant’s race number (if matched)

Chip ID

Unique identifier from the timing chip

Time

When the read was captured

Status

Whether the read has been scored

Raw Reads vs Scored Reads

Remember from Module 1:

  • Raw Reads = Every chip detection, unfiltered

  • Scored Reads = Processed reads matched to participants

When to Use Each View

View Use When

Raw Reads

Troubleshooting missing times, verifying test tag reads, investigating chip issues

Scored Reads

Checking participant results, verifying correct times

Example: Interpreting Raw Reads

Consider a participant who lingers in the antenna field (perhaps stopping to tie their shoe near the timing line):

Chip ID: ABC123  Time: 10:15:32.145  Status: Used
Chip ID: ABC123  Time: 10:15:32.891  Status: Unused (duplicate)
Chip ID: ABC123  Time: 10:15:33.234  Status: Unused (duplicate)
Chip ID: ABC123  Time: 10:15:47.567  Status: Unused (duplicate)

Raw reads show all four detections. Only the first read is marked "Used" because the timing location is configured to take the first read. The subsequent reads are duplicates within the gap factor and marked "Unused".

The Scored read would show only the first detection (10:15:32.145).

Understanding Used vs Unused

When investigating reads, pay attention to the Used/Unused status:

Status Meaning

Used

This read will be included in scoring and results

Unused (duplicate)

Read occurred too close to another read (within gap factor)

Unused (before event)

Read occurred before the Scored Event started

Unused (max occurrences)

Location already has the maximum configured reads for this participant

If a participant’s read exists but is marked Unused, the read was captured successfully. The issue is with timing or event configuration, not the equipment.

Spotting Missing Reads

Sometimes participants cross the timing line but no read is captured. Here is how to identify this.

Signs of Missing Reads

  • Participant complains they have no finish time

  • Read count is lower than expected

  • Gaps in bib number sequence

Checking for a Specific Participant

  1. Get the participant’s bib number or name

  2. Use the search function in RaceDay Scoring

  3. Check if any reads exist for that participant at your location

Common Causes of Missing Reads

Cause What to Look For

Chip not on participant

They forgot to attach it, or it fell off

Chip in wrong position

Attached to clothing instead of shoe, or not positioned correctly

Chip damaged

Participant ran in rain, chip was bent, or battery dead

Antenna issue

Antenna cable loose, antenna misaligned, or reader issue

Avoided the timing line

Participant went around the timing line

If you identify potential missing reads, report them to race control. Do not attempt to manually enter times unless specifically instructed.

Basic Participant Lookup

You may need to look up a specific participant to answer questions or verify reads.

Finding a Participant

  1. Navigate to the Participants section

  2. Search by:

    • Bib number

    • Name

    • Chip ID

  3. View their timing information

Information Available

For each participant, you can typically see:

  • Registration details (name, bib, category)

  • All timing reads captured

  • Current status (started, finished, etc.)

Understanding Read Status

Reads can have different statuses:

Status Meaning

Scored

Read has been processed and assigned to results

Unmatched

Chip ID does not match any registered participant

Duplicate

Read is a duplicate of another read (filtered out)

Pending

Read is waiting to be processed

Unmatched Reads

If you see many unmatched reads, possible causes include:

  • Participants registered after chip assignment

  • Incorrect chip assignments in registration

  • Non-participant chips (spectators with chips from another event)

Report significant numbers of unmatched reads to advanced staff.

Quick Verification Techniques

Verify Test Tag Reads

  1. Switch to Raw Reads view

  2. Search for your test tag chip ID

  3. Confirm reads appear with correct timestamps

Verify System During Race

  1. Note the current read count

  2. Wait for a participant to cross

  3. Confirm read count increased

  4. Check that new read appears in list

Spot Check Results

  1. Pick a random participant who has finished

  2. Verify their time appears in Scored Reads

  3. Compare to expected time if known

What You Can and Cannot Do

You Can:

  • View all reads at your timing location

  • Search for specific participants

  • Verify test tag reads

  • Report issues to race control

  • Spot potential problems

You Should Not:

  • Manually edit or delete reads

  • Change participant data

  • Modify timing location settings

  • Adjust stream configurations

Data modifications should only be performed by advanced staff. Your role is to monitor and report.

Summary

You now know how to:

  • View reads by timing location

  • Understand Raw vs Scored reads

  • Spot potentially missing reads

  • Look up specific participants

  • Interpret read status indicators

Next: Module 5: Issues & Escalation