The Reason Behind the Unnecessary Mystery from Cricket Australia Regarding Cummins and Khawaja for the Second Ashes Test?
One might speculate whether Cricket Australia intentionally chooses to be opaque about team selection or simply lacks effectiveness in communications, but once again, the health status of athletes and the makeup of the XI must be inferred from the selection in the larger squad for the second Ashes Test.
Normally, an identical team list would not attract attention, 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 not being included, with the regular captain and pace spearhead progressing in rehabilitation from initial symptoms of a back injury. The only public acknowledgment was a brief mention with the team announcement stating that “Pat Cummins will travel to Brisbane to continue his preparations.”
Insider reports indicate that this is all situation normal and his healing is proceeding well, with a likely addition to the team in the near future. In theory, he might still be added to the Brisbane squad in coming days if deemed fit by staff. However, something the claims doesn’t add up.
Going back to when his medical tests came back positive in October, initiating the countdown on his buildup to match fitness, all official statements from the player and timelines from CA indicated he would just be unavailable for the initial match and was set to practice 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.”
After returning to Sydney following the team’s raucous two-day win, he was seen bowling in the state facilities without any visible restrictions and, importantly, was using a pink Kookaburra ball, presumably as preparation for the day-night Test.
What prompted the shift, more than four weeks since Cummins said he would need a month to prepare bowling loads, and with less than a week to go in Brisbane? Not to mention, there are over a week’s break between Brisbane and the third Test. Should he target Adelaide, it will be more than seven weeks since he resumed bowling.
This is acceptable: prognoses can change, medical staff can be conservative, 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.
If care is the priority with Cummins, 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 doing so 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 creates concern that they might recur in the heat of the next Test.
His inclusion 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 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 whole XI when picking their squad, and plans can change. But some plans are firmer than others, and given the way 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 creating it out of the broadly obvious is unnecessary. For those aiming of winning over audiences, transparency is crucial.