Declaration and forfeiture
In the sport of cricket, a declaration occurs when a captain declares their team's innings closed and a forfeiture occurs when a captain chooses to forfeit an innings without batting. Declaration and forfeiture are covered in Law 15 of the Laws of Cricket. This concept applies only to matches in which each team is scheduled to bat in two innings; Law 15 specifically does not apply in any form of limited overs cricket.
Declaration
[edit]The captain of the batting side may declare an innings closed, when the ball is dead, at any time during a match.[1] Usually this is because the captain thinks their team has already scored enough runs to win the match and does not wish to consume any further time batting which would make it easier for the opponents to play out for a draw. Tactical declarations are sometimes used in other circumstances.
In May 1889, the laws of cricket were revised to allow for declarations but on condition they only took place on the final day of the match.[2][3] The first captain to declare in English first-class cricket was Charles Wright in 1890. In a game against Kent at the Bat and Ball Ground in Gravesend, Wright declared Nottinghamshire's second innings closed on 157 for 5 to set Kent a target of 231 to win. The tactic nearly paid off as the game was drawn with Kent on 98 for 9 and Nottinghamshire requiring one more wicket to win.[4]
Frank May proposed at the Annual General Meeting of the Marylebone Cricket Club on 2 May 1906 that in a two-day match, the captain of the batting side has power to declare their innings closed at any time, but such declaration may not be made on the first day later than one hour and forty minutes before the hour of drawing stumps. After some discussion the resolution was passed.[5]
Before declarations were made legal the batsmen of a team that wanted to get the other team to bat again would have to deliberately get themselves out.
Tactical considerations
[edit]The basic tactical idea of declaration is that a team declares because they feel they have enough runs to produce a positive result in the current match situation. The specifics of when to declare will come down to which innings of the match is being played, the time when the declaration occurs and how much of the match is left to play. A common example of timing a declaration is when the declaration comes near the end of play for the day. A team who have batted through the day may decide that the extra runs on offer are worth less than the opportunity to bowl at a team who are tired from standing in the field all day.
A team in the first of the four innings can have to make a tactical choice between continuing to bat in their first innings and declaring. The existence of the follow-on law makes amassing a very large lead worthwhile as it can prevent the game from being lost due to how long it would take a team to equalise the scores even if they avoid being bowled out. Declaring with a large total and many wickets in hand can be a choice that backfires if the team batting second go on to make their own very large total. A significant amount of the highest innings totals in Test cricket have come from the team batting second and some have gone on to win those games.
Weather conditions can also make a team decide to declare. If rain may put an end to a match prematurely and there is an incentive to product a result it may make a team declare on what would normally be a low total as they try to win the shortened match. The Sticky wicket that existed before covered pitches could induce very low total declarations. In the First Test of the 1950–51 Ashes series.[6] As recorded in The Ashes' Strangest Moments, as the pitch at the Gabba began to dry, England declared their first innings at just 68/7, in order to exploit the conditions.[6] Australia were even more extreme, declaring at 32/7.[6] "...the ball proceeded to perform capers all against the laws of gravitation, and there came the craziest day's cricket imaginable, with twenty wickets falling for 130 runs and two declarations that must surely be unique in the annals of Test cricket."[7]
A team batting in the 3rd innings of the match can declare in order to attempt to bowl out their opponents in a short amount of time rather than allowing the game to meander to a draw. In their 1984 tour of Sri Lanka, New Zealand beat the hosts by declaring to set a target of 263 runs shortly after lunch on day 5. Arjuna Ranatunga scored 51 but the rest of the team collapsed around him and shortly after his caught & bowled exit off John Bracewell it was Stephen Boock who took the final wicket with Sri Lanka on 97 from 28 overs. In games where innings have taken a significant amount of time, or where weather has delayed play there are cases of a "draw by agreement" that ends the game following a declaration of the third innings.
The fact that a team ends their innings and gives up the chance to score mores runs can make declarations a bad decision in hindsight. In the 2nd Test of the 2012–13 Border–Gavaskar Trophy the Australian side declared so they could bowl at India for 3 overs at the end of the first day rather than see if their final pair of batsmen could score additional runs. India went on to score 503 in their only innings of the game as Australia collapsed all out for 131 in their 2nd innings, losing the game by an innings & 135 runs.
In 2017 England declared while hosting the West Indies in the 2nd test, at 490/8d in their 2nd innings. This left the West Indies a target of 322 to win from 96 overs. The opening batters navigated the 6 over spell before stumps and on the final day Kraigg Brathwaite scored 95 & Shai Hope 118 not out to give his side an unlikely 5 wicket win 6 overs before the close of play.
During the English tour of South Africa in 1948/49, the 5th test ended with an English victory. South Africa declared on 3/187 to give England a target of 172. The English achieved that figure in their 24th over for the loss of 7 wickets. Jack Crapp hit 10 runs off 3 balls to secure the win which came one minute before the 4 day game was due to finish.[8]
There have been occasions where a team have declared in both their innings and lost. South Africa faced Australia in Sydney in 2006, South Africa scored 451/9d and 194/6d. Australia scored 359 in their first innings and were set 287 runs for victory in their second. Matthew Hayden & Ricky Ponting put up a 150 run partnership for the 3rd wicket then Ponting & Brad Hodge secured the win in the 61st over as Ponting finished not out on 143. In 1968 Garry Sobers and his West Indian team declared on 526/7 and 92/2 to set England 215 to win in 3 hours, that the English did through half-centuries to Geoffrey Boycott and Colin Cowdrey to win the game with 7 wickets & 3 minutes to spare.
Forfeiture
[edit]Under the current Laws, a captain may forfeit either of their side's innings.[1] A forfeited innings shall be considered as a completed innings. Usually this happens in shorter competitive two-innings matches, where captains need to agree with each other how to set up the match so that there is a reasonable chance of a result. Winning a game gains a team considerably more points than drawing it, so captains are often willing to risk giving the opposition an opportunity to win that they otherwise would not have had as long as they are getting a similar opportunity in return.
In August 2020, in a rain-affected match between Durham and Leicestershire in the 2020 Bob Willis Trophy, both teams agreed to forfeit an innings in an attempt to produce a result.[9]
Test cricket
[edit]Only one innings has been voluntarily forfeited in Test cricket. This was on 18 January 2000 at Centurion, South Africa, in the fifth and final Test between South Africa and England. South Africa had already won the series, as they were up 2–0 (with 2 matches drawn) after the first four matches. After South Africa scored 155 for 6 on the first day, rain washed out the next three days. With only one day remaining, the match was set for a certain draw.
That was until Hansie Cronje, the South African captain, entered into a deal with his English counterpart, Nasser Hussain, that South Africa would continue batting till they reached about 250 and then declare. England and then South Africa would then both forfeit an innings, leaving England approximately 250 to win (in the event the target was 249). At that time, the laws only permitted a side to forfeit its second innings,[10] so England's first innings was treated as having been declared at 0 for 0 after 0 balls. England went on to score 251 for 8 and win by 2 wickets.[11]
It later emerged that Cronje had been approached by a bookmaker, and asked to ensure the game would end with a positive result.[12] Nasser Hussain and the England team were not aware of this at the time, taking the South African request at face value.[13]
References
[edit]- ^ a b "Law 15 – Declaration and forfeiture". MCC. Archived from the original on 1 October 2017. Retrieved 29 September 2017.
- ^ "The Marylebone Club". Cricket: A Weekly Record of the Game. Vol. VIII. 2 May 1889. p. 101. Retrieved 4 September 2024 – via ACS.
- ^ "Laws of Cricket - 1889 Code - As Revised in 1889". ACS. Retrieved 4 September 2024.
- ^ "Scorecard of the game in which Wright became the first captain to declare an innings closed". Cricketarchive.com. Archived from the original on 1 July 2017. Retrieved 9 August 2013.
- ^ "Wisden - Obitauries in 1907". ESPNcricinfo. 30 November 2005. Retrieved 10 May 2021.
- ^ a b c Baldwin, Mark (1 January 2005). The Ashes' Strangest Moments: Extraordinary But True Tales from Over a Century of the Ashes. Franz Steiner Verlag. ISBN 9781861058638. Archived from the original on 29 April 2022. Retrieved 22 March 2017 – via Google Books.
- ^ John Kay, Ashes to Hassett, A review of the M.C.C. tour of Australia, 1950–51, John Sherratt & Son, 1951 p129
- ^ https://www.espncricinfo.com/story/defeated-after-declaring-384021
- ^ "Durham and Leicestershire Forfeit An Innings Each To Set Up A Result". NDTV. Archived from the original on 18 August 2020. Retrieved 18 August 2020.
- ^ MCC (1980). "Law 14 – Declarations". Laws of Cricket 1980 Code. Cricinfo. Archived from the original on 17 November 2020. Retrieved 20 February 2011.
- ^ "Scorecard of 2000 RSA vs ENG Centurion Match in which Cronje & Hussein forfeited innings". Aus.cricinfo.com. Archived from the original on 30 January 2006. Retrieved 9 August 2013.
- ^ Stone, Simon (16 June 2000). "Cronje admits $100,000 in bribes". The Independent. London. Archived from the original on 1 September 2010. Retrieved 22 March 2010.
- ^ Aggarwal, Shubh (18 January 2023). "Nasser Hussain's sweetest memory that turned out to be a scam". Cricket.com. Archived from the original on 5 December 2023. Retrieved 30 September 2024.