From Eden's Press Box: When a Cricket Story Stops Being a Fact and Becomes a Guess

On a February morning, four of us sat in the press box at Eden Gardens and all four were looking at the same phone. Below, the grass on the nets was still wet; a groundsman was pulling off the covers and unknotting the ropes. Upstairs, someone turned the screen around and showed a number — a strike rate, to two decimal places. The question was not whether the number was right. The question was which format it belonged to, and somewhere in the hands that carried it to that screen, the label had gone missing.

Nobody filed a story that morning. By afternoon the number had travelled through three WhatsApp groups, two tweets and a television panel, arriving slightly more naked at each stop. By evening it had become a fact that people were passing to each other with the phrase "I hear".

I went home that day and opened my notebook. It had no score from that session in it — only who stayed long against which bowler at the nets, who walked across to the second pitch to call a spinner over, and who cut practice short. I keep a page for the things nobody writes down. For fifteen years that page has been my real capital.

And that day, for the first time, I felt that capital leaking away. The factory that produces cricket news now builds the guess first and goes looking for the fact afterwards. This is not carelessness. It is a structure — and a structure has to be named.

Context: one session, three formats, one mistake

One thing separates cricket from other sports, and it is structural rather than technical. The same player runs three separate careers at once. A Test average, an ODI average and a T20 strike rate come from three different games, and treating them as comparable is like comparing a marathon runner's time with a sprinter's.

Cricket numbers are dangerous precisely because they look so clean. One figure, one decimal, one percentage — no expertise is needed to read them. That is why they travel fastest and lose their context fastest.

Over the last few seasons I have watched a pattern inside my own profession. When a story leaves the nets, it carries five things: who, when, in what situation, in which format, and in what context. By the time it reaches the copy desk, three survive. By the time it reaches a social feed, two. By the time it reaches an argument, perhaps one.

The worst error in cricket's information system is not caused by lying. It is caused by labels falling off.

In this tournament cycle that is easier to see. The number of matches has grown, the window has shrunk, and every fixture needs space for commentary, feeds, clips and thumbnails. When the speed of production is that high, the first thing to fall is context.

I learned this work in three places: an old sports desk in Delhi, a digital newsroom in Kolkata, and from the groundsmen who are on the pitch at six in the morning and whose names never appear in a byline. All three taught the same rule — a thing that is true in its own place can become false in another.

Where a story comes from: nets, circulars, scorecards

Cricket stories come from three sources, and their reliability runs in almost the same order every time.

The first is the ground — nets, pitch, practice session. It is the slowest source and the most trustworthy. Here you get no summary; you get sequence. Who bats first, who bats last, who lingers over throwdowns. I went back to the Eden nets to see what had changed. Almost nothing had. Same ropes, same angle, same two pitches — and yet sitting there you see the thing a press conference never shows you.

The second is the board — circulars, contract lists, schedules, selection announcements. This source is hard, but it has to be read carefully. What a board document says and what it means are often different. A schedule does not tell you that a team plays three cities back to back and when its fast bowler will tire. That is the reporter's job.

The third is the scorecard — and this is the most misleading, because it looks the cleanest. A scorecard gives you fact but not story. It tells you who made how many; it does not tell you what that innings was for.

Some careers are built in the spaces between scorecards. And when an information system reads only scorecards, it leaves those spaces empty.

This year there is another layer. A tournament cycle demands immediate reaction after every match — panels, threads, reels. I made a rule early in my career: no opinion within the hour of a defeat. That rule did not come from ethics; it came from arithmetic. A reporter who files an opinion in an hour is resting it on the facts he has just received, not the ones he would gather over three days.

Today's system rewards that one hour. And that is where the empty space gets manufactured.

The format of a number: when a decimal lies

My notebook has a page from 2026. In the tenth IPL season I stayed with KKR in Salt Lake, tracking them from the Eden Gardens nets to their away flights. That season Chris Lynn made 295 runs in seven innings. The number was printed everywhere. But the number was not the story.

The story was that the team's balance leaned towards its bowling, and that balance gave the opening pair licence to take risk. So the 295 meant a risk taken inside a structure. Lift that 295 out and place it beside an average from another format, and the number will not lie — the person using it will.

No cricket number is true on its own. It becomes true only when its structure, its format and its role travel with it.

That is why I ask three questions before printing any figure. First, which format. Second, in what situation — where did the batter come in, what state was the team in. Third, how large is the sample — three innings or three seasons.

The third question is the most ignored. In this cycle a large claim is built every week on three innings and collapses the next week, and the reader is never told that the claim was never solid to begin with.

The notebook says it rained on the third day. Nobody else remembers that. The rain changed the pitch, and the spinner who became the hero of the second innings was ineffective in the first. Both numbers are accurate. Print only the second and you have not printed the truth — you have printed half of it and made a whole lie out of it.

This problem shows fastest in Test cricket, because conditions change most there and therefore summaries are scarcest there. When someone tells me Test cricket is losing popularity, I ask: on what measure. In the grounds? Tests fill, especially in India. On television? The numbers work differently there. In media coverage? The decline is real there — but that is a cost-of-coverage outcome, not a popularity outcome.

