138 Sessions and 64 Rooms: When the Ground Clock Speaks Truer Than the Scoreboard

At the 17th over of a Rajshahi T20 league match I saw something that never makes a scorecard. Left-arm spinner Salauddin Sakib bowled, the right-hand batter twice shuffled his feet, then let it go. Third ball, same shape, this time he bent low and scooped the sweep. Four. Next ball, slightly wider outside off, he played the same shot. Plumb. The difference between those two balls was not technique but decision-making. And decisions are logged at the nets, not on the scoreboard. That afternoon I understood: what fills my notebook will never appear on the stadium screen, because the screen only shows outcomes, not process.

In June 2026 I left a desk-editing job at a Dhaka daily and talked my way into Abahani Limited Dhaka's pre-season. My MS in Sports Management was the lever; a numbered notebook was the tool. Across the 2026 Bangladesh Premier League season I attended 138 of 141 training sessions. After each, I filed a 'Ground Notes' newsletter on a zero-budget Facebook page. By December it had 4,200 subscribers. A national daily lifted two session reports, unattributed. Abahani finished runners-up. But I did not write about the result. I wrote about those 138 sessions, where a single drill took 138 days to take hold, because trust between coaching staff and players does not arrive after one result—it arrives after counting. Only after session 138 did I trust that drill. The training ground keeps time better than the scoreboard. The scoreboard measures outcomes; the ground measures process. Yet our entire cricket journalism infrastructure is built around the scoreboard. Match ends, report filed, numbers tallied—in that rush we forget how many sessions, how many taping tables, how many physio straps sit behind one delivery. We record the pace of a quick bowler. We never ask why he is bowling in Rajshahi's midday sun instead of Mumbai.

From my second notebook, a calculation: a first-class match in Bangladesh runs five to six hours a day. The ball clock holds two to two and a half. The rest accumulates in rooms, the dressing room, field placements, changes, drinks breaks, injury treatment. Less than half of what we call a match is cricket. The rest is infrastructure. At Russia 2026 I had no accreditation, so I watched all 64 matches in 64 different rooms—tea stalls, a barber's shop, a rickshaw garage, two mosque courtyards, a projector club. I filed 64 dispatches in 32 days, not about pitches but rooms. A street split over Argentina-Brazil; 300 people watched France 4-2 Croatia on an open field. My following jumped from 4,200 to 61,000. That is where my two-column format was born: match in one column, viewing room in the other.

Applying that to cricket creates friction. Cricket matches are long and the room stays the same. In football you can change rooms inside 90 minutes; in cricket you sit in the same dressing room for five days. So I changed the index. In football, room count was the measure; in cricket, the temperature inside the room is the measure. On the third morning of a Test, who sits beside whom, who visits the taping table, who skips the drinks—add those three facts and you read the internal weight distribution of a squad. Across two first-class seasons I sat through 40 matches with this method. In 33 cases I found a relationship between dressing-room social patterns and the following innings' partnership breakdown. In 62 percent of batting collapses, a silence had appeared in the room the previous session—someone not speaking to someone, or a pair of gloves deliberately left inside out. These are anecdotes, not statistics. But statistics start here, not at the scoreboard.

Now a counter-argument aimed at myself. Being scoreboard-skeptical is not denying the scoreboard. Those 138 Abahani sessions taught me one thing; a 2026 national team series defeat taught me the reverse. The drills were precise, the process clean, and the results still did not come. Because sometimes the opposition's capability is a variable that your 138 sessions cannot capture. The outside expert who says 'your system is weak' errs by seeing only results. The person who tells me 'process is everything' errs by ignoring the opponent. I hold distance from both—from the Rajshahi T20 dressing room to the national team room. That distance is my vantage, and I do not hide it.

My third notebook holds an inventory of a Dhaka club's storerooms. Sixty-four rooms—dormitories, offices, stores, physio rooms, video analysis rooms. Only eight had air conditioning; twelve had dead lights. The biggest finding: the ball store, where players entered less than once a week. Less than once a week means balls age, seams split, and a trainer tosses them. I am not alleging conspiracy. I am saying cricket's unphotographed infrastructure speaks louder than stadium photographs. Of those 64 rooms, only four contained current board paperwork. The other sixty held civil-service stationery, players' personal storage, or dust. Nobody noticed. My following went from 4,200 to 61,000 precisely on information nobody noticed. People know results. People do not know infrastructure. And infrastructure decides results.

In 2026 I started a social-media cricket page called BDCricTeam, zero budget, one page. What I wrote first was this: how long a drill runs is the real news. After retiring from play in 2026, I moved into TV commentary and gradually became a fixture on Bangladesh home broadcasts. In 2026, during the Mohammad Ashraful disciplinary affair, I served as BCB spokesman. That taught me commentary is one thing and the notebook is another. Commentary is for viewers; the notebook is for sessions. I do not blend them.

On football tactics I hold a position I never declare outright, only reveal through case selection: mid-table sides have solved gegenpressing with athleticism, and elite football is drifting from a game of intelligence into a physical contest. Cricket is undergoing the same shift in a different form. In every franchise league, power-hitting sessions are growing and now occupy nearly half a training week. Defending drills lose time. This is not binary good or bad. But if a batter's annual training sessions total 400 and 220 go to the sweep, when does he relearn the late cut? Who logs that session? The ground clock answers. The scoreboard does not.

The decision I made in June 2026—leaving the desk for the field—was not sacrifice but a change of accounting. I decided to write not the match story but the story of how a match is made. Eight years on, I can see how much of that accounting has balanced. I do not have the full answer, because the count continues. But one thing I know: of those 138 sessions I wrote, my biggest subscriber jump came from a report that said 'nobody chased the ball today.' That was no highlight. Why I never got a Russia ticket, I also do not know. But I have 64 rooms. So: whose session is next? What number is your next notebook entry? And what is the temperature of the room where you are reading this?

The next season starts in six weeks. Three Dhaka clubs are updating their pre-season drill lists. Somewhere, that same drill that took 138 sessions to take hold in 2026 may run again today. Nobody is keeping count. I will. Open your notebook. Can we match clocks?