Test Match Sessions, Lunch, Tea, and the Over-Rate: How a Day of Test Cricket Is Structured
A Test match day consists of 3 sessions of play separated by a lunch break (40 minutes) and a tea break (20 minutes). Each session typically lasts approximately 2 hours. The over-rate requirement is 15 overs per hour — 90 overs per day. Teams that bowl too slowly can face fines and points deductions. In T20 cricket, the over-rate target is 14.11 overs per hour. Bad light or rain can curtail sessions. The 'scheduled close of play' is 6 hours of play (excluding breaks).
A Test match day is structured into three playing sessions, separated by breaks. This structure has been virtually unchanged since Test cricket's origins in the 19th century, and it gives Test cricket its unique rhythm — the transition from one session to the next creates natural tactical pressure points as teams seek to end a session with a wicket or build partnerships through.
The Three Sessions
Session 1 (Morning session): approximately 11:00 to 13:00 (2 hours). The new ball is typically taken here. Conditions are freshest — the dew has dried, the pitch is most lively. Lunch: 40-minute break. Session 2 (Afternoon session): approximately 13:40 to 15:40 (2 hours). The pitch typically begins to settle; batting becomes easier. Tea: 20-minute break. Session 3 (Evening session): approximately 16:00 to 18:00 (2 hours). The ball is older; reverse swing possibilities; the day's second new ball may be taken after 80 overs. The exact times vary by country, climate, and daylight hours. Australian summer Tests start at 10:30 due to heat management; English Tests start at 11:00.
Over-Rate Requirements
The ICC requires fielding teams to bowl 90 overs per day in Test cricket — approximately 15 overs per hour. Slow over-rates are penalised: fines for the team, ICC World Test Championship points deductions, and personal fines for the captain. Teams that consistently bowl slow (taking 7 minutes between overs) face significant financial consequences. Some teams deliberately bowl slowly when a match situation favours the fielding side — this is penalised but teams sometimes accept the fine as preferable to losing.
Frequently asked questions
What happens when a Test match is drawn, and how do teams try to force a result in the final session of day 5?
Test match draws and day 5 tactics: how results are forced. A Test match is drawn when: (1) Neither team has completed both innings OR (2) The team batting last has not been bowled out but has also not reached the target. In a draw, no winner is declared — both teams receive 0 wins and 0 losses (though ICC WTC awards 4 points for a draw vs 0 for a loss). How teams force results on day 5: Declaring: if a team leads significantly, they declare their second innings (announce their batting is complete) and set the opponent a target to chase. A good declaration sets a target that is achievable in the remaining overs (say 300+ runs in 60 overs) but risky enough that the batting team must attack and can lose wickets. Too aggressive a declaration: sets 180 in 80 overs — almost certainly draws (batting team blocks). Too defensive a declaration: sets 380 in 30 overs — impossible, batting team draws comfortably. The art of declaration is setting a target that stretches the opponent. Famous declarations: England set 478 vs India in the 1st Ashes Test (2023, Bazball) — India chased but fell short (win for England). Batting out for a draw: the team with a deficit needs to bat out the remaining overs. Typically: play blocks, defend every delivery, run between wickets for singles only. Famous examples: Rahul Dravid's 270-ball 35* (drawing a match in Antigua), England's 2009 Ashes draws. The tactical dynamic on day 5: every session creates a 'shift.' An hour of batting without wickets shifts momentum toward the draw; a wicket cluster shifts toward the bowling team. Test cricket's greatest day 5 tensions emerge from this delicate balance.