A Report With No Numbers That Did Cricket Analysis Its Greatest Favour

It was a quarter past one in the morning. I opened a file on my laptop in the London flat, headed Stage-2 Deep Analysis Report, Cricket Domain. Eight sections. One table after another. And in every cell the same sentence came back: N/A, insufficient information. The only living word in the entire document was cricket_asia.

I have stood in a fan zone on an evening when fifty thousand of us forgot to breathe. Nobody around me asked what happened; everyone asked who did it. The cricket brain reaches for the story first and the evidence much later. That file walked the opposite road. The story was not written, because the evidence never arrived. The analyst who made that call did the hardest thing this trade asks of anyone: he kept his hands still.

The file is the second stage of a two-step research pipeline. The first stage is simple work — taking an article apart. What is the headline, what is the source, what is the central claim, how many information points exist, who is involved, how time-sensitive is it, how good is the sourcing. The second stage runs eight deep dimensions on top of that: format and match, player technique and numbers, team landscape, league and commercial ecosystem, rules and governance, risk, public narrative, and industry transmission.

Stage one came back empty-handed. No headline, no source, a blank central claim, zero information points. What survived was a single classification tag — cricket_asia.

That is where my attention stuck. The tag names a region. It does not name a format. Asian cricket could mean an Asian Cricket Council bilateral series, the India-Pakistan freeze and its neutral-venue arrangement, the IPL or the PSL or ILT20, or a board's selection row. Those four things carry completely different resource arithmetic and completely different risk profiles.

And in cricket, format is the first door. Leave it shut and every other door stays shut with it. A Test average and a T20 strike rate are not the same currency. A batsman's 35 means respect in a Test and a question mark in a T20. Without the format you can read a number; you cannot understand it.

Let me draw you the shape before the ball ever moves — that has been my habit for forty years. But a captain who never received the pitch report sets his field from habit. He keeps a slip, because a slip is always there. That night, the analysis refused to do the habitual thing. It named the failure mode instead: narrative fill-in, the substitution of a familiar story for missing data.

When information stops, narrative starts — and in cricket media the narrative always sells better.

What the report asked for was seven things: the format, the nature of the event, the named teams and players and boards, a time anchor, the venue and conditions, every quantitative claim with its format and window attached, and the identity and grade of the source. All seven are really one sentence stretched out. A number that cannot state its own format is not a number; it is decoration.

The sharper lesson sits inside the document itself. Where it says N/A, plenty of readers will hear 'no problem here'. The report blocked that reading in advance.

N/A does not mean the risk is absent. It means the risk has not been looked at yet.

My own 2026 comes back to me here. Commentating through empty stadiums, I heard for the first time the coach shouting, the pressing trigger being called, the keeper's feet shifting. Much of what I had written for twenty years about a bowler 'finding his rhythm' was crowd noise papering over a gap. When the crowd left, the gap turned out to be mine, not his.

Now the counter-intuitive part. An empty report does not usually reach an editor's desk, and if it does it reaches the bin. Yet this document is worth more than a fluent fifteen-hundred-word match piece, because it did the one thing the industry rewards least: it said 'I do not know'.

The reality of our trade is that the writer who says 'I do not know' loses his panel slot the following week, and the writer who is confidently wrong gets invited back. Fluency passes as competence here, and silence is filed as failure.

The report does have a blind spot, and it is the question I would put first. It assumes the failure happened in the pipeline — that text went in and the parser could not read it. The alternative is that the source article was itself a two-line wire brief, and the deficit belonged to the source, not the parser. The remedies are entirely different: one is a code fix, the other is a source upgrade. The report admits it could not tell the two apart.

So the next time a dazzling figure floats across your screen — his average this series, his economy in this spell — ask one thing first: in which format, over which window. If the answer never comes, knowing the number buys you nothing, because you still cannot understand it.

Every number is a sentence somebody has not finished writing.

And my question stays open: that night, was the pipeline blind, or was there genuinely nothing there to read? Tell me the answer and I will pass it on.