A Blank Scoresheet Is Not a Closed Case File: The Cricket Data Clause Nobody Is Officiating

Hook

There is a file open on my Bengaluru desk. Where the title should be, it reads N/A. Where the source should be, N/A. Article type: unclassified. Time sensitivity: never assessed. And the one field the whole analysis runs on — information points — is an empty list. Eleven of twelve formal boxes are blank.

This is not a cricket report. It is the output of an automated cricket-analysis pipeline, and the most startling thing about it is that nothing in it is startling. No score, no player, no team, no dispute, no auction figure. Beside eleven boxes sits a polite phrase: "insufficient information, cannot assess."

If that file moves downstream without a label, the desk will read it as "no risk identified." The actual text is "no data supplied." In cricket the distance between those two sentences decides careers. I learned that lesson on the B ground, not in a server room.

Context: cricket already wrote the answer to this question

I have umpired three seasons of Karnataka State Cricket Association league matches on the B ground at M. Chinnaswamy Stadium, on a pitch where the cameras are few and the sweat is plentiful. The hardest question there was never whether the ball hit the stumps. It was: when I have no evidence capable of deciding, what do I declare?

Cricket answered that decades ago, and the answer is the spine of this piece.

Take the old soft-signal protocol. The on-field call stood unless the third umpire had conclusive evidence to overturn it. Read the wording — conclusive evidence. "Not out" was never a finding there. It was a procedural default, not a verdict on the evidence. The ICC later removed soft signals from the playing conditions precisely because audiences kept reading process as verdict. That confusion has now returned, wearing a data jacket.

DRS does the same thing. If ball-tracking shows the ball clipping the stumps within the margin, the announcement is umpire's call, on-field decision stands. Nobody declares that the ball would have hit. The declaration is: insufficient evidence available. Cricket's entire dispute architecture rests on that one sentence.

Now take the IPL final of 21 May 2026. Mumbai Indians won by one run — 129/8 against 128/6. That night I had six camera angles and fourteen frames in front of me, and I had to write a Law 38 run-out commentary. The most honest line I filed was the one I did not write as a verdict: the available angle was not enough to nail the call. The piece drew 300,000 reads in 48 hours and the "Laws & Officiating" vertical was greenlit the following Monday.

At the time I thought I had explained a run-out. Later I understood I had explained institutional honesty. The rulebook said one thing; the replay said another — and I had gone looking for the third answer, the one printed neither in the Law nor in the broadcast graphic.

Core: eleven blank boxes and one unlabelled conclusion

That pipeline file was opened across eight layers. I keep them in cricket's own order of authority, because the chain is the same — format first, then event, then player, then team, then competition, then governance, then risk, then narrative.

It stopped at the first layer. Format was undefined. That is cricket analysis's first and final doorway. The batter with a T20 strike rate of 150 can hold a Test strike rate of 50, and those two numbers measure two different competencies rather than two readings of one. A middle order that is judged by surviving to the sixteenth over in T20 is judged for entirely different virtues in a five-day game. Blending them is like pasting a one-day scorecard onto a five-day match.

The format gate is the first condition; without it every number is decoration, not conclusion.

Layer two — player. No name in the file. Without a name there is no role, and without a role there is no benchmark set. An opener is not measured by a finisher's expectations; a seamer's economy and a spinner's economy compete in different markets. The entity field read: "identify from the information points above." There were no information points above. That is a definitional loop where one empty box cites another.

Layer three — team. No team, so no tier classification. No venue, so the single largest explanatory variable in team performance cannot be applied at all — home spin dominance and overseas pace adaptation being the canonical pair.

Layer four — competition and commerce. Whether the subject was the IPL, the BBL, The Hundred, the PSL, SA20, ILT20 or MLC is undetermined. No broadcast value, no franchise valuation, no salary. Here one standing principle deserves repeating: an auction price does not measure international strength. The bid is evidence of availability and appetite, not of batting. There was no bid in this file, so even that principle sat unused.

Layer five — governance. No rule incident, no DRS controversy, no DLS intervention, no NOC dispute, no central-contract friction. And one line must be written carefully here: an absence of information is not an absence of integrity risk. It is only an absence of data. Drawing a conclusion from silence is the same mistake an on-field umpire makes when he reads a bowler's quietness as innocence.

Layer six makes it explicit. The risk matrix carries six rows — sporting, personnel, commercial, integrity, public opinion, systemic — and every one reads N/A. Then a seventh row had to be added, and that row is the real finding of the whole document: downstream decisions taken on a zero-fact input, risk level: high.

The file had made its own failure its conclusion. In cricket terms that is an over-rate report which states that the match was never played, therefore no slow-over-rate problem was identified.

And the sharpest section is the rating table. Sporting value, industry value, timeliness value, reference value — one star each. Not zero. One. Because the file established something unambiguous: the underlying content is not available. That is itself decision-relevant. The most useful fact in an empty file can be its emptiness — but only when the file declares the emptiness itself.

One field note. I have re-watched a single phase of play forty times so readers only have to read it once, and a persistent error in cricket analysis is believing that more viewing equals more truth. A broadcast feed carries no snickometer, no split-screen, and often not the angle that settles it. Drawing the boundary between what a frame proves and what it merely suggests is the actual work. The pipeline never drew that boundary, so it wrote N/A and fell silent.

Contrarian: the failure is silence, not invention

The comfortable accusation against machine analysis is that these systems invent — that they fabricate statistics and manufacture stories with no basis. It is a flattering accusation, because it saves the analyst from doing any work.

The danger arrives from the opposite direction. Systems do not lie, they go quiet — and silence has no form to fill.

Sports governance is behind on exactly this point. An over-rate report has a form. A match referee's report has a form. A code-of-conduct charge has a form. No cricket administrative document exists in which a box may simply remain empty without anyone having to say so. In its own way this is the blind spot of cricket's most elaborate clause economy. Every transfer window carries a laws-of-the-game problem nobody is officiating — and in this case file that un-officiated decision is the blank box.

Consider thresholds. "Clear and obvious error" has a defined margin. Umpire's call has a defined margin. A wide has a defined measurement. Cricket writes a threshold onto almost everything. Data pipelines have written no threshold for an empty field at all. The letter of the law is easy; the spirit of the law is where careers get decided — and here the letter was never written.

Takeaway: declare it, don't bury it

I am putting this on the record with a date attached so it can be audited later. Before the next mega auction cycle or the next ICC event, at least one major cricket outlet will publish material traceable to an unlabelled, empty data output. If that does not happen, my call was wrong, and I am stating the falsification condition now rather than inventing one afterwards.

The fix is cheap: let cricket lend its own protocol. Just as a third umpire declares insufficient evidence available, every pipeline should declare an explicit error state instead of an empty box. Name it, timestamp it, and mark whether the on-field decision stands. A blank scoresheet is never a closed case file; it is only a scorebook waiting to be filled.