Litton Das Skipped the October 24 Fitness Test: Bangladesh's Question in Mirpur Is Five Days of Wicketkeeping, Not Batting

The most useful line in this story is not the one everyone is quoting — "batted comfortably in the nets, played some big shots". The most useful line is the test that never happened. Litton Das did not take the fitness test scheduled for October 24.

Skipping a fitness test and failing one are not the same document. A failure tells you where the body stands. A skip tells you the medical staff decided the test itself, and the load required to pass it, carried re-injury risk. One is a measured result; the other is a result that was deliberately not measured. The BCB chose the second.

The deposit landed on a Tuesday; the story took three weeks. Here the order runs backwards. The test was due on October 24; the decision arrives on the morning of October 28. What I have at this desk is one specialist outlet's report and a public calendar. That is all, and it is enough to read the mechanism.

Context: Mirpur is the worst possible venue for this particular injury

The first Test begins on October 28 at the Sher-e-Bangla National Cricket Stadium. Late-October Dhaka brings post-monsoon humidity, residual rain risk and heat stress. Humidity accumulates soft-tissue fatigue — precisely the debt already sitting in Litton's gluteal tendon.

Mirpur's surface is slow and low-bouncing, and it takes turn as the match wears on. Two consequences follow. A keeper stands up to spin for long spells, which maximises hip-flexion load. And Bangladesh's home win path runs through spin, which makes the quality of the glovework directly outcome-relevant. The condition that gives them their best chance of winning is the condition that punishes this injury hardest.

The series is two Tests, so there is no runway. The second Test begins on November 5 in Sylhet, traditionally the better batting surface of the two. The South Africa tour — two Tests, three ODIs, three T20Is — starts on November 15. There is effectively no recovery window between the second Test and the flight. Follow the wage bill and it tells you before the headline does. Here the wage bill is the calendar, and the calendar has already spoken.

Core: a five-field deal chain where only one field leans positive

Every deal leaves a receipt, and most are filed in five fields. An injury story takes the same treatment. The five fields here are: current medical status, recency of match-play, physical load of the format, quality of the replacement, and the calendar ahead.

Field one is half-filled. Inflammation has subsided and pain has reduced — that is real and good news. On the same receipt sit three further lines: joint stiffness, limited mobility in certain joints, muscular weakness. Recovery is partial and load-dependent, not complete.

Field two is empty. Litton missed the entire tri-nation ODI series against Zimbabwe and Afghanistan. No competitive match, no first-class innings, no fifty-over hit-out before a five-day Test. Returning from a soft-tissue problem straight into Test cricket is an established re-injury pattern, and it applies to wicketkeepers as readily as to fast bowlers.

Field three is the heaviest. Test cricket is the format where a keeper stands for 150 to 200 overs across five days, squats repeatedly, and on a Mirpur turner stays up to the stumps for long spells. Net batting tests none of that. A gluteal tendon problem plus limited joint mobility hits three specific actions: the depth and speed of the keeper's squat, lateral movement for catches down leg, and footwork against the short ball plus running between the wickets. "Played some big shots" is the least diagnostic evidence available, and it is being placed at the top of the file.

Field four is clear. Bangladesh have competent glovemen in reserve — Nurul Hasan as the experienced option, Jaker Ali as the emerging one. The drop-off in glovework is modest. The drop-off is in batting. This is a batting question dressed as a keeping question. Litton's Test average sits around 36–37 across roughly 45-plus Tests with four centuries, and his strike rate runs near 58–60 against a team Test strike rate of about 48–52. Those figures come from public records rather than the source report and should be treated as pending verification. They establish an important player, not an irreplaceable one. The case for risking him rests on these specific conditions and the quality of the replacement, not on raw output.

Field five is decisive. In a two-match series the first Test decides more than its share. A 0–1 deficit going into Sylhet, with a flight to South Africa four days after that Test, is where a one-match call becomes a six-week call. The downside is asymmetric. The upside is one home Test; the downside is an entire multi-format tour.

One technical point has been buried. "Chronic workload" means the root cause is cumulative load across formats and franchise commitments rather than a single incident. If the driver is accumulation, playing the first Test resolves nothing; it borrows from November 15. And there is a structural constraint here: a fast bowler can be load-managed through a shortened spell. A keeper cannot be partially deployed.

Contrarian: "100% fitness is not needed" is a coaching-committee sentence, not a medical clearance

Team management's framing is that functional training is not the same as full fitness, and that he must meet "minimum requirements". The sentence is self-revealing: it concedes he is not at 100% and reframes the question as how little will do. "Minimum requirements" is procurement language, not medical language. When the selection panel says it "cannot say whether he is available or unavailable", it is not reporting uncertainty — it is transferring risk from the medical staff to team management. This is not the first time that transfer has happened in Dhaka.

The second contrarian point is the player himself. He is keen to play. In a contract and inclusion environment, self-assessment is systematically optimistic — not a character flaw, a feature of the incentive structure. Treating his keenness as evidence of readiness is the easiest and most expensive error in this file.

Third, rain. Late-October Dhaka showers could paradoxically reduce the keeper's load through interruptions and less time in the field. If any scenario argues for picking him, it is that one, and it depends on weather rather than on his body.

Fourth, something about my own position. My desk is in Brisbane, my network sits with Indian and Australian boards, and my receipts on Dhaka selection calls are thin. What I have here is a specialist outlet's report and a public calendar. The Mirpur surface I have watched across recent seasons is slow and turning — that is eyewitness testimony, not a document, and I will not sell it as one.

There is one more trap to avoid: mixing formats. His unavailability for ODI and T20 cricket is not a proxy for Test keeping readiness. The load, the posture and the duration all differ. A man who looks fine across fifty overs can break in the third session of day five, squatting to spin.

Takeaway: who signs off, and which month the signature borrows from

The call will come on the morning of October 28, after a warm-up and a fielding assessment, and the squad announcement will carry a "subject to fitness" rider. If he plays and the injury opens, the likeliest picture is not a dramatic moment but a gradual loss of mobility between days three and five — exactly the phase in which Mirpur Tests are decided.

Fifteen years in, my first question is still: who signed off? If Litton Das's fitness is signed off on the morning of October 28, the same page will have to state who pays the bill that falls due on November 15.