🔗 Share this article

One might speculate whether the Australian cricket board intentionally chooses to be unclear about team selection or simply has a deficiency in communications, but yet again, the health status of athletes and final team composition must be deduced from the 14-player squad announcement for the Brisbane match.

Typically, an identical team list would not attract attention, but this time it is, thanks to the possible movement involving both key players, neither of which has now eventuated.

Cummins is the surprise for his omission, with the team skipper and pace spearhead deep into his recovery from early signs of a stress fracture. The sole official statement was a cursory line with the team announcement stating that “Pat Cummins will travel to Brisbane to further his training.”

Insider reports indicate that this is all situation normal and his recovery remains happily on track, with a probable return to the side soon. Theoretically, Cummins could even join the Test squad in coming days if he and management so choose. But still, the explanations seem inconsistent.

Recalling when Cummins’ scans were cleared in last month, initiating the countdown on his return to play, all official statements from the player and board schedules indicated he would just be unavailable for the first Test and was scheduled to train at nearly full tilt with the team during the match. Coach Andrew McDonald said, “Cummins will be fit to bowl in Perth, and people will be sitting there questioning why he’s not playing.”

After returning to his home city following the victory in the west, he was observed practicing in the state facilities without any apparent limitations and, importantly, was using a pink Kookaburra ball, what one would assume as readiness for the Brisbane day-night game.

So, why the change of plans, more than four weeks since Cummins said he would need a month to prepare bowling loads, and with six days until the first ball in Brisbane? Not to mention, there are over a week’s break between matches. Should he target Adelaide, it will be more than seven weeks since he resumed bowling.

This is acceptable: prognoses can change, medical staff can be conservative, players can be cautious. It’s just peculiar is that during the most anticipated and closely followed Ashes contest in the season, the board officials seem not to think it necessary to provide updates about the skipper’s condition or the evolving status of either.

If care is the priority with the captain, the opposite applies with Khawaja’s back injury. He had muscle spasms in Perth during brief periods on the field, preventing the regular batsman from playing his role in the match and from making an impact when he eventually batted. Even if his symptoms have subsided, the fact he’d not experienced them before surely leaves some risk that they could return in the heat of the next Test.

His inclusion logically means he is set to return to the top order, even though his replacement scored a historic hundred in his place. Khawaja wouldn’t be picked as a backup or to bat down the order. Once more, there is no confirmation about this, just the selection.

This doesn’t mean that teams should have to give a whole XI when announcing selections, and strategies may shift. But some plans are firmer than others, and considering how Travis Head’s explosive performance captured public attention, it would cause no issue to clarify where those two players are slotted to play. A bit of mystery in life is a good thing, but manufacturing it out of the clearly evident is unnecessary. For those aiming of engaging fans, communication goes a long way.