Empty Scorecard, Full Responsibility: The Discipline of Absence in Cricket Analysis

The first page of my beat journal always carries an empty box. In 2026, travelling with Bengaluru FC across fourteen away days, I learned to draw that box beside each date and label it 'What I do not yet know'. That season I filed a 12,000-word locker-room diary after a 2-0 win over Mumbai City; Sunil Chhetri's twelfth professional season and the club's eight clean sheets filled its pages. Looking back now, the most useful part was the empty box. I keep the beat from bus seats and locker-room silence, and the first condition of that beat is admitting what I do not know.

Last night a scorecard opened on my laptop with no numbers in it. A match had been played, balls had been bowled, yet the data feed came back empty-handed. At first I blamed the system. Then I understood the question was not about the system — it was about me. When cricket promises a number for every ball, missing data tempts us into the easiest move: filling the blank with narrative. That is the deepest illness of today's cricket media.

The datafication of modern cricket is a small industry of its own. From the handwritten scorebook to ball-tracking, pitch maps, expected runs, field-placement heatmaps and opponent swing angles, every match now generates lakhs of data points. The scorebook was cricket's first immutable ledger — once written, it could not easily be erased; digital verification, review logs and timestamps are extensions of that same idea. In Doha in 2026, while covering Morocco's run to the semi-final, I used Sofyan Amrabat's 12.1 km per match to help casual fans see how a 4-1-4-1 shape protects the back four. The number worked because it was verified. And precisely for that reason I know that cricket does not always give you numbers.

Rain falls. Light fails. Matches are abandoned. At the 2026 Champions Trophy final, India and Sri Lanka — the final in Colombo, then the replay — were both washed out, and the two sides were declared joint winners. There is no analysis of winning there, only a decision. At the 2026 World Cup semi-final at Eden Gardens, India versus Sri Lanka ended in crowd unrest, the result awarded to Sri Lanka, and much of what happened on the pitch stayed outside the record. Cricket keeps teaching us that the result and what actually happened are not the same thing. That gap is where the analyst truly works.

Consider Duckworth-Lewis-Stern. The model Frank Duckworth and Tony Lewis built in the 1990s came precisely because there was no verifiable basis for setting a second-innings target after rain. Steven Stern later updated it. The model is not perfect, and no one claims it is; but it accepts that information is incomplete and still builds an honest estimate inside that incompleteness. That is discipline.

The 2026 World Cup final is a harder example. England and New Zealand — 241 each, a super over, fifteen runs each. Ben Stokes and Jos Buttler batted England's super over; New Zealand's Jimmy Neesham and Martin Guptill answered with fifteen, and Guptill was run out going for the second on the final ball. The outcome was settled on boundary count — England 26, New Zealand 17. That rule still unsettles fans, because on the pitch the two sides were level, yet a technical row on the scoreboard wrote the history. Where the play is level, the inequality of the rule becomes the real subject of analysis — and that cannot be hidden behind a story.

DRS 'umpire's call' says the same thing. Ball-tracking predictions carry a margin of error; how much of the wicket the ball would have hit is an estimated band. The technology honestly admits its own limit, and that admission is what legitimises the decision. For analysts the lesson is direct: what cannot be verified must not be slipped into a decision — it has to be marked separately.

My own method therefore has two rules. First, two independent sources before publication. What I see at the training ground I match against the team manager's or scorer's notes; if they do not match, I write 'unverified'. Second, sensory truth. Locker-room silence, bench talk, warm-up patterns are also data, but I write them only when they are tied to a specific name or time. In the 2026 Goa ISL bubble, during a 1-0 win over Kerala Blasters, I stood forty metres from the pitch; only boots, breath and the fourth official's whistle could be heard. Chhetri would clap toward an absent East Stand before matches — that silence is as reportable as an event, because a verifiable routine stood behind it, and I wrote the routine, not the tears.

Now the hard part. In cricket's information economy the most profitable place is not analysis — it is speed. Live data flows straight to betting companies and fantasy platforms, where one wrong number or an incomplete result can, for even a few seconds, swing decisions worth lakhs. The darkest side of sport's datafication is this direct pipeline — there is no time to verify, because time is money. This is my deepest concern.

Under that pressure, some analysts fill the blank. A weak innings foundation still becomes 'back in form'; a two-match sample announces 'the best of his era'; injury history, age curves and home-away splits quietly drop out. I check such claims by name, and when the basis is missing I write it plainly — there is no more than a two-match sample behind this conclusion. It may read as weak writing; in practice it is honouring the contract with the reader.

There is another trap — star worship. Hanging a story on a big name is easy, but cricket is held upright by invisible people: groundstaff, scorers, physios, managers, bus drivers. In sixteen days in Qatar in 2026 I spoke with twenty-three Moroccan fans and sat with two assistant coaches; none of them made a headline, yet their words were needed to understand the cruelty of the shape. An analysis that erases supporting labour and distant fans is not analysis — it is advertising.

Watching cricket from Bangladesh to India, across a border, means accepting a time gap. In Russia in 2026, the story of Japan's 2-1 win reached readers in Bangalore a night late; my most-read piece was a 1,500-word guide on how an Indian fan could watch the knockouts at 11:30 p.m. IST. The final whistle in Russia reached Bangalore before breakfast — celebration and grief both delayed, both true. Accepting that delay makes an analyst more patient: there is no need for noise about what did not happen; deliver well what did.

So I return to that empty box. When data does not arrive, the honest answer is — 'I do not know yet, and I need two independent sources to know'. In cricket's next cycle, when even more numbers arrive from every match, the real question will be inverted: which numbers can we not verify, and will we let them into our decisions? I don't chase headlines; I keep time with the team — and keeping time means writing the question correctly before the answer arrives.