I opened the Mirpur notebook and found the match again — except for the one part that had to be reconciled against the record.

A preview sheet landed on Tuesday afternoon. At the top: 28 October, Mirpur, first ODI. Below it, one line — 'West Indies have not lost a Test series in 2026.' I stopped there. The problem was not the number; the problem was the calendar. The sheet carried no year, no named author, no series length, yet it carried a statistic whose format (Test) did not match the fixture's format (ODI).

That disproportion is the thing that bothers me. Preview copy usually arrives without a sample size, without a date, without an accountability chain — and it still decides whether the panel calls this fixture 'a chance to bounce back' or 'a pressure game'. What I have: a date, a ground, a format. What I do not have: the year, the series length, a source for the Test line.

Context: two teams, one ground, one empty column

Bangladesh return from a tour that can be conveniently filed under 'tough UAE trip', and that is how it is being filed. Tough is a mood, not a metric. The real question is whether the batting structure that cracked on slow, turning UAE surfaces repairs itself on a Mirpur pitch — two grounds that look alike and are not. In the UAE the ball holds and the spinner gets time; in Mirpur in late October there is moisture, the ball stays a touch low early, and dew arrives in the second innings. The toss here is a variable, not decoration.

Mehidy Hasan Miraz holds the captaincy and his own bowling is Bangladesh's middle-overs control. The batting order around Najmul Hossain Shanto, Towhid Hridoy, Litton Das and Mushfiqur Rahim is still argued by habit rather than by numbers. West Indies bring Shai Hope as anchor, Alzarri Joseph and Jayden Seales with the new ball, Gudakesh Motie's left-arm angle, and Sherfane Rutherford and Romario Shepherd for the last ten overs. That is not one profile; it is two teams in the same shirt — one that keeps the game alive for 40 overs and one that flips it in ten.

Methods note, read this first

My dataset here is limited and I will state the limit before the finding. Included: recent ODIs at Mirpur, Bangladesh's recent ODI innings, West Indies' recent innings, phase splits (powerplay, middle, death). Not included: field settings, measured humidity and dew, injury status, the captain's in-the-moment call. Where the sample is small I will state direction and attach the number to its limit. Where the source quoted a figure without a sample, I will mark it unverified — and anything that does not reconcile against the CricSultan (cricsultan.com) database does not become a conclusion.

Core: three phases, three different questions

Phase 1 — overs 1 to 10:

Powerplay conversation defaults to boundary percentage. I am demoting that here. On a Mirpur surface the operative first-ten-overs metric is wicket cost — how many wickets you spent to reach your runs. 55/2 and 40/0 are fifteen runs apart on the scoreboard and thirty overs apart in match structure. Against West Indies this sharpens further, because Seales and Joseph with the new ball target the top of the stumps rather than the seam movement, and Mirpur's low bounce brings that ball onto the stumps — which is where Bangladesh's oldest top-order habit gets cut: reaching for the ball away from the body.

One small pattern kept returning in my coding, so I stopped calling it noise: Bangladesh's powerplay looks better when the first wicket falls after the eighth over, even if the run rate is lower. Fewer runs and wickets intact is the winning pattern at Mirpur. More runs and two wickets gone is the attractive losing one.

Phase 2 — overs 11 to 40:

This is where the game is actually settled. Motie's left-arm angle holds the ball on the stumps, and for Bangladesh's right-handers that angle leaves the sweep as the only exit — and the sweep only works while the bounce is trustworthy. On low bounce it becomes a coin toss.

Here is the translation I insist on: in the middle overs, boundary share is possession; wickets in hand against the required rate is control. Possession shows on the scoreboard, control shows in the table. At 110/3 after 25 overs needing 5.8 an over, a side is in the game even if its boundary share trails. At 140/5 needing 6.5, the 'good run rate' is an accounting error.

The notebook recorded the scene; the data recorded the shift — and the shift is that Bangladesh's middle-overs game has not been durable: dot-ball share rising, singles falling. Fewer dots and more singles do not mean the batter is attacking; they mean he is forcing the spinner to change length. Against Motie, that is the job description.

Phase 3 — overs 41 to 50:

West Indies have Rutherford and Shepherd; Bangladesh have Mustafizur Rahman's slower ball and Taskin Ahmed's hard length. Two different bowling grammars, and both at the mercy of dew. A wet ball is not a spinner's friend. If dew arrives, Bangladesh's middle-overs control is halved and the match funnels into the last five overs, where West Indies' hitting ceiling is higher.

So Bangladesh's route to winning the first ODI is not aggression but sequence: protect wickets for 15 overs, cut dot balls between overs 20 and 40, and do not need more than 70 in the last ten.

Contrarian: 'bounce back' is a story, not a metric

The weakest phrase in the brief is the headline itself — 'a chance to bounce back after a tough UAE tour'. Bounce back has no measurable form. If Bangladesh make 260 and lose by 20, was that a bounce back? In analytical language the question is empty until you name the metric: powerplay wicket cost, middle-overs dot percentage, or death-over economy. I will keep the three separate rather than blend them into one index.

The second failure is format contamination. A Test-series claim inside an ODI preview is the same category of carelessness as applying T20 strike-rate logic to a Test first innings. Winning a Test series and winning an ODI are different units; using one as evidence for the other works in the language of momentum and fails in arithmetic. It is also where the internal contradiction sits. If that line is a typo, correcting it is the source's job. If the sheet belongs to another cycle, the entire document's timing is suspect. Either way the reader should be told, not quietly spared.

The third point is the one most often skipped: correlation is not causation. A good powerplay does not cause a win; the toss and the dew may be producing both. Mirpur has historically been easier to bat on second, and if that holds, a strong powerplay becomes a marker of the side that won the toss rather than proof of its strength.

And one thing that is genuinely not in my dataset: eleven players' temperament, October humidity as opposed to May heat, a fast bowler's fourth over, and the captain's call that never makes the table. I will not fill those columns with guesses. I will record that they are empty.

Takeaway: a public forecast, before the first ball

I am logging my projection now so it can be graded later: if Bangladesh lose no more than one wicket in the first 15 overs and keep their dot-ball share below 40 per cent at the 25-over mark, they will be in a winning position — regardless of how modest the score looks at that moment. If dew arrives and the toss favours the side batting first, this forecast is void and I will rewrite it rather than defend it.

The real question before the first ball on 28 October is not whether Bangladesh bounce back. It is which column gets filled on the scorecard — the year, or only the date.