🔗 Share this article

You could wonder whether Cricket Australia intentionally chooses to be unclear about player availability or simply lacks effectiveness in public relations, but once again, the fitness of players and the makeup of the XI must be deduced from the 14-player squad announcement for the second Ashes Test.

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

Cummins is the surprise for his omission, with the team skipper and fast-bowling leader deep into his recovery from early signs of a stress fracture. The only public acknowledgment was a cursory line 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 team in the near future. Theoretically, he might still be added to the Test squad in coming days if he and management so choose. But still, something the claims doesn’t add up.

Recalling when his medical tests came back positive in October, initiating the countdown on his return to play, all official statements from the bowler himself 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 team during the match. Coach Andrew McDonald said, “Cummins will be fit to bowl in Perth, and people will be sitting there questioning 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 New South Wales nets without any apparent limitations and, importantly, was using a pink Kookaburra ball, what one would assume as readiness for the Brisbane day-night game.

So, why the change of plans, more than four weeks since Cummins said he would need a month to prepare his workload, and with less than a week to go in Brisbane? Additionally, 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.

This is acceptable: prognoses can change, doctors may be cautious, players can be cautious. It’s just peculiar is that during the high-profile Test series in the season, the board officials seem not to think it necessary to provide updates about the captain’s fitness and availability or the evolving status of either.

And if caution is the watchword with the captain, the reverse is true with the opener’s issue. 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 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 heat of the next Test.

With Khawaja in the squad logically means 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. But again, there is no official information 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. But some plans are firmer than others, and considering how Travis Head’s explosive performance captured public attention, it would do no harm to confirm where those two players are slotted to play. A bit of mystery in sports is a good thing, but creating it out of the clearly evident is unnecessary. If you’re in the business of engaging fans, transparency is crucial.