🔗 Share this article

One might speculate whether the Australian cricket board deliberately prefers to be opaque about player availability or simply lacks effectiveness in communications, but once again, the health status of athletes and final team composition must be deduced from the selection in the larger squad for the second Ashes Test.

Typically, an identical team list would not be much news, but on this occasion it is, due to the anticipated changes involving both key players, neither of which has come to pass.

The unexpected element is Cummins for not being included, 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 squad release stating that “Pat Cummins will travel to Brisbane to further his training.”

Suggestions from within CA indicate that this is all situation normal and his recovery remains happily on track, with a likely addition to the side soon. In theory, Cummins could even join the Test squad in coming days if he and management so choose. However, something the claims doesn’t add up.

Going back to 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 suggested he would just be unavailable for the initial match and was scheduled to train at nearly full tilt with the squad in Perth. The head coach remarked, “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 seen bowling in the state facilities without any apparent limitations 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 Cummins said he would need four weeks to build up bowling loads, 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. If the latter is Cummins’ destination, it will be more than seven weeks 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 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.

If care is the priority with the captain, the reverse is true with Khawaja’s back injury. He had spasms flare up in the first Test during two paltry fielding innings, preventing the regular batsman from playing his role in the match and from making an impact when he eventually batted. Though he may have improved, 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 the top order, even though his replacement scored a historic hundred in his place. He wouldn’t be selected as a reserve or to play lower. Once more, there is no confirmation about this, only the squad listing.

This doesn’t mean that sides must reveal a whole XI when picking their squad, 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 those two players are due to bat. A bit of mystery in life is a good thing, but manufacturing it out of the broadly obvious is unnecessary. For those aiming of engaging fans, communication goes a long way.