🔗 Share this article

One might speculate 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 inferred from the 14-player squad announcement for the second Ashes Test.

Typically, an identical team list would not be much news, but on this occasion it is, due to the possible movement involving both key players, neither of which has now eventuated.

Cummins is the surprise for his omission, with the team skipper and pace spearhead progressing in rehabilitation from early signs of a stress fracture. The only public acknowledgment was a cursory line with the team announcement stating that Cummins is scheduled to go to Brisbane to continue his preparations.”

Insider reports indicate that this is all situation normal and his recovery remains happily on track, with a probable return to the team in the near future. In theory, Cummins could even join the Test squad in the next few days if he and management so choose. However, something the claims doesn’t add up.

Recalling when Cummins’ scans were cleared in October, 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 close to full intensity with the team during the match. Coach Andrew McDonald said, “Cummins will be fit to bowl in Perth, and fans will wonder 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, presumably as preparation for the day-night Test.

So, why the change of plans, well over a month since Cummins said he would need 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 matches. Should he target Adelaide, it will be over two months since he resumed bowling.

This is acceptable: prognoses can change, medical staff can be conservative, athletes might take care. It’s just peculiar is that during the high-profile Ashes contest in Australia’s calendar, 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 changing nature 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 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 newness of the problem creates concern that they could return in the heat of the next Test.

With Khawaja in the squad logically means he is due to resume opening the batting, even though Travis Head made a record-setting century in Perth. Khawaja wouldn’t be picked as a backup 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 full lineup when announcing selections, and strategies may shift. However, certain decisions are clearer than others, and given the way Travis Head’s explosive performance drew fan interest, it would do no harm to clarify where both batsmen are slotted to play. Some uncertainty in sports is a good thing, but creating it out of the broadly obvious is needless. If you’re in the business of winning over audiences, communication goes a long way.