138 Sessions, 64 Rooms and an Immutable Ledger: Cricket's Two Books of Account

The white sheet of paper taped to the outside wall of the Mirpur indoor nets said one thing in biro: Session 97/141. Inside, a left-arm spinner ran the same drill for twenty-eight minutes — no ball, just the foot and the shoulder rotating on the same beat, the same angle, without a break. Two sets of records sat on the physio's taping table beside him.

One was on paper. A tea stain in the corner, hand-numbered pages, dates, how many minutes each man logged, which drill repeated how many times. The other was an open laptop: a spreadsheet, contract timestamps, player-load data. Next to it, a phone screen glowed green and red with a dashboard tracking franchise-league fan tokens and on-chain records.

Two ledgers, two clocks. The paper one counts who did what, how often. The digital one counts who owns which data, when it changed, who holds the token. The scoreboard shows neither. Yet almost every argument we have about cricket ends at the scoreboard.

The gap that tournament cycles expose

Tournament years make the gap obvious. Attention drifts to outcomes — who reached the final, who went out in the group stage, what someone's strike rate was, what a bowler's economy looked like. Bangladesh reached the 2026 Asia Cup final in Dubai and lost to India by three wickets. The following year, at the World Cup in England, Shakib Al Hasan made 606 runs in eight innings at 86.57 with two centuries, the highest by a Bangladesh batter at a single World Cup. Further back, in March 2026 at Galle, Mushfiqur Rahim struck Bangladesh's first Test double hundred, and in January 2026 at Chattogram came the country's first Test win, against Zimbabwe.

Those numbers are permanent, public, checkable by anyone. The sessions that produced the 606 runs are not recorded anywhere, not even in part. This is exactly where tournament pressure operates: twelve matches in four weeks, the same question at every press conference, guesswork about squad depth. Results arrive hour by hour. Preparation arrives day by day. The cameras point at one of them.

I talked my way into Abahani Limited Dhaka's 2026 pre-season on the strength of an old MS in sports management and sheer stubbornness. I was present at 138 of 141 sessions that season, carrying a numbered notebook, and every evening I put out a newsletter called Ground Notes from a zero-budget Facebook page. By December it had 4,200 subscribers. Abahani finished runners-up that year, and two of those session reports turned up in a national daily, unattributed.

What gets counted becomes credible

A numbered notebook does one job. You cannot suddenly claim a drill has been running for three months. The pages carry dates, session numbers and an attendance list. That is the real virtue of any ledger — the past cannot be quietly renegotiated. Blockchain is a distant cousin of cricket's paper book. Both aim at the same thing: once it is written, it cannot be altered on the way back.

There is a fine trap here. Immutability blocks tampering, not omission. Data nobody falsifies is also data nobody may bother to enter. A flawless ledger that flawlessly tracks the wrong fields produces nothing but a faster wrong answer. The paper book on the taping table does not record what the physio did to a left shoulder for forty minutes. The spreadsheet does not record who dropped six catches in the third day's nets. Neither ledger knows its own edge.

I built a small instrument for my own use and called it the session-versus-scoreboard lag. In plain terms: it counts how many measurable repetitions sit before a visible change. Take one slip-cordon catching drill. Forty minutes, twice a day, twenty-two days running — forty-four sessions. Then, in the first match of a series, a catch at slip stuck, where the same chance had spilled in the previous series. Television says form has returned. The notebook says the hands had drifted off their line somewhere around session forty-four and came back today.

The lag index does not measure talent. It measures patience. The question is how many sessions a visible outcome took, and what was counted inside that window. A coach who does not count sessions cannot explain his own successes either.

The training ground keeps time better than the scoreboard. That is a rule of accounting, not a slogan. The scoreboard counts minutes. The training ground counts sessions. In 2026, a left-handed batter was out for thirty-six during a chase, sweeping. The scoreboard logged: out, sweep, failure. The training book logged: this batter had lost his shape on that shot four times in eleven days, because his top hand was dropping early against anything outside off. Two lines, ten days apart.

Now to the rooms that no ledger holds. I did not get accreditation for Russia 2026. So I made a rule: 64 matches, 64 different rooms, none of them mine. From 14 June to 15 July I watched in a tea stall, a barber shop, a rickshaw garage, two mosque courtyards and a projector club. Thirty-two days, thirty-two dispatches, followers moving from 4,200 to 61,000. Not one timestamp from those 64 rooms exists on any chain. Who bought the generator fuel, who swept the courtyard, why an Argentina-Brazil argument split a street down the middle — none of it enters anyone's database.

The franchise economy now builds ledgers around marquee signings, tokens and data. The bowler grinding through the 22nd over of a fourth innings does not light up a token dashboard. The loudest transfer battles are brand battles; real value gets built at smaller clubs, in the run-up, in that 22nd over. The data ledger is blind precisely there, because nobody sits down to write it.

Every match has a room, and every room has a different beat. Sixty-four rooms means sixty-four different tempos. No single dataset holds that tempo, because the tempo belongs to the people, not to the match.

What the ledger misses

The popular reading is simple: put everything on an immutable ledger and cricket's trust problem ends. The prescription sounds flawless. The application is partial. A record holds only what someone chose to type. Nobody will log who dropped a catch in the 40th over of a 36th innings. Nobody will log what a physio did to a left shoulder over ten days. Nobody will log who cleaned the Mirpur indoor floor so that the seven o'clock session did not start ten minutes late.

The second misreading is older. A result does not validate a method. I counted 138 sessions before I trusted the drill, but the trust arrived at session 139, when the coach changed the grip by hand and the ball's line returned to where it had been. Counting is not proof. Beside every number sits a counterfactual: what would have happened without this session, what did number 139 change?

The next signal

The real question now is who maintains the ledger, and who owns the empty room. On-chain data has its uses, but the paper book on the taping table is what says who is coming back and who is not. Before the next series, one signal will matter to me: session 139, the physio's log, and that seven o'clock drill the cameras will never see.