🔗 Share this article

One might speculate whether Cricket Australia intentionally chooses to be opaque about team selection or simply lacks effectiveness in communications, but once again, the fitness of players and final team composition must be inferred from the selection in the larger squad for the Brisbane match.

Typically, an identical team list would not attract attention, but this time it is, thanks to the possible movement involving Pat Cummins and Usman Khawaja, none of which has come to pass.

Cummins is the surprise for his omission, with the team skipper and pace spearhead deep into his recovery from initial symptoms of a back injury. 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 likely addition to the team in the near future. In theory, Cummins could even join the Test squad in coming days if deemed fit by staff. However, the explanations seem inconsistent.

Recalling when his medical tests came back positive in last month, starting the clock on his buildup to match fitness, all public commentary from the player and timelines from CA 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, “He will be up and bowling in Perth, and people will be sitting there questioning why he’s not playing.”

After returning to his home city following the team’s raucous two-day win, 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.

What prompted the shift, well over a month since he indicated requiring four weeks to build up his workload, and with less than a week to go in the Gabba? Additionally, there are over a week’s break 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, doctors may be cautious, players can be cautious. It’s just peculiar is that during the high-profile Ashes contest in the season, the board officials seem not to think it reasonable to share updates about the skipper’s condition or the evolving status 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 two paltry fielding innings, preventing the regular batsman from playing his role in both innings 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 pressure of Brisbane.

With Khawaja in the squad logically means he is due to resume opening the batting, even though his replacement scored a historic hundred in Perth. He wouldn’t be selected as a backup 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 considering how Travis Head’s explosive performance captured public attention, it would cause no issue to clarify where both batsmen are slotted to play. Some uncertainty in life is a positive, but manufacturing it out of the broadly obvious is unnecessary. If you’re in the business of engaging fans, transparency is crucial.