The Testimony of a Blank File: Why Verification Outruns Speed in Cricket Reporting

The lamp on my Pune desk was still burning at twenty minutes to three in the morning, and the file open on the screen was the one that was supposed to hold the night's match. The file arrived. It arrived empty. Where the scoreline should have been there was a small dash; where the format should have been there was 'insufficient information'; and where the players' names should have been counted, the list was bare. I made tea, then made it again, and then did what I have done for forty-eight years — I counted the calls the way I count overs.

The argument on the desk that night was a single argument: can a blank file be made to look full? Someone said, guess the format, it will be T20. Someone said, the tag reads 'cricket_asia', so attach a team from Asia. I asked three questions — in which over, at which ground, at what score? All three hung in the air. That night I wrote what could be written: a documented null result, plus a note on what would be needed to fill it.

This is not a new situation for me, only a new pipe. In 2026, when I joined Mid-Day, news still travelled on carbon paper. The scorer's pencil passed a number to a typist's desk, and if a light impression fell in between, a half-formed digit got printed. The rule even then was the same — a number that the pencil had erased does not enter the copy. Later came the All India Radio bulletin, where an entire innings had to fit in eighty words; then Doordarshan, which gave you pictures but no score in the headline; then the Cricinfo desk, where ball-by-ball data arrived before feeling did. The machinery changed every decade; the question did not — is the paper that came off the source true?

In 2026, when the season was played in empty stands and the IPL sat in the UAE from September to November, I built 'The Empty Stand' — twenty-four recorded conversations with the people a stadium actually employs: a groundsman at Gahunje, a vada pav seller from the old Pune club circuit, a ticket clerk, a Ranji scorer. I set one condition for that series: I will not form an opinion on anything I have not recorded. The empty stand is the loudest witness, and that night my file resembled one, except that where the sound should have been there was a dash.

Now read that blank file in the language of cricket. Format is the first gate, and it was shut. A Test opener is measured on average and balls faced; a T20 finisher at a strike rate of 180. The same player is a different man in each. Without a fixed format, every number written would be a vague sentence, not a statistic. The second gate is role — opener, anchor, finisher, pace, spin, all-rounder, keeper. Until role is settled, it is not even settled which metric matters. The third and largest gate is home ground. Of all the wrong forecasts I have watched over four decades, more than half were wrong because someone kept pitch, weather, dew and travel fatigue outside the count.

Which is why the most honest line in that night's file was 'insufficient information'. A blank verification sheet is not the story losing; it is the story refusing to be invented. A cricket report carries three things at once — the result, the process and the receipt. The result comes from the scoreboard; the process from the ball-by-ball ledger; the receipt from the testimony of where and when it happened. That night I had none of the three. To have begun writing would have been to cheat myself.

Remember the Hyderabad night of 21 May 2026. Mumbai Indians defended 129 and won by one run. I had the receipt for that result — I had watched the home leg from the Gahunje press box, the team had taken the captaincy from Mahendra Singh Dhoni and given it to Steve Smith in February, and an entire season the crowd had argued with its own city. I filed 4,200 words in thirty-six hours because beneath every word sat a date, a ground and a witness. A captain benched is still a captain in the story. But a captain whose name exists only in a blank file is not a story, he is a guess.

In Rostov-on-Don on 2 July 2026, Japan lost 2-3 to Belgium to a goal in the 94th minute, and I stood in the concourse watching supporters bag their own litter. There too I had verification — the minute, the score, the city, the date. Out of that discipline I made myself a rule: one observed image per column, introduced late. When the file is empty, that image does not come either, because an observed thing has no substitute.

Treating a regional tag as evidence is the oldest habit in this trade. See 'cricket_asia' and someone will say — it must be India-Pakistan, or the BCCI-ICC revenue dispute, or the Asia Cup. Those are hypotheses, not findings. The convenience of turning a hypothesis into a finding shows up in tomorrow's headlines and dies in a correction line the day after. One thing I have watched across a career: the scoreboard remembers what the stands forgot. The rumour the stands sway to today is the one they drop tomorrow, and by then it has already occupied a corner that belonged to real work.

This is why I treat a blank file as evidence rather than weakness. Look at the commercial frame and every cricket number hangs off a receipt — auction price, retention list, Right to Match, NOC, central contract, broadcast rights. Not one of these can be written without a source. The day we start reading a player's price separately from his play is the day we begin mistaking traffic for strength. That night my file held no price, no list, no contract — only a blank space.

The largest risk in the whole episode was procedural, not sporting. The danger was not who won the match; the danger was a blank file reaching another desk labelled 'analysable material' and someone there filling it with a plausible-sounding cricket tale. In Asian cricket that risk is specific, because here cricket is not only a sport but a language — and a language fills its blanks fastest.

There is a counter-side I want to state plainly. The digital cricket economy rewards the first version, not the corrected one. Nobody reads the two-line correction under the morning headline. So the loud take settles into collective memory while verification is benched. A benched analyst is still an analyst in the story, but nobody counts him. I think this is our profession's real bias — verification is slow, and therefore looks defeated. Yet every final leaves a receipt in the language of almost, and a report that holds no receipt becomes its own rebuttal by the next morning.

The next news cycle will arrive, and the file will be full. The question then will not be who wrote first, but who was standing in the queue outside the stadium at that hour. In my cupboard I keep a carbon copy from 2026 on which not a single letter printed — the impression fell too light. I never threw it away. It remains the most useful page I own, because it says news is not what can be printed; news is what has been verified and then printed. That night's null result made no headline. But if another desk must one day decide whether to fill a blank or leave it open, remember this — the man in the queue does not pay for a guess. He pays for testimony.

This analysis rests on public information and the source material available. In this instance the source material contained no analysable cricket fact, so the conclusion has been recorded as a documented null rather than filled with speculation. It is offered for sports-information reference only and forms no part of any betting advice. Sporting outcomes are highly uncertain; please treat the analysis rationally.