The Empty Box on the Scorecard: How Missing Data Distorts Age-Group Talent Selection

The west gallery of Sheikh Abu Naser Stadium, Khulna. Fourth row. January 14, 2026, half past nine in the morning. An under-16 trial match is running. In my hand is an old notebook, a scorecard grid on the right page, margin notes on the left.

At the end of the day the scorecard said this: one left-arm spinner took two wickets for nine runs in four overs. At the other end, a boy took five wickets for twenty-two in four overs. The name of the five-wicket boy was read out at the announcement. The left-armer's was not.

In my margin that day I had written a question: in which over did this boy bowl to the opposition's best batter, what was the team score then, and who was bowling into the wind. Three boxes on the scorecard were filled. Five were empty. The selection committee read the filled boxes.

I am not naming the left-arm boy. He is still a minor, and at his age, publishing a name risks more than it offers. But those empty boxes are what this piece is about.

I still keep the Khulna notebook; its margins hold more than scores.

Three Filled Boxes, Five Empty Ones

The pathway of a young Bangladeshi cricketer is fairly fixed. School and club cricket, the district under-16 national championship, then under-18, then under-19. In between sits BKSP at Savar, divisional academy schooling, and a chance in Dhaka league cricket. At the last stage: the eight divisions of the National Cricket League, the four zones of the Bangladesh Cricket League, and the fifty-over Dhaka Premier League. A file is created at every step. The question is what the file holds.

In my experience the file holds runs, wickets, overs, catches, sometimes a strike rate. It does not hold the three things without which no decision can actually be made.

The first is situation. If an under-16 side bats only 34 overs of a 50-over match, there is no death-over information at all. At that age the real selection question is who can bowl under pressure — and that is precisely the box the scorecard never prints.

The second is opposition strength. The same tournament includes a reigning district champion and a team formed three weeks ago. Five wickets can happen against either. The weight is not the same.

The third is the other side of the context. A spinner's economy of 4.5 on Khulna's slow, low, turning surface is not the same number as 4.5 on Dhaka's truer bounce. The scorecard records the place. It does not record the ground.

Where the 2026 File Went

February 9, 2026. Senwes Park, Potchefstroom. India all out for 177 in 47.2 overs. Bangladesh 170 for 7 in 42.1 overs, winning by three wickets, captain Akbar Ali unbeaten on 43. It was Bangladesh's first ICC title at any level. Source: official ICC match report, February 9, 2026.

Some of that squad are senior internationals now — Shoriful Islam, Towhid Hridoy, Mahmudul Hasan Joy. Others stopped at domestic cricket. The question is which exact point put one boy on that bus and left another behind.

The World Cup tape gave me the frame; the academy desk gave me the boy. After 2026 I tried repeatedly to obtain a complete development map for anyone in that batch: overs bowled by age, injuries by season, runs by opposition quality. I never got the whole picture.

What I did get was something else. I watched one under-19 side play three different competitions in five weeks, and nobody had counted the same quick's weekly overs. There was no bowling-load log. Only a wicket count.

The data that is never written down makes the loudest decisions.

What a File Actually Holds

When I began working at under-18 level in 2026, I built a template I still use. It has eight boxes.

Format context first — how long the match is, at what level, at what stage of the ball. Then sample size and opposition quality. Then venue splits, home and away kept separate. Then developmental age, meaning where the boy's date of birth sits inside his cohort. Then workload and injury history. Then performance at the decision moment — what he did when the score was 40 for 3. Then source and interest: who is telling you this, a coach, a club, a relative, or a three-minute video. And finally position on the age curve: what he is now, and what he might be in two seasons.

Of those eight boxes, the Bangladeshi age-group archive typically supplies three, and the first two only partially.

Which brings me to the point I did not make at the start. When an analysis arrives at an empty box and stops, that is not the analyst's failure; it is the archive's. Keeping those two apart matters, otherwise we blame the wrong person and preserve the wrong system.

The Left-Arm Spinner and the January-December Gap

Of all these empty boxes, the least discussed and most consequential is the fourth.

