The Spreadsheet Had Already Written It Before the Draw: Bangladesh Lost to Fixtures, Not to Nerve

February 7, 2026. Thirteen days before the first ball of the Champions Trophy. In my house in Barishal, the laptop was open on the work table, a half-finished cup of cold tea beside it, and on the screen a file named BAN_CT25_collapse_v3.xlsx.

The last row of the sheet already said it that evening: Bangladesh will not get out of the group, and none of the three likely causes is 'mentality'.

Thirteen days later, 228 all out against India in Dubai. Four days after that, a five-wicket loss to New Zealand in Rawalpindi. On February 27, the Pakistan match washed out. One point. Tournament over.

The screenshot has travelled a fair bit since. I could strut about it, but I won't, because of the three variables I flagged as causes, only one got a clean test. The other two never made it into the laboratory — the rain got there first.

Passing off an incomplete experiment as complete proof is the biggest fraud in cricket analysis, and a large share of columns written about Bangladesh cricket rest on exactly that fraud.

The story everyone is telling together

The talking points after the Champions Trophy were almost identical. 'The batters can't absorb pressure.' 'No courage in the middle order.' 'The captain can't set a field in time.' 'Factions in the dressing room.' 'Tiger spirit exists on paper, not on grass.'

I am not waving these away. They are not lightweight claims, and many who write them have watched more cricket than I have. So let me do the opposite — I will write the mainstream argument in its strongest possible form first.

The strongest form runs like this. Cricket has moments where skill is level and the difference is made by decisions. The 2026 World Cup defeat to Afghanistan, the last-over thriller against Nepal at the 2026 T20 World Cup, the two-wicket loss to New Zealand in the 2026 World Cup — in all three, Bangladesh were ahead on paper and still lost. In those matches, match temperament is a real variable, and the people pointing at it are not pointing in the wrong direction.

But I run a base-rate check, because that is what numbers are for — proving a feeling true or proving it false. Since the 2026 Champions Trophy semi-final, Bangladesh have played six ICC events: the 2026 World Cup, the 2026 T20 World Cup, the 2026 T20 World Cup, the 2026 World Cup, the 2026 T20 World Cup, the 2026 Champions Trophy. Group stage or Super 12 exit in all six.

Across those eight years there have been four different captains. Three different head coaches. Two formats — ODI and T20I. Venues in England, Australia, India, the USA, Pakistan and the UAE — seven countries, two continents.

If 'nerve' were genuinely the binding constraint, identical outputs would not survive such wildly different conditions. A variable that produces the same result under every condition is not a variable. It is a description. And when you sell a description as a cause, decisions do not change — only blame gets distributed.

I opened Excel to check a hunch, and a religion died

A word about the logbook. I started writing match reports on a page called BDCricTeam in 2026. In 2026, building a homebrew xG model in Barishal, I worked out that the market for description was big but the price was low. Since then every column opens with a falsifiable claim, never an observation. By December 2026 my own match log had crossed 1,400 matches, with a separate tab for Bangladesh's ODIs and T20Is and another for matches between the then top-eight sides.

Those tabs are where I picked three variables before the Champions Trophy. Anyone can check the picking, because the sheet was public and timestamped.

Variable one: the cost of venue relocation. Under the hybrid model for the 2026 Champions Trophy, two of Bangladesh's three matches were in Rawalpindi and one in Dubai. Dubai to Rawalpindi is roughly 2,200 kilometres, one time-zone change, one flight, and a temperature swing from a February low to the mid-twenties.

From my log I pulled every ICC event since 2026 in which Bangladesh played in two countries inside a ten-day window. The sample is small, and extracting an ODI run-rate difference from a tiny sample is close to measuring shadows in an empty room. I said so at the time — I assigned this variable a 'low' confidence level, not even 'medium'.

The argument survives anyway. When a side spends a week planning for India's spin-pace mix on a flat Dubai deck, four days later it needs a different plan for New Zealand's seam attack on a bouncier Rawalpindi surface. Preparation hours shrink, practice sessions shrink, and the rest-and-rotation maths for senior batters goes crooked.

Variable two: the middle-overs run-rate ceiling. This was my central hypothesis, and the only variable the rain could not spoil. In Dubai, Bangladesh were 228 all out in 49.4 overs. In Rawalpindi, 236 for 9 — a full fifty overs and still no 250.

In my log, from 2026 to 2026, Bangladesh's run rate against top-eight bowling between overs 11 and 40 sat inside a fixed band. I am deliberately not printing the exact decimal here, because the number is public with its timestamp and anyone can open it and check. What I will say is where the band sat: below the average of the four semi-finalists of that period, and below the tournament average.

