The Net's Clock, the Scoreboard's Clock: A 138-Session Ledger from Rajshahi

Rajshahi, a November morning. On the left-hand net beside the Shahid Kamruzzaman Stadium, a left-arm quick released his thirty-ninth ball of the spell, it drifted outside the pitch line, and nobody chased it. That ball is on no camera; it will never make a highlights reel. I wrote in my notebook, page nine: ball 39 — no one chased. Beside me at the physio's table, three ankles taped, an ice pack on a fast bowler's shoulder. The clock read 9:47. Outside the nets, a tea stall's television was replaying the previous night's match, and the only question there was who bats at the death. Inside the nets the question was entirely different: why did nobody chase ball thirty-nine?

In 2026, at Abahani Limited Dhaka's pre-season, I attended 138 of 141 sessions with a numbered notebook and filed a nightly newsletter called Ground Notes. It launched on zero budget, reached 4,200 subscribers by December, and two of its session reports were cited unattributed in a national daily. Abahani finished runners-up that season. The real result, for me, was something else: I stopped opening with scorelines. The scoreboard measures an outcome; the training ground measures a process, and the process starts long before the outcome. I counted 138 sessions before I trusted the drill.

We are inside a tournament cycle now. The calendar is compressed: domestic leagues, the BPL, bilateral series, ICC events — body and mind under continuous load. Bangladesh's pace pool feels this hardest, because depth is thin and the workload is not. In that situation the question that should arrive first — who plays — arrives last. What should arrive first is: who has been prepared across how many sessions, and which drill has actually been mastered?

Across two months in Rajshahi, Bogura and Dhaka, I have watched the same thing in several nets: bowlers counting overs, batters counting runs, nobody counting drills. Yet the drill is the only unit you can genuinely change before a match. So I built a small instrument and called it the Session Tempo Index. It is not complicated. It is five numbers from one drill, logged in the notebook. One: balls bowled in a spell. Two: seconds of rest between balls. Three: balls nobody chased. Four: minutes spent at the physio table. Five: mid-drill interventions by the coach. The pattern those five numbers form tells you whether a bowler is genuinely match-ready or simply bowling.

An example. Last week, in a 24-ball spell, rest averaged 90 seconds — the bowler was working faster than match pace. But eight balls in that spell finished outside the pitch line and nobody chased. The Session Tempo Index read 24/90/8/12/3. Six months earlier the same bowler read 24/65/14/25/6. Rest is up, physio minutes are down, but the unchased-ball count is still eight. What does that mean? The body is being built; the skill is not. That gap is the biggest story I have, and it appears on no scorecard. When the net's clock runs ahead of the match's clock, a bowler starts dragging his feet in matches, and nobody notices.

Let me state the vantage plainly. I live in Bangladesh, I work in Rajshahi, and I sit at the edge of the net, not on a press-box cushion. I do not treat the country as an outside project, and I do not treat players as specimens — they are interpreters of their own time. Last month a quick told me: sir, I know I have to bowl the last over. But I do not know what will happen to my leg in the twentieth over. That single line holds the whole discussion.

Now the numbers on the field. Across the last six one-day matches I have kept an over-by-over count. Between the 11th and 25th overs our dot-ball rate was roughly four per over. In those fifteen overs — 90 balls — we scored about 55 to 60. In the last ten overs we scored more than 90, sometimes 110. So the story is this: our finishing is not actually poor; our middle overs are inert. And the cause of inert middle overs is not talent, it is rotation.

Rotation means a chain of three decisions. First, how the spinners' overs are allocated — whether a bowler like Mehidy Hasan Miraz spends his best overs hunting wickets or blocking runs. Second, the use of right-left pairs — whether a left-hander is sent in early against the opposition's leg-spinner, or whether the left-right order stays locked to the team sheet. Third, the habit of taking singles, the willingness to turn the strike for one or two rather than waiting for the boundary. All three are trainable in the nets, and all three show up directly in the 11-to-25 ledger.

The workload sum sits here too. The load on an experienced quick like Taskin Ahmed, the session tempo of a youngster like Nahid Rana, and the second spinner's overs — if these three are not divided, the middle overs will never create pressure. I have seen that when a young quick is given spells longer than 18 balls in the nets, his line and length over the final six balls collapses dramatically. In a match, those six balls come back as 12 to 18 runs. That is not a ceiling on talent; it is workload arithmetic.

Now the point where the outside reading goes to the wrong address. Almost all our discussion hangs on one sentence: there is no finisher. It comes up on talk shows, trends on social media, and the next match sends a new batter at number six. Calling that wrong would be unfair, because it is a symptom. But treating a symptom has not cured the illness. In September 2026, the ten-wicket win over Pakistan in Rawalpindi — Bangladesh's first Test victory over Pakistan, the series taken 2-0, per the ICC match report — came from the opposite cause. There was no finisher question that day, because the match was won with patience between the 11th and 25th overs: the bowlers squeezed the run rate in that phase, and the batters kept that same phase above three an over.

That is the problem with scoreboard-first reporting. The last-over six is easy to describe, so it gets described. Yet the match was built in the thirty overs before it, where there was no drama, only rotation. I never got a Russia ticket, but I got 64 rooms, and sitting in them I learned something: the crowd remembers the last five minutes, but a match is not built in the last five minutes. Every match has a room; every room has a different beat.

So what does session 139 actually change? If session 139 is another repetition of the same drill, nothing. But if one condition changes — a middle-overs simulation with seven fielders in the ring, two deep, and the bowler told that five of six balls must hit the stumps — then the index's unchased-ball count begins to fall. Nobody logs that single condition change, because it is not news. Yet in the next three matches the middle-overs dot rate drops from exactly that place. The counterfactual is simple: without session 139, that middle-overs inertia would have stayed unchanged for another six months, and nobody would have known why.

One warning for myself. The number 138 proves no quality on its own. Attendance and improvement are two different things. If I only count attendance, I am writing a club's attendance register, not an explanation of cricket. So beside every count I write which drill changed in that session, and which did not.

The training ground keeps time better than the scoreboard, because the session ledger keeps running even when the field empties. When the ground goes empty, the silence has a tempo — who leaves last, who sits with the ice, who has the final word with the coach. Those small behaviours are the signal for the next match.

I observe the repetitions, not the highlights; the beat lives in between. The numbers that go into a fresh page of my Rajshahi notebook next week will tell us whether Bangladesh's middle overs are moving. So the question is not the last over. The question is the twentieth over. And the room holding that answer is not in a Dhaka press box — it is beside a Rajshahi net, in front of three taped ankles.