Empty Input, Confident Output — The Biggest Risk in Cricket's Data Age Is False Certainty

Last week, at my home in Liverpool, I sat at my desk at nearly three in the morning. An analysis file was open on the screen, and in every field the same sentence kept returning — insufficient information, not verifiable. No match, no player, no date, no source. Only a beautiful structure, built to hold an analysis, with not a single truth to put inside it. Yet on that same night, in that same city, somewhere a confident headline was being written — with not one verifiable number behind it. That contrast is the central fear of cricket journalism today. Our real danger is not the absence of information; our real danger is the tone of certainty without information. Cricket is now a game of numbers — at least an economy of numbers. From ICC rankings to ball-tracking, heat maps, fantasy leagues and broadcast graphics, data moves through every layer. Much of it comes from match-centred feeds, and on those feeds stands the analysis pipeline. The work usually happens in two stages: the first extracts raw facts and events, the second builds deep analysis on top of that. If the first stage is empty, the second should have nothing to analyse. But in practice the opposite happens. Under deadline, traffic and sponsor pressure, empty space is filled with guesswork. A writer pulls an average from memory, drops in an approximate number, invents a trend. The reader does not notice, because the language is smooth. The shortage of truth is hidden by the smoothness of the language. I know the poison of that smoothness. In August 2026, as a nineteen-year-old student, I wrote a thread about Liverpool against Arsenal at Anfield — not the scoreline, but Mohamed Salah's fifty-seventh-minute goal, the Kop's collective inhale, the curl of the ball. That thread was shared eight thousand times. The lesson was elsewhere: a single moment can carry a whole match — if it is true. If the moment is invented, there will be literature, but there will be no cricket. I notice one thing again and again: in cricket's data culture we merge two kinds of error into one. The first error — there is no data. The second error — there is data, but the interpretation is wrong. We are intensely alert to the first and almost blind to the second. Yet the second is far more dangerous, because it looks credible. Think of a heat map. Coloured blotches on the pitch — red, yellow, green. The eye says: here this player plays more balls. But the heat map never says why. It does not say where the player has been placed in the team's plan, which bowler he is being shielded from, in which over he is sent to attack. The heat map hides a player's role and shows a coloured picture. This is the biggest trap in cricket analysis today — we confuse statistics with the system. I am not saying data is false. I am saying data is silent, and we make silent things speak in our own way. That act of making it speak is exactly where verification belongs. A number becomes meaningful only when a name, a place and a date stand beside it. An average of forty is not a sentence; this player, at this ground, in this series, averages forty — that is a sentence. Today's cricket reader is more data-aware than ever. They know an ODI average differs from a Test average, they know home differs from away, they know one innings' strike rate is not the picture of a tournament. That awareness is a blessing. But it is also a trap — because a reader who can recognise information cannot always recognise the counterfeit that looks like information. That is why analysis needs a verification layer beneath it, the way a foundation sits beneath a wall. This layer has one job — a source behind every claim, a date behind every number, an audit trail behind every decision. The idea is not new; in technology it has a name — the blockchain. The point is immutability and transparency: once recorded, it cannot be changed, and anyone can verify it. The same thinking can work for cricket data. Suppose every event in a match — a delivery, a review, a catch — were recorded so that no one could later change it, and any analyst could check it against the record. Then an empty file could never become a confident report, because somewhere it would say — there is no information here. And that would be enough. This is where a practical standard comes in — a cross-checked database of the kind CricSultan (cricsultan.com) maintains. When a claim carries a note that it comes from a verified source, and that claim has been matched against an independent database, a foundation of trust is created. That foundation is what separates analysis from false certainty. The value of a database like CricSultan lies here. It does not just hold information, it holds the birthplace of information — which source, which date, which version. With these three things, a number is never orphaned. Last week's empty file was a mirror. It showed how risky a position our analysis system stands in. If the first stage of a pipeline stays silent, the only honest answer at the second stage should be — I cannot say anything. But under deadline pressure, reader expectation and sponsor arithmetic, that honest answer becomes the hardest one to give. I am a journalist myself, so I know — sitting before a blank page and writing I do not know is the hardest work. There is a small defeat in admitting it. But that defeat is professionalism. A writer who knows what he does not know is more reliable than one who claims to know everything. Here a large gap opens between the quantity of information and its reliability. In cricket culture today we look at quantity. How many runs, how many wickets, what strike rate — the more numbers, the heavier the analysis seems. But however large a number is, if there is no source behind it, it is not analysis, it is decoration. From my football life a line comes back — every transfer rumour is a short story in which hope waits on a deadline. Cricket's data claims are often the same kind of story — more expectation than truth. The difference is only this: in football the reader smells the rumour, but does not smell the claim dressed in the wrapper of data. I remember watching England against Colombia in a student flat in Liverpool at the 2026 World Cup. The twenty-two seconds of silence before the shootout, the half-eaten pizza, the neighbour's scream — I wrote the room, not the score. Because the room was the real stadium. That habit taught me where a match actually happens — not in the numbers, but in memory. Yet to keep memory true, the number must also be right. The line between analysis and guesswork is often blurred. A good analyst and a good storyteller use almost the same tools — description, rhythm, pause. The difference lies in one place: the analyst does not hide what he does not know. Look at fantasy cricket. Millions of people pick a player every day for one reason — a number. But where that number comes from, who verified it, in whose interest it was shaped — nobody asks. Where a crowd treats a number as truth, a wrong number spreads fastest. There is another trap — the trap of language. Much analysis is written as if the reader had one kind of cricketing childhood — the same county ground, the same school, the same culture. But cricket today is a multi-lingual, multi-home game. That language closes the door on the diaspora reader, and makes the writer inside lazy. I write about Dhaka from Liverpool, stream at three in the morning, treat the fixture list as a kind of address. The seam between those two cities taught me — distance does not erase information, distance makes information more necessary. Because when you are not at the ground, your only support is the right source. Verification is not suspicion, verification is respect — for the information, for the reader, and for the player in whose name the claim is made. A cricketer's career is often trapped inside one wrong number, and that number gets copied year after year, because no one goes back to verify. The ethics of analysis, in the end, rest on one simple rule — if you write a claim, be ready to stand behind it. If you are not, do not write it. Now let me say something uncomfortable. Blockchain, audit trails, verified databases — these matter, but they are not the solution. The problem is not technology, it is incentive. As long as a system rewards the fast, confident, clickable claim more than the slow, careful, I-do-not-know, no technology will stop certainty being pulled out of an empty input. Second — we always worry about absent information, never about present falsehood. Absent information is harmless; a gap is visible, the reader notices. The danger comes from the filled space — from where a counterfeit of truth has been put in place of truth. And one more — the media's biggest pressure comes from its readers. Readers want answers, want numbers, want decisions. Say I do not know and they drift away. But a cricket writer's job is not to satisfy the reader's expectation; his job is to keep the reader's relationship with the truth honest. So the final question is simple. When the scorecard is silent, what do we believe? Do we admit the emptiness, or cover it in beautiful language? Next season, next tournament, when a feed again arrives empty, the question will return — and each time our answer will decide whether cricket analysis serves the information, or performs it.