Eight Sections, Forty-Seven Blank Cells, Zero Information Points: How Not to Write a Cricket Report When There Is No Data

The file opened, and within thirty seconds what it showed was eight sections — format and match, player technique, team landscape, league commerce, rules and governance, risk matrix, public narrative, industry transmission. A table inside every section, cells inside every table. I counted: forty-seven cells carried one identical sentence — "N/A – insufficient information". Not one date, not one venue, not one player's name. And printed above all of it, eleven times: "Confidence: High."

Full confidence about something that does not exist.

I have done this work for forty-two years, and the press box teaches exactly one habit: fill the gap. The deadline is breathing, the editor is waiting, and whatever you do not know gets wrapped in handsome sentences. In a corridor in November 2026 I made myself a rule: no page number, no figure, no named source — no copy. This file is that rule's examination, and there is only one way to pass it: to write that the report cannot be written.

Understand the machinery first, because nobody ever explains it to the reader — and that same reader consumes its output every morning. Every cricket report travels in two stages. Stage one pulls information points out of the source material: what the headline is, which entities exist — team, player, event, league — what the core claims are, how time-sensitive the story is, how reliable the source is. Stage two builds eight analytical dimensions on top of those points.

Here stage one came back empty. No headline, no information points, no entities, no core claim, no time-sensitivity, no source quality. So stage two is arithmetic performed on zero — forty-seven cells filled with "insufficient information." And let me say plainly: that is an honest document. It invented nothing. A system that has nothing and says "I don't know" is a hundred times better than a system that has nothing and manufactures a Kevin Pietersen bid.

But a refusal is not a report, and that is where the reader starts losing — because refusal does not sell. When the machine returns empty, two doors open: the desk decides nothing happened today, or someone offers to fill it in. The second door is chosen far more often. So this blank file is not a technical glitch; it is a photograph of the moment cricket journalism meets its oldest temptation.

Now the audit. Better than listing what the blank file lacks is listing what the files that worked actually contained.

November 2026, Mumbai. Forty-one accredited journalists waited outside the BCCI disciplinary committee. I was the only woman in the room where the bans were read — the hearing itself was closed to us — and I filed nine hundred words from a corridor, working off a photocopy I had taken two weeks earlier: pages 44 to 61 of the CBI report, the Cronje phone transcripts, the amounts in rand, the dates. Mohammad Azharuddin got a life ban; Ajay Jadeja got five years. Two rival reporters filed the same story that evening with the wrong number of players named. Mine held.

February 6, 2026, Goa, the second IPL auction. I had spent three weeks building a source inside one franchise's war room. At 3:12 p.m. I posted that Bangalore would take Kevin Pietersen for $1.55 million — ninety seconds before the hammer, and at exactly that figure. Minutes later Andrew Flintoff went to Chennai for the same $1.55 million. I had under a thousand followers; by next morning I had four thousand, plus an angry call from a rival who had the right number and published it four minutes late. The bid was in my notebook ninety seconds before the feed, and those ninety seconds were the whole of my capital.

July 23, 2026, Lord's. The Women's World Cup final: seven women among roughly a hundred and twenty accredited media. India were 191 for 3 in the 43rd over, chasing 229, needing 38 from 45 balls. Then seven wickets fell for 28 runs across twelve overs and Anya Shrubsole finished with 6 for 46. The press box blamed the 44th over. Seven women were in the press box, and nobody blamed the over — I had counted thirty-one dot balls in the last twelve overs and wrote that the collapse was a strike-rotation failure, not a nerve failure.

January 19, 2026, on air at 4:30 a.m. from Bangalore. India were chasing 328 in Brisbane and had lost six for 186. Washington Sundar and Shardul Thakur put on 123 for the seventh wicket — neither was in anyone's first XI. Thakur took seven wickets in the match, Shubman Gill made 91, Rishabh Pant finished 89 not out, India won at 329 for 7, took the series 2-1, and used twenty players across the tour.

All four files had one thing in common: the first line carried a date, a venue, or a figure. The blank file's first line carries none of them. What it carries is formatting — a six-row risk matrix, five-star ratings, eleven declarations of high confidence. Format is not evidence. Being entirely certain that something is absent is the easiest certainty available; it requires verifying nothing.

Over the last few years I have seen more coloured charts on the field than players — charts that look like proof and are not, because they bury a player's real role inside the team's structure. This file is that disease in a different costume. Writing "insufficient information" forty-seven times is honest and it is also a template, and a template sometimes wears the costume of truth. When the first link in the information chain is empty, the analysis at the eighth link is literature, not journalism.

A cricket report needs at least one cricket column: which way the seam pointed, what the net run rate was, in which over the follow-on was decided, where the bowler's length landed in his third spell. This file has none of them, because it has no match. That is the real story: "insufficient information" is a valid answer, but it is not a report, and selling the two on the same sheet is the most expensive mistake on the desk.

Now the part I write every time and people resent: how could I be wrong?

First — perhaps this is not a crisis at all. Perhaps the source material really was empty: a stub, a bad paste, a test. In that case the system worked correctly and my entire argument is a fire with no document behind it. My rule runs both ways; on the day the ledger supports consensus I say so out loud. Here the ledger says: I do not know what the original article was.

Second — and this is the shiniest of my own old traps — I could turn "insufficient information" into a sermon about falling standards. That would be unsourced outrage in a lab coat. I have no page number to prove the desk is deteriorating; I have one blank sheet, and a blank sheet testifies against nobody.

Third — forty-seven N/A cells can become a habit. A desk that answers every question with "insufficient information" eventually publishes nothing, and silence is also a failure of accountability. You learn to count the silence before the vote; treating silence as the evidence is a different sickness, and the press box is full of it.

So the forward call, with a condition rather than a date: within the next tournament cycle this file takes one of two roads. Either it is re-run against the source text and its first three cells show a date, a venue and a name — or the same template starts producing fluent copy in identical formatting, with no evidence in its first line. Telling them apart is cheap. Look for a date, a place or a figure in the first three lines of any report. If all three are missing, the rest of the sheet is unverified, no matter how many stars are printed on it.