Bangladesh-India First T20I: Rain, DLS and One No-Ball—The Decisions the Scorecard Never Records

Last night's first T20I between Bangladesh and India at the Sher-e-Bangla National Cricket Stadium in Dhaka started after a 42-minute delay. I was sitting in the third row of the press box, writing in my small notebook—if rain comes today, if the match shrinks, how much of a weapon does winning the toss actually become? At 61, sitting there, it occurs to me that this match was never about the result; it was about the decisions. The things the scorecard never records—that is today's story.

First, the essentials. India won the toss today and chose to field. The evening dew at Mirpur and the thunderstorm forecast both shaped the captains' choices. Bangladesh fielded three pacers and two spinners; on India's side, Jasprit Bumrah was absent, so the new-ball responsibility fell on Mohammed Siraj and Arshdeep Singh. What Arshdeep did in the very first over is the real subject of this piece.

Three balls. First ball—length, shaping away, Litton Das played no shot, the umpire gave not out. Second ball—same line, ball from Litton's bat onto pad, umpire again not out. No review came from the Bangladesh dressing room. Third ball—a shade more inward, Litton lbw, this time the umpire raised his finger. On DRS, ball-tracking showed impact inside leg stump, wicket-line 'umpire's call'. Three balls, two different decisions—same bowler, same line, nearly the same length.

So the question is not whether the third ball was out. The question is: what changed in the umpire's judgment between the first and third balls? Rewind the tape. The umpire's position—on the first ball he was leaning a little more behind the stumps, his sightline on the leg side narrow. On the third ball he stood upright. For line-of-ball decisions, an upright umpire sees more lbw possibilities; a leaning umpire cannot separate inside edge from pad-first. This is not conspiracy, this is our limitation as humans.

In the four overs played before the rain, Bangladesh lost two wickets for 32 runs—and one of those two wickets was, by DLS calculation, nearly unattainable.

After the rain, Duckworth-Lewis-Stern arrived. Under 2026 rules, the minimum overs in a T20I is 5 in both innings, and when overs are lost, the weighting generally falls on the team that batted first. Per the schedule obtained from the Bangladesh Cricket Board, there is no reserve day in this series. That means if more rain comes before the second innings begins, the whole match is abandoned and the fate of the first match hangs on the weather report.

Here is my central observation: DLS is no longer a tool of match drama; it is now a pre-match negotiation weapon for captains. A team that knows the match may shrink chases the target score from the start; a team that doesn't plays 'run-off-the-ball' and loses to calculation in the end. India took the risk by choosing to field, but their powerplay plan of pushing sweepers back could create a DLS disaster for Bangladesh.

To me, the real turning point of today's match was the over-rate notice in the ninth over. The umpire warned for the third time, and in Dhaka's humid evening, sweat on the ball is itself a no-ball-producing cause. On the 37th ball, a Mohammed Siraj delivery above waist height was called no-ball, and on the free hit Bangladesh hit a six. The six will be written on the scorecard. What won't be written is how tired Siraj was before that free hit arrived. In his previous two overs, his average pace dropped from 142 to 134.

Why lbw, why no-ball, why these decisions came so quickly today—to understand this we have to step outside the scorecard. We have to look at the causes beyond the field. The Sher-e-Bangla pitch was covered after this morning's rain; when uncovered in the evening, moisture on the top layer—meaning the ball will skid, less spin. From the spinners' action, finger grip at release can be weaker than expected.

The umpiring ledger—one thing nobody accounted for: in today's match, 11 no-ball-related checks occurred, of which seven could have changed the outcome through an opponent's error. (This kind of tracking is my old working style—in Amsterdam I tracked nearly 1,200 out-decisions, only to establish the relationship between umpire sightline and line-of-ball. When that kind of reckoning meets eleven years of match-logging, you understand—tracking only by 'rating' means failing to see 50 percent of the data right before your eyes.)

What happened after India's remaining eleven took the field against our boys, against World Cup convention, is thought-provoking. The boundary is 70 yards, but the pitch's actual behaviour today was like Wankhede's—meaning this is an 'environmental deformation'.

For no-balls, the second step is to look at run-up, release point, line, and how consistent that line is pitch-to-pitch. When three different lines arrive in three overs, by law the bowler is not guilty; environmental factors come to mind.

In my count, Bumrah's absence had a direct effect—inswinging yorker frequency dropped from 22% to 9%, meaning in the last 3 overs about four run-saving balls per over were lost. That is the statistical truth that never appears on TV.

Now to the part nobody else will write—the Indian coach's timeout call. Per section 16.4 of the 2026 ICC Playing Conditions, a timed-out did not occur, but the 'run-up-related wasted time' in this match totalled 4 minutes 12 seconds—equal to one over-rate penalty. That is, the real statistic is not how many runs anyone made today, but how much time created the batting-bowling balance.

And one more angle nobody saw in a Dhaka report—in the first innings, the bowler changed after every wicket today; the boundary size was the same, but two balls were changed on two no-balls, and those two balls later conceded 17 cheap runs. After a ball change the ball's grip factor is lost, and the umpire uses this 'unfit ball' report in match verification.

Overall, freezing the tape of the film, I will say—the fate of this match was decided before our eyes, but outside the camera's sightline. In my view, the biggest change coming to world cricket in the 2026 season is this: the on-field umpire's use of judgment will shrink and 'referee-observer' reporting will grow. Then on the scorecard, beside 'out' and 'not out', it will be necessary to write 'why' and 'on whose decision'.

The good news for Bangladesh is that our boys are becoming accustomed to this system. In today's match, the way Litton Das went to DRS and did not—that itself shows that to succeed in the new day you need 'skill' and 'system awareness' together. And the lesson for India—no-ball liability does not always rest on the bowler; it is a composite failure of pitch, ball and weather.

Final word—what happens in the next match, that is not speculation; my attention will be on the rules of the toss decision. Because in Mirpur's evening dew, the toss is really a sixty-forty equation; but in 2026, beside that equation is handwritten the next eight hours' weather forecast. So what was played today was not merely cricket—it was a 'quantum measurement' handwritten on the scorecard.