🔗 Share this article

You could wonder whether the Australian cricket board intentionally chooses to be opaque about team selection or simply has a deficiency in communications, but yet again, the health status of athletes and the makeup of the XI must be deduced from the 14-player squad announcement for the Brisbane match.

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

Cummins is the surprise for his omission, with the team skipper and pace spearhead deep into his recovery from initial symptoms of a stress fracture. The only public acknowledgment was a brief mention with the team announcement stating that Cummins is scheduled to go to Brisbane to further his training.”

Suggestions from within CA support the view that this is all situation normal and his healing is proceeding well, with a likely addition to the side soon. Theoretically, Cummins could even join the Test squad in the next few days if deemed fit by staff. But still, something the claims doesn’t add up.

Recalling when Cummins’ scans were cleared in last month, starting the clock on his return to play, all public commentary from the bowler himself and board schedules suggested he would just be unavailable for the first Test and was set to practice at nearly full tilt with the squad in Perth. Coach Andrew McDonald said, “He will be up and bowling in Perth, and fans will wonder why he’s not playing.”

Once Cummins got back to his home city following the victory in the west, he was observed practicing in the state facilities without any visible restrictions and, most notably, was training with a pink ball, what one would assume as readiness for the Brisbane day-night game.

What prompted the shift, more than four weeks since he indicated requiring four weeks to build up his workload, and with six days until the first ball in Brisbane? Additionally, there are eight more days of rest between matches. If the latter is Cummins’ destination, it will be over two months since he started training again.

That in itself is fine: prognoses can change, doctors may be cautious, players can be cautious. It’s just peculiar is that during the most anticipated and closely followed Ashes contest in Australia’s calendar, the governing body’s representatives don’t appear to consider it reasonable to share updates about the skipper’s condition or the changing nature of either.

If care is the priority with the captain, the reverse is true with Khawaja’s back injury. He had muscle spasms in Perth during brief periods on the field, keeping Australia’s usual opener from doing so 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 creates concern that they might recur in the heat of the next Test.

With Khawaja in the squad suggests he is due to resume the top order, even though Travis Head made a record-setting century in his place. Khawaja wouldn’t be picked as a backup or to bat down the order. But again, there is no confirmation about this, just the selection.

It isn’t necessary that teams should have to give a whole XI when announcing selections, and strategies may shift. But some plans are firmer than others, and given the way Travis Head’s explosive performance captured public attention, it would cause no issue to confirm where those two players are slotted to play. A bit of mystery in sports is a good thing, but creating it out of the clearly evident is unnecessary. If you’re in the business of engaging fans, transparency is crucial.