By Onkar Jadhav · 8 min read
Live cricket scoring for a tournament nobody is televising.
The mechanics of getting a ball-by-ball record from one person at the boundary rope to a shareable page, a WhatsApp group and a stream overlay, and the three things that actually go wrong.
How does live cricket scoring work?
Live cricket scoring means one scorer enters each ball as it is bowled and that entry is published immediately to anyone holding a public link. The scorer’s device is the source of truth; the spectator page, the WhatsApp share and any stream overlay are all views of the same ball-by-ball log, so there is only ever one number to correct.
One source of truth, several views
The thing that makes live scoring workable is that there is only one writer. The scorer’s device holds the ball-by-ball record, and the spectator page, the WhatsApp share, the venue display and any stream overlay are all read-only views of it.
That is worth stating because the obvious alternative, letting a second person update a scoreboard or post scores to a group, is how a tournament ends up with two numbers in circulation and no way to tell which is right. If the overlay and the public page disagree, someone has a second writer.
What the scorer actually does
- Open the match before the toss and confirm both squads, so a late replacement is caught while it can still be fixed cleanly.
- Set the overs per side and any local playing conditions. Doing this after the first over means the over count and the net run rate divisor are wrong.
- Enter each delivery as it is bowled: runs, extras, wicket. One tap for most balls.
- At the innings break, check the three reconciliations before the second innings starts rather than at the end of the match.
- Close the match. The result, the points and both teams’ net run rate contribution follow from it.
Getting the score to the people who want it
| Channel | What it is good for | What to watch |
|---|---|---|
| Public match link | The default. No app install and no account, which matters because most of the audience opens one WhatsApp message and never returns. | The link has to work on a cold phone browser. Anything requiring a login loses most of the audience. |
| WhatsApp share | How the link actually spreads at local level. Share once per innings rather than per over. | Sharing a screenshot instead of the link means the number is stale the moment it is sent. |
| Venue display | A TV or projector at the ground showing the current state. | Needs a device that will not sleep. Disable screen timeout before the first match, not during it. |
| Stream overlay | A browser source in OBS pointed at a scoreboard URL, re-rendering as the scorer enters balls. | Set the scene up the day before. Nobody should be configuring OBS while the toss happens. |
The three things that go wrong
- Network. The most common and the most consequential. At a ground with patchy coverage, a platform that writes straight to a server stops accepting entries. A local-first one keeps going and syncs later. This is the single question to resolve before the tournament, not during it. See offline scoring.
- Battery. A full day of matches on one phone with the screen on will not finish the day. One power bank per scoring device, charged the night before, costs nothing and removes the problem entirely.
- The scorer leaving. Scorers are volunteers and sometimes have to go. Know in advance who takes over and make sure the match is on an account the replacement can reach, rather than only on one person’s phone.
What live scoring is worth to an organizer
The spectator benefit is obvious and is not actually the main one. The main one is that a live-scored match needs no post-match data entry: the scorecard exists the moment the last ball is bowled, the points table updates itself, and nobody spends Sunday evening transcribing paper books into a spreadsheet.
Across a fourteen-match tournament that is the difference between an organizer who publishes standings the same day and one who publishes them midweek with two corrections. The second organizer is not less careful; they are doing a job that should not exist.
Live scoring FAQ
How do spectators follow a live-scored local match?
Through a public match link the organizer shares. No account and no app install should be needed to read a score, because most of the audience is a parent or a colleague opening a WhatsApp message once.
What happens if the scorer loses network mid-innings?
On a platform that stores entries locally first, scoring continues and the backlog syncs when coverage returns, so spectators see a pause and then a catch-up rather than a gap in the record. On a platform that writes straight to a server, scoring stops. This is the single most important question to ask before a tournament at a ground with poor coverage.
Can live scoring drive a stream overlay?
Yes. The usual arrangement is a browser source in OBS pointed at a scoreboard URL, so the overlay re-renders whenever the scorer enters a ball. It needs no extra operator once the scene is set up.
How far behind the play is live scoring?
Roughly as long as the scorer takes to tap the delivery, so a few seconds. The honest limit is that a scorer at a local ground is also watching the game, so expect a lag of one ball during a busy over rather than instant updates.