N/A in the Feed: The Cricket Data Nobody Sits Down to Verify

Two forty-one in the morning. In that glass box in Kolkata we call a studio, two of the three monitors were running fine. The third had a scorecard open, and every row carried the same mark — N/A. No runs, no overs, no toss, no venue. The cursor blinked. The producer's voice came through the headphones: "Give me any number, anything." I said, "I am giving you what's there — nothing." A match was being played that night. The problem was that the road between the ball and the screen had broken somewhere in the middle, between the scorer's laptop and the app, at a spot whose name never appears on a news ticker. The notebook closed, but the desk kept taking notes.

After that night I spent three weeks digging through old diaries, because there was one question: had I ever written down the name of the man who sends the score? Over a hundred matches, fifteen years, and the answer is no. Cricket's information chain stands on three floors. First floor: the ground. The scorer's chair, ink on a finger, a register kept dry in the rain. Second floor: the middle layer. The place where ball-by-ball reaches an agency server first, and from there spreads to television graphics, websites, fantasy platforms and the commentary box. Third floor: us, the ones who read the number and pass judgement.

The first floor and the third floor get audited. The second never does.

Hold on to the dates. 23 July 2026, Lord's. India needed 229, were bowled out for 219, lost by nine runs. That day the scorecard was on paper and I could see the ink. 19 January 2026, the Gabba. Rishabh Pant 89 not out, and I wrote about the follow-through, not the win. Both times the information was in my hands, touched by me. In 2026 I called sixty IPL matches off-tube from the UAE, a producer's voice and canned crowd noise in my headphones. 19 December 2026, 36 all out in Adelaide at half past four in the morning, describing an empty stadium to a country that was asleep. The event was in the commentary; the information was somewhere else. Sixty nights of canned noise taught me the difference between crowd and chorus — and this too: when the feed goes quiet, the commentator is left with the truth, not a guess.

Here is the centre of the matter. Cricket's weakest link is not the scorecard; it is the middle layer that no institution will claim as its own. The board says data is the agency's job. The agency says it was sent to the broadcaster. The broadcaster says the app pulled it late. The app says the source was late. Nowhere in that circle does anyone sign their name. A newspaper report carries a byline, a reporter, an editor. The glowing '14.2 overs, 128/3' on a screen carries nobody.

There are three places where this frailty shows plainly.

One — domestic cricket. A large part of the Ranji Trophy is still not recorded the way it should be. Select matches are streamed; the rest depends on a portal or two. A spinner bowls seventeen overs across three days, takes six wickets, and his entire record sits on a website whose server is down in the afternoon. At the next auction, the scout setting that spinner's base price is deciding on that same incomplete data. The paper on the auction table is not the product of cricket; it is the product of data entry.

Two — language. The day Hindi, Tamil and Telugu commentary broke the English desk's monopoly, the game's audience doubled. The same day produced a new inequality: the regional feed is fast, but it has no cross-check staff of its own. An English desk puts two people on score verification; a regional bulletin takes the same agency feed straight to the microphone. Democratisation arrived without its audit.

Three — the calendar. There has been no India–Pakistan bilateral series since December 2026 to January 2026; the two teams now meet only in ICC events and Asia Cups. That is a calendar fact, not a sentiment. Yet every year some 'source' produces a bilateral series story, and every year it disappears exactly as it came. That is not reporting; it is a way of filling broadcast time. For a reader who wants a reliability filter, the rule is simple: a story without a date, a contract term and a named signatory is noise, not a headline.

Apply the same filter to the signing and auction market. A player's base price is not a market valuation; it is an entry fee. The real story starts afterwards — retention terms, release clauses, an agent's conversations, an NOC deadline. When a franchise releases a player, that decision is often about a slot in the wage bill, not about cricket. And when a player is described as 'week-to-week', read that sentence not as a medical bulletin but as the communications team's calendar. Return timelines are fixed by ticket sales and squad-announcement dates more often than by the state of the injury. So the question is not when he comes back; the question is whose interest the comeback story serves.

Now the contrarian angle. Blamin g the platform is easy, and wrong. The real failure is that nobody has been given the job of noticing that the feed is empty. We made cricket so data-dependent that we forgot data needs a custodian too. The second inconvenient truth: a blank field is trustworthy. A system that writes N/A is honest. A system that fills in a guessed score is dangerous, because its lie glows and no one looks at it twice. I left the studio to find the match still speaking in the hallway, but its voice was on no screen. The crowd was absent, so I listened for the game.

Which brings up what comes next. The 2026 cycle is already running — the domestic season, franchise preparation, the under-nineteen data, all of it more machine-readable than ever. Nearly every score that will be made will pass through a server. Whose signature goes under the scorecard? Next time a number glows on your screen, pause a moment and ask: did this come from the ball, or only from the server?