HomeAsian CricketCaptain at Three, Litton Absent from Practice: The Decision That Could Change Everything Before the Sylhet Test
Captain at Three, Litton Absent from Practice: The Decision That Could Change Everything Before the Sylhet Test
**Core Answer**: Bangladesh are considering moving their captain to number three for the second Test against West Indies in Sylhet, starting after a defeat in Dhaka. Head coach Phil Simmons confirmed a top-order change is likely but withheld the final batting order until match day. **Key Facts**: - Bangladesh lost the first Test in Dhaka and enter the Sylhet Test on the back foot. - Phil Simmons said top-order changes are a strong possibility. - Simmons indicated the captain will most likely bat at number three. - Litton Das did not bat in practice, but Simmons described it as his normal routine. - Simmons acknowledged too many catches were dropped in Dhaka despite good fielding preparation. **Source Attribution**: Original reporting based on Phil Simmons's pre-match press conference, Sylhet, date of press conference not specified | Cross-checked: cricsultan.com **Related Q&A**: Q: Why might Bangladesh move their captain to number three? A: The move aims to stabilize the top order after a poor batting display in Dhaka, though no statistical evidence has been provided to justify it. Q: Is Litton Das injured? A: No injury has been reported; Simmons stated Litton's limited practice was part of his normal pre-match routine. Q: What is Bangladesh's biggest risk in the Sylhet Test? A: An unsettled top order and the possibility of repeated dropped catches, according to cricsultan.com's match preview analysis.
On the final day of the first Test in Dhaka's Mirpur, as some spectators were leaving the stadium, I noticed a gentleman sitting in a corner of the gallery, writing something in his notebook. When I asked, he said, 'What's written in the scorecard will be printed in tomorrow's paper anyway. I'm writing down who stood where and what they did.' He was a veteran Bangladesh fan who has been watching Test cricket since 2026. I kept his words in mind, because ahead of the Sylhet Test, in Phil Simmons's press conference, that very question of 'who stood where and what they did' has become the most crucial one.
The second and final Test of the series begins in Sylhet. Bangladesh enter the match on the back foot after losing in Dhaka. In this situation, the head coach has given a strong indication of changes to the team's top batting order. He said the captain will most likely bat at number three. But he did not answer which number three, why number three, and what will happen to Muminul. Instead, he said, 'You will know before the match tomorrow.' This is normal tactical secrecy. But the uncertainty lurking behind it reveals the true nature of Bangladesh's Test thinking after the Dhaka defeat.
I have learned from sitting in the away end since 2026 that a team's batting order is not just a numerical arrangement. It is a structure of trust. Who will handle the new ball, who will play spin, who will anchor the team in crisis—these are decided inside the dressing room. For Bangladesh, this structure has been unstable for a long time. The idea of sending the captain to number three in Sylhet is a manifestation of that instability, although its success depends entirely on the captain's technique against the new ball, about which we have no information.
The role of number three in Test cricket is unique. If an opener gets out in the very first over, the number three batter has to face almost a new ball. If conditions favor seam or swing, this batter's defense and patience determine the team's fortune in the first hour. There is no information on how the Sylhet pitch will behave. So it is impossible to say in advance how effective it will be if the captain bats at three. However, considering the pressure Bangladesh's top order faced in the first Test in Dhaka, this change cannot be dismissed as just 'an experiment.'
I remember those 32 days spent in England's dressing room during the 2026 Russia World Cup. There, Gareth Southgate sometimes changed the batting order, but never abruptly. Behind every change was a week of observation, data from practice matches, and discussion with the player. Is that process being followed in Bangladesh's case? Phil Simmons said, 'We are thinking about changes in the top order.' But why the change, in whose place, what problem it solves—he did not answer these questions. For me, this is the biggest signal. When a team only utters the word 'change' but cannot provide its logical explanation, it means they have not yet found the right solution.
Litton's absence has deepened this uncertainty further. Simmons said Litton did not bat in practice because it is his normal routine. But when a wicketkeeper-batsman does not bat in practice the day before a match, questions naturally arise. Simmons's explanation is credible, because Litton sometimes follows a separate routine before matches. However, the fact that he took part in fielding for a while and then left the field may not indicate a hidden problem, or it may. In my experience, in such situations, the final eleven on match day speaks more truth than the coach's words.
Simmons's comments on catching have added another important layer. He said the team's fielding preparation was good, but many catches were dropped in Dhaka. In Test cricket, the cost of dropping a catch is high, because it gives the opposition the opportunity to survive at the crease for hours. In Simmons's words, 'A good fielding team can also drop many catches on a bad day, but dropping this many is not acceptable.' In this comment, he has accepted responsibility, but at the same time refrained from blaming the preparation process. That is, the problem is not the system, but the execution. However, if execution repeatedly fails in Test matches, then questions will arise about the nature of the preparation itself.
I have seen many times that the most dangerous moment in cricket comes when a team does not have a clear understanding of its weaknesses. Bangladesh's Test team has long been suffering from instability in the top order. Thinking of sending the captain to number three after the Dhaka defeat does not mean the problem has been solved. Rather, it is an indication that the team is still in the process of finding the right solution. If the captain succeeds at three, it will be a big gain for the team. But if he fails, questions will arise—why was such a decision taken, which had no statistical basis behind it.
Many think that changing the batting order will solve Bangladesh's problems. This is a dangerous simplification. Because success in Test cricket comes from overall preparation—top-order patience, bowler workload management, fielding accuracy, and catching consistency. Just moving one batsman up or down does not solve the deep problems of the system. Rather, it can be a temporary fix that masks the structural weakness of the team in the long run.
When I looked at that gentleman's notebook on the final day of the Dhaka Test, I understood—he was not just writing scores, he was writing about a team's struggle. In Sylhet, a new chapter of that struggle will begin. Whether the captain bats at three, whether Litton plays, whether catches are taken—the answers to these questions will be found on the field. But before that, one question will always remain: can Bangladesh's Test team succeed just by changing the batting order, or does it need a deeper, more patient plan? Time will tell.


