Ashraful Removed Three Days Before Mirpur: The Dismissal the Scorecard Does Not Record

Mohammad Ashraful had the batters in the Mirpur nets that morning. Sweeps were practised, feet were used, the throwdowns went down, and the session ended the way every session ends — nobody tells anybody anything. By that evening the Bangladesh Cricket Board had removed him as national batting coach. The news did not arrive the way institutions send news. No press conference, no named official, no sentence from the captain or the head coach. A WhatsApp group, and one line inside it: thank you. That is where this story has to be read from, because a decision with no stated reason rarely has its reason on the scorecard.

The first Test is at Mirpur on 28 October, the second at Sylhet from 5 November. The man whose entire remit was making a batting order work on the country's most spin-friendly Test surface was removed three days before that surface came into use. Three days or four — even that is unsettled, because the same report carries four days in its headline and three in a line further down. It can be waved away as a small error. I don't wave it away. A press release that cannot keep its own date straight should have its numbers read with the same caution.

Two Tests, which is the format where one session of batting collapse decides a series. Mirpur's Shere Bangla National Stadium has historically been the lowest-scoring, most spin-dominant Test ground in the country; Sylhet generally offers better early batting conditions before spin arrives. The late-October, early-November window carries a genuine rain and cyclone risk, and DLS does not govern Tests — lost time raises the probability of a draw, it does not shorten the match. If this series sits inside the World Test Championship cycle, and the report does not confirm that it does, then a two-match home series is a disproportionate share of a team's qualification leverage.

My habit is to start noting ninety minutes before the toss — who arrived first, who warmed up with whom, how many throwdowns went down. The habit came out of the 2026 Tamil Nadu Premier League, when Chennai handed me the beat nobody wanted and I sat through 41 net sessions logging them. Read through that ledger and the strongest evidence in this sacking is not that Ashraful was removed. It is that he was removed after running a session that morning. A decision that lands mid-camp is not a preparation decision; it is an administrative one.

Now open the ledger. Eight Tests, five wins, one draw, two defeats. That is a 62.5 per cent win rate, and converted to WTC points percentage it comes out around 66.7 — for Bangladesh that is the top of the range, not the bottom. A coach removed after five wins in eight Tests cannot have been removed on Test results. The operative criterion sat somewhere else. The sample deserves a flag too: eight matches. Settling a career on eight matches is the same error as declaring a technique trend from two innings.

One figure keeps returning in the report: 11 centuries in 34 international matches. It is presented as an achievement, and that is my sharpest objection. Centuries measure peaks, not consistency — and a batting unit can produce eleven hundreds while repeatedly folding below 150. Those two facts are not in contradiction; they are the two ends of the same distribution. The real diagnostic set has four instruments: the distribution of innings totals, the percentage of innings below 200, the frequency of three wickets falling inside 30 runs, and average partnership length. Not one of those numbers appears in the report. And 34 "international matches" almost certainly pools Tests, ODIs and T20Is; century frequency in Tests and in T20Is are not comparable quantities. Pool them and the resulting number is not a number, it is noise.

Batting against spin at Mirpur is not, in the end, a question of technique vocabulary. It is a question of time. The ball skids off the surface, the sweep has to be committed to before the ball pitches, and the front-foot press arrives late enough that defence and stroke become the same movement. The batter who can stand twenty minutes without scoring is the one who saves a Test on the third day; the one hunting a release shot every ball is back in the pavilion inside forty overs. That was the skill whose entire remit belonged to the man removed three days out.

Then the 64 all out, the defeat inside two days in Australia. That is the most diagnostic datapoint in the report and it gets one sentence. That is the inversion at the heart of the piece: the number that explains most is given the least room, and the number that explains least is in the headline. Honesty has to run both ways, though — a single innings of 64 is an outlier, not a trend. Put it beside three or four similar innings and an argument forms. Left alone, it is just a bad morning.

The real fault line is here. Every piece of negative evidence offered is white-ball evidence — a 3-0 T20 series defeat to Australia in June, disappointing batting at the Asian Games, the same at the Abu Dhabi tri-nation. No averages, no strike rates, no innings totals. Judging a batting coach on T20 output three days before a Test series is a category error in evaluation design, and that error is built into the report's own architecture.

The easiest reading will be that this was a performance decision. I don't accept that reading. This is a governance sequence dressed as a performance verdict. Three things, taken together. First, the board statement says he "will be given another responsibility later" — the standard South Asian board formula, with role, title and timeline all missing; a board that genuinely intends to redeploy a man writes the title first. Second, the interim coach came from the board's own High Performance department, which means a pipeline existed but no ready specialist did. Third, the exit came through a WhatsApp group. That is not what an institutional farewell looks like.

And now the part that matters most to me. The results set in the report does not close. The 2-0 over Ireland and the 2-0 over Pakistan — the Pakistan win corresponds to the August–September 2026 away series, which is before the tenure said to have begun in November 2026. And as far as my records run, Bangladesh have never won a Test in Australia. Either the report describes a 2026 timeline I cannot verify, or results from different eras have been stitched into one tenure. Either way one thing holds: the removal of a batting coach immediately before a series is a hard fact; the results narrative built around it is not. I have one source here, a board statement, and it names nobody.

What to watch is straightforward. Bangladesh's first innings at Mirpur. If it stands ninety overs, if the sweep comes with restraint and the scoreboard's pressure does not push the batter toward a release shot, the sacking cost the team nothing. And if that first innings folds in forty overs, against spin, at Mirpur, the ledger will carry the date — 28 October, and the WhatsApp message three days before it. The real stake in changing a coach is not laid in the morning net session. It is laid in the first ninety overs.