The File With Blank Columns: Cricket's Most Expensive Mistake Is a Document Nobody Filled In
**मुख्य उत्तर:** जब स्रोत से कोई सत्यापन-योग्य सूचना बिंदु न निकले, तो क्रिकेट रिपोर्ट का सही आउटपुट 'शून्य परिणाम' है — यानी दर्ज किया गया यह निष्कर्ष कि विश्लेषण के लिए आधार ही नहीं है। गढ़े गए विश्लेषण से यह इसलिए सुरक्षित है कि शून्य परिणाम सुधारा जा सकता है; गढ़ा हुआ दावा तब तक जीतता रहता है जब तक कोई उसे चुनौती न दे। **मुख्य तथ्य:** - 25 अप्रैल 2008, मोहाली: मैच रेफ़री फ़रोख़ इंजीनियर ने हरभजन सिंह पर 11 मैच और 100% मैच फ़ीस का प्रतिबंध लगाया। - अपील के बाद प्रतिबंध घटकर 5 मैच रह गया; आरोप और धारा वही रही, केवल सज़ा का परिमाण बदला। - मई 2013 आईपीएल स्पॉट-फिक्सिंग मामले में लोधा समिति की 2015 रिपोर्ट ने चेन्नई सुपर किंग्स और राजस्थान रॉयल्स को दो-दो सीज़न के लिए निलंबित किया। - 16 जून 2018: फ़्रांस बनाम ऑस्ट्रेलिया में विश्व कप का पहला VAR रिव्यू कुन्हा के इशारे से ग्रीज़मैन के पेनल्टी तक 82 सेकंड चला। - फ़ीफ़ा ने 2018 विश्व कप में निर्णय-सटीकता 95% से 99.3% बताई; यह आँकड़ा इस पर निर्भर है कि 'निर्णय' किसे गिना जाए। **स्रोत:** Stage-2 विश्लेषण दस्तावेज़ एवं दिए गए स्रोत-सामग्री विवरण (प्रकाशन तिथि दर्ज नहीं); ऐतिहासिक तथ्य सार्वजनिक क्रिकेट रिकॉर्ड से लिए गए हैं। चूँकि मूल लेख का URL और प्रकाशक उपलब्ध नहीं था, इस कैप्सूल में कोई सीआरआईसीएससल्टन डेटाबेस क्रॉस-चेक का दावा नहीं किया गया है। **संबंधित प्रश्नोत्तर:** प्रश्न: अपील पर सज़ा आधी क्यों हो जाती है? उत्तर: कोड ऑफ कंडक्ट का लेवल-4 अपराध सज़ा की एक सीमा-पट्टी देता है, कोई निश्चित संख्या नहीं; अपील पैनल तथ्य की दोबारा जाँच नहीं, उस पट्टी के भीतर परिमाण की समीक्षा करता है। 2013-2015 के त्रिब्यूनल फ़ैसलों की 400-प्रविष्टि वाली तालिका में सज़ाएँ अपील पर मोटे तौर पर आधी दर्ज हुईं। प्रश्न: 'शून्य परिणाम' और 'नकारात्मक निष्कर्ष' में क्या फ़र्क़ है? उत्तर: नकारात्मक निष्कर्ष कहता है कि दावा जाँचने पर ग़लत निकला; शून्य परिणाम कहता है कि जाँचने लायक़ आधार ही नहीं मिला, इसलिए कोई वर्डिक्ट नहीं सुनाया गया। प्रश्न: फ़ीफ़ा का 99.3% सटीकता आँकड़ा क्यों विवादित माना जाता है? उत्तर: क्योंकि प्रतिशत का भाग (denominator) तय करता है कि किसे 'निर्णय' गिना गया; भाग जितना बड़ा, सटीकता का आँकड़ा उतना आसान हो जाता है। इसी सिद्धांत से क्रिकेट में DRS और ओवर-रेट के आँकड़े भी जाँचे जाने चाहिए।
At about eleven at night a file opened on the wire desk. The headline was there, the byline was there, the date was there, and every section heading sat neatly in place — 'One-sentence summary:', 'Author's stance:', 'Core argument:', 'Information points:'. Under every heading, blank space. Not a single theory, not a single date, not a single name. Everyone on that desk knew no story was coming out of that file. Everyone on that desk also knew that if we quietly dropped it into the pile marked 'low-value item', nobody would ever notice.
The most expensive mistakes I have seen in cricket are exactly this — a blank column that everyone assumed had been filled in. The question is not what was in that file. The question is what the correct call on it was, and how often we have got that call wrong.
This piece is not about that blank file. It is about the clause that applies when such a file arrives — the clause that in cricket always gets skipped on page forty-seven, where nobody reads.
Let me be plain, because a reader is entitled to know what he is reading. The material handed to me for analysis had no title, no source, no format, no team, no player, and zero information points. Writing a match report from it was impossible without inventing one. So this is not a piece about a match. It is a piece about the trade I have practised for thirty-four years: reading documents, and deciding what the absence of a line in a document actually means.
A match referee's report is the same kind of file. It has a column for the charge, a column for the clause — the level under the Code of Conduct, the article, the sub-article — a name for the panel, a quantum for the sanction, and a route for appeal. Those four things make a report a story. Everything else is anecdote. I learned that in 2026 and I have never gone back.
The same two-desk process now runs behind every major cricket outlet. At the first desk sits the person who extracts facts from the source — dates, scores, names, numbers. At the second sits the person who reads them, joins them, and draws meaning. If the first desk comes back empty, the second has nothing to read. At that point it has two options. It can say nothing came through, or it can fill the gap from general knowledge and hope nobody catches it. The first is professional. The second looks better for a night and destroys everything over a year.

