What it was, and what it became
The original reading and the corrected value are both kept. The first is not overwritten, so it is always possible to see what the machine thought and what the human decided.
Reading a card is the easy half. What happens when the reading is not certain is where automated scoring either earns a committee's trust or loses it for good.
One must-fix and two worth-a-look. Settle all three and the card can be marked as checked — until then it genuinely cannot be, exactly as in the product.
The digit on hole 7 could be a 6 or a 5. The same writer's 6 on hole 2 closes at the top; this one does not.
Pick a reading, type your own, or confirm the card is right. The audit trail builds as you go.
Split into two groups by consequence, not by severity of feeling. A must-fix exception stops the card. A worth-a-look is shown to you and blocks nothing.
| Exception | What it means |
|---|---|
| Not a scorecard | The photograph is of something else. |
| Poor quality | Glare, blur, shadow or a cropped edge make it unreadable. |
| Unreadable name | A player's name cannot be made out. |
| Unreadable handicap | A handicap cannot be made out. |
| Missing score | A hole is blank and has not been confirmed as a no-score. |
| Impossible gross | A score outside believable bounds for the hole. |
| Unmapped column | A column on the card cannot be matched to a player. |
| Exception | What it means |
|---|---|
| Low confidence | A digit is ambiguous, with alternatives recorded. |
| Crossed out | The writer changed their mind and the correction is unclear. |
| Stableford mismatch | Written points disagree with the points we calculate. |
| Total gross mismatch | The holes do not add up to the written total. |
| Total points mismatch | The written points total disagrees with the holes. |
| Player not in roster | A name that is not on the entry list. |
| Handicap mismatch | The card's handicap differs from the roster's. |
| Missing handicap | No handicap written, and none on file. |
| Handicap index only | The card shows an index like 15.9 and no whole-number handicap to play off. |
| Missing player | A column with scores but no name. |
| Duplicate card | This card appears to have been photographed already. |
| Course mismatch | The card's printed par or stroke index differs from the setup. |
A total that does not add up is worth knowing about, but it does not stop you scoring the competition: the holes are usually right and the written total is an arithmetic slip. A blank hole does stop you, because there is no honest way to score a hole nobody wrote a number on. The distinction is about whether the competition can proceed, not about how annoying the problem is.
A committee does not need software that is always right. It needs software that can show its working when somebody disputes a prize six weeks later.
The original reading and the corrected value are both kept. The first is not overwritten, so it is always possible to see what the machine thought and what the human decided.
Each correction carries the person who made it and the time. Each card carries who checked it and who locked it.
The history does not live in a log somewhere else. It stays with the competition, which is what makes it useful when it is needed.
A scorer at the desk can photograph cards, settle exceptions and mark a card as checked. Locking it and publishing the result needs an admin. That separation is enforced by the API, not agreed informally.
The person photographing cards at the desk
Switch role and watch the publish control change.
No. That is the entire point. ScribbleScore brings you the values it is unsure about and the ones that disagree with something else on the card, and leaves the rest alone.
There are nineteen kinds of exception, split into two groups. Must-fix ones, like a missing score or a name nobody can read, stop the card being marked as checked. Worth-a-look ones, like a total that does not match the holes, are shown to you but do not block anything.
It becomes an exception and comes to you, with the photograph of the card beside it and the readings it thinks are possible. You pick the right one, or type the right one.
A cell nobody can read is not silently filled in. It is either resolved by a person or it stops the card from being marked as checked.
You are told, and shown both numbers. ScribbleScore adds up the holes itself and compares that with the total the player wrote at the bottom of the card.
It does not silently pick one. In practice the holes are usually right and the written total is an arithmetic slip, but that is a judgement for the committee, not for software.
Yes. Every correction is kept against the card, with the original reading, the corrected value, who made the change and when.
That history stays attached to the published result, which is what lets a committee settle a prize dispute weeks later from the record rather than from memory.
Accurate enough that reviewing a card is quicker than typing one, and built so that where it is unsure, it says so instead of guessing.
Every value it reads carries its own confidence score. Where a digit is ambiguous it records what else it could be, and it pays particular attention to the handwriting confusions that actually matter on a scorecard: 3 against 5, 1 against 7, 4 against 9, 6 against 0 and 2 against 7. Anything it is unsure about is read a second time, on its own, before you are ever asked about it.
We do not publish a single headline accuracy percentage, because the number that matters is how many cells you have to check on your cards, not on ours.