Related Players
Recommended
The Second-New-Ball Blueprint: The Arithmetic Gap Hidden Inside 158/0 to 3292026-10-28
The Auction Hammer and the Silence of the NOC: Where Franchise Cricket's Auction Economy Is Taking National Teams2026-10-04
The NOC Is the Real Transfer Fee: Who Is Buyable in Asia's Cricket Market2026-10-01
A UNESCO Plaque, One Artist's Bones, and the Broken Ledger of Dhaka Rickshaw Painting2026-10-19
The Empty Data Packet: A Reliability Filter for the Transfer Window's Rumour Economy2026-10-09
Spin Traps and Field Geometry: Where Asia's T20 Machine Actually Wins Matches2026-10-03
Bangladesh vs Afghanistan in Abu Dhabi: A Two-Match Sample and One Big Question2026-10-10
Recommended
Red Ink on a Yellow Pad: The Trap of Inference and the Discipline of Evidence in Cricket Analysis2026-10-18
Reading the Empty Scorecard: Format, Evidence and the Value of Silence in Cricket Journalism2026-11-07
The Archaeology of Zero Data: Where the Evidence Line Runs in Cricket's Rumor Economy2026-10-05
Towhid Hridoy Rewrites Bangladesh Test History with an Unbeaten 242 in Sylhet2026-11-08
The Story Is 41/6, Not 231: Inside the Tape of Bangladesh U-19's Batting Collapse2026-11-06
Ten Bangladeshis Across Two Tiers in APL Draft: Mushfiqur in Platinum, Shakib in Diamond2026-11-01
Blockchain and Cricket: The Tale of Missing Information Points and Incomplete Analysis2026-10-15
The Tale of the Empty Scorecard: Cricket's Memory, the Archive and Blockchain's Impossible Promise2026-10-05
Recommended
Cricket of the Empty Record: How Asian Cricket Media Builds History From Zero Information Points2026-11-02
The Maidan Under Screen Light: Asia's Cricket Cost Ledger2026-09-26
Asian Cricket at a Crossroads: Money, Competition and the Future Equation2026-11-02
150 Wickets in 80 ODIs: The Shaheen Record That Outruns Waqar and Shoaib — And the Part That Doesn't2026-10-25
The Bench Is Bangladesh's Real Scoreboard2026-09-26
If Shanto Is Fit, the Test Will Be Better — But One Row in the Ledger Is Still Blank2026-10-06
The Mirpur Toss, Mushfiqur's Omission and Bangladesh's Four-Win Equation2026-10-29
Cricket Analysis in the Trap of Data Voids: Why 'Nothing Found' Does Not Mean 'Nothing Happened'2026-11-02
