All Out vs Declared: The Two Ways a Cricket Innings Ends
The two ways a batting innings concludes in Test cricket — being bowled all-out (all 10 wickets taken) vs declaring (the captain voluntarily ends the innings with wickets remaining), when declaration is used and why, the risk calculation behind declarations, records for the latest declarations (most runs lost by declaring team that still won), and why limited-overs cricket has no declaration option.
All Out: The Default Ending
An innings ends 'all out' when 10 of the 11 batting side players have been dismissed — the 11th batsman has no partner and the innings is complete. The score is recorded as the number of runs scored (e.g., '240 all out' or simply '240'). All-out endings happen when the bowling side takes 10 wickets before the batting side voluntarily ends their innings. All-out totals in Test cricket can range from low disasters (England's 45 all out at Cape Town 2023 is one of the lowest recent Test totals) to huge accumulations (Sri Lanka's 952/6 declared ended voluntarily rather than all-out — but teams have batted all-out for 800+). In limited-overs cricket, all out means the batting side used all 10 wickets within the overs allocated.
The Declaration: A Captain's Choice
A declaration (denoted by a 'd' next to the score: '450/6d') is available only in multi-day cricket (Tests and first-class matches) — the batting captain can at any point voluntarily close the innings and send the opposition to bat, regardless of wickets remaining. The primary motivation: if the batting side has scored enough runs to feel confident of winning, continuing to bat only wastes time that could be used to bowl the opposition out. The declaration decision trades potential additional runs (from the remaining batsmen) against bowling time (needed to take 10 wickets of the opposition). A premature declaration that sets too small a target allows the opposition to win; an excessively cautious declaration that sets too large a target leaves insufficient bowling time and results in a draw.
The Calculation Behind Declaring
The declaration calculation: how many runs is a 'safe' total to set, and how many overs will remain to bowl the opposition? The general Test cricket guideline is that a lead of approximately 250-350 runs with 90+ overs remaining gives the bowling side a good chance of taking 10 wickets (assuming a decent pitch); a lead of 150-200 runs with 50 overs remaining requires excellent bowling; and a lead of under 100 runs with 30 overs remaining is usually insufficient to win. These are rough parameters — pitch conditions, team bowling strength, and the psychological state of the match all affect the calculation. Some of cricket's most dramatic moments have come from 'sporting declarations' where a captain set what appeared to be a too-generous target that their team then failed to take wickets against, resulting in an unexpected loss.
Frequently asked questions
Can a team declare in limited-overs cricket?
No — declaration is not permitted in ODI or T20 cricket. In limited-overs cricket, the innings ends either when all overs are bowled or when all 10 wickets fall — whichever comes first. The batting side has an incentive to continue batting (more overs = more scoring opportunity) that makes voluntary early closure never strategic. In limited-overs cricket, even a team that has already scored an overwhelming total will continue batting if overs and wickets remain — there is no benefit to declaring (no bowling time saved, since the opposition's over allocation is fixed regardless). The declaration is a feature unique to multi-day cricket where bowling time is the scarce resource that makes voluntary innings closure strategically valuable.
What is a forfeiture and how does it differ from a declaration?
A forfeiture (also called 'forfeiting an innings') is when a team voluntarily forfeits an entire innings they have not yet started — effectively conceding that innings and immediately inviting the opposition to bat. This allows a team in an unusual match situation (typically a county or first-class match where rain has disrupted the schedule) to create an artificial chase that produces a result rather than a draw. A declaration ends the current innings before all wickets fall; a forfeiture skips an entire upcoming innings. Forfeitures are rare in international cricket but have been used in county cricket when teams need to generate results for league points. In Tests, forfeitures are extremely unusual — no Test match result has been determined by a forfeiture in the ICC era.
Is it possible to declare with 0 wickets down?
Technically yes — the Laws allow declaration at any time after the innings begins, including with 0 wickets down. In practice, declaring with 0 wickets down (after the openers have batted for some time) would only make sense if the team had already scored a very large total and any additional runs were unnecessary. This almost never happens because even very large totals (600, 700) use the full potential of the batting order — the captain wants to maximise the lead as much as possible given the bowling time available, which means batting until the optimal point rather than closing early when wickets are unnecessarily available. The 0-wickets-down declaration is essentially a theoretical possibility rather than a practical cricket situation.