When the Chain of Information Breaks: A Silent Failure Inside Cricket's Invisible Pipeline

I set the cup of tea down before opening the file, out of habit — I like both hands free when I read, so the pen does not shake while I take notes. But when the file opened, there was nothing worth reading inside it. No title. No source. No one-sentence summary. No author stance. No description of an event, no player name, no match score, no venue report. Only small boxes, and inside each box the same sentence returning again and again — insufficient information, cannot assess.

I spent 127 days inside the Goa bio-bubble. There, every morning meant one nasal swab, one temperature reading, one form. There, emptiness never meant a blank; emptiness meant something was hidden, something not yet caught, something tomorrow morning's session might reveal. But today's empty file is a different kind of emptiness. Here the question is not about a player; the question is about the process. If the pipeline that builds our news quietly breaks somewhere, what exactly is the reader reading? Is he reading a story, or the absence of a story?

This empty file is not an accident; it is a signal — the chain of information has broken, and no one sitting inside the chain noticed.

My way of working needs explaining, because if you do not understand where this emptiness sits, it is easy to misread. I am not merely a craftsperson of match reports. I use the scorecard, but the scorecard is not my starting point — it is my ending point. My real work begins at the training ground, in the early net sessions, in the dressing-room corridors, in the hotel lobby. I belong to a profession that listens to a team's inner tempo — who gets the ball, who gets the word, who gets the silence. At one point in my career I stopped chasing the ball and started reading the room. Because the ball changes every day, but the room does not. And if the room does not change, you can actually hear a team. You can hear a team, if you can sit still, silently, for long enough.

Inside this whole work there is an invisible structure the reader never sees. I call it the chain of information. Each link of the chain is a stage. The first link — raw material. Training sessions, press conferences, matches, scorecards, data feeds, local-language radio, fan rumours, the board's silent hints. The second link — extraction. What did someone pull from that raw material, which information point did they isolate, which entity did they identify. The third link — analysis. Placing that information point inside technical, tactical, cultural context. The fourth link — publication. Reaching the reader. The fifth link — verification. When a reader or a colleague asks a question, whether the chain can be held together.

In our current tournament cycle, this chain is being stressed every day. Because a tournament cycle compresses emotion. Across a long season a story is woven slowly — a young fast bowler's first five wickets, an experienced batter finding rhythm, a coach's patience. But once the tournament arrives, time shrinks. Four matches in a day, two at night, one at dawn, plus travel, dew, injury, questions of squad depth. Under this pressure raw material grows, but verification time shrinks. And when verification time shrinks, every link of the chain weakens. The most dangerous weakness appears in the second link — extraction. Because if extraction comes back empty, analysis comes back empty too, and empty analysis is either frightening or fraudulent to the reader.

The file I received today is the testimony of a failure in that second link. An analytical document whose every dimension — format, player, team, league, governance, risk, public narrative, industry transmission — is marked insufficient information. There is no player here, no team, no match, no league. There is only a failure, and the honest acknowledgement of that failure.

This is where the real lesson hides, and this is the centre of my piece. When an analysis returns empty, the biggest danger is that a reader mistakes it for zero risk. But it is zero data, not zero risk. The difference between the two is the largest invisible crack in today's cricket newsroom.

A comparison helps. Imagine a train station where a fire warning was supposed to arrive. But the sensor is broken, so the signal is blank. Now if someone decides that a blank signal means the station is safe, they are at the extreme of error. A blank signal is not proof of safety; a blank signal proves the instrument of proof is not working. The same applies to cricket analysis. If a player's score is blank, it does not follow that the player is bad. If a team's ranking is blank, it does not follow that the team is weak. What does follow is this: our extraction pipeline has broken, and we must repair it.

