Empty Tables, Full Stories: Eight Layers, an Evidence Ledger, and the Discipline of Honesty in Cricket Analysis

At 11:42 pm on a Friday, a screenshot landed on my phone. A franchise name, a fee, a foreign player's name, and two words — "done deal". No source, no timestamp, no newsroom logo. I had opened my notebook before I opened the replay; that night I opened an empty table. In all eight rows the analyst had written the same sentence — "insufficient information, cannot assess." Yet around that empty table three stories had already formed: the franchise's "long-term plan", the player's "discontent", and the agent's "power". There is not a single number in the table, but there is no shortage of stories. This scene is a perfect specimen of today's cricket-news environment. A transfer window is an abnormal noise. Retention lists around the IPL auction, the Hundred's player draft, the overseas quotas of SA20 and ILT20, players leaving mid-season in the Pakistan Super League, and the expiry of England's central contracts — all of it creates a din in which the speed of speculation outruns the speed of information. I work inside that din. What I lack is confirmed information; what I have is an endless supply of "according to sources" claims. I grew up in Dhaka, where cricket was first the sound of tape-ball in the alley, then the radio commentary. Now I live in Manchester and write cricket for the British market. The difference between these two worlds I noticed on day one: in a Dhaka adda it takes courage to make a claim, and at a British desk it takes a timestamp. Slowly I understood — courage and evidence are not the same thing. Courage is currency in the adda; evidence is currency at the desk. In this piece I will do three things. First, explain why I arrange cricket analysis into eight layers. Second, show what should and should not be done when a layer has no information. Finally, I will leave a counter-intuitive point — while the industry is busy filling boxes, the courage to leave a box empty is the real professionalism. Context: the notebook before the replay My working habit is simple, though many find it tedious. I open the notebook before I open the replay. In 2026, at seventeen, I began logging referee decisions on a high-school blog. In 2026, at eighteen, as a first-year Broadcasting student in Manchester, I watched all 64 World Cup matches and kept every VAR review in a paper notebook — 29 in total. On June 16, in France versus Australia, Griezmann's 58th-minute penalty was the first World Cup penalty awarded through VAR. That day I logged the camera angle, the referee's signal, and the exact minute. I did not celebrate chaos; I tested whether each decision followed the Laws. That habit taught me that a beautiful analysis without a timestamp is only an opinion. So today I publish no VAR analysis unless I hold a chronological review log and at least one precedent. This has slowed my output but made it verifiable. I made that trade knowingly: reliability in place of speed. I see the record of decisions as a kind of ledger — an immutable book in which every entry is written with a timestamp, a camera angle, and a clause of law. What is written there cannot later be erased; it can only be corrected, and the correction too is written as a new entry. Cricket's VAR log, umpire reports, and match-referee decisions are all pages of such a ledger. The question is: where is that ledger in the noise of the transfer window? The answer is not easy. The noise is itself an industry. Spreading a rumour costs nothing, but it pays — in clicks, retweets, and the authority of an obscure person called "a source". In the economics of the transfer window, the real story never makes the headline. The structure of the release clause, the balance of the wage bill, the shape of the agent's commission, the split of image rights, the terms of the performance bonus — these quiet numbers decide whether a club survives in the competition over the next three seasons. The bigger the headline about a "record fee", the more complex the structure behind it. The analyst who sees only the fee sees a number; the analyst who sees the structure sees a future. The eight layers: the design of an analytical framework I do not compress cricket analysis into a single sentence. I arrange it into eight layers, exactly as an umpire arranges a case file before writing a match report. Each layer answers a different question, and each has its own information demand. Where a layer has no information, I write "insufficient information" and stop. That stop is the heart of this piece. Layer one: format and match. The first question — what kind of cricket is this? Test, ODI, T20, or the Hundred's 100-ball? Without that answer every other calculation is meaningless, because change the format and the metric changes. A batter's T20 strike rate is not his ODI strike rate; a bowler's death-over economy is not his first-session economy in a Test. I have often seen a 150 strike rate celebrated when it came on a small ground, a flat pitch, tiny boundaries, against a weak attack. In this layer I look at the powerplay-middle-death split, session-by-session Test performance, pitch type, weather, dew, the DLS effect, and the role of the toss. Take one example. On July 14, 2026, the World Cup final at Lord's. England versus New Zealand tied, the Super Over tied, and England became champions on the boundary-count rule. The overthrow that ran four off Ben Stokes' bat, and New Zealand's discipline under Kane Williamson — those two moments decided the result. That decision belongs to the layer of rules, not of play — and that is layer five's work. Layer one's job is only to say this: the match was played in a specific format, on a specific pitch, in specific weather, and without that context no number has meaning. Layer two: player technique and data. Here I look at average, strike rate, economy, situational splits (home versus away, spin versus pace, first innings versus fourth), recent trend, and the age curve. But I match every number against a benchmark — the contemporary league, the contemporary era. An average of 40 is good in Tests but nearly irrelevant in T20. This is where I see the most error. Someone takes a player's last three scores and declares he is "back in form", when two of those three came at home and one against a weak bowling attack. Small sample, convenient ground, convenient opponent — when these three meet, the conclusion is not analysis but publicity. I hold one rule here: before any player