Runs Per Over by Phase: How Scoring Rates Shift Through an Innings
Modern cricket analytics tracks scoring rates differently across an innings' phases — powerplay, middle overs, and death overs each have distinct characteristics. This article explains how teams score differently across phases, why middle-over run rates are so often the decisive match variable, and what over-by-over data reveals about batting strategy.
The Three Phases of ODI and T20 Scoring
ODI cricket analytics recognises three distinct phases: the powerplay (overs 1-10, fielding restrictions apply), where top-order batsmen typically score at 5-6.5 runs per over against the new ball with attacking fields; the middle overs (overs 11-40 in ODIs, overs 7-16 in T20s), where scoring rates often drop to 5-5.5 per over as fielding restrictions ease and batting becomes more conservative; and the death overs (overs 41-50 in ODIs, overs 17-20 in T20s), where scoring rates spike to 9-12 runs per over as batsmen attack with wickets in hand and field restrictions apply again. T20 cricket phases are compressed: powerplay 1-6 (average 8-9 RPO), middle overs 7-15 (average 7-8 RPO), death overs 16-20 (average 10-12 RPO). The phase differences reflect both batting tactics (risk tolerance varies by phase) and fielding configurations (powerplay and death overs allow fewer boundary fielders).
Middle-Over Scoring as the Key Variable
Match data shows that middle-over scoring rate is the phase most correlated with match outcomes: teams that score 6+ per over in the middle overs of ODIs win at significantly higher rates than teams scoring below 5 per over in the same phase; in T20 cricket, scoring below 7 per over in overs 7-15 puts teams in a position where the death overs must deliver an unrealistic acceleration. The middle-over challenge: fewer boundary opportunities (4-5 fielders can be placed on the boundary), dots accumulate through bowling changes and tight bowling spells, and wickets lost here are particularly damaging because replacement batsmen need rebuilding time. Teams that solve middle-over scoring — through specific batting roles (the 'floater' role that attacks middle-over bowling), innovative shots (ramp, reverse sweep), or aggressive running — have the highest success rates in bilateral series.
Phase Data in Team Selection and Match Planning
Phase-specific runs-per-over data now drives team selection and batting order decisions: a batsman with a high powerplay strike rate but poor middle-over performance may be selected only for T20 matches where the powerplay is the primary contribution needed; specialists who score at 7+ runs per over in overs 7-15 (rare — most batsmen score at 5-6 in this phase) are assigned the specific middle-over batting role; and bowlers are evaluated against phase averages — a bowler who concedes 6 RPO in the powerplay is actually below-average for the phase, while 6 RPO in the middle overs is slightly above-average. Video analysis systems now routinely present bowlers' and batsmen's phase-specific data in pre-match briefings, allowing very specific tactical matchup targeting.
Frequently asked questions
Why do powerplay scoring rates sometimes look misleadingly low?
Powerplay scoring rates can look lower than expected (below 7 in T20 cricket) for several reasons: high-quality pace bowling with the new ball limits the batsmen's ability to attack freely — bowlers using swing, seam, and aggressive bouncer strategies in the powerplay often limit the top-order to cautious batting; wickets falling in the powerplay also reduce the effective run rate — the scoring rate calculation includes the overs where wickets fell and runs weren't being scored from balls after dismissals; and team strategy deliberately selects a conservative powerplay approach when facing high-quality opening bowling attacks. A team that scores 45 in the 6-over T20 powerplay has scored at exactly 7.5 RPO, while one that scores 55/3 might appear more aggressive but has actually consumed wickets that damage the remaining 14-over scoring.
What does 'required run rate' tell you about phase performance?
The required run rate (RRR) — runs needed per over to win a run chase — is the primary real-time indicator of phase performance in batting chases. When a chasing team's required run rate climbs above 10 after 30 overs of a 50-over ODI, they've under-performed in the first 30-over period and the death overs must now produce nearly double the sustainable scoring rate. Tracking how the RRR changes across phases tells you exactly when a team lost a chase: if the RRR was 8 at over 20 and 12 at over 30, the team scored only 2 per over (well below required) in overs 20-30 — those 10 overs are where the match was lost. Phase-by-phase RRR analysis is one of the most useful post-match analytical tools for identifying where batting collapses in run chases originate.
Has the introduction of T20 cricket changed ODI scoring phase rates?
Yes — T20 cricket has significantly accelerated ODI scoring across all phases: T20 experience has made batsmen more comfortable playing aggressive shots in the powerplay and death overs, raising average scoring rates in those phases from 5.5 and 7.5 respectively (2005-era averages) to 7.0 and 10+ (2020s averages). Middle-over scoring has also increased but less dramatically — from approximately 4.5 in 2005 to approximately 6 in the 2020s. The ODI first-innings world record progressed from 400+ (2006) to 450+ (2018) to 500+ (2024), with most of the scoring increase coming from powerplay and death-over improvement rather than middle-over acceleration. T20 batting techniques (ramp, scoop, switch-hit) have migrated into ODI cricket, increasing scoring options in the middle overs.