Morning Vesa,
I wasn’t sure whether to send this directly or post in the user group – but figured others may share similar thoughts or use cases.
Now that our Cross Country season is underway here in NZ, I’ve run into / been reminded of a couple of situations with Webscorer that might benefit from added flexibility:
1. Dead Heats in Individual Results
Currently, if finishers have the same displayed time (e.g. to the nearest second), Webscorer lists them as tied, even when we know the actual order of finish based on visual observation. In NZ XC races, ties aren’t allowed—an official at the line determines order.
Could you add an option to calculate placing from more precise recorded times (e.g. tenths or hundredths), while still displaying results to the nearest second?
Example option settings:
Display time: nearest second
Calculate place: nearest tenth
This would help remove unintended ties without showing overly precise times that aren’t accepted by governing rules.
2. Dead Heats in Team Scoring
We also encounter ties in team scores. For our events, we use a tie-breaker based on the best finishing position of the last scoring team member.
For example:
Team A and B both score 25 points.
Team A’s 3rd runner finishes 12th; Team B’s 3rd runner finishes 10th.
→ Team B wins on the tiebreaker.
Locally, I add a small fraction (e.g. last scorer’s position ÷ 1000) to the team’s score to automate this, then round for display. Could Webscorer consider supporting something similar as a built-in option?
I understand Webscorer can’t cover every edge case, but these features might support a wider range of race formats—especially for organisers needing to meet official rules while still using Webscorer as the public-facing results platform.
Thanks for a great product—it covers 99% of what I need!
Apologies for the long note,