Format First, Player Second: A Notebook Method for Reading Asian Cricket Data

Chittagong's Zahur Ahmed Chowdhury Stadium. An evening match. Rain arrived, then stopped; the game was reduced to 20 overs, and the target shifted under the Duckworth-Lewis-Stern method. On the press-box screen, beside a batter's name, a number appeared — a strike rate of 142. The colleague beside me asked, "He's in form, isn't he?" I did not answer. I opened my notebook and wrote a question instead: 142 in which format? A T20 strike rate of 142, an ODI strike rate of 142, and a Test strike rate are the same number but three different realities.

For years I have kept one habit. Before a match, on the first page of my notebook, I draw three boxes — format, venue, sample size. The scorecard comes much later. Because if the format is not fixed, any number in cricket loses its language. Most of the faulty analysis I have seen in Bengali cricket media over the past decade was born in that single gap.

When we write about Asian cricket, a trap is always set — we start mistaking a region for a format. "Asian cricket" is a geographic tag, not a format. It contains Test cricket, ODI cricket, T20 cricket, Asian players in The Hundred, the IPL and PSL, the Asia Cup, and pre-season warm-up matches. Each has its own tactical logic, its own data metrics, even its own definition of success.

Take an example. In the 2026 ICC World T20 in Bangalore, India versus Bangladesh: Bangladesh needed two runs off the last three balls and lost by one run. The measure of heartbreak — one run, three balls. Two years later, the 2026 Asia Cup ODI final in Dubai, on September 28, 2026: India won by three runs. Same rivalry, same two teams, but an entirely different measure of defeat. Three runs across 50 overs is a calculation of six balls; two runs off three balls is a calculation of one shot. If we cite both results together and say "Bangladesh always loses narrowly to India," the formats blur — and the analysis is wrong before it begins.

I came to cricket from football, and from there I carried one habit — seeing the field as coordinates and arrows. What football calls the half-space, cricket calls the fielding ring, the bowling corridor, and the geometry of the powerplay. I find the half-space in a notebook before I find it on grass. Asian cricket works the same way — first you fill the format box on paper, then you write the player's name.

My notebook has a rule: before a player's name is written, the format is written beside it. Say a batter has a T20 strike rate of 135 and an ODI average of 40. If someone writes "strike rate 135, average 40 — brilliant form," they have joined two different skills from two different games into one line. A T20 strike rate of 135 asks "how fast," while an ODI average of 40 asks "how consistent." One is a story of intent, the other a story of durability.

Data does not replace the eye; it teaches the eye where to blink. In Tests I watch a batter's first ten balls — footwork, the decision to leave, how much the ball is seaming. In T20 I watch which line he chooses against which bowler in the last two overs of the powerplay, and how he attacks spin in the middle overs. Same player, two datasets, two truths.

In Bangladesh this has a practical side. What a bowler does in domestic cricket must be measured separately when he enters the national side as a T20 specialist. The seam movement of the red ball and the new-ball swing of the white ball are not the same. In Tests a fast bowler is valued by how many overs he bowls for how many runs; in T20 he is valued by how predictable his cutter is in the death overs. With Mustafizur Rahman this difference is clear — his cutter is a weapon in ODIs, and in T20 it is his entire identity. Every broken formation is a confession the old shape could not make. When a bowler drops from Tests to T20, his broken line and length make the same confession — the old discipline no longer holds in the new rhythm.

Look at Shakib Al Hasan the same way. He plays all three formats, but his value is measured differently in each. In Tests he is a left-arm spinner who adds batting depth; in ODIs he is the controller of the middle overs; in T20 he is a power-hitter who can bowl an over when needed. One player, three roles. If someone says "Shakib is equally good in every format," they have said nothing at all — because the format-specific meaning of "good" is different.

With Tamim Iqbal it is even clearer. In Tests he is an opener who absorbs the new-ball movement; in T20 he is an opener who scores in the powerplay. The first is measured by how many balls he survives; the second by how many runs he scores per ball. Same role — opening — but two different jobs. Mushfiqur Rahim's chasing record is his greatest asset in ODIs, because 50 overs give you time; in T20 that time does not exist, so the same mindset becomes a risk there. Change the format and the same skill can turn from asset to liability.

We are now in the transfer and auction season. The fastest-growing thing in cricket news at such times is the story without a named source. In my notebook I keep four tiers for sources: official announcements — from a board, a franchise, or the player himself; reliable journalists who report under conditions of anonymity and whose track record is good; general media who copy from other sources; and traffic accounts who spread rumours for clicks. The weight of a story depends on its tier, not the size of its headline.

Suppose a franchise is said to be signing a foreign pacer. My first job is not to look at the price but at the structure of the contract — is there a release clause, what is the effect on the wage bill, and what are the terms for breaking with the parent franchise. The transfer market is chess played with human pawns and hidden contracts. A story without the contract's structure is not news — it is atmosphere. And you cannot build a team on atmosphere.

In the Bangladesh Premier League auction this verification matters even more, because the money is smaller, so the cost of a wrong decision is higher. You cannot sign a foreign player on his IPL record — because the bowlers he faced in the IPL are not the bowlers in the BPL, and the pitches differ too. Just as we match formats, we must match league contexts. A franchise that builds a team on names alone is buying a scorecard, not a system.

