🔗 Share this article

You could wonder whether Cricket Australia intentionally chooses to be unclear about player availability or simply has a deficiency in public relations, but yet again, the health status of athletes and the makeup of the XI must be deduced from the selection in the larger squad for the Brisbane match.

Typically, an unchanged squad would not be much news, but on this occasion it is, due to the possible movement involving both key players, neither of which has come to pass.

The unexpected element is Cummins for his omission, with the team skipper and pace spearhead progressing in rehabilitation from initial symptoms of a back injury. The sole official statement was a cursory line with the squad release 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 likely addition to the side soon. In theory, he might still be added to the Brisbane squad in the next few days if deemed fit by staff. But still, the explanations seem inconsistent.

Recalling when his medical tests came back positive in last month, initiating the countdown on his return to play, all public commentary from the bowler himself and board schedules indicated he would just be unavailable for the initial match and was scheduled to train at close to full intensity with the squad in Perth. Coach Andrew McDonald said, “He will be up and bowling in Perth, and people will be sitting there questioning why he’s not playing.”

After returning to Sydney following the team’s raucous two-day win, he was observed practicing in the New South Wales nets without any visible restrictions and, importantly, was using a pink Kookaburra ball, presumably as readiness for the Brisbane day-night game.

So, why the change of plans, more than four weeks since he indicated requiring four weeks to build up his workload, and with less than a week to go in Brisbane? 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 resumed bowling.

That in itself is fine: medical opinions evolve, medical staff can be conservative, athletes might take care. It’s just peculiar is that during the most anticipated and closely followed Ashes contest in the season, the governing body’s representatives don’t appear to consider it reasonable to share updates about the skipper’s condition or the evolving status of either.

And if caution is the watchword with the captain, the reverse is true with Khawaja’s back injury. He had spasms flare up in the first Test during brief periods on the field, preventing the regular batsman from playing his role in both innings and from having any influence when he did bat down the order. Even if his symptoms have subsided, the newness of the problem surely leaves some risk that they could return in the pressure of Brisbane.

With Khawaja in the squad suggests he is set to return to the top order, even though his replacement scored a historic hundred in Perth. He wouldn’t be selected as a reserve or to play lower. Once more, there is no official information 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 given the way Head’s whirlwind captured public attention, it would do no harm to clarify where those two players are due to bat. Some uncertainty in life is a good thing, but manufacturing it out of the broadly obvious is needless. If you’re in the business of engaging fans, transparency is crucial.