Module 3: During the Race
This module covers what you need to do while the race is in progress - from starting read collection to monitoring for issues.
Starting Read Collection
Before participants begin crossing your timing location, ensure read collection is active.
Monitoring the Dashboard
During the race, the Dashboard is your primary view. Keep it visible at all times.
Key Information to Watch
| Dashboard Element | What to Monitor |
|---|---|
Stream Status |
Should remain "Collecting" - watch for disconnections |
Read Count |
Should increase as participants cross |
Last Read Time |
Should update regularly during active crossing periods |
Warnings/Alerts |
Any red indicators require attention |
Normal vs Abnormal Patterns
Normal:
-
Read count steadily increasing
-
Last read time updating frequently during crossing periods
-
No error messages
Abnormal:
-
Read count stops increasing while participants are crossing
-
Last read time becomes stale (not updating)
-
Error or warning messages appear
-
Stream status changes to "Disconnected"
Time Machine Monitoring
While watching the dashboard, periodically check the Time Machine:
Tag Activity Indicators
-
Should flash with each participant crossing
-
Consistent flashing = healthy system
-
No flashing during crossings = problem
Status LCD
Glance at the LCD display periodically:
-
Network indicator should remain stable
-
Logging should show active
-
No error codes should appear
See Time Machine Front Panel for detailed indicator meanings.
Handling Wave Starts
For races with multiple waves or corrals, you may need to track which wave is currently on course.
What Is a Wave Start?
Instead of all participants starting together, they start in groups (waves) at intervals. This is common for:
-
Large running events (5K, 10K, marathons)
-
Cycling events with different categories
-
Triathlon swim starts
Your Role During Wave Starts
-
Know the schedule - Be aware of wave start times
-
Monitor transitions - Watch for gaps between waves at your location
-
Continue monitoring - Each wave generates reads just like a single start
|
Wave management is typically handled by race control and advanced staff. Your job is to ensure reads are being captured for all waves. |
Common Race Day Scenarios
Scenario: Finish Line at a Running Event
At the finish line, you will see:
-
Early finishers arriving individually
-
Main pack arriving with steady flow
-
Late finishers trickling in over time
Monitor for:
-
Consistent reads during heavy traffic
-
No "gaps" where the system stops recording
Quick Actions During the Race
If you notice something unusual:
| Observation | Action |
|---|---|
Read count stops increasing |
Check Time Machine tag activity, verify stream status |
Dashboard shows disconnection |
Check network cable, verify WiFi connection |
Error message appears |
Note the message, attempt to restart collection, escalate if it persists |
Test tag does not register |
Check antenna connections, escalate immediately |
|
When in doubt, use your test tag to verify the system is working. If the test tag registers correctly, the issue may be with specific participants' chips rather than the system. |
Communication with Race Control
Stay in contact with race control:
-
Report any issues immediately
-
Confirm when waves pass your location (if requested)
-
Alert them to any unusual patterns