The best way to learn ball-by-ball cricket scoring is not to read about it — it is to score one over. This piece walks through that first over, then the rest of the innings, from the point of view of the person holding the phone. If you have volunteered to score for a friendly this weekend and you have never done it before, read this once on the bus and you will be fine when the first ball is bowled.
The examples use ForthUmpire — a free live cricket scoring app that runs in your browser. The mechanics translate cleanly if you are on paper or in a different app; the labels change, the events do not.
Before the first ball: three things to write down
Get these into the app or your notebook before the toss:
- The two team names, spelled the way the captains will want them spelled when the highlights get shared on WhatsApp that evening.
- Overs per innings, and any house-rule quirks (some grounds cap the bowler at two overs; some box formats give the last batter a runner instead of an all-out).
- The toss result — who won, who chose, whether they bat or bowl. This one gets skipped more often than any other and shows up as an argument in the group chat afterwards.
Open the app, tap Quick Match, enter the two team names and the overs. Total time: roughly forty seconds. The batting order can be filled in during the walk from the pavilion to the crease.
Ball one — the anatomy of a single delivery
The bowler runs in. Ball is bowled. Four things can happen; each one has a tap.
- The batter hits it and runs. Watch the boundary umpire's arm. If the ball crosses the rope on the bounce, that is a four; on the full, a six. Otherwise, count the runs the batters completed on their feet. Tap that number.
- The batter hits it and does not run. That is a dot. Tap the 0 (or the "dot" button, depending on the app). It is not nothing — dots pressure a batter and are the bowler's currency.
- The ball misses the bat. If the umpire signals nothing, it is still a dot. If the umpire signals bye or leg-bye, tap the corresponding extras button and record the runs the batters ran.
- The wicket falls. Straight to the wicket dialog — pick the mode of dismissal, name the fielder if one is involved, and confirm the new batter.
That is the whole vocabulary of one legal ball. A full match is that same sequence, roughly two hundred times.
The umpire's signals — what to look for
You score what the umpire signals, not what you saw. If the umpire has raised the finger, the batter is out even if the appeal looked hopeful. If the umpire has spread the arms wide, that is a wide even if the batter reached it. The signals you will see most often on a Saturday afternoon:
- Wide — arms straight out. Tap wide. The penalty runs are set once in match settings and applied for the rest of the innings.
- No-ball — arm out at shoulder height. Tap no-ball. If the batter also hit runs off the delivery, tap those next. A free hit prompt follows for the next legal ball if your rules include one.
- Bye — one arm straight up. The ball passed the bat and the keeper. Runs count for the team, not the batter. Tap byes and the run count.
- Leg-bye — a tap on the raised knee. Same idea, but the ball touched the pad. Tap leg-byes.
- Four — arm swept across the body at waist height. Tap 4. The batter gets it.
- Six — both arms above the head. Tap 6.
- Dead ball — arms crossed in front, then split. Nothing to record. Wait for the re-bowl.
The end of an over — a small ritual
After the sixth legal delivery, three things happen at once. The fielders swap ends, a new bowler walks in, and the strikers change ends automatically (if they took an odd number of runs off the last ball, the same batter faces; otherwise the non-striker does). You do only one thing: tap the new bowler before their first ball. If you tap after, the first delivery lands under the wrong name and you will spend the next over untangling it.
Once you have done this a dozen times it becomes muscle memory. The first four or five overs you will be a beat behind; that is normal, and every scorer has been there.
When a wicket falls
Wickets are the moments the scorer has to slow down. Confirm the mode of dismissal with the umpire before tapping — bowled and caught are usually obvious, but LBW, run out and stumped can look the same from the boundary. Enter the mode, the fielder who caught it or ran it out, and the incoming batter. The partnership breakdown, fall of wickets and dismissal card update themselves.
If you are unsure, ask. A ten-second pause with the umpire is faster than a ten-minute conversation with an angry captain at innings break.
Sharing the live scorecard
Halfway through the first over, do one more thing — tap the share icon and send the live link to your team's WhatsApp group. Everyone who could not make it to the ground is now watching the match, refreshing itself, in a browser tab at their office. This is the single feature every scorer underuses because it feels like a distraction; it is not, it is the whole reason the app exists.
Innings break — five minutes of yours
When the last wicket falls or the overs run out, the innings closes automatically. The second-innings target appears on the shared link, so everyone reading it already knows what the chasers need. Put the phone down. Drink water. Come back for the second innings with fresh eyes and, if the captain of the batting side asks for a screenshot of the innings card, take it now.
What changes on your third match
The first match you will chase the ball. The second, you will keep pace. By the third, you will be ahead — your thumb hovering over the run buttons before the bowler has released, and you will start noticing the rhythm of the game the way a working scorer does. You will glance up more often, argue with yourself less, and the running total on the top strip will stop feeling like a fact you have to verify.
Everything else — retired-out vs retired-hurt, penalty runs, the finer LBW columns, super-overs — comes later. The how-to-score reference page covers the edge cases when they show up. What you have above is the working core, enough to score any friendly, box game, gully match or school fixture on the weekend.
If you would like to try it before Saturday, open ForthUmpire and tap Quick Match. Enter two nicknames as the team names, six overs, and score a fake innings against yourself on the sofa. Twenty minutes of practice is worth ten pages of reading.