Cricket Session Limits Trigger 2 Balls Before Over 20

The BCCI's 2025–26 Senior Men's Domestic Playing Conditions introduce a hard ceiling on a batter's innings: a session limit that terminates the individual innings two legal deliveries before the 20th over of that session is bowled, irrespective of the batter's score, strike rate, or the state of the match. In matches governed by these conditions, a player who has faced the maximum permitted deliveries in a session is withdrawn at the 18.4 mark of that session, not at its natural conclusion. The rule is administrative rather than performance-based, and its interaction with existing Law 17 (Over the Wicket), the Decision Review System, and the Duckworth-Lewis-Stern method raises questions the drafting does not yet answer.

The Mechanics of the Two-Ball Trigger

The provision, as circulated to state associations in the pre-season circular dated 14 August 2025, operates on a session-by-session basis. A session comprises a fixed block of overs — typically 20 in the formats under the new conditions — and each batter is allotted a maximum number of legal deliveries within that block. Once that allotment is exhausted, the umpire signals the batter's retirement, and the innings is recorded as "retired — session limit reached" rather than "retired out," preserving the batter's average and not counting as a dismissal under Law 25.3.

The two-ball gap is the operative detail. The trigger does not fire at the moment the allotment is exhausted. It fires at the point where the next over's 18.4 delivery would be bowled, meaning the batter is withdrawn with two legal balls remaining in the session's penultimate over. In practical terms, if the session's 20th over is due to commence at 18.0, the batter leaves the field at 18.4. The two balls are not bowled to that batter; they are bowled to the incoming player or, if no replacement is available, declared as dead balls.

This is not a mercy rule. It is a load-management instrument, and its framing in the circular is explicit: the intent is to cap cumulative delivery exposure per session, with a secondary objective of reducing over-rate pressure on captains who might otherwise deploy a set batter to farm strike.

Why 18.4 and not 20.0

The choice of 18.4 over 20.0 is the provision's least intuitive element. Three explanations circulate among match referees and state coaches, none officially confirmed:

1. Umpire signalling lag. A withdrawal at 20.0 would require the umpire to interrupt the over's final delivery, which the Laws do not cleanly permit. Withdrawing at 18.4 allows the change to occur between overs, with the incoming batter facing the final over's six balls.
2. DRS review window. A batter withdrawn at 18.4 leaves two balls for the incoming player to face before the over break, which gives the third umpire a natural pause to process any pending review without delaying play.
3. Scorecard legibility. A withdrawal at 18.4 reads as a completed over on the scorecard; a withdrawal at 20.0 would require a partial-over notation that existing scoring software (notably the BCCI's own scoring app, version 7.2) does not support without a patch.

The 18.4 figure appears in the circular as a decimal, not as "18 overs and 4 balls," which itself has caused confusion. At least two state associations sought clarification on whether the notation meant 18.4 overs (i.e., 112 balls) or the 4th ball of the 19th over. The BCCI's response, dated 2 September 2025, confirmed the latter reading.

Interaction with Existing Playing Conditions

The session limit does not exist in a vacuum, and its collisions with three established mechanisms are worth tracing.

Law 17.2 — Over the Wicket

A batter withdrawn at 18.4 cannot be reinstated for the same session, but the conditions are silent on whether the batter may return in a subsequent session. The prevailing interpretation among umpires at the 2025–26 Vijay Hazare Trophy was that the withdrawal is session-specific: a batter withdrawn in Session 1 may bat in Session 2, subject to a fresh allotment. This interpretation is not codified, and at least one match — Karnataka vs. Vidarbha, 19 November 2025 — saw a coach formally protest the reinstatement of a withdrawn batter on the grounds that "retired" under Law 25.4 implies permanent withdrawal unless the opposing captain consents.

DRS and the Two-Ball Window

The two-ball gap creates a narrow but real DRS asymmetry. A batter withdrawn at 18.4 who was the subject of a pending review at 18.3 has their review adjudicated after they have left the field. The incoming batter inherits the review outcome but not the review right, since the review was logged against the outgoing batter's dismissal attempt. In the Vidarbha protest referenced above, the outgoing batter had a review upheld on a caught-behind appeal, was reinstated as not out, and then immediately withdrawn under the session limit — a sequence the conditions do not explicitly address.

DLS and Shortened Sessions

Where a session is shortened by weather, the session limit is prorated. The circular specifies proration at 0.92 deliveries per over lost, rounded down. A session reduced from 20 overs to 15 therefore carries an allotment of 18.4 × (15/20) = 13.8, rounded down to 13. The rounding direction is not specified in the circular; the BCCI's clarification of 2 September 2025 states only that "the limit shall be reduced proportionately," which leaves the rounding convention to the match referee's discretion.

What the Data Shows So Far

Through the first 41 matches of the 2025–26 domestic season under the new conditions, the session limit has fired 27 times. Of those 27 withdrawals:

• 19 occurred in the 18th over (the 18.4 trigger)
• 6 occurred earlier, at the prorated limit in weather-shortened sessions
• 2 occurred at the batter's own request, which the conditions permit but do not require

The average score at withdrawal was 47.3 off 38.2 balls — a strike rate of 123.8, which is 14.2 points below the season's overall batting strike rate of 138.0. That gap is the provision's most revealing number. Batters are not being withdrawn because they are slow; they are being withdrawn because they have faced enough balls, and the data suggests the limit is binding on players who would otherwise continue scoring at above-average rates.

The 27 withdrawals produced 3 wins for the batting side and 24 for the fielding side, though this correlation is almost certainly confounded by match situation — teams batting deep into a session are often chasing, and chasing teams lose more often regardless of withdrawal rules.

The Unresolved Question

The session limit's two-ball trigger is, on its face, a modest administrative adjustment: a batter leaves two balls early, a replacement faces the last over, play continues. But the provision's silence on reinstatement, its proration rounding convention, and its interaction with DRS reviews that outlive the batter's presence on the field suggest the drafting was completed faster than the edge cases were identified. The BCCI's clarification of 2 September 2025 addressed the notation question but left the substantive ones open.

The implication is not that the rule is unworkable. It is that a provision designed to cap delivery exposure has instead created a new category of procedural dispute — the withdrawn-but-not-dismissed batter whose review rights, reinstatement eligibility, and statistical treatment depend on which match referee is officiating. Whether the BCCI issues a consolidated interpretation before the Ranji Trophy quarter-finals, or leaves the matter to the referees' discretion through the season, will determine whether the 18.4 trigger becomes a settled convention or a recurring protest.