Guide
The Most Common Race Timing Errors: Why Readings Go Missing and How to Prevent Them
· 6 min read
In short
- Many timing errors are caused not by the technology but by poor preparation: incorrect chip placement, unsynchronized clocks, no backup procedure or an incorrect start list.
- An RFID reading may be missed if the chip is covered, placed on metal or too close to the body, or if competitors pass outside the antenna’s range.
- Manual timing fails when the finish is crowded or the operator loses concentration. More staff, a phone recording and backup timing can solve the problem.
- Always test the complete system before the start using the actual chips and the actual operators.
Competitors forget when everything goes right. They remember when their time is missing. Yet most timing errors can be anticipated and prevented.
Missing RFID readings
This is the most common error. Chip placement is usually the cause: a competitor attaches it to their back, covers it with a backpack or places it directly on metal. The body and water weaken RFID signals, while metal can detune a standard chip. Antenna setup and the width of the passage can also cause problems: if the timing point is too wide, someone may pass outside its range. How an RFID chip works in running and where to place it explains correct chip placement.
Duplicate records
The reader may detect a chip several times if a competitor remains within the antenna field for a moment. The software therefore needs a filter that merges multiple reads of the same chip within a short period into a single passage. Without it, meaningless split times appear in the results table.
Wrong bib number, wrong competitor
When tapping in the app, the timekeeper may enter the wrong bib number during a crowded finish. It helps to keep the start list in the app, allow bib numbers to be entered through search and display the competitor’s name so that errors are easier to spot. An incorrectly prepared start list in which two competitors have the same bib number is equally dangerous.
Clocks
If several devices show different times, split times and results will not match. All devices therefore need to be synchronized to the same time before the start. Learn more in Synchronizing clocks for race timing.
Signal, battery and power failures
There may be no signal in forests or mountains, and readers or phones can run out of power. The app must work offline and store data locally until an internet connection becomes available. Bring a power bank and a spare device.
No backup
The most expensive mistake is having no backup procedure. A backup can be a second antenna, manual tapping in the app on another phone, finish-line video or a paper record. Learn more in Backup timing: why you need it.
An untested system
A pre-start test reveals most problems. Cross the finish line with the actual chips, at realistic intervals and with the actual operators, then check that all passages appear. Delete the test records afterward and reset the event for the race.
How TAQIO helps
TAQIO stores records locally even without an internet connection, filters repeated reads of the same chip and lets you combine RFID with manual tapping as a backup. Try it free for up to 5 participants per event.
Frequently asked questions
Why does an RFID system miss a competitor?
The most common causes are chip placement—covered, too close to the body or on metal—weak antenna range, a passage area that is too wide or too narrow, and a loss of power or connectivity to the reader.
How can I tell that a reading is missing?
Compare the number of competitors at the finish with the number of chips detected by the reader, and check the split times. If a competitor has a split time but no finish time, the finish reading may be missing—unless the competitor did not finish, which must first be ruled out.
How can a missing reading be corrected?
Use one of the backup sources: a reading from a second antenna, a manually recorded time or finish-line video. That is why having a backup procedure is worthwhile.
How often do race timing errors occur?
It depends on the preparation. Errors are rare at a well-prepared event with pre-start testing and backup timing. An event held without testing is likely to have more of them.