From years of watching matches, I can say this misreading of a blank signal is nothing new in cricket. It is an old habit that has taken a new shape in the data age. I remember a scene from childhood. Rain had stopped play in a match, and the scoreboard showed only one number — 47. A friend sitting beside me said the team must be very bad. Yet nothing could be read from that 47 — how many overs, how many wickets, how the pitch behaved, what Duckworth-Lewis was saying, none of it was known. He had simply turned one blank piece of data into a complete verdict. Today's instrument behaves like that friend, only faster, and with far more confidence.

Now I turn back to my own work. For years I have kept a trust log for every player. This log is not a ledger of statistics. It is a ledger of belief. Who said what, and when; who stayed silent, and when; who quietly pulled a newcomer aside; who stood in the corridor on the night of a defeat. In Navi Mumbai's training ground, in 2026, I attended 42 of 45 pre-season sessions. There I built enough trust with Balwant Singh to document his six-goal ISL season. Those six goals were never abstract numbers; behind each goal was a silent rule, an internal decision of the team, who would give the ball and who would not.

The core of this trust log is that information never arrives alone. Information arrives in a voice, at a time, inside a relationship. The journalist who grabs the number without understanding that relationship gets the number but loses the truth inside the number. This is why I practise double-checking. Colleagues call me the slowest fast reporter on the beat. There is a joke in that phrase, but also a truth. I am deliberately slow, because I know it is easier to confirm a fact slowly than to correct a fact later.

Behind this slowness is a painful lesson. Years ago I received a piece of information from a trusted source who was always accurate. But that accurate source, one day, fell inside a rumour — not deliberately; he himself believed the error. That incident taught me that loyalty to a source and loyalty to the truth are not the same thing. You must love the source, but you cannot believe the source blindly. So now I test every trusted source at least once a season — going beyond what they give me, searching also for what they leave out.

The bio-bubble experience deepened this lesson. Between 2026 and 2026, in Goa, I spent 127 days in the bubble with Mumbai City FC. There every meal was a set piece and every hallway a scouting report. Zero spectators, zero noise, zero external clamour — only a sealed bubble. Inside that bubble one had to hear only the team's own breath. There Sergio Lobera's possession football worked like a philosophy, and to sustain it every player had to know when to release the ball and when to hold it. Adam le Fondre's eleven goals, goals from Bipin Singh and Bartholomew Ogbeche — and a 2-1 win over ATK Mohun Bagan in the final. Those numbers were never isolated for me; they were like the fruit of one continuous silence.

Inside that bubble, inside the sealed room, the silence had a rhythm, and the players were learning to hear it. I still write this line, because it is not only about football. It is about every cricket dressing room. A team that learns to recognise the rhythm of its own silence finds its tempo even under pressure. And a journalist who can recognise that rhythm can read the match behind the match.

Now imagine that journalist holds an instrument that can measure that silence, and the instrument suddenly returns blank. What then? Does he measure the silence, or the instrument's failure? If he cannot tell the difference, he reaches a wrong conclusion. He says the team is healthy, because the instrument found no problem. But the truth is that the instrument found nothing at all.

This is the real test of our profession. We have long learned how to read information. Now we must learn how to read the absence of information. These are not the same skill. One tells you what the team is doing; the other tells you what our system of knowing is doing.

I stress this because in the current tournament cycle the reader's demand is sky-high. Flag and story pull him along. Amid this emotion, if the analyst does not look at his own pipeline, he will drift with the reader's emotion, and the crack in the pipeline will stay buried.

Now I want to examine every side of this empty file, because behind each empty box there is a lesson.

The first box — format and match analysis. Here it says the format itself is unknown. Test, ODI, T20, or something else — nothing is specified. This is the whole point. In cricket, if you do not know the format, you know nothing. The same innings, the same thirty runs, is a symbol of patience in a Test and a mark of failure in a T20. The same economy rate is superb in one format and a disaster in another. The analyst who forgets the format mixes the data of all formats and hands the reader a fake universal truth. This empty box is therefore a warning — if you do not know the format, it is better to stop before analysis begins.