A match can never be understood by watching it once. I watch at least three times — first the whole match, then the bowling spell, then one specific phase. I break an over into pieces. Example — a pacer in the death over. First ball: yorker, dot. Second ball: low full toss, four. Third ball: slower ball, the batter steps out and misses. Something is hidden inside those three balls — the batter was standing back at first, then stepped out. The bowler read it and changed the very next ball.

An over is a sentence; a spell is a paragraph; an innings is a story. If you read only the scorecard, you lose the meaning of the sentence. Beside every over in my notebook are three words — "line change," "length change," "field change." Those three words reveal when the bowler changed his plan, and when he moved a fielder five yards. Without micro-sequence forensics, you cannot see where a match was actually lost.

Inside a spell I look for five things — the direction of swing in the first two overs with the new ball, the consistency of length in the third and fourth overs, variation in the middle overs, the accuracy of the yorker in the death, and finally the change in the batter's footwork. Without separating these five steps, it looks as if the bowler "was in rhythm or was not." Rhythm is not a mystery — it is the sum of five measured steps.

Luck is a real variable in cricket results, and analysis is dirty if it is not removed. Toss, Duckworth-Lewis, rain, home-ground bias — each must be noted separately. On the spin-friendly pitches of Chittagong or Mirpur, a home bowler's numbers must be read separately, because the pitch is familiar — that is a blend of skill and familiarity. Mehidy Hasan Miraz does not reproduce at an overseas flat pitch exactly what he does at home; so his home average and away average cannot be written in one column.

Likewise, you cannot praise the batting in a run-out-decided match, nor criticise the bowling in a DLS-decided match. I tick every risk flag in my notebook — toss, DLS, venue bias, DRS controversy. Until those ticks are in, my verdict hangs. With DRS it is subtler still — a DRS controversy does not just change one wicket; it changes the bowler's plan for the next over. That chain reaction does not show up on the scorecard.

Empty stadiums taught me that silence is just data with no audience. A low-crowd match keeps an identical scorecard, but the context behind it is different. A morning match in Chittagong has few spectators, yet it is exactly where young players get a chance to prove themselves — because there is less light, less pressure, and more examination. Those matches matter to me because the structure becomes visible to the naked eye.

In the same way, an empty dataset is itself information. If an analytical process returns zero information points, it does not mean the game did not happen — it means the process failed. Zero is not emptiness; zero is a signal. I keep a notebook for the spaces that do not exist yet. An empty box is not an invitation to fill it but an invitation to question — why is this box empty?

Here is my contrarian view. Everyone says Asian cricket analysis needs more data. I say the opposite — we need fewer columns and more context. A vast dataset with an empty format box is not vast; it is incomplete. We collect statistics but leave the format, venue, and sample-size boxes blank. Then we reach confident conclusions with that incomplete picture. Systems break before stars arrive. To find why a team loses, look not at a star's performance but at the holes in its system.

My second contrarian point — we assume the India-Pakistan rivalry is format-neutral. It is not. The tactical logic of two teams in a T20 is different from that of the same two teams in a Test. In T20, the powerplay and the death overs decide; in Test, the new-ball sessions and the fifth-day pitch decide. The rivalry is one; the game is different. Someone who refuses this distinction and views two formats through one lens is not watching the game — he is watching emotion.

My third contrarian point — the dominance of star-centric explanation in our media. When a match is won we write "one player won it," and when it is lost we write "he failed." But the system breaks first, the individual later. You cannot judge a spinner by his economy in an ODI unless you see which batter he faced, in which phase, and how the field was set. Whether a Taskin Ahmed spell succeeded cannot be measured by his economy — it must be measured by which over he bowled and what the objective was in that over. An individual's performance is an output; the system is the input. We ignore the input and write about the output.

One more thing must be added — the cycle of expectation. Before a major tournament in Bangladesh, expectation swells, then collapses after a single jolt. This cycle does not always match the results, because expectation is built from emotion, not data. After winning the Under-19 World Cup in 2026, we thought the senior side would advance at the same speed. But age-group cricket and senior cricket are two different systems — the definition of success differs, the pressure differs, and the opponent's maturity differs. If expectation is not built with format and level matched, it is not analysis; it is preparation for disappointment.

Why does this format discipline matter so much? Because cricket's industry runs in three layers — upstream, the supply of young talent; midstream, national teams and leagues; downstream, broadcast and commerce. A format-wrong analysis does not just ruin one article; it creates expectation, expectation creates selection pressure, and that pressure eventually damages a young player's career. This transmission runs from upstream to downstream. So the format box is actually a safety valve, not merely paper discipline.

What, then, should be done? I offer my own habit. At the start of every analysis, fill three boxes — format, venue, sample size. Then verify the tier of the source. Then enter the micro-sequence. Then strip out the luck factors. Finally, write the verdict — but write the condition too: note what information would change it. That written condition is what separates an analyst from a fortune-teller.

In the next match I will watch one thing — whether the format box is filled before the scorecard arrives. If an analyst throws out a number without naming the format, I will not write that number in my notebook. Because a format-less number is not a number; it is a claim — and a claim demands evidence. The question remains: an analysis that cannot even name its own format — how much of the game has it really understood?