Event-Day Reliability

The short version

Scoring keeps working without a connection. Each scorekeeper's phone holds an on-device outbox: scores entered while offline are saved locally and sync automatically the moment the signal returns — no refresh, no re-typing, nothing lost. The leaderboard catches up on its own once devices reconnect.

Offline scoring

The scoring app is installable (a Progressive Web App) and is built to run on a flaky connection:

• Scores are written to the phone first, then sent to the server.
• If the phone is offline, entries queue in the outbox and the app keeps working normally.
• When connectivity returns, queued scores send in the background and are acknowledged by the server before being cleared locally — so a dropped request is retried, not lost.

Sync & score conflicts

Because scores carry their team and hole, the server reconciles updates deterministically:

• Each hole is keyed by team and hole number, so a re-sent or duplicated entry overwrites cleanly rather than double-counting.
• A signed (finalized) scorecard and individually locked holes are protected — late or stray writes cannot silently change a card that has been locked or signed.
• The organizer can always make a deliberate correction, which is recorded in the audit trail.

A lost, dead, or swapped phone

Scores live on the server, not only on the phone that entered them. If a scorekeeper's phone dies or is lost:

• Any device can pick up scoring for that team using the team's access code — already-synced holes are right there.
• Only entries still sitting unsent in a powered-off phone's outbox are affected; everything that reached the server is intact.

Leaked or shared team codes

Team access codes are designed to be handed out — and re-issued if one leaks:

• An organizer can rename or regenerate a team's code at any time, which immediately invalidates the old one.
• Auto-named teams can be renamed once by the golfers themselves during setup.
• Scoring actions are scoped to a single team, so a shared code cannot reach another team's or another organizer's data.

Provider or network outages

The platform is fronted by a global CDN with DDoS protection, and the database, email, and payments run on managed, independently-operated providers (listed in the Trust Center). If an upstream provider degrades, scoring already entered on-device is preserved in the outbox and syncs when the path recovers. Current operational status is published on the Status page.

Backups & recovery

Stated honestly (mirrors the Trust Center):

• Automated daily backups of the managed database.
• RPO ~24 hours; RTO target ~4 hours.
• Point-in-time recovery (PITR) is available from the database provider but is not currently enabled (planned).
• Periodic restore tests are not yet performed (planned).

Help on event day

If something looks wrong during a live round:

• Email: [email protected]
• For a suspected security incident: [email protected]

Keep scoring — entries are held in the outbox and will sync once the connection returns.