Cricket's Trust Ledger: Format, Evidence, and the Chain of Verification

Cricket's Trust Ledger: Format, Evidence, and the Chain of Verification

Hook

In the press box at Mirpur's Sher-e-Bangla Stadium, an analysis report landed in my hands. On paper it looked superb — bold headings, bullet points, "Core Data," "Risk Matrix," "Final Verdict." But beneath every heading the cells were empty. Not a single number, not a single player's name, not a single date. The more complete the report looked, the less it actually said.

That night I wrote in my notebook: between the structure of paper and the substance of information, a bridge is needed, and the bridge is verification. When empty cells are neatly arranged, they stop being empty; they become misinformation. If someone carries that sheet into a meeting, they will believe the analysis is done. Yet there is no fact, no source, no format.

Cricket is now the most data-dense sport on earth. The speed of every ball, the angle of every shot, the duration of every over — all of it is recorded. Yet drowning in this ocean of data, we routinely reach wrong conclusions, because we do not match formats, we do not verify sources, and we mistake an empty report for a complete one. This piece is about those three gaps.

Context

In 2026, at sixteen, while a high-school student in Dhaka, I started a Facebook page called the Dhaka Beat Sheet. I covered fourteen matches of the Abahani Limited Dhaka under-18 side — 1,260 minutes, 87 corners, and the departure time of every bus. Back then I did not realise that this habit of writing down time would later become my entire method.

In 2026 I wrote a 64-match data diary for the Russia World Cup for a local sports blog. I tracked 29 penalties and 22 VAR reviews, then checked each controversial call against FIFA's post-match reports. The France-Croatia final taught me one thing: emotional readings fade, timestamps remain.

But this discipline is harder in cricket, because in cricket the same data carries different meaning across three or four different games. An economy of 3.5 runs per over is excellent in a Test; in a T20 it is nearly catastrophic. The same bowler, the same delivery, changes the entire story simply because the format changed. This is why, in 2026, when I was writing the Mohammedan SC beat in COVID-emptied stadiums, I decided that before any tactical claim I would write down both the format and the source.

I covered eighteen matches in empty stadiums that season. Zero crowd noise. Players' wages delayed by three months. Other reporters chased takeover rumours; I built a timeline from contracts, payment schedules and club statements. Mohammedan finished seventh, but my notebook held exact dates, unpaid bonuses, and absences from the training ground. Those empty stands taught me that silence, too, is data — you just have to know how to measure it.

Core Analysis — Part One: What a Number Means Without a Format

The first step of any cricket analysis is a question: which format is this? Test, ODI, T20, or The Hundred? Because each format has a different structure, and that structure decides which numbers matter and which are merely noise.

Take a pace bowler's Test economy of 3.2. In Tests that is excellent — because in Tests a bowler concedes runs willingly in order to hunt wickets, and the batter wants to survive. If the same bowler keeps an economy of 8.5 in T20, that too is acceptable. But if someone puts the Test 3.2 and the T20 8.5 side by side and declares "this bowler is inconsistent," they are weighing two entirely different jobs on the same scale. This error is very common in Bangladeshi cricket discussion.

I follow a simple rule: before comparing a number, write down its format, its period, and its venue. In Tests the new-ball spell and the T20 powerplay are both "the new ball," but the job is completely different. In Tests the new ball means seam movement and four or five overs of patience; in T20 the powerplay means maximum attack across six overs. The same bowler, the same ball, two different professions.

Consider Mirpur. Its pitch is historically slow and low — heaven for spinners, an examination for pacers. The bounce this pitch offers on the first morning of a Test is nearly halved by the third afternoon. Now, if someone stops at "spin works at Mirpur," they have uttered a traditional claim but given no date. In August 2026, Bangladesh beat Australia by 20 runs in the Mirpur Test — what that specific pitch offered, how the air was on that specific date, must be examined separately. Tradition is a hint, not proof.

When I work abroad — in 2026, sitting in Qatar, I tracked Morocco's seven matches and counted Sofyan Amrabat's 62 ball recoveries — my biggest lesson was this: change the conditions and the reading changes. Morocco's 4-1-4-1 block worked in Europe because opponents could be forced wide; but the same block would produce a different result under different weather and bounce. I refused to call it a "tactical revolution" until the numbers said the same thing across five matches. That patience is the rarest thing in cricket analysis.

Core Analysis — Part Two: The Chain of Evidence

The second gap in cricket analysis is the source. How reliable a claim is depends on how many independent sources stand behind it. I follow a two-source rule: before publishing any tactical claim, I need at least two separate, verifiable sources.

I first learned this rule at the Russia World Cup. There was pressure to write quickly about a controversial VAR decision; but I waited for FIFA's official report. It later turned out that what had gone viral as a "clear error" was within the rules — only the camera angle differed. Had I written at the speed of virality, I would have made a false memory permanent.