The second box — player technique and data. There is no player here at all. No average, no strike rate, no economy, no situational splits. In my experience one thing is clear: a player cannot be judged by his home-ground performance. Home ground hides his weaknesses. Before getting excited by a rising strike rate, one must look at how many balls he did not play — that is, how many dot balls hide inside his account. But today there is no material here even to ask that question. So an honest silence is the only worthy answer.

The third box — team, ranking, squad structure. Batting depth, bowling combination, bench strength, age structure — all unknown. Yet these four pillars are the real place to judge a team. I have seen many times a team win a tournament on the goals of two stars, then collapse the next season even with the same two stars — because the bench depth and the age structure had decayed. The scoreboard never tells the story of that decay. Only the dressing room does. So if this box is empty, the team's picture stays incomplete.

The fourth box — league and commercial environment. Broadcast rights value, franchise valuation, player salaries, auction prices — none of it. This layer is cricket's economic blood pressure. If a franchise buys a player at an inflated price, that is not only a batting-order decision; it shapes the whole season's strategy — whom to play, whom to rest. Reading only on-field performance without understanding this financial pressure makes the analysis stand on one leg. Today that leg is missing.

The fifth box — rules and governance. Distribution of power and revenue, controversies over playing rules, anti-corruption, eligibility and selection, political influence — all unknown. This layer is the quietest, and therefore the strongest. Behind a selection committee's decision there is strategy, and also a balance of power. Without knowing it, you misread the reason a player is dropped, and from a wrong reason you make wrong predictions.

The sixth box — risk. Here is the subtlest lesson. In the risk list there is no player, no team, no commercial matter. But an empty list does not mean zero risk. This document itself makes that clear — the only identified risk is a process risk: that in future someone might mistake this blank result for a valid safety signal. This is today's most important sentence. We read a failed analysis correctly only when we read it as a failure — not as a decision.

The seventh box — public narrative and expectation. How excited the market is, how sustainable the narrative is, how wide the gap between expectation and reality is — none of it could be measured. Yet in a tournament cycle this gap is the biggest trap. When fans see one innings from a player and declare him the next great star, the analyst's job is to measure the narrative's foundation — how much sample it rests on, how strong the opposition was, how favourable the conditions were. If the material to measure that is absent, the analyst should stay silent, not drift with emotion.

The eighth box — industry transmission. From youth development to national team, league, broadcast, investment, fantasy market — how an event spreads through this whole chain is observed here. But no event was identified here, so the path of transmission cannot be drawn either.

Together these eight boxes make one picture. And that picture has one name: a tear in the second link of the chain.

Now I come to the moment in my career when I first understood how fragile the chain really is. In 2026, at the Tokyo Olympics, I covered the Indian hockey team from its Bengaluru camp all the way to Tokyo. Under Manpreet Singh's captaincy, that side beat Germany 5-4 to win bronze after 41 years. I wrote that bronze story through Graham Reid's pressing tactics and the revival of fan clubs in Punjab and Odisha. But behind that writing was a silent labour — after every press conference I separately verified what the coach had actually said and what the media had written. Often the two differed. Catching that gap was my real job. Amid the joy of bronze, no one saw that gap, but I knew it was the truth inside the team.

At the 2026 Qatar World Cup, I spent 28 days in Doha, watched 12 matches, including Argentina's final win over France on penalties after a 3-3 draw, and spoke with 150 Argentina fans from Kerala. There I understood that the real key to understanding a team is not its star but its fans. I would ask fans what they had lost and what they had won — not predictions, but memories. Because memory tells you what place a team has taken in people's lives. When Luka Modric won the Golden Ball, I spoke with 200 members of Mumbai's Croatia fan club, in 2026. Those conversations taught me how a team's emotion crosses borders, and how it also gets stuck at borders.

