The Fitness Test That Never Happened: Before Mirpur, Litton Das's Question Left the Ground

On Saturday, 24 October, the BCB medical team's diary had a line reserved for one item: Litton Das's fitness test. Nobody crossed the line out. The test simply never took place. More than fifty years of sifting through cricket's paperwork has given me one habit I cannot shake — a failed test hands me a verdict, a skipped test hands me a vacuum. And a vacuum is never empty. People fill it, not protocol.

In the Sunday net session Litton batted comfortably and played some big shots. Nobody is arguing about what the eye can see. The question is not there. The question is this: for a man who will be asked to squat through 130 to 180 overs across five days, a man with a history of inflammation in a gluteal tendon, what does a twenty-minute net innings actually prove? The answer, in my notebook, is uncomfortably plain. Almost nothing.

I trust the second replay, because the first is only a rumour. What the second replay of this story shows is not the state of one player's hip. It is the picture of a process. One step inside that process has been skipped, and the skipped step is the real story of the Mirpur Test beginning on 28 October.

The first Test starts at the Sher-e-Bangla National Cricket Stadium on 28 October; the second begins in Sylhet on 5 November. Roughly a week after the series ends, on 15 November, the South Africa tour opens — two Tests, three ODIs, three T20Is. Lay those three dates side by side and the shape becomes obvious: the decision Bangladesh are taking in the last week of October will echo into the middle of November.

Litton Das is this side's middle-order wicket-keeper batter. The problem sits in the hip region — inflammation of a gluteal muscle tendon, restricted mobility in certain joints, muscular weakness. He did not play the tri-nation ODI series, which also involved Zimbabwe and Afghanistan. Injury-related discomfort has followed him around in recent times; the report says so plainly.

Four distinct voices sit inside this story. Team management. A selection panel member whose stated position is “50-50” and who will wait “till the end”. Another member of the management, whose caution runs — “functional training doesn't mean he is 100% fit; we might be taking some time”. And the BCB medical team, who did not conduct the scheduled 24 October fitness test at all. Beyond these, one more data point: the player himself is understood to be keen to play. The room where the decision is taken includes team management and senior BCB officials.

Four voices that appear to look in the same direction are in fact looking in four different directions. The medical team wants time. The selection panel wants an outcome. The player wants the ground. The administration wants a risk calculation. When those four wants converge on a single point, the decision becomes easy. When they do not, the decision migrates to a meeting table and the accountability dissolves.

Venue logic is part of the arithmetic. Mirpur has historically been a low-bounce, dry, spin-favourable surface. Sylhet offers a little more for seam early and deteriorates later. Both point to the same Bangladesh plan: bat long, bowl dry, and load the spinners with more than 130 overs of work. In that plan the keeper is not merely a catcher. He is the man who absorbs those heavy overs for five days.

Home advantage here is venue-concentrated, not nationwide. Mirpur and Sylhet favour Bangladesh; the same side travelling abroad flips the picture entirely. In Test cricket Bangladesh's home-away delta is among the widest in the world game. So this series cannot be filed under a generic line about being strong at home. Without the pitch description, that line is incomplete.

The physical language of keeping is not the physical language of batting, and that distinction is the centre of this story. Batting loads arrive in a handful of deliveries — explosive, short-lived. Keeping loads arrive in repetition: a small squat every ball, a rise, a lateral push, an asymmetric load down one side of the body. In a Test, when spinners bowl, the repetitions multiply. Ninety overs of spin in a day, 130 to 180 across two innings, and the gluteal tendon is the structure that keeps getting pulled, because hip extension and abduction are precisely its job.

A batting net was never the best way to test a keeper's readiness. The best way is a long keeping session with the load stepped up — fifty overs, then rest, then again. Whatever the medical team had scheduled for 24 October was probably something of that order. Because it did not happen, we know how his batting feels. We do not know how his keeping is tolerating anything.

Pain resolution and load tolerance are two different events, and the report concedes the gap itself. In one breath it says the inflammation has subsided and the pain has reduced. In the same breath it says the body remains stiff from chronic workload, that muscular weakness persists, that strength has not fully returned. The medical team's own phrasing — “we might be taking some time” — admits exactly this. Inflammation settling is one marker; strength returning is another. The first arrives quickly. The second arrives late.

In my ledger this injury belongs in a separate drawer. It is not an acute traumatic event; it is the product of accumulated load. A broken finger resolves on a two-stage timeline: broken, then joined. An overuse presentation resolves on three: pain settles, load is tolerated, the same load is carried without re-breaking. Nobody measures the third stage, because measuring it requires playing a match. And the match is where you find out.