This discipline matters even more in cricket, because cricket's data now works like a trust ledger. Every delivery is an entry — ball-tracking, Snicko, UltraEdge all come from separate systems as separate records, which together produce a decision. DRS is in effect a distributed verification system: three independent systems, on the same ball, at the same moment, must reach the same decision. Here lies cricket's real connection to blockchain.

Blockchain does not mean only crypto. Blockchain means a ledger in which every entry is linked to the previous one, and no single party can alter it alone. Cricket's ball-by-ball record now stands on exactly this logic. A match scorecard is not just a list of numbers — it is a verified sequence of events, where each over is linked to the one before. If someone changes one over's account, the whole chain breaks. This is why cricket's fan engagement and ticketing are moving toward blockchain-based systems — because the spectator wants both their ticket and their memory to be immutable.

But here lies a danger. If the ledger is immutable, errors become immutable too. If bad data enters the ledger, it cannot be deleted, only corrected — and the correction must be recorded as a separate entry. In exactly this way, a false claim in cricket journalism, once printed, cannot be deleted; only a correction can be logged, and readers remember who got it wrong.

This is why I verify every traditional claim with a date. "Spin always works at Mirpur" — since when has that been true? The 2026 Australia Test? Some 2026 series? Or has the pitch report changed in the last season? Tradition comforts my memory, but tradition is not proof. The ISTJ temperament rewards the old blueprint and suspects novelty — and in cricket analysis this temperament is often wrong.

Core Analysis — Part Three: The Sound of an Empty Report

The third gap is the most cunning: a report can look complete and yet be empty. The sheet that reached my hands had every cell empty — no evidence, no viewpoint, no source, not even a stated format. Yet the sheet ended in the tone of a verdict.

There is a meta-risk here, one that is not a risk of the game but of the system. If an empty analysis is presented in a fine format, someone downstream will take it as a completed analysis. Someone in a meeting will say "the report is ready," when there is no fact at all. This is precisely the moment where silence and emptiness are not the same thing. Silence is data — it can be measured, it can be interpreted. Emptiness means there is no data — there is nothing to measure.

An empty stadium and an empty report are both zero, but they mean different things. In 2026, in empty galleries, I heard fielders call, a bowler re-lacing his boot, the keeper whispering behind the stumps — that silence was full. But the silence of an empty report is hollow, because nothing happened there to be measured. Miss this distinction and the reporter errs by treating silence as "nothing there," while the analyst errs by treating emptiness as "everything there."

This is why I keep two separate columns in my notebook. One column for verified information, one for information still to be verified. No claim goes into print until it reaches the first column. This discipline is slow, tedious, and often unprofitable — because in a race to publish fast, no one waits for verification. But once a reader catches you having published a false claim, they do not come back.

Contrarian View — Where Everyone Reads Wrong

Outside readers think the problem is a lack of data. Their solution — more data, more stats, more charts. But I have watched for nine years, and the problem is not a lack of data; it is a lack of discipline in the data.

Accumulating more data does not reduce errors, it increases them — if the formats of that data are not matched. Put a Test batting average and a T20 strike rate side by side and you can build as many charts as you like; the conclusions will be all the more wrong. I call this the "volume trap": the illusion that more numbers mean more truth is cricket discussion's biggest trap.

The second contrarian reading: many believe a transfer or auction price proves a player's ability. This is often false. A high IPL price meaning a great international player — this equation has broken repeatedly. Price is set by demand, timing, and auction atmosphere; ability is set by something else — dressing-room chemistry, the curve of development, and a specific role in a specific format. To avoid this error, I return every number to its context.

The third contrarian reading: people assume cricket analysis means prediction. But good analysis does not predict; it defines the limits of possibility. Not "who will win," but "under which conditions a win is possible, and under which conditions it is impossible" — that is the work of analysis. An empty report does not do this work, because it has nothing to claim.

I went to Morocco's semifinal not to predict but to watch — where everyone was using the word "miracle," my data card said otherwise: exactly at which moment the opponent was forced wide, exactly in which over the match's rhythm broke. Use the word "miracle" without matching the numbers and you turn a structured strategy into superstition.

Final Thought — Signals Ahead

What will be worth watching over cricket's next few seasons is where this format discipline breaks. In every series, pitch reports, the dew factor and over-rates — three things — are increasingly deciding results, and all three are routinely neglected in analysis.

I have now added a new column to my notebook — "missing data." The information that should have been there but is not is itself a signal. An empty cell sometimes means "there is nothing," and sometimes means "no one wanted to look." Catch the difference and you will hear the sound of an empty report — and it is louder than any noise.

The beat is not the noise; it is the interval between two balls. And who wrote down what in that interval decides, five years later, who was actually telling the truth. No claim without a timestamp, no number without a format, no verdict without a source.