Empty Feed, Full Stadium: The Discipline of Saying 'Insufficient Information' in Cricket Analysis

2:40 in the morning. A laptop lies open in the study of a Mumbai flat, and on the screen sits a table. Eight rows, and all eight carry the same answer: insufficient information, assessment not possible. The headline cell at the top is blank too, and the source cell below holds not a single name. It is an analysis file for a cricket report, and there is not one sentence of cricket inside it.

That night I kept thinking of another date — July 14, 2026, Lord's. After fifty overs the score stood at 241 apiece. After the Super Over it was level again. England won the match on boundary count, 26 to 17. In that final, a ball brushed the inside edge of Ben Stokes' bat and reached the rope, and those four runs turned the match. Every ball of that day is written into the scorecard; not a single cell is empty. Yet the question remains open.

An empty feed and a flawless scorecard are two faces of the same limit. One holds no information, so it holds no verdict. The other holds everything, and still the question of justice hangs in the air.

In 2026, after India's 0-3 defeat to the United States at the FIFA U-17 World Cup in New Delhi, I spent three days tracing the disciplinary code and published a 2,400-word explainer citing Article 12 of the FIFA Disciplinary Code. The site's usual 2,000 readers were replaced by 18,000. The architecture of that piece was simple: a specific article, a specific minute, a specific referee's name. The rulebook was my first stadium, and I still walk its empty stands.

In cricket the method is harder, because cricket's rulebook is not one book. The MCC Laws of Cricket, the ICC playing conditions, the tournament-specific regulations — a system in three layers, where silence at one layer opens a gap at another. Law 3 of the 2026 Code states that two scorers shall be appointed for every match. Which means a match where the scorer writes nothing has no legal existence at all.

Modern coverage has largely taken the scorer's place with the ball-by-ball feed. Event data, live scores, auto-generated match reports, graphics — a pipeline with two tiers. The first tier extracts information points from an article: claim, actor, number, date. The second tier runs the analytical frame over those points. When the first tier returns empty, every cell in the second goes blank — mathematically inevitable, professionally humiliating.

Last night that is exactly what reached my desk. No team, no player, no format, no source, no date. A complete analytical document in which every cell gives one answer: I do not know.

Three roads were open at that moment. The first: delete the file, as if nothing had happened. The second: pour World Cup history, ICC rankings and Big Three politics into every empty cell so the reader stays content. The third: call the gap by its name. The first is incompleteness rather than dishonesty. The second is a professional offence. Only the third lets an analyst admit his own limit.

Cricket has an old name for that third road: umpire's call. When ball-tracking in DRS shows the ball heading towards the stumps but the point of impact is too uncertain to overturn the on-field decision, the technology announces itself — I do not have enough evidence. The screen flashes 'umpire's call', the field decision stands, and the review ends. Nobody calls this a failure. The cleverest part of DRS is not its accuracy but its capacity to say 'I don't know'. Technology that tries to answer every question lies; technology that knows the boundary of its own silence can be trusted to judge.

Analysis should follow the same rule. Without information points a format cannot be fixed; without a format, the question of which benchmark to use has no answer. A Test opener's average of 45 and a T20 finisher's strike rate of 180 can be placed on one scale arithmetically, and mean nothing analytically. On June 29, 2026, at Barbados, India made 176/7 in the final against South Africa; the Proteas needed 16 off the last over and stopped at 169/8, with Hardik Pandya bowling it. Those seven runs are a number; to explain them you must know which over carried what pressure, who was afraid, who forgot to breathe.

Cricket's datafication has increased the volume of information, not the volume of meaning. The ball-by-ball feed now reaches the market in fractions of a second, and the biggest buyer of that live data is the betting market. Here lies the darkest side of the information economy: the faster feed is the most expensive feed, and speed has no relationship with accuracy. A feed can carry four numbers per ball — runs, wickets, over, striker — and still contain not one sentence of the match.

On that night at Lord's the boundary-count clause was legal, published, and unjust all the same. The ICC later added the condition that a tied Super Over be replayed — an admission that a correct rule and a just rule are not the same thing. That distinction is the centre of my work. A ruling can be technically flawless and still feel like a crime to the stadium. A penalty is not a moment; it is a sentence the stadium must serve — in football as in cricket.

The most powerful person in cricket never appears on television. He is the scorer. Under Law 3 his duty is not merely to record runs but to protect the truth of the match. In 2026, working inside the ISL bio-bubble in Goa, I spoke to eleven players until two in the morning and learned one thing: analysis stays incomplete unless the clause of a contract and the fear of a human being sit at the same table. Cricket is no different — the numbers of the scorecard and the silence of the dressing room must be read together.

Last night's empty file taught me one more thing. The likely causes of the failure are three: the article could not be read at the fetch stage; the article was too short to yield any information point at all; or a taxonomy error, with 'cricket_world' slipping into the slot meant for 'Cricket'. All three are process defects, not cricket defects. To the reader the difference is invisible, because a report born of a bad feed looks exactly like a correct one.

This is where I part company with my own profession. A large section of analysts believes the crisis is data worship — that some have turned numbers into gods. My experience says the danger is less dramatic and far more ordinary. The crisis is not in wrong interpretation but in the failure to record absence. A feed with nothing in it, if it will not admit it has nothing, will invent instead. And invented data does more damage than a wrong ruling, because a wrong ruling creates argument while invented data removes even the room to argue.

The other side deserves admission too. 'Insufficient information' is an honest answer, and it can also be a hiding place for laziness. Writing 'I don't know' in an empty cell is easy; the hard work is picking up the phone and asking the source what they know and what they fear. In 2026 I learned that the second question holds more truth. So the discipline of the empty feed does not mean stopping; it means verifying before filling.

That is why my proposal is both technical and judicial. The entry point of data collection needs a validation layer — a minimum of eight to twelve information points, each with actor and date, and a mandatory format tag. The document should declare which claim rests on whose testimony. And an empty result needs its own marker, so that it never travels downstream as a finished analysis.

My small three-person research group runs on exactly this rule, because the pressure to fill a blank cell is heaviest in a large editorial meeting. The question the referee's eye keeps raising applies here too: a decision being correct does not mean it was just. A report being full of information does not mean it is true.

The scorecard does not lie. But the scorecard does not say everything either — and a system that cannot recognise its own silence will one day believe its own lie. So the question stays: is your feed empty today, or are you simply unable to see it?