IND vs AUS 3rd Test: Has Rohit Sharma made the right choice by opting to bowl first at The Gabba?

Has Rohit Sharma made the right choice by opting to bowl first at The Gabba? (AFP Photo)

Just 13.2 overs are a small sample size to judge any cricketing decision. India won the toss in the third-Test of the ongoing series against Australia and chose to bowl first. On a rain-truncated day, the hosts moved to 28 for no loss when the skies opened up again – there was a drizzle before the downpour – and the day was done.

Usman Khawaja and Nathan McSweeney looked mostly untroubled against the new ball, with the former scoring 19 not out and the latter remaining unbeaten on four. Jasprit Bumrah, and especially Mohammed Siraj, searched for the right length in their first spells. Akash Deep, coming in as first change, was impressive. He swung the ball and nipped a few into the right-hander.

The question, however, is whether Rohit Sharma has made the right call by inserting the opponents? Overhead conditions, a thick cloud cover, and a green pitch prompted the India captain to bowl first. Also, data supported his decision. The team bowling first has won six of the last seven Tests at the Gabba. Mind, India’s most memorable Test win, in 2020-21, came when they batted last at this venue. So far so good.

India vs Australia 3rd Test, Brisbane weather forecast: Will rain play spoilsport on Day 2? Revised match timings in IST

But did Rohit’s decision reek of some uncertainty as well? A couple of months ago, in almost similar conditions in Bangalore, he had elected to bat first against New Zealand after winning the toss. They were bundled out for 46 in their first innings. The skipper had owned up his mistake, confessing about misreading the conditions.

“Clearly, misjudgement of the pitch. Obviously, I didn’t read the pitch well enough, and we sit in that situation today,” he had said. The Bangalore Test, though, wasn’t a case in isolation.

First-innings batting has become India’s bugbear of late. Over the last five Tests, they haven’t reached 300 in their first innings on a single occasion, getting bowled out for less than 200 four times. This is a batting unit which collectively is bereft of runs and short of confidence. Rohit decided to bat first after winning the toss in the pink-ball Test in Adelaide. A batting implosion followed. In Brisbane, he kept boldness at arm’s length.

“Yeah, a little bit overcast as well and there’s a little bit of grass and (the pitch) looks a little soft. So we want to try and make the best use of the conditions,” Rohit said at the toss.

Traditionally, though, the Gabba pitch quickens up on Day 2 and 3. Also, in Australia, visiting teams have won only eight times after sending the hosts in. Clearly, there’s also a downside to the bowl-first decision.

Two changes

India made two changes by bringing on Akash and Ravindra Jadeja for Harshit Rana and Ravichandran Ashwin respectively. Rana made an impressive debut in Perth, but the youngster wasn’t required to bowl long spells in the first Test. In Adelaide, however, Rana looked to be running out of steam and losing pace during his later spells. A course correction was due.

With regards to Jadeja, he is arguably the world’s best all-rounder and should have played in the first two Tests as well. As Sunil Gavaskar says, a team should always play its best players irrespective of the conditions. In seaming conditions, Jadeja’s role is mainly of a batting all-rounder. He has scored runs everywhere and remains the best outfielder in this Indian side. His inclusion has come a couple of Tests too late, but better late than never.