🔗 Share this article

You could wonder whether Cricket Australia deliberately prefers to be unclear about team selection or simply lacks effectiveness in public relations, but once again, the health status of athletes and the makeup of the XI must be inferred from the selection in the larger squad for the second Ashes Test.

Normally, an identical team list would not be much news, but this time it is, due to the possible movement involving Pat Cummins and Usman Khawaja, neither of which has come to pass.

Cummins is the surprise for not being included, with the regular captain and pace spearhead progressing in rehabilitation from early signs of a back injury. The only public acknowledgment was a brief mention with the squad release stating that Cummins is scheduled to go to Brisbane to further his training.”

Suggestions from within CA support the view that everything is on track and his recovery remains happily on track, with a probable return to the side soon. In theory, he might still be added to the Brisbane squad in coming days if deemed fit by staff. But still, the explanations seem inconsistent.

Going back to when his medical tests came back positive in October, initiating the countdown on his buildup to match fitness, all official statements from the bowler himself and board schedules indicated he would just be unavailable for the initial match and was set to practice at close to full intensity with the squad in Perth. Coach Andrew McDonald said, “Cummins will be fit to bowl in Perth, and fans will wonder why he’s not playing.”

Once Cummins got back to Sydney following the victory in the west, he was seen bowling in the state facilities without any visible restrictions and, importantly, was training with a pink ball, what one would assume as readiness for the Brisbane day-night game.

What prompted the shift, well over a month since Cummins said he would need a month to prepare bowling loads, and with six days until the first ball in the Gabba? Not to mention, there are eight more days of rest between Brisbane and the third Test. Should he target Adelaide, it will be over two months since he started training again.

That in itself is fine: medical opinions evolve, doctors may be cautious, players can be cautious. What’s strange is that during the high-profile Test series in the season, the governing body’s representatives don’t appear to consider it reasonable to share any information about the captain’s fitness and availability or the evolving status of either.

And if caution is the watchword with the captain, the opposite applies with the opener’s issue. 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 having any influence when he did bat down the order. Even if his symptoms have subsided, the newness of the problem creates concern that they might recur in the heat of the next Test.

His inclusion logically means he is due to resume the top order, even though his replacement scored a historic hundred in his place. He wouldn’t be selected as a reserve or to bat down the order. But again, there is no confirmation about this, only the squad listing.

This doesn’t mean that sides must reveal a whole XI when announcing selections, and strategies may shift. However, certain decisions are clearer than others, and considering how Travis Head’s explosive performance captured public attention, it would cause no issue to confirm where those two players are due to bat. Some uncertainty in sports is a good thing, but creating it out of the clearly evident is needless. For those aiming of engaging fans, communication goes a long way.