Giving one answer to three separate questions is the oldest habit of this trade.

The arithmetic of an auction and its illusion

In 2026 the IPL went to the UAE and the stadiums stayed empty. I worked from team hotels, on remote media calls. KKR finished fifth on 14 points, missing the playoffs on net run rate. The auction headline that year was Pat Cummins, at INR 15.5 crore.

Look at what happened. The number that could travel most easily was 15.5 crore. The number that could not travel was how that team's balance was built and where it broke — and that was the actual story.

In auction coverage, price is the one fact that survives every handover. Structure, need and balance die at the first one. That is why auction journalism looks so confident and is so incomplete.

I have a simple test. On any big buy I look at three things: what problem the player solves, how much of that problem the team already had solved, and what the price forced them to give up. The third question matters most and is asked least, because its answer is not in the price — it is in the rest of the squad list.

In 2026 that test earned its keep. KKR's UAE leg turned when Brendon McCullum and Eoin Morgan pushed Venkatesh Iyer to opener. He made 370 runs in ten matches and the team reached the final, losing to Chennai Super Kings by 27 runs. The headline was 370. I did not write that. I wrote about how the promotion released pressure on the middle order and gave the bowlers a cleaner target.

That is the difference. 370 is a number that will be compared with someone else's 370 next year and the argument will end. What the promotion changed will still matter next year.

I also learned that season to check numbers with the analyst, because a good tactical read is worth more than a loud take. A reporter's mistake is not that he does not know the numbers. It is that he mistakes the numbers for the story.

Young players: load, expectation, and a cautious profile

In early 2026, after the Under-19 World Cup in New Zealand, I followed Shubman Gill back to Kolkata. He had made 372 runs in the tournament and was Player of the Tournament; India beat Australia in the final. KKR had bought him for INR 1.8 crore. I watched his first Eden Gardens nets, spoke to his age-group coach, and tracked his 203 runs in 13 IPL matches.

What I wrote was not a celebration. It was a question: can a teenager be held in a top order without being overexposed.

Watching tournament-cycle coverage now, that question seems to be reinvented every season and left unanswered every time. Three good matches and a whole story is constructed. Three bad ones and the player is filed away as "not ready". The error is identical in both directions — sample size.

I keep a column in my notebook: how much has he played, where has he played, against whom. It is the most boring format available and the one that works. When a young batter's runs are counted, nobody counts how many came on home pitches against spin and how many came away against pace.

The most important fact in a young player's story is the thing he has not yet done. His workload, his batting position, and his room to fail.

That is why I start a profile with the team's question and the viewer's question — what does this player give the side, and what will the watcher get. The name and the shine arrive on their own. When I talk to a coach, he does not praise the name; he tells me when the boy's wrist gets tired.

That detail never makes a headline. It decides whether the player is still there next year.

Women's cricket: the ledger after the win

What changed in women's cricket coverage after 2026 is not sentiment. It is paperwork. Contracts, match fees, broadcast slots, domestic schedules, and WPL auction dates.

So when a big win arrives, I treat it as an audit rather than a celebration. The question is not how large the win was — it was large, it happened on the field, and shrinking it would be dishonest. The question is how many girls got to play consecutive matches in one place six months later.

The real test of women's cricket is not the trophy. It is the schedule. A team playing seven matches in a month is not developing talent, it is spending it.

One thing I have watched over recent seasons worries me most — results from domestic women's cricket are still not recorded as thoroughly as men's domestic results. Without data you have no justification for selection. Without justification, selection stays permanently under suspicion.

This is where the information system and the sporting system become the same thing. A coverage gap is not only a coverage gap; downstream it becomes a transparency gap in selection.

There is a cycle here that repeats every season. A batter makes 400 runs in a domestic women's tournament. A paper reports that she should be in the national side. Nobody knows which pitches, which position, how many matches. When she is not picked, the same paper writes that the selectors treated her unfairly.

Both times, facts are missing. The first time sentiment becomes fact; the second time, suspicion does. In between sits the thing that real reporting is — the information without which no opinion stands up.

Ranji and the arithmetic of coverage

There is an odd contradiction I have watched for fifteen years. Test stadiums fill. Ranji Trophy grounds stay empty, and its media presence keeps shrinking.

That decline did not come from the quality of the cricket. It came from cost. For any publication, covering Ranji means sending someone to a small town for three days from which no clicks and no reads will return. When the media's measure becomes views, the coverage that goes is the coverage with no immediate commercial value.

And that creates a dangerous condition. If there is no Ranji coverage, the Ranji data is incomplete too. If there is no data, the question of how the next Test player was chosen simply will not be asked.

In cricket, a coverage gap is never only a loss to the reader. It is always a loss of accountability.

There is a version of this story only the groundstaff know. They know how often a particular pitch was watered over three days, and how quick a particular fast bowler was on the first morning. That is the information that tells you how big a score really is. We do not have it, so we have the score but not the scale.

