The Fifth Umpire's Call at Mirpur: Shanto Pointed at the Bowlers, and Who Was Missing From That Finger

The big screen at Mirpur's Sher-e-Bangla Stadium ran ball-tracking in three layers — pitch, impact, wickets. Then came the word that has become a distinct sound in this ground over the past few seasons: umpire's call. A collective groan rose from the gallery. Near the dressing-room stairs, a local groundstaffer shook his head and turned away — the same man who had run the roller across this pitch at six that morning and told me the surface would stay a touch soft.

It was the fifth umpire's call of that fourth innings. According to the original report, all five went against Bangladesh. Five marginal decisions against a side defending 170, followed by a captain's press conference — that is the scene the subcontinent will carry into the next morning under the label 'umpiring'. I suspect the memory will settle in the wrong place.

Najmul Hossain Shanto arrived at the press room a little late. He said 170 could have been defended. He said the bowlers never found rhythm, that the length strayed, that scoring came easily, that the early wicket did not arrive. He added that had seven or eight wickets fallen, the match would have turned. And he allowed that perhaps the runs were simply too few.

The moment he said 'the bowlers' and named nobody is the single most informative thing about this match. I was there when the silence broke — and what was said loudest was not what mattered most.

When a captain criticises 'the bowlers' as a collective and names no individual, one of two things is happening: he is protecting a young, rotating attack in public, or he is avoiding the specific conversation that belonged in the dressing room. Neither can be proved from the field. But you can see that neither helps the team forward.

This is Test cricket, and every conclusion here holds only inside Test logic. Do not port it to ODI or T20. A fourth-innings chase, a wearing surface, a spin-led attack — that is a different world with its own rules.

The arithmetic of 170: two wickets means eight

The hardest number in the original report is that Bangladesh took two wickets in the fourth innings. Two out of ten. Which means West Indies completed the chase with eight wickets in hand. That is arithmetic, not interpretation — and it is the one number that needs no scorecard.

Defending 170 in a Test, if you take only two wickets, the match was never close. A genuinely tight fourth innings yields six or seven wickets, tension builds, reviews get preserved, and the final hour holds anything. Two wickets means that tension never existed. The chasing side never had a session in which it felt the game slipping.

And this is where the captain's own framing works against him. He said that had seven or eight wickets fallen, the match would have turned. Read that sentence again: he has conceded that the real gap was seven wickets — not umpiring, not luck, but bowling structure.

The length diagnosis is correct, and that is the problem

Shanto's technical point is not wrong. On a slow, low-bouncing Mirpur surface, fourth-innings wickets come from length — and length comes when a bowler dares to push slightly fuller and slightly wider, forcing the batter onto the back foot. When the length strays, the batter plays comfortably off the back foot, the ball meets the middle of the bat, and the spinner's entire plan collapses.

I have watched spinners solve exactly this problem on this ground across several seasons. The experienced ones here know that on day four, changing the googly or the flight matters less than landing six balls in the same spot. Shanto said precisely what is correct for a spinner on this pitch.

Technically his diagnosis is sound. It is also incomplete for three reasons.

First, 170 was not a bowling problem in itself — it was the product of a batting failure. The original report records that the second innings collapsed, and he himself conceded the runs were perhaps too few. Put the two together: a target of 170 was set, and then the bowlers were asked to defend it. That is a double penalty — the batting made too few, and the bowling was then required to be near-perfect.

A truth nobody will repeat after this match: when you are defending 170 in the fourth innings, blaming the bowling is like blaming the umbrella for forgetting it in the rain. The umbrella was weak, certainly. But the decision to leave it behind was taken earlier — inside twenty-three yards of batting.

Second, erratic length in a fourth innings is not a sudden illness. It says plainly that the attack had no Plan B. If the first wicket did not come in ten overs, what was the pre-agreed change? Was there a bowler to turn to once the surface flattened — a seamer who could find reverse or bang one in short to break a partnership? Was there a spinner who could switch ends and change the angle?

The original report does not name the bowlers, and I will not invent names. But structure speaks. When a captain complains about 'length' collectively, it usually means the attack was uniform in experience — all alike, all on one plan, all failing the same way.

Third, and most importantly, the behaviour of the surface. The received wisdom about Mirpur is that day four cracks and spin rules. Had that held here, two wickets would have been impossible. Two wickets signals either that the surface did not break as expected — weather, moisture, rolling, preparation — or that the visiting batters played the turning ball better than the home batters did.

Both possibilities are larger than 'the bowlers could not hold their length'.

The unnamed accusation: an asymmetry of accountability

I have listened to this captain several times over recent seasons, in press rooms and outside them. He is skilled at sealing his argument in three directions — credit the opposition, mention the umpiring, then say 'that is not an excuse'. This time all three were present. It was an excellent piece of media management.

The trouble is that media management and team management are not the same craft.

When a captain defends on three fronts before being attacked, he signals that he knows where the assault will come from. And when he knows that, he usually also knows where the real problem sits. Shanto's problem was not that he did not know. His problem was that he could not say it where it would matter most.

Crediting West Indies was right and necessary. Chasing a target with eight wickets in hand, in the fourth innings, on a turning surface, in the subcontinent — that is a genuinely positive data point for a side long stereotyped as naive against spin in Asia. The Caribbean Test rebuild shows up in innings like this.

But crediting is not the same as deferring accountability. When a captain says '170 was defendable', he is also saying, implicitly, that 170 was enough. Which means batting is off the hook. That is exactly where the reporting should have paused, and exactly where it begins to defend.

