From Khulna's Notebook to a Verifiable Ledger: The Youth-Cricket Data Nobody Writes Down
Seven in the morning. On the practice ground beside the Khulna District Stadi...
Seven in the morning. On the practice ground beside the Khulna District Stadium the dew had not yet dried. A coach held a handwritten scouting sheet in which five of the eight boxes were empty. A question mark sat in the age column, a bare dash in the height column, and next to "bowling speed" nobody had written a number. The sixteen-year-old on the field kept bowling, and I sat looking at those blank boxes. That day I understood that the loudest part of a scouting report is never a complete number—it is the empty boxes, the ones nobody could fill in, or chose not to. An empty box is not merely missing information; it is a decision—someone's not knowing, someone's not looking, or someone's looking away. The dew dried, but those blank boxes stayed in my notebook. To this day they are what taught me to ask the most questions.
In 2026, after my playing career ended at twenty with a knee injury, I was a sports-science student at Khulna University. That year I got the chance to work as a volunteer data logger at the Khulna District Under-18 Championship. Over fourteen matches I recorded 327 passes by seventeen-year-old midfielder Rakib Hossain of Khulna Abahani Under-18; his passing accuracy was 89 percent. That data earned him a divisional trial. But what moved me more was my nine-page handwritten dossier—where, beside the match numbers, sat the story of his family's sacrifice and his coach's guidance. That dossier, with numbers and daily life written side by side, circulated among local coaches.

This points to a simple truth. In South Asian youth cricket—in analytical terms the cricket_asia region—most talent-spotting still happens on the basis of paper notebooks, phone memos and spoken memory. In Bangladesh, India, Pakistan, Sri Lanka or Afghanistan, countless boys walk onto the field every day along the Under-16 and Under-19 pathways. But how many of them have every session recorded? How many have an injury history written down? The answer is usually the same—very few. In this system the biggest enemy of information is not falsehood; it is absence. And that absence is the centre of today's discussion.
In 2026, after the Russia World Cup, Khulna Tigers FC hired me as a junior youth academy observer. The World Cup tape gave me the frame, but the academy desk gave me the boy—and that difference changed the tempo of my writing forever. Back then I was studying France's Kylian Mbappe, nineteen years old, four goals in seven matches. I wrote an internal memo whose central idea was how to integrate a teenage talent without burning him out. At the same time I tracked sixteen-year-old winger Arif Sheikh across twenty-two Under-18 matches; he scored seven goals. My cautious report recommended a gradual senior debut, and it introduced the ideas of a readiness window and a welfare checkpoint. In 2026 Arif got only twelve minutes. Someone could call those twelve minutes a failure. But in my notebook those twelve minutes were the result of a readiness window—a decision made from data and patience, not from emotion.
Then came 2026. The stadiums were empty, and Khulna Tigers FC cut its youth budget by forty percent. Empty stadiums taught me that full responsibility does not need a crowd. In that silent time, seventeen-year-old defender Sumon Mia tore his knee ligament during isolated training. I was not his coach, yet I quietly organised eighteen weekly video-analysis sessions and thirty mental-health check-ins. At the same time I mapped forty-six local youth players whose families had lost their income. Sumon returned in 2026 and played eighteen matches. In 2026 I also watched Spain's Pedri, then eighteen—six Euro matches and six Olympic matches. That load led me to write about the overuse of young players.
Here the link between data and care becomes clear. A name, a date, a session—these three things are what save an injured teenager from being forgotten. An incomplete data archive is really a broken mirror—it reflects not the player but the system. I am writing this not as an advertisement for any technology, but from a simple analogy.

The core lesson of a blockchain is the immutability, transparency and verifiability of information—once written, data cannot be changed, and anyone can cross-check it. The problem of youth cricket's data archive is the exact opposite. Here data changes, gets lost, and is never cross-checked. A boy's age becomes two years older within a single year, his pass count is written nowhere, his injury history is recorded nowhere. Yet these very facts decide when he steps up to the senior side, how much load he can carry, how quickly he returns. Age verification is the most familiar example. Suspicion over age in Asian age-group cricket is long-standing. A lost birth certificate, a different date on a school record, a different medical result—these inconsistencies would be caught easily if there were a verifiable ledger. Today they surface only when a controversy erupts, which is far too late.
If youth cricket had a verifiable ledger—where every session, every injury, every readiness window were written down with dates—then talent-spotting would stand on evidence instead of guesswork. Imagine Rakib's 327 passes written not only in my notebook but in a cross-checkable record; every minute of Arif's twenty-two matches logged; every stage of Sumon's injury and rehab preserved with dates. Then no coach or selector would be forced to guess. Decisions would be slow, but correct. And that very slowness is what protects a teenager.

There is another layer. When data is incomplete, the analysis itself goes the wrong way. Say a young batter's T20 strike rate looks brilliant—but if it comes from only three innings, that number is not proof of talent, only a picture of luck. Drawing big conclusions from small samples is the most common error in youth cricket. The reverse also happens: a bowler's economy looks poor because nobody recorded his hardest overs. Missing data damages both directions—it inflates one player's talent and buries another's effort.
Venue and format data likewise vanish at youth level. Who knows how much a ground's breeze turns the ball, or where the bounce is higher? At district level nobody writes this down, so every new venue is entirely unknown to every new boy. Where the senior game analyses the character of every ground, the youth game keeps it only in conversation.
My notebook has a rule: what was not written, I record separately. Who was absent from a session, whose data could not be found in a match—this "missing" list sometimes says more. Because a missing name often means the boy either dropped out through injury, or nobody looked at him. In both cases the question is equally important.
Another reality is tied to this. The betting and fantasy market built around teenage cricketers is huge today, yet the data underpinning that market is often incomplete. If a sixteen-year-old's name is wrongly entered on an Under-19 scorecard, it later affects his identity, his valuation, even the pressure on him. Where data is not verifiable, protection is not guaranteed either.
I know someone will say a digital ledger is expensive, unrealistic for a rural academy. But my nine-page handwritten dossier was no app—yet it worked, because it was consistent. The problem is not a lack of technology but a lack of consistency. Data written one day and not the next is not data—it is only a memory. And memory changes; a ledger does not. The fundamental difference between a notebook and a digital ledger is durability, and that durability is the first condition of accountability.
The normal expectation is that more data means better decisions. But in youth cricket I have repeatedly seen the opposite. A highlight reel magnifies talent, while a silent ledger preserves it. The problem is that nobody keeps this ledger, because there is no fame in it. Seven goals across twenty-two matches is no viral clip; but a sixteen-year-old's whole season of patience rests on exactly that data. The harm comes not from a lack of information, but from the habit of filling the blank spaces however we like. When a box is empty, we often fill it with assumption—he seems a bit old, he seems to be growing fast. That assumption then becomes a decision, and that decision makes or breaks a teenager's career. An empty box is not a lie, but it can be filled with one—and that is youth cricket's biggest risk.
Another uncomfortable truth is that accountability is built precisely where nobody is watching. Empty stadiums, ignored domestic fixtures, unglamorous coaching desks—this is where Bangladeshi cricket's real responsibility is formed. Where there is no crowd, there is less urge to keep records; and in that very gap the name of a future player is lost. In a district match whose scorecard nobody preserves, perhaps another Rakib played—but his 327 passes never reached anyone's notebook. We lost him because we did not write him down.
The question now is not about the quantity of data, but about who holds the responsibility. Who will keep that ledger—where every morning, every injury, every wait of a teenager is written down with a date? The empty boxes may be the documents of our shame, or perhaps our most honest mirror. Which one it is will be decided by what we agree to write—and what we leave blank forever.