In team terms Litton is not one slot. He is two. A keeper-batter who bats in the top six gifts the side an extra bowling option, because wicketkeeping does not occupy a separate place — there is no need to slip a specialist keeper in at seven or eight. Remove Litton and the side loses two things at once: a top-order batting position and a bowling option. The tail lengthens and the attack shortens. That double loss is what puts the phrase “very important for us” into management's mouth.

The damage reaches the result through exactly one channel — the first-innings scoreboard. Bangladesh's route to victory at Mirpur is clear: 350-plus, then spin in hand and the opposition under scoreboard pressure. Pressure comes from runs, not from weather. If a lengthened tail collapses to 220 in innings one, the spin weapon still exists but the conditions to wield it do not. West Indies' route opens: two or three early wickets with the new ball, time at the crease, and Bangladesh batting last.

The South Africa tour sits outside this conversation but inside the arithmetic. The Sylhet Test ends on 5 November; from 15 November come two Tests, three ODIs and three T20Is across three formats and three weeks on opposite surfaces. Three weeks on low-bounce spin tracks followed by a sudden diet of bounce and pace means a preparation window close to zero. An accumulated-load injury behaves worst on a calendar of that shape. Litton is the first name here, not the last.

One methodological warning is needed. Absence from a tri-nation ODI series is not evidence about Test readiness. White-ball keeping loads differ, innings lengths differ, recovery windows differ. Thread the two together and the analysis walks off in the wrong direction. A second error keeps surfacing in the same conversation: rain and DLS. DLS does not apply to Test cricket. Rain removes overs and reshapes the declaration calculus; it does not create a revised target. Anyone reaching for DLS in this series is misreading the format itself.

Form and availability are two separate columns, and we hold data for only the second. His recent problem has been continuity of participation, not quality of output. On that evidence no judgment about form is possible. What is possible is an incomplete picture of physical readiness. My rule is simple: I do not add imagination where data is missing; I make the gap itself part of the analysis.

Source quality deserves ranking too, the way rumours get ranked by evidence in a transfer window. Most reliable is the physiological description — gluteal tendon, restricted joint mobility, muscular weakness; language that specific rarely survives a recycled team-news cycle. Next come the dates and venues — 28 October, 5 November, 15 November; settled facts. Then the selection panel's “50-50”, which is a position rather than a measurement. And last, “keen to play” — not medical information, a pressure signal.

When I logged the empty-stadium matches of 2026 one after another, a habit formed: mark every observation either transferable or environment-dependent. That habit applies directly here. The character of Litton's injury is transferable information. The “50-50” line is environment-dependent, because it was said to manage expectation. Put them in the same row and you misread both.

The debate has stalled on a single question: will Litton play? My reading is that the question is standing in the wrong place. The actual event is that the fitness test which would have made the decision mechanical — pass or fail, one of two — did not happen. A test not taken means accountability moves out of the medical team's ledger and into a room where management and administration sit together. When protocol decides, blame stays concentrated. When people decide, blame spreads.

One option nobody is naming is the most rational of the three: play Litton purely as a batter and hand the gloves to a deputy. That removes most of the acute hip loading while preserving the batting. Whether squad balance permits it is unknown — an extra keeper costs a bowling option, and at Mirpur a four-man attack thins the batting further. But the option belongs on the table. Without it, the decision collapses into play-or-sit, and that binary is where teams usually get it wrong.

The second unexamined item is the time horizon. Had the question been framed at series level rather than match level, the answer would have been simpler: Sylhet on 5 November and South Africa from 15 November are worth more than one Test on 28 October. But when a side says “very important”, nobody specifies which match the importance attaches to. Somebody benefits from that ambiguity. The player's body pays for it.

And “50-50” is not only a statement of probability; it is a communications tactic doing three jobs at once. It manages domestic expectation. It keeps pressure on the medical department to clear him. And it denies the opposition a settled team sheet — West Indies must prepare for two different Bangladesh XIs. All three are legitimate. My objection is narrow: when tactical communication and medical information occupy the same sentence, readers and fans both end up misled. The archive remembers what the crowd forgets, and I dust for fingerprints — in this case the prints have not yet separated.

So what do we watch on the morning of 28 October? The team sheet at the toss. If a specialist keeper is named, the decision came from the medical side. If Litton plays and fields in the slips, someone has attempted to manage the load. And if Litton takes the gloves, the real examination is the third day of the second innings — the test that was not conducted on 24 October.

Sylhet and South Africa will surface the same arithmetic