Paperless Electronic Scoring (via PractiScore)
We prioritize these things and strive to implement them as simply as we can:
- Score Accuracy – the score reflects what you shot
- Score Transparency – trust that the score isn’t changed (accidentally or maliciously)
- Score Security – making sure scores aren’t lost thru physical damage
- Scoring Efficiency – make scoring as easy/fast as feasible with less staff
This document will only cover the first 3.
Score Accuracy – early is accurate
The basic tenant here is to push data entry to as close to the performance as feasible and to have the people most familiar with the performance (the RO and the Shooter) approve it there.
Accuracy is aided here by target count validation, offering up procedural / DQ rules, and also in some cases by extremely good/bad or unlikely score checking.
The shooter is the person who MOST CARES about the score. We have them approve it directly on the device it is entered in, prior to stage restoration or clearing of the scorekeeper’s mind by another shooter’s performance.
Copying to paper isn’t particularly accurate, especially when considering handwriting of most adults (or any adult in the rain). Printing is technically challenging outdoors (and expensive) and is subject to readability issues as well (smeared ink).
The key to accuracy, in our opinion, is that the shooter (if they choose to) examine the score then and there. Anything later is inherently less accurate. The closer this inspection happens to the score happening, the more accurate it is.
If a shooter is too tired or flustered after a run to pay attention, we strongly encourage the RO wait, or for the shooter to designate a proxy prior to the stage.
The ScoreKeeper explains the score to the shooter while it is still fresh in both their minds. We are more interested in making sure this is a cogent and understood explanation than getting a signture or some other authorization.
The ScoreKeeper needs to be satisfied that the shooter understood their score. This is primary, ahead of getting a signature or a PIN or even a verbal authorization. This is human communication – and the accuracy of the entire match rests here.
We rely on existing match structures to know that the shooter is the shooter, and that the RO asked the shooter to approve. If a shooter isn’t asked, they can protest immediately. We do have provisions for signing, but those were forced on us, we don’t like them, we just do them.
We have not added PIN codes because we view them as an unnecessary and inefficient step that also keeps out the use of a proxy for scoring verification – something we think should grow not be harder.
Score Transparency – let the sun shine
“If the broad light of day could be let in upon men’s actions, it would purify them as the sun disinfects.” Louis Brandeis
Score Logging brings sunlight to the scoring process…. When it is enabled PractiScore provides complete transparency of all scoring in a match.
The PractiScore system provides an electronic receipt of any editing of a score in the system. It is a transactional log of activity in the system. Like a bank uses. And like a bank PractiScore and the matches that use it have a very high interest in you believing it is treating you right.
PractiScore’s sends you an electronic receipt for ANY edit of a score. It also posts any edit of the score to https://www.practiscore.com/scorelog in full public view.
Tools in PractiScore permit easily finding odd editing patterns, such as too long between edits, edits after match hours, or edits on multiple devices.
Ultimately, though, the shooter looking at their own score logs will notice editing that doesn’t match their reality. This could be editing the wrong shooter, or something malicious, either way the shooter cares the most and is the first to learn of the issue.
One extra level of transparency we are considering adding is logging who the ScoreKeeper was for a given score, and what Range Officer issued the penalty. Another is logging of the reason for an edit, especially if done after a certain time limit or if on another device.
Score Security – set and know your risk level
What happens if you drop your tablet in a puddle? Or slam it in a truck door? Or it is stolen or lost? Anything that exists only on it is lost.
PractiScore tries to get scores to exist in different physical locations as soon as it can. Score Logging sends it to the cloud. Synching sends it to other PractiScore devices. Posting scores sends the entire match to the cloud.
With PractiScore you specify the level of physical security you want in terms of number of scores you are willing to lose to physical loss of a device. For a club match, perhaps you set it as squad size you are willing to reshoot. For a major, maybe 1 or 2.
PractiScore keeps track of the number of scores that ONLY EXIST on the current device. If it grows beyond that permitted amount, the ScoreKeeper is warned.
Score logging clears this count. Synching clears this count. Auto Synching clears this count. And posting results clears this count.
You are informed when you have scores at risk. You can write them down, post interim results, call stats for a synch, or turn on the internet and have score logging happen.