I am not arguing that every match deserves a report. I am arguing that if a tournament is part of a system — and Ranji is — its documentation should be part of the system too. This is not a question of newsroom priority. It is a question of design.

A report that was empty

A few weeks ago I was handed something that pushed me into writing this piece. An analysis system returned a report with no hard facts in it at all. No title, no source, not a single information point, no player, no team, no format. Pages of framework, with the same line everywhere — "insufficient information, cannot assess".

My first reaction was that it was worthless. My second was that it was the most useful thing I had read all year.

Because it did the one thing this profession almost never does. It admitted it had no facts.

Our trade works the other way. We have half a fact and we write the whole story. We have one source and we make him three. We have a number and we turn it into a claim.

One line in that report went into my notebook: "no risks identified" and "risks unassessable" are different things, and they must never be read alike.

I thought about how many places in cricket coverage that sentence applies to.

The contrarian angle: "no risk" versus "risk not measured"

The outside reader concludes this — if there is no news of a player being injured, he is fit. If there is no controversy around an appointment, the appointment is clean. If an auction showed no irregularity, the auction was fine.

That is the most common reading and the most wrong one.

Silence is the most misleading signal in any information system. Information that does not exist is not proof of cleanliness.

I connect this to something that happens every week in this tournament cycle. No official update arrives on a player's workload. In the next match he is out. Nobody had written that there was a risk, because no risk had been declared. That was not an absence of risk. It was an absence of information.

This is where I distrust my own habit. I put verification first, and that is right. But verification has a bad form — saying nothing until everything is certain. The result is that by the time you say something, a faster reporter has set the frame.

So I changed my method. I now publish the verified kernel first and state plainly, with a timestamp, what remains unconfirmed. I hold the frame and deepen it later rather than holding the fact.

That is not softness. It is accountability. If I write "not yet confirmed", the reader sees the empty space. If I delete the sentence, that same space fills up in the reader's head as "all fine".

A third contrarian point: we are trying to fill this gap with technology. We assume more data, more charts, more dashboards will clarify the picture. In my experience the reverse holds. More numbers increase the appetite for context, and when context is missing the reader simply treats the number as the context.

When analytical depth rises and source depth does not, the output is not information but confidence — and that confidence is hollow.

This is the thing I have seen most in my own trade: the commentary that sounds most certain is usually the least checked.

The accountability we cannot trade away

One more thing, because it is the biggest weakness in my own work. For fifteen years I have gone on the same tours, stayed with the same team, talked to the same groundstaff. That access is mine, and it is my capital. But access is also a trap.

When you know someone personally, asking the question becomes hard. And if you do not ask, your access turns into something that benefits only you, not the reader.

My rule is this — before a trip I settle what I need answered, and if the question is uncomfortable it gets asked on day one, not on the last day. Separating what is owed to a person from what is owed to the reader is not a technique. It is a discipline.

There are things in fifteen years of notebooks I have never printed — names, dates, the seasons when a player was under mental strain. That material is not mine. It belongs to the man who trusted me. But the same notebook holds things about the board that are mine — which circular came on which date, which date it took effect, and what happened in between. Printing that is my duty.

This is the distinction I want people to hold. Protective discretion is good. When protective discretion starts protecting institutions as well, it has already curdled.

It took three seasons for the rhythm to show

Now all of this has to land somewhere, and a conclusion is the most dangerous thing here.

Let me use the example I actually have. Fifteen years in a trade and three seasons watching one team share one property: you spend the early part accumulating knowledge, and the later part discovering where the knowledge was wrong. It took three seasons, but the rhythm finally showed itself. And it showed through the repetition of boring details, not through a headline.

That is my structure, and I will put it in one sentence, because a sentence placed after the evidence is not a burden. Indian cricket's biggest problem is not a shortage of talent; it is a shortage of information — and that shortage always arrives as silence, which we mistake for safety.

When a squad is not explained, when rest is not explained, when a pitch is not explained, what survives is the cricket and what is lost is the accounting. And without accounting, every selection is an argument and every argument becomes politics.

In this tournament cycle one thing is clear to me. We will argue about the number of matches, about workload, about who should play. The thing we argue about least is how we would even know.

What to watch next

I am not telling anyone whom to doubt. I am pointing at where the next signal will come from.

Watch three things over the coming months, and all three are internal — they will come from documents, not press conferences.

First, watch whether the format label survives in match reporting. If a strike rate is printed without its format next time, a link in the chain has broken again.

Second, watch whether complete domestic data is made public. That is the first door to selection transparency, not a statement.

Third, watch whether the number of back-to-back matches in the women's schedule falls or rises. Trophy photographs will arrive every year. Only the schedule's ledger will tell you whether that win is holding.

I am sitting in the same Eden press box where this piece began. Below, a batter is still standing in front of the bowling machine. My notebook is open and there is a line in it from that morning, written for nobody's story but my own: the thing that was not printed still happened.

The question is not what the next big story will be. The question is whether, next time an empty page lands in front of you, you will read it as "no news" or as "the news has not arrived yet".