How to Build an Innings in Cricket Without Running Out of Balls

Almost every guide on how to build an innings in cricket was written for 50 over and first class cricket, where a batter can afford to spend twenty balls getting used to the light and still finish with a hundred. If your matches last 5, 10 or 20 overs, that advice is actively dangerous. It will either get you out playing a shot you delayed too long, or leave you stranded with runs needed and no balls left.

The short answer

Building an innings means spending your balls in the right order: defend the deliveries you cannot score off, take runs off the ones you can, and keep enough balls in hand to accelerate at the end. A 20 over innings gives you 120 balls, a 10 over innings gives you 60, and a 5 over innings gives you 30. The correct length of your settling-in period is a percentage of that number, not a fixed count of overs, which is why a careful start that works over 50 overs loses a 5 over match outright.

Count balls, then split them into thirds

Overs are a scoreboard unit. Balls are the thing you actually spend. Convert the innings first:

5 overs: 30 balls
10 overs: 60 balls
20 overs: 120 balls

Now split the innings into three jobs rather than three time periods.

Assess. Work out what the bowler is doing. Length first, then line, then whether the ball is moving.
Accumulate. Take the low-risk runs that are on offer and rotate the strike.
Accelerate. Spend what is left on the highest-value shots you have.

Every batter does all three. The only question is how many balls each job gets, and that is pure arithmetic.

What ten balls costs you

Ten balls of looking around is a reasonable assessment period in longer cricket. Look at what it costs in a short game:

Ten balls out of 120 is about 8 percent of a 20 over innings. Affordable.
Ten balls out of 60 is about 17 percent of a 10 over innings. Expensive, but survivable if you cash in later.
Ten balls out of 30 is a third of a 5 over innings. That is not an assessment period, that is the innings.

This is the single most common reason a decent batter posts a bad score in a short match. They are not playing badly. They are spending a 50 over budget out of a 30 ball account.

Format by format

The rest of how to build an innings in cricket is applying that three-way split to the innings length you have actually been given.

20 overs, 120 balls

You have room. Give yourself six to eight balls to read the bowler, then score off anything that is not a good ball. Aim to be clearly ahead of a run a ball by the halfway point, because the final third of the innings is where wickets get expensive and the bowler starts aiming at your feet. If you are two or three down with 40 balls left, your acceleration window has already shrunk whether you like it or not.

10 overs, 60 balls

Three or four balls of assessment, maximum. In a 60 ball innings the middle phase barely exists: you go from reading the bowler to scoring almost immediately. A useful check is whether you can name the bowler's stock length after four balls. If you can, start scoring. If you cannot, you are watching rather than looking, and you are burning balls you will want back at the end.

5 overs, 30 balls

There is no assessment phase. Your first ball is a scoring ball, and your reading of the bowler happens while you attack rather than before it. The discipline in a 5 over innings is not patience, it is shot selection: pick one scoring area and go there repeatedly instead of trying to hit every ball somewhere different. Thirty balls is too short an innings to recover from two wasted overs, and it is too short for the bowler to hide a weak delivery either.

What assessment actually buys you

People treat the early part of an innings as a superstition. It is not. There are exactly three things worth finding out, and you can find all three while scoring:

The stock length. Where does this bowler land it when nothing special is happening? Everything else is a variation from that.
The one they go to under pressure. Hit a bowler for a boundary and watch the next ball. Most bowlers have a single reflex delivery, and the ball after you score is when you see it.
Which of your shots is available. The shot you trust on a given day is not always the shot you practised. Find it in the first few balls rather than discovering it in the last over.

Once you have those three answers, extra defensive balls add nothing. They just reduce the number of balls you have left.

Wickets are a budget too

Balls are one resource. Wickets are the other, and short formats invert the usual logic. Over 50 overs, losing early wickets is close to fatal because there is so much innings left to rebuild. Over 30 balls, a wicket costs you the few balls that batter would have faced and little else, which is why risk is cheaper in a short innings than players expect.

The practical version: in a 20 over innings, protect your wickets through the middle because you need batters at the end. In a 5 over innings, a wicket while trying to score is a far smaller mistake than a dot ball while trying to survive.

Setting a total and chasing are different jobs

When you are batting first you are guessing at a number, so build toward a rate rather than a target. Pick a run rate you believe is competitive for the format and check yourself against it every over.

When you are chasing you have the number in front of you, which makes innings building much simpler: divide the runs still needed by the balls still left and keep that figure from climbing. The moment it starts rising over several overs, your accumulation phase is over whether you feel ready or not. There is more on that split in the blog.

Practise this against something that fights back

Everything above is theory. Learning how to build an innings in cricket is a decision skill, and you cannot drill decisions in a net where every ball is thrown at the same length. You need an opponent who is choosing deliveries against you.

That is the part play cricket online is genuinely good for. Howzat Live is a free browser game with no download: two real people play a live 1v1 match, one batting and one bowling, with in-match chat, in 5, 10 or 20 over formats, in day or night conditions. Because you can choose the format, you can test the same batting plan across a 30 ball innings and a 120 ball innings in the same sitting and see exactly where the arithmetic breaks.

A sensible way to work on it:

Play a 20 over innings and count how many balls you faced before your first scoring shot. Most players are surprised by the number.
Play a 10 over innings with a rule that you must score off one of your first four balls.
Play a 5 over innings with no defensive shot available to you at all, and see what your shot selection does under that constraint.
Go back to 20 overs and notice that the early phase now feels unhurried.

If nobody is waiting in the lobby, the three computer opponents, Gully bot, Club bot and Academy bot, are useful for the pattern-reading half of this. Those results are rated at half weight, capped at a few per day, and cannot carry you past Scale 3, so the badge itself still has to be earned against real people. You can create a free account to start a quick match or send a private link to a friend, and rated matches build your Scale badge from 0 to 10 after five of them, with wins over stronger opponents moving you up faster. The leaderboard is the honest test of whether your innings building survives a human bowler who is reading you back.

The one line to remember

Divide the innings into balls, decide how many of them you are willing to spend before your first scoring shot, and treat that number as a cost rather than a right. Thirty balls, sixty balls and a hundred and twenty balls are three different games, and the batter who plays all three the same way is only ever correct in one of them.