← Back to Blog

Cricket scoring looks simple on the surface, does it not? Count the runs, track the wickets, note the overs. How hard can it be? Well, let me tell you, anyone who has actually sat with a scorebook through a full match knows the answer: surprisingly hard. One misrecorded extra can throw off an entire innings total. A missed strike rotation can leave you chasing errors for overs, scratching your head while the game moves on without you.

I have seen scoring mistakes cause arguments that lasted longer than the match itself. Whether you are scoring on paper or using an app, understanding these common pitfalls will make you a sharper, more reliable scorer. So let me walk you through the ten mistakes we see most often, why they happen, and how to get them right.

1. Wrong Strike Rotation on Wides

What goes wrong

A wide is bowled and the batsmen run two. The scorer records three runs (the automatic penalty plus two ran) but then gets confused about whether the strike should change. Some scorers assume wides never change the strike. Others assume they always do. Both camps, I am afraid, are wrong.

The correct rule

Here is where it gets interesting. A wide itself does not count as a ball faced, but the batsmen can still physically run. The key is that the automatic one-run penalty on a wide is not a physical run. The batsmen did not cross for it. So on a wide, the number of physical runs is one fewer than the total extra runs awarded. Strike rotates when the number of physical runs is odd. A wide with no additional runs (1 extra total, 0 physical runs) means no strike change. A wide plus one run (2 extras total, 1 physical run) means the strike swaps. A wide plus two runs (3 extras total, 2 physical runs) means it does not.

How to avoid it

Always separate the automatic penalty from the runs actually taken. Count how many times the batsmen crossed. Odd number of crossings? Swap the strike. Even or zero? Keep it the same. Simple when you break it down like that, is it not?

2. Crediting Byes or Leg Byes to the Batsman

What goes wrong

The ball beats the bat and races to the boundary. The scorer instinctively adds four runs to the batsman's tally. But wait. Those are byes (or leg byes if the ball hit the pad) and should not appear on the batsman's scorecard at all. I have seen this inflate batting averages in club cricket more times than I can count.

The correct rule

Byes and leg byes are extras. They add to the team total but not to any individual batsman's score and not to the bowler's figures. The only runs credited to a batsman are those scored off the bat: drives, edges, deflections where bat contacted ball.

How to avoid it

Ask one simple question: did the ball touch the bat? If the answer is no, the runs are extras. Record them under byes or leg byes in the extras column, not against the batsman's name. It sounds obvious when you say it out loud, but in the heat of a match, this one catches people out all the time.

3. Counting a Wide or No-Ball as a Legal Delivery

What goes wrong

A bowler sends down a wide, and the scorer marks it as ball three of the over. Now the over finishes after five more legitimate deliveries instead of six, and the bowler effectively gets away with bowling fewer legal balls. Nobody notices until someone checks the maths later, and by then it is a headache to fix.

The correct rule

Wides and no-balls are not legal deliveries. They do not count toward the six balls required to complete an over. The over counter should only advance on balls that are neither a wide nor a no-ball. So an over with two wides in it will actually have eight deliveries bowled: the six legal ones plus the two illegal ones.

How to avoid it

Keep a clear distinction in your mind between "balls bowled" and "legal balls bowled." Only increment the ball-in-over count on legal deliveries. When recording a wide or no-ball, note it but do not advance the over counter. This feels fiddly at first, but it becomes second nature after a few matches.

4. Forgetting the Automatic 1 Run on a Wide or No-Ball

What goes wrong

A wide goes straight through to the keeper. No one runs. The scorer records it as a wide but puts down zero runs. But here is the thing: every wide and every no-ball carries an automatic one-run penalty, regardless of whether anyone actually runs. It is one of those rules that catches out new scorers constantly.

The correct rule

A wide always costs at least one run, awarded as an extra to the batting team. A no-ball also costs at least one run. If the batsmen run additional runs on top, those are added to the total. On a no-ball, any runs scored off the bat go to the batsman's personal tally, while the one-run penalty stays in extras. On a wide, all runs (including the penalty) are extras.

How to avoid it

Treat the penalty run as automatic. The moment you record a wide or no-ball, start at one run minimum. Then add anything else on top. Never, ever record a wide or no-ball as zero runs. Make this a non-negotiable habit.

5. Crediting the Bowler with a Run-Out Wicket

What goes wrong

The batsman drives the ball to mid-off and is run out attempting a second run. The scorer adds the wicket to the bowler's figures. Now the bowler has a wicket they did not earn. I have actually seen arguments in club cricket that lasted longer than the match itself over exactly this kind of mistake. And the bowler, naturally, never wants to give that wicket back.

The correct rule

A run out is not credited to the bowler. The bowler's wicket tally should only include dismissals where the bowler directly caused the wicket: bowled, caught, LBW, stumped, hit wicket, and caught-and-bowled. Run outs, mankads, timed out, retired out, obstructing the field, and handled the ball do not count in the bowler's figures.

How to avoid it

Before crediting a wicket to the bowler, check the dismissal type. If it is a run out, the wicket goes on the scorecard as a team event but does not appear in the bowler's analysis. Note the fielder who effected the run out instead. Give credit where credit is actually due.

6. Not Recording Who the Non-Striker Was

What goes wrong

A wicket falls or the over ends, and the scorer suddenly realises they have lost track of which batsman was at the non-striker's end. Now they cannot correctly record the new batting pair, partnerships become muddled, and reconstructing the innings later turns into a detective exercise that nobody enjoys.