These experiences taught me a habit I call the culture notebook. On every trip I fill a notebook — not only match facts, but the smell of the market, the delay of a train, a local word, a joke, a silence. Later, when I write about a transfer window, those notebooks come in useful. Because a transfer is never merely a transaction; it is a new rhythm looking for a pulse. And to find that pulse you need a chain of information whose every link is intact.

But this empty file showed me where the chain can tear. And it strikes at my own point of pride. Because I have a tendency I consciously restrain — over-verification making every fact feel provisional. I am never fully certain. This habit keeps me careful, but it also endangers me — if I keep verifying forever, I will never write anything at all. So I have set a rule: tiered verification. Score, quote, context — a separate standard for each. A score needs only one reliable source; a quote needs a direct voice; context needs at least two independent sources. Without that standard I would either write wrong or write nothing.

This empty document reminds me of another thing, my profession's biggest trap — pseudo-analysis. That is, when real information is absent, filling the template's empty boxes with plausible-sounding cricket content. It is easy, it is fast, and it looks almost true to the reader. But it is a lie. Because information that exists in no source does not become information when placed in a template; it stays a guess — and calling a guess information is fraud.

In this piece I did not want to do that. I did not want to fill the empty boxes with fictional player names, fictional rankings, fictional commercial numbers. Because my job is to protect the chain, not to break it and fill the gaps.

Still the question remains — what about the reader? He wants a story. The tournament is on, his team is playing, his star is on the field. If you hand him an empty document, what will he do? This question is the real one. My answer is — the reader should not be handed an empty document, but the document's gap should be told to him. That is, where we are certain, we speak loudly; and where we are not certain, we say clearly — here we are not certain. This honesty is our real contract with the reader.

Here I hold a firm opinion deeply tied to this subject. In modern cricket everything is becoming the same — the same format, the same tactics, the same kind of star being produced. The diversity that once existed is being erased. One reason behind this sameness is that we all depend on the same information, drawing from the same pipeline. When everyone builds analysis from the same blank dataset, the analysis too becomes the same. To protect diversity we need different sources, different eyes, different voices — and the courage to acknowledge that difference.

One saying is common in my profession, and I want to change it. It is said that speed is the journalist's life. But I have seen that in cricket the real life is patience — the patience to understand a team's rhythm, the patience to understand a player's silence, the patience to acknowledge an empty piece of data as empty. Whoever loses this patience delivers news fast, but delivers wrong news.

Now I want to face a likely objection. Someone may say, will so much caution not paralyse analysis? Someone may say, if a journalist stops at every empty box, he will never write. This objection sounds reasonable, but it holds a misunderstanding. Caution does not mean stopping; caution means not stopping at the wrong place. A good journalist never stops — he merely tests the ground beneath his feet.

This is where I want to state a counter-intuitive point, the centre of today's discussion. In my view, the biggest problem in cricket journalism is not a shortage of information but an excess of confidence in it. We receive so much information that we think we know everything. Yet a large part of that information comes from the same raw source, through the same extraction pipeline, in the same analytical mould. So we do not verify independently; we repeat each other's information. If a wrong fact enters the chain once, it grows in every link, and finally establishes itself as truth.

So my advice is plain: make the verification process as independent as possible. Every fact needs at least one different kind of source — scorecard, eyewitness, local voice, or analytical data — so that a mistake is caught by another source. A chain is strong only when each link is independently tested, not when each link hangs from the same source.

Here my own way of working has to change a little. I no longer only chase the ball; I read the room. Entering a dressing room, I first see who sits beside whom. Walking a corridor, I hear who talks to whom, and who avoids whom. At warm-up I notice who goes to the nets first, who goes last. These small signals together make a large picture — who is the team's real leader, who is the real trust. This picture is the truth behind the scorecard.

I believe this method can reach the reader, if we also teach him those silences. Fans today do not only want highlights; they want stories — but those stories must be true. Respecting a fan means not pleasing him with a fake story; respecting a fan means helping him build the real story from small true pieces.