There was a pattern in the file that bothered me most. The headings were populated; the values were not. That does not happen by accident. A system that refuses to read an article still lifts its title and its source, because those sit at the top of a page, not in the body. A missing title suggests the body text never arrived at all — a paywall, a JavaScript-rendered page, a geo-block, an encoding failure. The distinction matters enormously, because 'the article was thin' and 'the article was never retrieved' have entirely different remedies. In the first case you drop the story. In the second you re-order it.
I have a cricket parallel for that difference. Suppose a match referee files a report with the charge column left blank. No clerk reads that as 'no charge'. The clerk reads it as 'no footage'. Those are not the same thing, and only one of them closes the case.
Now to the archive where I learned all of this.
25 April 2026, Mohali. Mumbai Indians played Kings XI Punjab, and Harbhajan Singh slapped Sreesanth. It was six weeks into the IPL's first season, and on our London wire desk I was the only reporter who had read the forty-page IPL Code of Conduct end to end. Match referee Farokh Engineer filed his report: eleven matches and 100 per cent of the match fee. Harbhajan appealed. The sanction came down to five matches.
I sat through both hearings, and that was the day I understood that the second story is better than the first. The first story is: a man hit another man and got punished. The second story is: the charge stayed, the article stayed, the panel stayed — only the quantum moved. The appeal was not a retrial of fact; it was a review of quantum. And quantum reviews turn on how much discretion a clause grants. The Level 4 offence under the Code of Conduct supplies a band, not a number. A panel sitting inside that band exercises judgement. So the real story was never eleven becoming five. The real story was that eleven could become five, and nobody had written that in advance.
On the field it changed one thing: Harbhajan sat out five matches, the tournament carried on, and for three weeks nobody asked why a sentence already announced had been halved.
Five years later that habit took me to a spreadsheet. In May 2026 I was in Mumbai when Sreesanth, Ankeet Chavan and Ajit Chandila were arrested in the IPL spot-fixing case. For the next two years I read the documents almost nobody opened — the Mudgal Committee findings, and the Lodha Committee's 2026 report that suspended Chennai Super Kings and Rajasthan Royals for two seasons each.
I built a four-hundred-entry spreadsheet of tribunal outcomes. The columns were charge, panel, sanction, appeal result. When the table first laid the rows out end to end, the number was plain: sanctions fell by roughly half on appeal. That was not the story of one case. It was the story of a structure in which a first verdict was almost never final.
And here I have to concede my own spreadsheet's blind spot. It recorded outcomes; it did not record who appoints the panel. Half a sanction is a number. A panel's composition is a secret, and secrets do not enter a spreadsheet. Pressure, workload, selection politics — none of them had a column. So I still use that table today, but I use it with a label saying it is incomplete. What the sheet knows is true. What it does not know may matter more.
Hence the line I keep on the desk: the spreadsheet did not lie; the ban sheet did.
18 June 2026. The tribunal spreadsheet had made me insufferable enough that I went to Russia that summer, sat in front of a monitor with a stopwatch, and waited to find out how long the first World Cup VAR review actually took. France against Australia. Referee Andrés Cunha signalled, watched the monitor, gave the penalty, and Antoine Griezmann scored. Eighty-two seconds from signal to goal. I filed a protocol explainer that night, then eleven more, one per round, while FIFA claimed decision accuracy had risen from 95 per cent to 99.3 per cent.
There are two ways to read that claim. You can accept it. Or you can ask what the denominator is — every percentage has a denominator, and the denominator is the biggest claim in the sentence. 99.3 per cent means something different if 'decision' includes every offside flag, every throw-in, every time a referee blew. The larger the denominator, the easier the percentage. That is where the line I keep came from: I counted the seconds the officials never counted.
That practice has a limit too. Three beats are enough for frame forensics: signal, monitor, verdict. If a fourth frame does not change the outcome, it is a hobby, not a paragraph. I apply that rule to myself, not to anyone else.
Back to the blank file. I ask any document three questions, and I asked all three that night. Which paragraph is actually making a claim? Where is the basis for it written down? And if there is no basis — is the correct output 'no', or is it 'don't know'?
Here is the core of it, and it is less obvious than it sounds. A negative finding and a null result are not the same thing. A negative finding means: I looked, and the claim being made does not hold. A null result means: I tried to look, what arrived contained nothing worth claiming, so I am not issuing a ruling. The first is a verdict. The second is a logged entry. Cricket conflates the two constantly.
Any analysis written on a report containing zero information points is not analysis — it is fabrication. And fabrication is more dangerous than an empty page precisely because it looks tidy. A blank tells the reader there is nothing here. A filled-in blank tells the reader there is something here, and the reader has no way of knowing it was invented. A null result can be corrected. A fabricated claim cannot — until somebody challenges it, it wins every time.
There was one small technical detail I could not ignore. The document carried a regional sub-label instead of the plain sport label. That will read as trivial to most people. It is the same error as a miscalculated over rate: one over wrong carries forward for twenty matches. When the label is wrong, everything downstream lands in the wrong place, however well the work itself was done.
Now the argument against this entire piece, stated fairly, because it is easy to ignore and wrong to ignore. The mainstream reading runs like this: a news desk does not exist to stay silent. The reader wants copy by morning. If the file has no basis, an experienced reporter can supply context from what he already knows — precedent, history, the general shape of the matter — and that is better than a blank. That argument is sound, and I accept it fully. A desk that files nothing every night is useless. I have watched such desks close.