What does that mean? It means Bangladesh's problem was not at the top, and not in the last five overs. It was in the middle thirty, where a match is slowly decided — where spinners bowl dots and batters rotate strike while telling themselves they are 'waiting'. The middle-overs run rate was the altar, and my spreadsheet was the knife at it.

Variable three: the weight of the structure. At the start of 2026, Bangladesh's ODI middle order carried two batters over 35, both built on a specific tempo — see the ball, bat time, extend the innings. That model was magnificent on 2026-18 pitches. On the 2026 surfaces in Dubai and Rawalpindi, where the baseline was 280, its hidden cost surfaced: the set batters bat time, and there are no wickets left in hand for the last ten overs.

And this is where the cleanest evidence of the whole Champions Trophy is hiding, and almost nobody talks about it properly.

In Dubai, against India, 24-year-old Towhid Hridoy scored a hundred. First major tournament of his ODI career, India's attack, a Dubai pitch — in the worst possible conditions, the youngest batter in the side held. Bangladesh still stopped at 228 in 49.4 overs.

This is not the story of Sisyphus. This is a systems diagram. If the team's problem were 'losing nerve in big matches', the least experienced man in the XI would have crumbled first that evening. The opposite happened. A young player produced the hardest innings of the match, and the team still failed to reach a score that was defensible on that pitch. Only one explanation survives — the match was not lost inside one man's head. It was lost inside the structure of the innings.

Here is the bitter part of my own argument. Hridoy's innings was not a problem for the opposition, because the tempo of the men at either end did not match his. A 75 strike rate on one side, a 95 on the other — the collision of those two speeds burns a hundred balls. In international ODI cricket, a hundred balls is roughly fifteen to twenty runs, and that was exactly why India were never under pressure in the chase.

Where I could be wrong

Now let me turn the knife on myself, because an accountant who will not open a ledger against his own name is not read by anyone.

First objection, and it is against my own model. I published a prediction built on three variables, and only one of them was ever tested. The Pakistan match was rained off, so 'cost of venue relocation' was never tested — the third match never began. Which means two-thirds of my model is inference, not evidence. Many of the people who shared the screenshot forget that my falsification conditions were timestamped, and that not one of them was met.

Second objection, more uncomfortable. At the 2026 Champions Trophy, Bangladesh reached a semi-final — under broadly the same structural conditions. Same board, similar fixture load, similar selection philosophy. Yet the output differed. So my model explains six of eight years and cannot reconcile the seventh. That unexplained residual is precisely where player agency lives, and there is no way around admitting it.

Third objection, about spreadsheet theatre. At the bottom of my sheet I listed confidence levels — low, medium, high. If someone doubles the weight on the middle-overs variable and reruns the model, the output does not change. But if someone drops the 'role of experienced batters' variable entirely, the model keeps Bangladesh in the tournament. In other words, my result is not a decision of the model. It is a framing decision inside the model. I do not enjoy writing that, but it is true, and anyone who reads me has the right to demand it.

Fourth objection: I am drawing national conclusions from a single tournament. Two of Bangladesh's three Champions Trophy matches came against top-eight sides and one was washed out. Two innings of tempo cannot explain eight years of culture. I am not doing that — I am doing the reverse. I am saying that anyone who explains two matches with eight years of culture is standing on ground exactly as shaky.

The ledger after the sheet

February-March 2026, the T20 World Cup in India and Sri Lanka. I do not know any result and will not pretend to. But I am registering now, because an opinion without registration is not an opinion — it is a comment.

Primary prediction: Bangladesh will not reach the Super 8 at the 2026 T20 World Cup.

Supporting condition: between overs seven and fifteen, against Full Member bowling attacks, Bangladesh's run rate in that tournament will stay below 7.5.

Falsification condition, with a date: if Bangladesh reach the Super 8, this column is false, and I will write a post-mortem the following week and publish the sheet — which variable was wrong, which should have been dropped. No explanatory spin.

In cricket, 'nerve' is a convenient word. It lets you blame the captain in the morning, the selectors in the afternoon and the board at night, and still get dinner on time. But the numbers do not go to the kitchen. The numbers stay, and they say that if a team has failed in the same place for eight years, winding the clock forward an eighth time will not help — you have to open the spring.

The question, then, is not when Bangladesh will stop being afraid. The question is whether someone, looking at the next ICC event's fixture table and the age profile of the squad, can write the result down before the first ball. If they can, we have spent eight years balancing a ledger named culture that was never the right account.