History
Origins and Early Development
The concept of penalizing delays by incoming batsmen emerged in the early codified laws of cricket during the 18th century, primarily to curb deliberate time-wasting and ensure the game's progression in an era of multi-day matches on uncovered pitches susceptible to weather interruptions. Although the specific dismissal mode known as "timed out" was not formalized until later, precursor rules addressed the issue through team-level penalties rather than individual outs. In the 1774 code of laws, umpires were instructed to "allow two minutes for each man to come in" following the fall of a wicket, with an additional fifteen minutes between innings; failure to comply after the umpire called "Play" resulted in the defaulting side losing the match.[7] This provision, without numbering in the early informal codes, underscored umpires' discretion in managing delays, reflecting the need for efficiency in village greens and early county fixtures where logistics like horse-drawn travel could already prolong proceedings. The rule was refined in subsequent revisions, with the 1884 code designating it as Law 45, maintaining the two-minute allowance for the incoming striker while explicitly stating that umpires "shall allow two minutes for each striker to come in" to expedite play and deter stalling tactics.[8] The emphasis on umpires' authority highlighted the era's challenges, including longer formats without modern protections, where even minor delays could significantly impact match outcomes. Despite these stipulations, no verified instances of the rule's enforcement appear in records before 1900, attributable to its informal application and the slower pace of early cricket, where travel constraints and rudimentary organization often led to natural pauses rather than deliberate infractions.[6] The current MCC Law 40 extends this to a three-minute limit for individual dismissal, evolving the original intent to penalize wilful tardiness. The first recorded instance of a timed out dismissal occurred in 1987-88, when South African batter Andrew Jordaan was timed out in a first-class match for Eastern Province against Transvaal due to travel delays from flooded roads.[6]Evolution and Rarity Prior to 2023
The timed out dismissal was formally introduced as a specific method in the 1980 revision of the MCC Laws of Cricket, stipulating a two-minute limit for the incoming batter to be ready to face the next ball after the fall of a wicket.[9] This provision aimed to prevent deliberate time-wasting, building on earlier informal practices where umpires could rule a batter absent without formal dismissal status. In the 2000 code revision, the time limit was extended to three minutes to accommodate evolving aspects of the game, such as more complex protective equipment and strategic fielding rearrangements that could delay the incoming batter's arrival.[9] Prior to 2023, the rule's application remained exceedingly rare, with umpires showing reluctance to enforce it due to the "Spirit of Cricket" preamble introduced in the 2000 MCC Laws, which emphasized fair play and mutual respect over strict adherence to technicalities.[10] This cultural norm, reinforced by a preference for issuing warnings rather than dismissals, aligned with cricket's tradition of sportsmanship, where appeals for timed out were viewed as contrary to the game's ethos. Additionally, logistical challenges in pre-1980 cricket, including inconsistent timing mechanisms and the absence of standardized stopwatches at many venues, contributed to non-enforcement, as umpires relied on visual estimates rather than precise measurements.[4] Statistics underscore this infrequency: before 2023, only six confirmed timed out dismissals occurred worldwide, all in first-class cricket spanning 1987 to 2017, with zero instances in international matches across Test, ODI, or T20I formats.[6] These cases typically involved exceptional circumstances, such as travel delays or personal issues, rather than routine delays.Legal Framework
MCC Law 40
Law 40 of the Marylebone Cricket Club's (MCC) Laws of Cricket governs the dismissal method known as "timed out," establishing a strict timeline for an incoming batter to be ready after a wicket falls or a batter retires.[1] The precise wording of the law, as per the 2017 Code (3rd Edition 2022), is as follows:40.1 Out Timed outThis provision ensures the game progresses without undue delays, with the 3-minute window beginning at the moment the umpire signals the dismissal of the previous batter or announces the retirement.[1] The enforcement of Law 40 requires an appeal from the fielding side, typically initiated by the captain or a fielder asking the umpire, "How's that?" or a similar phrase; without such an appeal, the dismissal cannot be given, even if the time limit expires.[1] If the appeal is upheld and the batter is given out timed out, the decision is final, with no provision for the batter to return or for the innings to resume from that point.[11] Umpires are responsible for accurately timing the interval, starting the clock immediately upon the wicket's fall or retirement call, and they may account for brief, justifiable delays such as those caused by injury or equipment retrieval only if deemed reasonable under the circumstances.[1] An key exception suspends the 3-minute countdown if the umpire calls "Time," such as during intervals or other official breaks, resuming only when play is ready to restart.[11] Law 40 applies universally across all formats of the game—Test, One-Day International, and T20—unless specific playing conditions approved by governing bodies like the International Cricket Council explicitly modify the timing or procedures.[1]
40.1.1 After the fall of a wicket or the retirement of a batter, the incoming batter must, unless Time has been called, be ready to receive the ball, or for the other batter to be ready to receive the next ball, within 3 minutes of the fall of the wicket or retirement. If this requirement is not met, the incoming batter will be out, Timed out.
40.1.2 In the event of an extended delay in which no batter comes to the wicket, the umpires shall adopt the procedure of Law 16.3 (Umpires awarding a match). For the purpose of this Law, either umpire shall call and signal ‘Time’ after the 3 minutes is up.[11]
Variations in Playing Conditions
In international limited-overs cricket, the International Cricket Council (ICC) modifies the timed out rule under MCC Law 40 to enforce stricter time limits aimed at minimizing delays. For One Day Internationals (ODIs), the playing conditions stipulate a 2-minute window for the incoming batter to be ready to receive the ball after a dismissal or retirement, as applied during the 2023 Men's ODI World Cup.[12][4] This reduction from the MCC's default promotes faster play in 50-over matches, with umpires required to enforce it upon appeal from the fielding captain. For Twenty20 Internationals (T20Is), the ICC further shortens the limit to 90 seconds to suit the format's emphasis on pace, a standard implemented since the early 2010s and reaffirmed in updates to the playing conditions.[12][13] This adjustment ensures minimal interruption in the short 20-over game, where appeals for timed out must still be made explicitly. Domestic competitions often adapt these international standards or revert to the MCC baseline. In the Indian Premier League (IPL), a major T20 league, the timed out limit is set at 2 minutes to balance speed with the format's demands, while first-class matches typically default to the MCC's 3-minute allowance unless tournament-specific conditions specify otherwise.[14][1] Following the 2023 ODI World Cup, the Marylebone Cricket Club (MCC) issued a clarification on interpreting timed out in cases of equipment delays, stating that such issues do not excuse the dismissal if not communicated to umpires within the applicable time limit, though extraordinary circumstances may allow discretionary extensions under umpire authority.[15]| Format/Organization | Time Limit | Appeal Requirement |
|---|---|---|
| MCC (default, e.g., first-class) | 3 minutes | Yes, by fielding side captain |
| ICC ODI | 2 minutes | Yes, by fielding side captain |
| ICC T20I | 1.5 minutes | Yes, by fielding side captain |