Most golf software says it is easy to use. We wrote down what “easy” means for scoring on a golf course, built Back9Ops to those rules, and added automated tests that fail if a future update breaks one of them. Here is what we promise, and how each promise is protected.
Each card says what we promise, and what stops it from quietly changing later.
Big enough to read outside. Scoring screens use large numbers and large type, so a player standing on the tee in bright light can see the score they just entered.
How we protect it: a minimum text size is written into the product as a rule, and automated tests stop scoring screens from quietly shrinking into tiny text.
Tap the score once. Move on. No tiny plus and minus controls. The number you tap is the number that is saved, on every scoring screen.
How we protect it: every screen that takes a score uses the same big number keys, and automated tests fail if a plus-and-minus control ever comes back.
A late save cannot silently replace a newer score. Your score should not disappear because two updates crossed paths. When a slow connection delivers an older score after a newer one, Back9Ops keeps the newer one.
How we protect it: every save carries the time it was tapped, the server compares it against what it already holds, and automated tests replay the crossed-paths case to make sure the newer score wins.
Keep scoring through a dead spot. If a guest who scanned a QR code loses signal on the back nine, Back9Ops holds those scores on the phone and sends them when the connection returns. The player sees plainly what has been saved and what is still waiting.
How we protect it: automated tests drop the connection mid-round, confirm the scores are kept on the phone, and confirm they arrive once signal is back.
We would rather you know the edges now than find them on event day.
No account setup is required for guest scoring. Print scorecards with a unique QR code for each player or group. They scan it at the first tee and enter scores on any phone, in the browser. No download, no password, no sign-up screen between a first-timer and their scorecard.
Guest scoring is the part that needs no account. Registering, seeing your own history, and running events still use a sign-in, because those belong to a person.
More about scoring →You set the cutoff. Until then, a player who cannot make it cancels from their own private link, and a player who changes their mind puts themselves back in. The waiting list moves up on its own.
Your rules stay in charge. Self-service only narrows what a player can change; it does not let them past a cutoff you set.
A player who can read the screen, tap once, and fix their own spot does not need to call the pro shop. That is the whole idea.
Buttons say what they do. When something cannot be done, the screen says why, in a sentence a person would actually say.
On player screens, a button a thumb aims at is at least 48 pixels tall, and text on scoring screens stays above a minimum size we set on purpose.
Deleted the wrong team or moved the wrong player? A plain green strip says what just happened and offers one button to undo it. It waits until you decide.
Create a free account, set up a test event, and score a few holes from the parking lot. No credit card, no sales call.