The correct rule

The scorebook should always reflect both the striker and non-striker for every delivery. Knowing who is at which end is essential for tracking partnerships, ensuring the right batsman faces after strike changes, and correctly recording which batsman was dismissed in run-out situations. Was it the striker or the non-striker who was short of the crease? You need to know.

How to avoid it

After every delivery, mentally confirm who is on strike and who is at the non-striker's end. After every run or over change, update your record. If you lose track mid-over, stop and verify with the umpires or players before recording the next ball. Trust me, it is far easier to pause for five seconds than to untangle errors three overs later.

7. Missing the End-of-Over Strike Swap

What goes wrong

The over ends and the scorer forgets that the batsmen automatically swap ends. The next over starts being recorded with the wrong batsman on strike. Every subsequent ball in that over is now attributed to the wrong player. And once that happens, you have a real mess on your hands.

The correct rule

At the end of every over, the bowling changes ends, and so the batsman who was at the non-striker's end is now facing the new bowler. This is a natural consequence of the bowling alternating ends. The batsmen do not physically move, but the "striker" label transfers to whoever is at the end the new bowler is bowling to.

How to avoid it

Build it into your routine: when the over ends, note the strike swap before recording any detail of the next over. Write down who is on strike at the top of each over. And here is a nice little trick to remember: if the last ball of the previous over involved an odd number of runs, the combined effect (end-of-over swap plus mid-ball swap) means the same batsman stays on strike. Once you internalise that, it becomes automatic.

8. Confusing No-Ball Bat Runs with Extras

What goes wrong

The bowler oversteps and the batsman smashes the no-ball to the boundary for four. The scorer records all five runs (1 penalty + 4 hit) as extras, or records all five against the batsman. Both are wrong. And this one trips up even experienced scorers, so do not feel bad if it has caught you out.

The correct rule

On a no-ball, the one-run penalty is an extra. But any runs scored off the bat are credited to the batsman, not to extras. So in our example, the batsman gets 4 runs on their personal score, and 1 no-ball extra goes into the extras column. The bowler is charged with all five runs in their bowling figures (batsman runs plus the no-ball penalty, but not byes or leg byes). This is different from wides, where all runs are extras.

How to avoid it

Remember the split: no-ball penalty goes to extras, bat runs on a no-ball go to the batsman's score. If the batsmen run without the ball touching the bat (no-ball byes), those runs go to extras as well. Only runs off the bat go to the batsman. Once you get this distinction clear in your head, it sticks.

9. Wrong Maiden Over Tracking

What goes wrong

A bowler completes an over where no runs came off the bat, but two byes were scored. The scorer does not mark it as a maiden because runs were scored. Or, going the other way, the scorer marks it as a maiden even though wides were bowled. Both are wrong, for different reasons. This is one of those areas where the rules are more nuanced than people realise.

The correct rule

A maiden over is one in which six legal balls are bowled and zero runs are conceded by the bowler. Now here is the important part: byes and leg byes do not count against the bowler, so an over with only byes is still a maiden. However, wides and no-balls do count against the bowler (and also mean the over has not yet reached six legal balls). An over containing a wide or no-ball can never be a maiden.

How to avoid it

To determine a maiden, first check that six legal deliveries were bowled with no wides or no-balls. Then check that no runs were scored off the bat and no wide or no-ball penalties were incurred. Byes and leg byes are irrelevant to the bowler's figures, so ignore them for maiden calculations. It is a two-step check that takes seconds once you are used to it.

10. Not Recording Free Hits After No-Balls

What goes wrong

A no-ball is bowled. The next delivery, the batsman is caught at mid-on. The scorer records it as a wicket. But that delivery was a free hit. The batsman cannot be dismissed caught on a free hit, so the wicket should not stand. You can imagine the conversation that follows with the fielding team. It is never a pleasant one.

The correct rule

Every no-ball (in limited-overs cricket) results in the next delivery being a free hit. On a free hit, the batsman can only be dismissed by run out, obstructing the field, or hitting the ball twice. All other forms of dismissal, bowled, caught, LBW, stumped, hit wicket, are invalid. And here is a detail many people miss: if the free hit delivery is itself a no-ball, the following delivery is also a free hit. The chain continues until a legal, non-no-ball delivery is bowled.

How to avoid it

Every time you record a no-ball, immediately flag the next delivery as a free hit. Do not rely on memory. Mark it visually in your scorebook or scoring system. If a wicket falls on a free hit delivery, verify the dismissal type before recording it. Only run outs and obstructing the field are valid.

Let the Software Handle It

Here is what all ten of these mistakes have in common: they happen because a manual scorer is tracking dozens of interrelated rules simultaneously, and human attention slips. It just does. We are not machines, and nobody expects us to be. A digital scoring app handles most of these automatically. Strike rotation is calculated after every delivery. Extras are categorised correctly based on the delivery type. Maiden overs are determined by the system, not by mental arithmetic under pressure. Free hits are flagged the moment a no-ball is recorded.

That is exactly why we built Skipper. The app enforces the Laws of Cricket in real time so you can focus on what you should be doing: watching the game. Runs go where they belong. Strike swaps when it should. Free hits are never forgotten. You just tap what happened, and the scorebook stays accurate.

Of course, understanding the rules yourself still matters. No app can replace a scorer who truly knows the game. But having software as a safety net means fewer errors, cleaner records, and a lot less stress when the match gets intense. And honestly, is that not the best of both worlds?