Built for the people who run the competition

The problem is the paper, not the golfers

Golf has been keeping score on paper for a very long time, and it is good at it. A scorecard is cheap, works in the rain, needs no battery, and two players attest it between them. Nothing about the round needs fixing.

What needs fixing is what happens next. Someone at the desk types eighteen numbers per player into a spreadsheet, works out the Stableford points, applies the allowance, sorts out a countback, checks it twice because a prize depends on it, and then writes the whole thing out again for the noticeboard. On a golf day with a hundred players that is an evening's work, and it happens after an already long day.

ScribbleScore takes that evening away without asking a single golfer to change anything.

Why we are not chasing golfers

The obvious product here is an app for golfers. We are deliberately not building it, and it is worth explaining why, because it shapes everything else.

GolfRSA is the official World Handicap System authority in South Africa, and HNA operates the technology behind it. They already have the golfer: the official handicap, the score entry, the relationship. Asking a golfer to keep a second app, with a second identity and a second set of numbers, in order to solve a problem that belongs to the organiser, is a bad trade for the golfer.

So we took the other half. HNA keeps the golfer and the official handicap. ScribbleScore takes the paper-to-results workflow that nobody currently owns: reading the cards, resolving what is unclear, applying the competition rules, and publishing a result the committee can stand behind.

That is a smaller ambition than a golf super-app, and a much more useful one. It also means we can be genuinely complementary rather than quietly competitive, which matters if the two layers are ever going to work together properly.

What we think we are actually good at

Reading handwriting is the part people find impressive, and it is the part we would rank third.

The first is knowing when the reading is wrong. Every value carries its own confidence, ambiguous digits carry the alternatives they might be, doubtful cells are read a second time before anyone is asked about them, and a card cannot be marked as checked while a must-fix exception is open. A system that reads a card perfectly ninety-nine times in a hundred and hides the hundredth is worse than useless to a competition committee, because they cannot tell which one it was.

The second is the record. Every correction is kept, with who made it and when, attached to the published result. Committees do not need software that is always right. They need software that can show its working when somebody disputes a prize six weeks later.

Where we are

Early, and we would rather say so. ScribbleScore has a small number of users, no independent security certification, and no customer logos we are entitled to show you. When clubs are willing to be named, they will appear on this site and not a moment before.

What we do have is a product that works end to end, a scoring engine covered by automated tests for every format it claims to score, and a policy of describing capabilities as what they are: shipped, or configured for your club as implementation work.