The Ranji Camera Map: The Selection Machinery Hidden in Nine Televised Matches That the Scorecard Never Explains

In the 2026 Ranji season there were 27 teams, roughly 115 matches played, and of those only nine had any kind of broadcast feed at all. That figure did not come from a boardroom presentation — I logged the broadcast coverage of every match in that season in my own notebook, venue by venue, feed by feed. When I turned that sheet over, what emerged was not a cricket scorecard but a map of a system that decides who gets seen and who does not. Pairing that sheet with my ball-by-ball ledger — which I have kept since 2026, when wire copy still arrived as bare scorecards — I found a 21-year-old batsman from Mumbai whose name was recorded far more solidly in the numbers outside the nine-match highlights package. Shreyas Iyer: 1,321 runs, average 73.38, and a strike rate better than nine an over through the first 15 overs. I published that table with method notes attached and mailed it to every franchise analyst whose address I could find. After that day I stopped writing 'talented youngster' and started writing '1,321 runs, 73.38, phase split attached.' This piece is the product of that habit: log every ball by hand before you trust a single number, and audit television coverage the way others audit batting averages. The Ranji Trophy is the largest tournament in Indian domestic cricket, but its broadcast architecture has never been uniform over the past decade. On one side are matches with multiple cameras, Spidercam, Drone technology and clips that circulate overnight; on the other are grounds with one fixed camera in front of the scoreboard, and sometimes not even that. This gap is not merely a difference in viewer experience. It is a difference in the information that reaches the national selection process. The scope of my own ledger is limited and I state that upfront: in 2026 I watched roughly 31 of the 115 matches with my own eyes, and filled the rest from local correspondents, scorecards, and broadcast footage wherever possible. My sample is not complete — it skews toward grounds I could reach easily. But when the question is which matches coverage chooses, the coverage map itself is the clearest evidence, and that map is public. Most of the nine televised matches that season were at grounds in major cities — where permanent camera infrastructure existed and logistics were cheap for the broadcaster. The more than 100 matches with no feed included grounds in smaller towns, newly promoted states, and teams without big names. That is where the real story was hidden. The Shreyas Iyer case makes this clearest. In that 2026-17 season he scored 1,321 runs at 73.38, and those runs were not only in the matches whose highlights appeared on TV. When I broke his innings into phases — first 15 overs, 16 to 40, and after 40 — his strike rate in the first 15 overs was above nine runs an over. That number was in no discussion at the time because phase splits were not a public metric in domestic cricket then. The man who appeared on TV had highlights packages made of his innings; the man who was not covered had only a scorecard left — and a scorecard does not record at which over a batsman accelerated, against which bowler, on which pitch at which ground. Let me make one thing clear that I have seen repeatedly across my career: the scorecard is not a neutral document. It is a summary written by someone with an interest — someone who has to decide what to record and what to leave out. Dismissal type, field settings, dot-ball pressure, who bowled the difficult overs — none of that appears in the scorecard. And when it does not appear, the selection committee has only one dimension of that innings: runs and average. That is where selection errors are born. In 2026, when a digital-first outlet hired me at 43 as its first data editor, within six weeks I had standardised a post-match template — phase splits, control percentage, wicket value — that published 25 minutes after the last ball. That July at Lord's, in the women's World Cup final, India were 191 for 3 chasing 229 and lost by nine runs, bowled out for 219. My template showed the last seven wickets fell for 28 runs. I reported that collapse as a sequence of deliveries rather than a mood, and the template became the outlet's default match skeleton. Every reporter on staff now had to file numbers before adjectives, and I enforced it for four years in a two-line email sent without variation. I applied this process to Ranji, and the result was what it always is: the coverage map and the performance map do not sit on top of each other. Several of the nine matches with cameras featured players whose numbers were middling, but they were on TV. And in the more than 100 matches without cameras, performances happened for which no highlights package was ever made. Iyer's case is not the exception but the confirmation of the rule — he did not appear in any of the nine, yet his numbers exceeded everyone else's. Had I watched only the TV feed that season, I would never have found that number. Now comes the part where the real question begins. Is this relationship between coverage and selection causal? No. It is correlation, and treating correlation as causation is exactly the error I have spent my career correcting in others. It may be that pitches were better at grounds with cameras, or that the teams playing there were stronger, or that the broadcaster chose matches that already had stars. My dataset does not separate that. I have only shown that the coverage and performance maps are different — not that one created the other. Those who say 'being on camera causes selection' are making exactly the unsourced assertion I criticise. What I can say is this: if the selection committee receives only the data that appeared on television, then its decision is built on an incomplete basis. And that incompleteness is not the result of a conspiracy but of a structural gap. One more thing is essential here, something I learned over the years: the data the BCCI holds — ball-tracking, fitness data, selection analytics — stays inside the board's walls. This is a governance question, not a technical one. Who is measured, who is measured accurately, and who decides which measurement counts — that is a matter of accountability. Players in the Ranji matches without cameras generated no ball-tracking data. When the same player entered the selection debate the following year, he had only a scorecard average, while a player who competed in televised matches had a record of control percentage, phase splits, and ball speeds. This inequality is not a question of anyone's intent but of the system's structure. My own ledger has a scope too, one I do not wish to hide. The 31 matches I watched in 2026 were at grounds I could reach — around cities like Mumbai, Pune, Rajkot. I was not present at the far-flung grounds with not a single camera. My data suffers from the same bias I am criticising. I write this because anyone who does not disclose the limits of his own sample has an incomplete conclusion. The most solid thing that emerged from this whole exercise is not the name of any one player. It is the realisation that a parallel system is operating in Indian domestic cricket — one that plays in front of cameras, whose data reaches selection, and another that plays outside the cameras, whose data is confined to the scorecard. Both are playing for the same trophy, but their means of access are different. Next season, when you look at a scorecard, ask one question: does footage of this innings exist or not? If not, what you are seeing is not the whole truth of the match, but the part someone decided to write down.