Cricket Basics for New Fans: How to Follow a Test Match Over Five Days
A Test match can begin on a Wednesday morning and still be unfinished when the players walk off on Sunday evening. Five days, three sessions a day, and — the part that confuses newcomers most — no guarantee that anybody wins.
None of that is a flaw. It is the format's whole design. Once you know how the days are carved up, what an innings actually consists of, and why a captain would ever choose to stop his own team batting, the match stops looking like a slow blur and starts looking like a story with chapters.
Three Sessions, Ninety Overs, Every Day
Each day of a Test is scheduled for 90 overs, split into three sessions of roughly two hours. An over is six balls bowled from one end, and the next over comes from the opposite end, so the bowler changes every over while the batters stay where they are.
The breaks are fixed points you can plan around: lunch after the morning session, tea after the afternoon, then the evening session. If a team is bowling slowly, the umpires can add up to half an hour at the end of the day to make up overs. Rain and bad light stop play, and those overs are usually lost rather than recovered.
Here is why the sessions matter. Players and commentators talk about a match in session-sized pieces: "they won the morning, we fought back after tea." If you only have two hours to give a Test, watch a single session and judge it on its own. You will follow the plot better than someone half-watching all day.
The new ball
Each innings begins with a new ball, which swings and seams and makes batting hardest. After 80 overs, the fielding captain may take another new ball. It is a moment worth watching: the old, scuffed ball usually favours spin, the new one favours pace.
The Four-Innings Skeleton
Each team gets two innings. In the standard pattern, Team A bats, Team B bats, Team A bats again, Team B bats again. A team is all out when ten of its eleven players have been dismissed — the last batter cannot bat alone.
Most of the vocabulary on a scorecard follows from this. A few terms to keep straight:
- 240 for 5 — 240 runs scored, five batters out, five wickets in hand.
- Trailing by 112 — the batting side needs 112 more runs just to draw level.
- Leading by 200 — they are 200 runs ahead of the other team.
- First-innings lead — the gap between the two first innings, which shows who is dictating the match.
Worked example. India make 350. England are 120 for 3. England trail by 230 with seven wickets left; if they reach 351, they have a lead. That single number, the lead, is the spine of the match, and it is the first thing to check when you open a scorecard.
Declarations: Stopping on Purpose
A captain can end his own team's innings at any point while batters are still in. That is a declaration. The logic is simple once you see it: runs are only useful if you have time left to bowl the other side out. Leading by 400 with five sessions remaining, batting on achieves little. Declare, set a target, and give the bowlers a chance to take ten wickets.
It is a genuine gamble in both directions. Declare too early and the opposition might chase the target down. Bat too long and the clock runs out, turning a match you were winning into a draw. When you hear a target announced — "England need 320 from 88 overs" — the captain has already made that call.
The Follow-On
If a team leads by 200 runs or more after both sides have batted once, its captain may ask the opposition to bat again immediately instead of batting himself. That is the follow-on. It saves time and is meant to press home a large advantage.
Two things beginners get wrong here. It is optional, not automatic, and captains are cautious about it. Bowlers who have just toiled through a long innings are tired, and asking them to immediately do it again can backfire badly. If the follow-on is not enforced, the match simply returns to the usual four-innings order.
Why a Draw Is Not a Failure
Test matches run out of time. That is the short answer. If the final innings is not complete when the fifth day ends, the match is a draw, whatever the balance of play — a team can dominate for four days and still not win.
Do not confuse a draw with a tie. A tie means the scores finished level with the last wicket falling, and it is extraordinarily rare in Test cricket. A draw means the clock beat both teams.
Draws become likely when the pitch stays good for batting all five days, when a full day or more is washed out, when one team piles up a huge first-innings total, or when a side decides to survive rather than chase. That last one is a skill in its own right: batting out two full sessions to save a match, with close fielders crowding the bat, is some of the most tense cricket played.
A Routine for Following a Test Day by Day
- Day 1 morning: note the toss and the conditions. Whoever wins the toss usually bats first on a fresh pitch, unless overhead conditions favour the moving ball.
- After each first innings: write down the lead. Everything that follows is measured against it.
- Day 3 evening and Day 4 morning: declaration and follow-on calls cluster here. If you can only watch two sessions of the whole match, watch these.
- Day 5: find the runs needed and the overs left, then divide one by the other. A required rate above four runs an over in a Test is a serious ask.
- Track the 80-over mark in each innings. The new ball often changes the mood of a session.
Watching Your First Test Without Getting Lost
Pick one session a day rather than trying to absorb all fifteen. Choose a bowler and follow his spell — six or seven overs from one end tells you more about the conditions than flicking between everything. Keep the scorecard open, and check the lead every time you look away.
And accept the draw as part of the deal. A fifth day with the match on the line, one team pushing for wickets and the other blocking, is not a slow finish. It is the format at its most uncomfortable, which is exactly why people watch it.
Photo: Sarowar Hussain / Pexels