Now I can see a positive side in this empty document too. This document was honest. It did not fill its boxes with fictional data; it made clear that there is no data. This honesty is in fact the first step in repairing the chain. Because as long as you do not acknowledge the problem, you cannot repair it. An empty box is therefore not a shame; an empty box is an honest question.

In this context I recall how often I have received information that everyone else received, yet no one verified. In one transfer window a team bought a player, and everyone wrote that it was a great success. But no one noticed that the player's rhythm did not match the team's striking style. Mid-season, the player was sitting on the bench. The analysts were stunned. Yet the truth was hidden in the absence of verification — no one asked whether a win on paper would be a win on the field.

One big reason for this absence of verification, I think, is the nature of our relationship with the information supply pipeline. We assume the pipeline is neutral. But every pipeline has a point of view. Which information rises to the top, and which gets pushed down, is determined by the pipeline's structure itself. So a journalist's real job is not only to read the pipeline's output but also to question its structure.

I am asking that question today, sitting before this empty document. The document tells me extraction failed. But it tells me more — this failure may not be a single accident. Perhaps it is a small expression of a larger trend — the chain of information is increasingly machine-dependent, and as machine dependence grows, the human duty of verification shrinks.

I think this problem will only grow. Because the volume of data increases daily, and the tools of artificial analysis get easier daily. Today anyone can press a button and generate an analysis. But the tool that extracts information cannot ask the right question. Only a human can ask the right question — one who was on the field, one who was in the room, one who heard the silence.

So my appeal to the future is plain. Increase the tools of analysis, but do not abandon the human habit of verification. Read every empty result as an empty question. See every empty box as a warning. And teach the reader that empty data does not mean safety; empty data means we must dig deeper.

I am thinking of the most instructive moment of my life. It was an ordinary pre-season match where no star played. The stadium was nearly empty. But in that empty ground I heard one thing — a coach telling his young player, if you score today I will not count it; I will count how many times you returned to your position. That sentence taught me that real assessment never lies only in results; it lies in process. And to see the process you must sit even in an empty ground, and read even an empty document.

This lesson is the core of today's piece. When a cricket analysis returns empty, it is not a failure if we learn the truth of the process from it. Rather, it becomes a failure if we bury it, fill it, or mistake it for a safety signal.

Let me say one last thing from my own experience. For many years I have returned to the same ground, watched the same players, stood in the same corridor. This habit of returning builds trust on one side, and creates a danger on the other — I may start assuming I know everything, because I have watched everything for so long. That assumption is the biggest trap. So now each time I return I look anew, as if it were the first day. I consciously search for signals that were not there before — perhaps an old player now silent, perhaps a new face now speaking. These small changes are the real news inside a team.

This empty document is that new signal. It tells me it is time to look at my own pipeline. The duty of protecting the chain is not only technology's, not only the editor's; it belongs to every journalist, every verifier, and every reader too. Because if a reader can tell empty data from safe data, the path of fraud narrows.

Before I finish, I want to hold on to one thing that is the foundation of my whole profession. Cricket is never only a game of runs and wickets. Cricket is a game of belief — who gives the ball to whom, who speaks to whom, who lets whom stay silent. This account of belief must be kept, and keeping that account is what we call journalism. When the pipeline of that account breaks, our duty grows, not shrinks.

I finished my tea and looked at the file again. It is still empty inside. But now that emptiness is no longer nothing to me; now it is an instruction, a reminder. What I will do next is clear — I will return to the original source, re-run the extraction, and verify every information point again. Because I know that before hearing a team, one must make sure one's own instrument is hearing correctly.

Finally, I leave the reader with a question. Next time you read a clean, confident analysis, will you ask — where did this information come from? And when you see an empty result, will you think — there is nothing here, or will you think — here is something to search for? Your answer will decide how much of next season's cricket journalism stays true, and how much merely sounds confident.