The Empty Desk, the Silent Press Box: What the Record Booked in Chennai's Ranji Fixture That the Cameras Never Saw

At the M.A. Chidambaram Stadium in Chennai on Wednesday morning, around eleven o'clock, there were only three pairs of footsteps on the press box stairs. I was in the fourth chair, and the seat beside me was empty, with a thin film of dust on it — the kind of film that settles not in one session but in one week. This was a Ranji Trophy Plate Group fixture, Tamil Nadu versus a team whose name you have probably not read once this season. The game had begun on the field, but of the three journalists in the box, two sat with laptops closed, and the third refreshed the scorecard screen twice, then picked up his phone and walked out.

I took out my old notebook — the one whose spine wore thin in 2026 on the Rising Pune Supergiant final trip — and wrote the first sentence: 'Three men in the box today, two tomorrow, but the scorer's chair was never empty.' That is my beat. In forty-five years on the cricket desk, the most important thing I have learned is that the truest report of a match is written where the camera does not turn — on the rota board, in the scorer's book, and in the attendance sheet kept under that empty chair.

Context: The framework you do not see on screen

There were eight matches in this round of the Ranji Trophy. Let me remind you that the Ranji is the spine of the Indian domestic calendar — played since 2026, it is the pipeline from which generations emerged, from Sunil Gavaskar to Virat Kohli. But this season, five of those eight matches had not a single broadcast camera present. That is not new. What is new is that the number keeps growing.

I remember 2026, when I joined The Indian Express, Madras, as a trainee. Back then, covering a Ranji match meant a sub-editor was sent to the stadium, the score was taken from the scorer over the phone, and two columns appeared the next morning. That era is gone, and I am not mourning it. But one thing changed that nobody kept account of: Ranji coverage now rests more on numbers than on score — how many runs, how many wickets, how many balls — and because of this, the question of which player won the contest in what conditions is disappearing from the record.

The same happened in this Wednesday's fixture. In the afternoon session, Tamil Nadu were 89 for three when the rain came. During the drinks break I went down to the ground staff — the same three men who are always found in the same corner. One told me the pitch had held moisture since Wednesday morning and they had tied the covers properly overnight. That information goes into no scorecard. But if you want to understand the first hour of play on the first morning, it is as essential as the batsman's average.

Core analysis: What changed across three sessions

The fast bowler who opened in the first ten overs of the first session bowled seven overs, four of them maidens. That figure gets printed as 'economical bowling.' But I watched from the box that all four maidens came in overs where the batsman facing was playing at this ground for the first time. So it was not economical bowling but the cost of inexperience — and that distinction is almost always lost in Ranji coverage.

In the second session, Tamil Nadu's captain made his first change when the score was 112, and that change came not from a number but in response to the spinner's short ball. I wrote the sequence of three deliveries in my notebook: one short, one fuller, one short again. On the third ball the batsman went for the pull, was caught on the half-volley, and was caught out. Commentary calls it a 'brilliant set-up.' In the box, the scorer wrote only: 'caught, 47.'

Let me clarify something I learned in 2026, when the whole newsroom was in Russia and I sat alone on the cricket desk analysing India's 4-1 Test defeat in England. Every analysis of that series began with 'Virat Kohli's 593 runs.' But the real story was in those innings at Edgbaston and Southampton where the team collapsed inside 100 — and that collapse was not caused by the bowling but by the order in which batsmen were sent. I apply the same lesson here. Numbers tell you what happened, but order tells you why.

In the third session the rain returned and play stopped twice. While play was halted, I noticed a young Tamil Nadu batsman, debuting this season, sitting outside the dressing room. He had no coach, no data analyst — only a senior player sitting with him, correcting his grip. That is the scene no highlights package will show. But that scene explains why domestic cricket runs — because here senior players teach the young, and that teaching is in no contract.

The story in three figures the average does not show

When this match's scorecard is printed the next morning, it will show one batsman's 63 runs. I watched those 63 ball by ball. In his first 20 balls he had only 4 runs, and he left eight deliveries that were not on the stumps. That was not a 'slow start.' It was deliberate examination — he was reading the pitch's bounce, and when he trusted it, he made 59 off the next 40 balls.

If you look at such an innings only through strike rate, it looks slow. But if you know that three batsmen were out inside 20 in the first session on this pitch, that innings becomes the most valuable for the team. The Ranji scorecard has a column for strike rate, but no column for 'time spent reading the pitch' — and that is the biggest oversight of domestic cricket.

Contrarian view: What the record does not say

Looking at this match, one obvious conclusion emerges: Tamil Nadu played well, the bowling was strong, and the points were shared. That reading is not wrong. But it is incomplete.

One thing no scorecard will show: the two rain interruptions in this match meant different things to the two teams. The first rain came in the morning when Tamil Nadu were batting, and the second in the afternoon when the opposition was batting. After the second rain, moisture increased on the pitch and spinners began to get turn — information no scorecard reader can extract.

And here an interesting thing emerged. In the second innings, when the opposition needed 180 with 40 overs left, their captain made only 19 runs in the first ten overs. Commentary would call it 'slow batting.' But I saw that in those ten overs he played only two balls in the air. So he was not scoring runs, he was reading the spinner — and when the spinner changed, 74 runs came in the next 15 overs. Had he been aggressive in those first ten overs and lost two wickets, the match's direction would have changed.

So the obvious reading is that slow batting hurts a team. But on this pitch, in these conditions, that slow batting was what saved the team. This is the nuance the broadcast camera does not have, because the camera follows only the ball, not the batsman's intent.

I remember the 2026 final when Rising Pune Supergiant lost to Mumbai Indians by one run in Hyderabad. After that match I wrote a 3,000-word oral history, interviewing twelve players and staff. The most useful thing in it was not Rahul Tripathi's 391 runs — it was the order in which those runs were made. Young players were sent up in that team and given the licence to fail. The same is happening in domestic cricket, but here nobody records it.

A senior colleague said to me that year that 'women don't understand tactics.' I did not argue. I simply wrote that piece — with data visualisation and player interviews. Reader engagement rose forty percent. After that he said nothing. That was when I was 52, and I still believe the strongest answer is never an argument — it is the record.

The signal ahead

After the match ended I stayed in the box. The stadium began to empty, two of the three journalists left, and the scorer closed his book and put it in his bag. I asked him what was hardest in this match. He said — 'the rain cut overs three times, and each time I had to add it all up again.' That answer will appear in no newspaper. But it explains how a record is made — by the patience of one person who starts the count over every time.

When you look at a Ranji scorecard next round, remember for a moment the person who filled that book. And consider this too: until the broadcast camera reaches all five of five Ranji matches, how many stories of cricket will we keep losing — and will we ever be able to record that loss?