The Toss in Cricket: How It Works and Whether to Bat First

How the toss works under the Laws

Law 13 of the MCC Laws of Cricket covers the toss. The captains toss a coin on the field of play, in the presence of at least one umpire, no earlier than 30 minutes and no later than 15 minutes before the scheduled start. Traditionally the home captain tosses and the visiting captain calls. Competitions can set their own arrangement, and some leagues have experimented with letting the visiting captain choose without a toss at all.

The captain who wins chooses whether to bat or field first and must tell the other captain immediately. Once that choice is made, it cannot be changed. Team lists should be handed over before the toss, which is why the Laws also say each side nominates its players before the toss happens.

In a local friendly nobody is checking the stopwatch, but the timing still matters. A toss 15 to 30 minutes before the start forces both captains to be at the ground early, gives the batting side time to pad up, and lets the fielding side warm up their bowlers.

Making the local toss fair

Most toss arguments at local level have nothing to do with the coin. They are about players arriving after the toss, team lists changing once the result is known, or one captain claiming they called first. A little structure stops all of that.

If there is no umpire, ask a neutral player or spectator to watch. Let the coin land on the ground rather than catching it, because a caught coin can be turned over by accident. If the call is unclear, toss again.

1. Both captains confirm their playing lists, including substitutes.
2. Agree the rule sheet: overs, bowling limits, wides and any ground rules.
3. One captain tosses, the other calls clearly before the coin lands.
4. The winner announces bat or bowl immediately.
5. Record the toss result in the scorer's notes before the first ball.

The factors that should drive your decision

Good captains do not decide at the toss. They decide on the way to the ground and confirm when they see the pitch. The question is simple: in which half of the match will conditions be harder, and do you want to face them with the bat or the ball?

Look at the pitch first. A damp or green surface helps seamers early and usually gets easier as it dries, which favours bowling first. A dry, cracked or dusty pitch tends to get harder to bat on as it wears and helps spinners later, which favours batting first. Then look at the sky. Overcast, humid conditions help swing bowlers, while bright sunshine generally helps batters.

Light and time matter more in local cricket than in televised games. An evening start without floodlights means the side batting second may chase in poor light. On winter afternoons in north India, fog and early sunset can cut a game short, which makes batting first more attractive. In humid coastal cities, evening dew makes the ball wet and hard for bowlers to grip, so batting second becomes easier.

Your team matters more than the pitch

In local cricket, the gap between conditions on either side of the innings break is often small. The gap between your players is not. If your side has two good hitters and several nervous batters, chasing often suits them because they know the rate required and can pace themselves. If you have one quality bowler and a weak supporting attack, defending a total gives that bowler more value at the end.

Think about how many players will actually arrive on time. If two of your top-order batters are running late, bowling first gives them time. That is a perfectly sensible reason to bowl, and more common than anyone admits.

Experience matters too. Teams that panic under scoreboard pressure tend to do better batting first, where there is no target to fear. Teams with calm finishers usually prefer to chase.

Why chasing often wins short games

In very short formats, the side batting second has a clear advantage: they know the target. A 10-over side chasing 85 knows it needs 8.5 runs an over and can plan the innings around that. The side batting first has to guess what a good score is, and in local cricket that guess is often wrong.

That advantage shrinks in longer games where conditions can change a lot between innings. It also disappears when the pitch is deteriorating, when the light is going, or when the side batting second has a long tail. Use the default of bowling first in short games, then adjust for conditions.

Whichever side bats second, the scorer should show the required run rate after every over. Cricket Score Counter shows the target and required rate as the chase progresses, which saves the batting side from doing maths on the boundary.

Common toss disputes and how to avoid them

The most common dispute is a late arrival. A player turns up after the toss and the captain wants to add them to the team. Under the Laws, nominated players are fixed at the toss, but in friendlies most groups allow a late player to join with the opposing captain's agreement. Write that down on the rule sheet so it is not decided by whoever argues loudest.

The second is a disputed call. If the caller mumbles, or both claim they said heads, toss again. The third is a changed decision, where the winning captain says bat and then changes to bowl after seeing who is opening. Once announced, the choice should stand.

Finally, record the toss. It sounds trivial, but over a season it is useful to see how often the toss winner won the game and which choice worked on your regular ground.