5 of the most questionable declarations in Test cricket history

Archie Starkey 15 Dec 2024

Michael Clarke was renowned for putting the team before a particular player when declaring in Test cricket.

The captain’s impact on the team in Test cricket is unlike anything you’ll see in other sports.

As a skipper, you dictate your team’s tactics and approach while out on the field and act as the middleman between the coaching setup and the rest of the players.

Test cricket can be a game of cat and mouse – a lot of trial and error if you like.

Every great decision the captain makes is joyfully celebrated, but a poor one is equally scrutinised.

Captains’ calls can define their legacy and often overshadow the individual’s achievements.

One of the toughest to make as a captain is the timing of a successful declaration to put the team in the best position to get a result.

A hard decision, sometimes a gamble, can go either way, such are the fine margins in a five-day Test match.

Here, we take a look at 5 times the captain may have got the declaration wrong.

1. Don Bradman, Australia vs India, 1947

He was a flawless leader who was seldom questioned, with his team’s actions speaking louder than words.

However, Bradman’s declaration leaving India a target of 361 nearly fell sour, with the opposition just 14 runs shy of their target and the match ending in a draw.

A little bit close for comfort for the ever-dependable Bradman.

2. Michael Atherton, England vs South Africa, 1995

With wickets in the sheds, England skipper Atherton decided to declare on 351/5, leaving the Proteas a target of 204 runs with a generous 36 overs left in the day in Johannesburg.

The captain’s strategy was questioned, with him presumably thinking the guests would lock up shop and settle for a draw.

But instead, they came out firing and chased the total with two balls to spare.

3. Andrew Strauss, England vs Australia, 2009

With the weight of an Ashes Test at Lord’s on the line for England, Strauss declared on 311/6, leaving a sizeable target of 522.

Australian skipper and wicketkeeper Michael Clarke and Brad Haddin began to take control and had everyone in London sitting nervously in their seats.

The home side managed to get over the line but by only 115 runs – a bit too close for comfort.

4. Graeme Smith, South Africa vs Australia 2006

The South African declared in Johannesburg, setting a target of only 287 on a surface that was very much favouring the batters.

The visitors had no trouble as they surged to a humiliating seven-wicket victory.

With the strength of Australia‘s batting and the nature of the pitch, this was one of the most questioned calls in Test cricket history,

5. Michael Clarke, Australia vs Sri Lanka 2012

If a player is nearing a milestone such as a century, the captain usually waits until after this before calling the declaration.

However, with Phil Hughes on a gritty 86 against Sri Lanka, skipper Clarke wasn’t as courteous.

The Australians went on to win the game in Hobart, but the captain’s decision not to let Hughes chase the 14 runs he needed for a first test century since returning to the team has long since been questioned.