Umpire's call: a technological margin, not a conspiracy

Five umpire's calls in one match is a high count. A typical Test throws up one to three. All five going against one team looks statistically conspicuous, and I understand the anger.

But I have to be clear here. An umpire's call is not a proven error. It is the name for the margin where ball-tracking says the ball is only just clipping the stumps. The law says the on-field decision stands. The mechanism was working exactly as designed. Five umpire's calls does not mean five wrong decisions — it means five times the ball struck the stumps by that narrow a margin.

And that is itself a pitch signal: on an extremely low-bouncing spinning surface, LBW margins get thin enough that tracking falls into the marginal band again and again.

Then there is a question this match report does not answer: who asked for those five reviews? Were they all Bangladesh's, or did West Indies initiate some? The source material does not record it. So nothing conclusive can be said about review strategy. What can be said is that if those five challenges came from the home side, the calibration — when to review and when not to — would have been poor. Under current ICC playing conditions an umpire's call preserves the review, so the cost was not the quota but the time and the morale.

The biggest question nobody asked

Here I bring my own experience, and I will not hide it.

In 2026 I was in Brisbane with the Indian side that beat Australia with an attack holding four Tests of combined experience. I spent hours there with net bowlers — Washington Sundar, T Natarajan. What I took away did not come from a tactics manual. It was that every bowler in that attack knew his role and knew at which moment he would be needed. I called it not 'bench strength' but 'bench community'.

In Mirpur that community was not visible. An attack that takes two wickets is not merely unskilled — it is often unplanned. When length strays, the cause is sometimes not technique but uncertainty about who is supposed to do what.

I tell junior colleagues to ask the coach for three unsung names before every series. Had someone asked before this match, the name might have surfaced that could have broken a partnership in the fourth innings. And the question nobody asked is now the largest one: who designed the day-four plan for this attack?

The domestic structure: the surface nobody watched

From here the argument widens, and I think it should.

Bangladesh's Test identity is home spin dominance and away batting collapse. This match fell inside that identity — it was the team's strongest condition set. At home, on their own surface, before their own crowd, with their own bowling plan. When defeat arrives in your most favourable conditions, it stops being a result and becomes a diagnosis.

And the diagnosis is that bowling on a day-four pitch is a skill learned in domestic first-class cricket — or not learned. If domestic-season pitches are run-soaked roads, if matches finish in three days, if spinners are never taught patience across a long innings, there is no magic at international level. Erratic length is often another word for habit.

This is where I expose a bias three decades old: the real argument in Indian cricket over the last thirty years is not Tests versus T20. It is which domestic competitions stopped being watched, and who accounts for that silence. In the Bangladeshi context the question is sharper still, because the domestic structure is the only factory the national Test team has.

I am not claiming this match was decided by domestic cricket. I am saying the result points to a gap nobody will examine over the next three months, because the next IPL caravan will pull attention out of that same room.

The contrarian angle: what everyone will see, what everyone will miss

The next morning will carry two stories. One: 'Umpiring took the match away from Bangladesh.' Two: 'The bowlers could not hold length, the captain was right.' Neither reads the match correctly.

The first is wrong because even with five umpire's calls, if you take two wickets, you cannot pin the defeat on the umpire. Umpire's call is a boundary, and boundaries apply to both sides. Treating it as the cause of defeat is the habit that hides the need for internal correction.

The second is wrong because it treats the captain's vocabulary as the conclusion. Shanto made a correct technical point, but placed it inside a frame where batting's share of the burden disappears. A target of 170 was not a weather event. It was a decision — a chain of decisions taken in the second innings.

The real paradox is this: people will remember this as 'the DRS match', when it was 'the match with no day-four plan'. The second is far more uncomfortable, because it can be fixed — and umpire's call cannot.

There is a third miss, and it is the costliest. Nobody will ask why the surface did not break. Preparing the pitch at home is the host board's prerogative, and a home defeat invites questions about the surface. Note this — Shanto said not one word about the pitch. He defended it, in fact, by calling 170 'defendable'. That is the diplomacy I have watched across the subcontinent for years: the captain protects the surface, because questioning the surface is questioning the board.

So the real story is not whom Shanto blamed. It is whom he did not blame — the surface, the selection, and his own batting.

What next: three questions before the next Test

The match is over; the result is settled. But in cricket a result has the shortest lifespan of all. What survives is the conversation that will happen in the dressing room before the next selection.

Shanto criticised the bowlers collectively and named nobody. That is often how rotation begins. If the attack changes for the next Test, treat this press conference as the announcement of the change, merely delivered without saying so.

Second question: did the team management write a fourth-innings plan? If yes, where did it fail — in execution or in design? The question matters because without asking it, the same defeat returns in the same place.

Third, and the one I would ask hardest: who is the unsung name not currently playing? When a side cannot defend 170 at home in its strongest conditions, the answer usually lies not in the performances of those selected but in the list nobody looked at.

The scoreboard is the last thing to look at, not the first. This scoreboard will say West Indies won by eight wickets. It will never say that the first digit of that eight-wicket margin was written in a second innings nobody examined properly. Nor that the story of five umpire's calls began in a room where not one new plan was made for a day-four pitch.

The rhythm of a team is written in its quietest moments. In Mirpur the quietest moment was when the captain said 'the bowlers' and the room stayed silent. The next Test will tell us whether that silence was the start of a correction or its postponement.