An Empty Scorecard Is Still Data: Where Asian Cricket's Information Chain Breaks

I opened the ledger at 4:40 in the morning. The file arrived with nine fields, and eight of them said the same thing — N/A. Only the ninth slot carried anything at all: a tag. cricket_asia. I opened the ledger before sunrise; by noon the numbers had rewritten the story — except this time the story was not about a match but about the system that delivers matches to my desk.

The real news that morning was not that a team had won or lost. It was that a cricket desk's entire information chain had produced one tag and eight empty boxes. And the most dangerous thing I could have done in that moment was to fill the silence with a good story — to call a spinner's wickets 'help from the pitch', to call a captain's field placement 'pressure', to call a young batter 'in form'. All three sentences sound fine. All three can be written with no data at all. I wrote none of them. That is what this report is about.

Stage-1 extraction is the desk's checkpoint. A source article, match report or feed is read, and out of it are separated the information points, the core viewpoints, the entities (players, teams, organisers), the time sensitivity and the source quality. Stage-2 then applies an eight-part frame to those points: format and match nature, player technique and numbers, team landscape and rankings, league and commercial ecosystem, rules and governance, risk, public narrative, and industry transmission. The frame works only if something sits on the table beneath it. That morning the table was bare.

One thing survived — cricket_asia. That is not content, it is a category. But a category is still a statement, because it tells you the system at least recognised the subject as Asian cricket. Nothing beyond that. No format, no match, no player, no date. In that situation there is exactly one honest answer: stop the analysis, leave all four columns blank, and send the chain back to source. That is not a failure. That is the protocol.

Which raises the useful question: how often does this happen across Asian cricket's data supply? In my experience, far more often than the industry admits.

Asian cricket's data chain runs on three layers of very different quality, and the limits of any analysis are set precisely where one layer meets the next.

The first layer is international cricket. India, Pakistan, Sri Lanka, Bangladesh, Afghanistan — those matches have ball-by-ball records, tracking data, the works. Here you can build a runs-above-expectation metric and publish it.

The second layer is domestic first-class cricket. Ranji Trophy, Duleep Trophy, Vijay Hazare — scorecards exist, but ball-by-ball data for every match does not. There is streaming, but no tracking engine behind the stream. The result is that domestic performance gets priced on average, strike rate and economy — numbers that tell you nothing about conditions. A batter averaging 40 and a batter averaging 40 look identical, even if one made them on shirtfronts and the other on green tops.

The third layer is associate and women's domestic cricket, and this is where the gap is widest. ACC events are often scored manually, with no automated feed. Women's domestic competitions sit in a similar place: the WPL got a good feed, but the structure beneath it is still scorecard-based. When I try to apply the same metric — say, runs conceded per dot ball under a rising required rate — to a women's domestic fixture, the model has no input to work with. The metric is not useless. The input is absent.

I first felt that gap properly on the night of 21 May 2026 in Hyderabad. Mumbai Indians were bowled down to 129/8 and beat Rising Pune Supergiant by one run. I had every delivery logged, which is why I could surface what the headlines did not — Jasprit Bumrah's 17th over, where the count of dot balls under a climbing required rate decided the match. If all I had held that night was the final scorecard, that over would never have appeared. That is the difference between a score and data.

I have the reverse case too. 1 July 2026, Moscow: Spain completed 1,029 passes against Russia, a World Cup record since 2026, took 25 shots, and my shot-quality model put them above 2.5 expected goals. The match finished 1-1 and Russia won on penalties. That night I wrote that possession without penetration is a bookkeeping error, not a style. I could write that sentence because I had the full data — every pass, every shot, every shot's quality. The model was built for football; cricket broke it by the eleventh over — but breaking it still required data from the eleventh over.

That is exactly where Asian domestic cricket gets stuck. There the model does not break. It never gets built. And whatever does get built speaks in priors — and priors speak in the most beautiful language available.

So the desk runs three checks. First, the ingest check: did the source document actually enter the system. Second, the chunk check: once inside, was it read or merely counted. Third, the entity check: did names, teams and dates come out the other end. If any one fails, analysis does not begin. And above all of them sits a traceability rule: every conclusion must tie back to a numbered Stage-1 information point; a conclusion that cannot be traced is not a conclusion, it is an opinion.

I did not invent that rule for fun. When we built the Talent Resource Development Wing with the KSCA in 2026, we had no television feed, no Hawk-Eye, no software. What we had was a scout in the stands, a notebook, and a fixed template. The BCCI replicated that model nationally in 2026, and names like M. S. Dhoni, Suresh Raina, Irfan Pathan and R. P. Singh are credited to that pipeline. The lesson was clean: scouting is data too, and it gets generated only when a human sits where the camera does not reach. Today we have cameras — but not everywhere. And where there is no camera, there is no algorithm either. There is only a person.

Now the part that sells least at my desk.

An empty field is not the enemy. It is the control group. An empty stadium is not silence — it is a control group with seats. When I look at which matches have ball-by-ball records and which do not, I learn less about players and more about the people who decide where the camera goes. One Ranji match and one IPL match both field 22 players. The difference is not technology. It is budget and priority. So when a board or a broadcaster talks about 'growing the game', my first question is: where is that growth's data trail? A category whose scorecard is incomplete has no measurable meaning left for the word 'development'.

And my own ledger is owed too, because I publish my wrong calls beside my right ones every month. Some years ago I explained a domestic spinner's season as 'help from the pitch'. At the time I did not have ball-by-ball data for more than half that season's matches. I filled the gap with my prior. When the footage and the detailed scorecards arrived later, a good share of those wickets turned out to be batters' errors, not the pitch's. Since that day my rule has been hard: no data in the field, no sentence in the field. It is easy to write and hard to keep, because readers want a story and 'I don't know' is the least-read sentence in journalism.

This is the door through which 'momentum', 'pressure' and 'destiny' walk in. The problem with those words is not that they are emotional. It is that no measurable proxy has been declared for them. When I write 'pressure', I need the ratio of dot balls to a climbing required rate standing behind it. When that ratio is missing, I do not write the word. It reads as severity; it is actually the only way the same report can be re-audited next year. What cannot be re-audited is not analysis. It is weather.

So what was the answer to those eight empty boxes? The file went back. That was not a defeat; it was the only honest move available. Count first, question second, narrative last — that is the whole method. The day we write the narrative first, data becomes decoration.

What to watch from here is clear to me. Signal one: whether the re-run Stage-1 returns populated information points — if it comes back empty again, the fault is not in the source but in the system, and fixing that is an engineer's job, not a reporter's. Signal two: how long it takes for ball-by-ball feeds to become standard at associate tournaments. Signal three, and the most important: when women's domestic cricket gets its first complete, clean, season-on-season dataset — because until it does, 'equal standard' remains a speech, not a metric. The data did not change the game; it changed the way we watched it — and that way of watching has not yet reached large parts of Asia.

The next time an empty field lands on your desk, ask yourself one question: will I fill it, or will I send it back? Your answer decides whether you are analysing the game or telling a story about it.