Suppose one boy in an under-16 squad was born on January 2, another on December 28. Both play in the same cohort. In reality they are almost twelve months apart in lived age. At adolescence, twelve months means a large gap in physical maturity — height, shoulder strength, consistency of pace.

Research across several countries has examined this relative age effect in youth cricket, and the general pattern is consistent: boys born early in the year are likelier to be selected. How severe it is at Bangladesh's district level, I have no published number for. The reason is simple — our age-group scorecards do not print performance next to date of birth.

So the selector sees a mature boy and an immature boy, both described as the same age. The selector is not making the mistake. The selector is being handed the mistake. Once that error enters a cohort it reproduces itself, because next year the mature boy performs again, is selected again, and builds confidence on a foundation that belongs to the calendar rather than to him.

The boy born in December is lost exactly when his body and technique are in their most sensitive phase. That loss never appears on a scorecard, because what is not written has no statistic.

Wrong Data Is Worse Than No Data

The comfortable assumption is that missing data means no problem yet. My experience runs the other way. A vacuum does not stay empty. Something fills it.

In age-group cricket that something is a hundred-second clip of a boy hitting six sixes, captioned with the name of a future star.

Another thing fills it: the radar gun. A fifteen-year-old quick at 128 kph sounds lovely and looks even better on television. But that number says nothing about his action, that day's pitch, his overs, the state of his back. Distance covered and sprint counts are sold in football as proof of effort, when pointless running also produces beautiful numbers; cricket's speed-gun figure is the same package. It sells. It does not develop.

The easy route in talent selection has always existed, and it is looking at physical maturity. The boy who grew first wins first. It is easy because it works — until about sixteen. Plenty of mid-table sides build an identity on exactly that shortcut, the way some in football believe pressing has been solved by running capacity. That solution only holds to a certain level; after it, strength without craft spends itself. Cricket's version is crueller, because the physically advanced teenager is fast-tracked into the national frame before his tactical base is laid, and the road back is closed.

I fell into that trap once myself. In a 2026 under-18 report I softened a boy's weaknesses because his coach was my friend and the boy was honest. One sentence in that report did not survive the following season. Now I write affection and assessment on separate lines — affection first, then finding. Because one eighteen-year-old's career matters more than my discomfort.

The notebook does not argue; it waits until the pattern becomes a person.

The Star Cycle Fills the Vacancy Itself

Across the last two seasons I have sat through at least fourteen district-level matches with a notebook. One pattern returns.

The boy who made a big score in one match has his name travelling to three districts within a week. The boy who made thirty to forty runs in six straight matches has his name travelling nowhere. Yet consistency and a single-day explosion are entirely different skills. The first is a long-term asset. The second is one evening.

Without data, people fill the vacuum with story, and stories remember the loudest chapter. The result cuts both ways. The boy who flashed once is pulled up quickly and loaded with expectations that do not match his age. The boy who works daily becomes invisible and eventually leaves the game. When selection is made by story instead of number, both errors are the same error with the face turned.

Empty stadiums taught me that full responsibility does not need a crowd. In 2026, when the grounds were empty, the boy training alone and then getting injured never appeared in any large outlet. That was when I learned that accountability is built where nobody is watching.

What I Will Watch in the Next Two Seasons

I will not make predictions; in age-group cricket, prediction is the easiest work and the least reliable. I will watch three signals.

First, whether district scorecards start printing date of birth beside performance. If they do, two seasons will be enough to see how much age bias sits inside our selection.

Second, whether an opposition-strength column appears. One column could change selection quality within a single season, because five wickets would stop equalling five wickets.

Third, whether the workload ledger travels with the boy from one competition to the next. If school matches, district matches and club matches are not counted in one place, injury will not arrive suddenly. It will arrive from a load nobody ever measured.

One line keeps returning to my notebook: if a file cannot hold the boy's age, his date of birth, his opposition, his ground and his load together, that file serves nobody — not even him.

And the question of those fifteen from 2026 is still with me. How many of them had a file that could answer a selector's first question today?