The answer is that context and premise are different things, and the line between them is erased by a single word — 'roughly'. Context is legitimate when it is named: 'in 2026 the Lodha Committee suspended these two teams for two seasons.' That is a verifiable fact and I will write it any day. A premise is fabricated when it is unnamed: 'this player's strike rate has dropped across four matches.' If I did not watch those four matches, I have no right to that sentence, however plausible it sounds. The first is context. The second is manufacture.
There are two places where the consensus still holds and I should say so. First, context is not padding, it is a duty — leaving out the 2026 timeline for a reader arriving cold is carelessness. Second, speed matters. In a live result, a fast correct scoreline beats a slow perfect essay. The discipline of the null result applies to claims, not to facts you already hold.

There is a third thing that troubles me, and it comes from outside cricket. What happened on the football pitch is what happens to every system: a structure copied without being understood becomes ritual within two seasons. Mid-table sides run a gegenpress as though they picked it up from a video — with the right design and the right coaching it works. Running a full pipeline over an empty file is the same ritual. A two-desk process without a status flag becomes a ritual of output, not a check.
So what is the clause I want read first next time?
I know its name in one word, and it is not written in any Code of Conduct or on any field. It sits in the column between the first desk and the second, the column no form currently contains: status. Complete, partial, or failed. A broken line and an empty story look identical on a desk. They are not identical.
The next time a file arrives blank, the question should not be 'what does it say' — the question should be 'was it read at all'. Because if an entire tournament record, an entire panel's ruling, and an entire story's future hang on who filled in which column, then which column do we read first next time?
