🔗 Share this article

One might speculate whether the Australian cricket board intentionally chooses to be unclear about team selection or simply lacks effectiveness in public relations, but once again, the fitness of players and final team composition must be deduced from the 14-player squad announcement for the Brisbane match.

Typically, an identical team list would not attract attention, 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 his omission, with the regular captain and pace spearhead deep into his recovery from initial symptoms of a back injury. The only public acknowledgment was a cursory line with the squad release stating that “Pat Cummins will travel 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. Theoretically, Cummins could even join the Test squad in coming days if deemed fit by staff. But still, the explanations seem inconsistent.

Going back to when Cummins’ scans were cleared in October, initiating the countdown on his buildup to match fitness, all public commentary from the player and board schedules suggested he would just be unavailable for the first Test and was set to practice at close to full intensity with the team during the match. The head coach remarked, “Cummins will be fit to bowl in Perth, and fans will wonder why he’s not playing.”

After returning to Sydney following the victory in the west, he was seen bowling in the state facilities without any apparent limitations and, most notably, was training with a pink ball, what one would assume as readiness for the Brisbane day-night game.

So, why the change of plans, well over a month since Cummins said he would need four weeks to build up bowling loads, and with less than a week to go in the Gabba? Not to mention, there are over a week’s break between matches. If the latter is Cummins’ destination, it will be over two months since he resumed bowling.

That in itself is fine: prognoses can change, medical staff can be conservative, athletes might take care. What’s strange is that during the most anticipated and closely followed Ashes contest in Australia’s calendar, the governing body’s representatives don’t appear to consider it necessary to provide updates 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 spasms flare up in Perth during two paltry fielding innings, keeping Australia’s usual opener from doing so 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 creates concern that they could return in the heat of the next Test.

With Khawaja in the squad suggests he is due to resume opening the batting, even though his replacement scored a historic hundred in his place. He wouldn’t be selected as a reserve or to bat down the order. But again, there is no confirmation about this, just the selection.

It isn’t necessary that teams should have to give a whole XI when picking their squad, and strategies may shift. But some plans are firmer than others, and given the way Travis Head’s explosive performance captured public attention, it would do no harm to clarify where both batsmen are slotted to play. Some uncertainty in life is a positive, but manufacturing it out of the clearly evident is unnecessary. If you’re in the business of engaging fans, transparency is crucial.