A Test match day looks shapeless if you do not know what governs it. It is in fact tightly structured, and almost every tactical decision a captain makes across five days is a response to that structure.
The sessions
Play is divided into three sessions of roughly two hours each, separated by two breaks.
- Morning session, then a lunch interval of about forty minutes
- Afternoon session, then a tea interval of about twenty minutes
- Evening session, until the day's overs are complete or the light goes
A minimum of ninety overs is scheduled per day. If they are not bowled in the allotted time, play is extended, and a side that has bowled slowly can be fined or docked championship points for it.
The sessions matter because they are natural units. Commentators talk about winning a session because a side that takes four wickets between lunch and tea has changed the match regardless of what the overall score looks like. Batters aim to survive to the next break. Bowlers are given spells that end at one.
The new ball
A fresh ball is available after eighty overs of an innings, and the fielding captain chooses when to take it.
An old cricket ball is soft, its seam is worn flat, and it does very little through the air or off the pitch. A new one is hard, seams and swings, and carries through to the wicketkeeper. The difference is enormous, and the eighty over mark is a genuine turning point in every long innings.
The decision of when to take it is a real one. Take it immediately and you get maximum help while your best bowlers may be tired. Wait ten overs and you keep the reverse swing an old ball can offer, but you give a set batsman ten easier overs. Captains agonise over this and are second guessed constantly.
The follow on
If the side batting second finishes at least 200 runs behind in a five day match, the side that batted first may ask them to bat again immediately rather than taking their own second innings.
It is used less than it once was. Enforcing it means your bowlers go straight back out, potentially for two long innings in succession, and modern scheduling makes captains protective of them. The alternative, batting again to build an unreachable lead, also removes any possibility of losing.
The declaration
A captain can end their own innings at any point. This exists because a Test match can be drawn, and a side that bats too long may run out of time to bowl the opposition out twice.
The declaration is the most interesting decision in cricket, because it is a genuine trade. Bat on and you make the target safer but leave fewer overs to take ten wickets. Declare early and you have time, but you may have given the opposition a target they can actually chase. Captains who get it wrong in either direction are remembered for it.
Light and weather
Play stops when the umpires judge the light unsafe for batting, which usually means the fast bowlers are operating in conditions where the batter cannot pick the ball up. Offering spin instead sometimes keeps play going. Rain stops it entirely, and lost overs are added to later days where the schedule allows.
Time lost is not neutral. Two rain affected days turn a match that one side was winning into a draw, and the fifth day of a Test is frequently a race between a bowling attack and the clock.
Why the draw is not a failure
Newcomers to the format find it strange that a match can end with nobody winning after five days. It is the source of the format's tension rather than a flaw in it. A side batting through the final afternoon to save a match is playing for something, everyone in the ground knows what it is, and the outcome is genuinely in doubt until the last over.
Our Test match archive records draws as results in their own right, which is what they are.
Comments 0