One might speculate whether the Australian cricket board intentionally chooses 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 14-player squad announcement for the Brisbane match.
Normally, an unchanged squad would not be much news, but this time it is, due to the anticipated changes involving Pat Cummins and Usman Khawaja, none of which has now eventuated.
Cummins is the surprise for not being included, with the team skipper and pace spearhead deep into his recovery 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 support the view that this is all situation normal and his healing is proceeding well, with a likely addition to the side soon. Theoretically, he might still be added to the Brisbane squad in the next few days if he and management so choose. However, the explanations seem inconsistent.
Going back to when his medical tests came back positive in last month, starting the clock on his return to play, all official statements from the player and timelines from CA indicated he would only narrowly miss the initial match and was scheduled to train at close to full intensity with the team during the match. 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 team’s raucous two-day win, he was seen bowling in the New South Wales nets without any apparent limitations and, most notably, was using a pink Kookaburra ball, presumably as preparation for the day-night Test.
What prompted the shift, more than four weeks since he indicated requiring a month to prepare 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 more than seven weeks since he resumed bowling.
This is acceptable: medical opinions evolve, medical staff can be conservative, players can be cautious. It’s just peculiar is that during the most anticipated and closely followed Ashes contest in the season, the board officials don’t appear to consider it reasonable to share any information about the skipper’s condition or the evolving status of either.
And if caution is the watchword with the captain, the reverse is true with Khawaja’s back injury. He had muscle spasms in Perth during brief periods on the field, keeping Australia’s usual opener 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 fact he’d not experienced them before surely leaves some risk that they might recur in the heat of the next Test.
With Khawaja in the squad suggests 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 reserve or to play lower. But again, there is no official information about this, only the squad listing.
This doesn’t mean that teams should have to give a whole XI when picking their squad, and plans can change. 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 both batsmen are slotted to play. A bit of mystery 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.
A passionate gamer and tech writer, Aria shares expert insights and reviews on the latest video games and gaming culture.