The Dot-Ball Ledger: Two Truths of the BPL Regular Season — Scoreboard and Process

Sylhet International Cricket Stadium, one night in the regular season. A chase of 178, and 119 on the board after 14 overs. In the commentary box the phrase "controlled chase" kept floating around. Beside the scoring bay I had a notebook open, logging ball by ball — bowler type, line, length, field placement, the batter's swing pattern, and how hittable that delivery actually was before it reached the bat. Across the first four overs of the last six, seventeen consecutive deliveries produced a dot or a single; only three arrived in a stroke-making length.

The failure did not come from the batter's hands. It came from the bowling plan and the field angles. When the match ended, the scoreboard declared one side the winner; my ledger showed a gap of roughly twenty-two runs between the two sides' processes. That night a fielding plan won, and a batting side did not lose its talent. The space between those two sentences is what I want to open up here.

When I was building PitchMetrics Asia's data desk in Sylhet in 2026, there was no Hawk-Eye and no tracking contract. There was a notebook, a pen, and match video. That year I charted 14,800 deliveries from 132 matches by hand into coordinates — release point, pitch location, footwork, shot direction. Two junior writers were trained on a single rule: write every ball's chance quality on the same scale, so that different people on different nights would log data in one language.

Out of that habit came my expected runs model — xRuns for short. It is not cricket's xG. In football, the shot and the goal are nearly the same instant; in cricket, ball meeting bat, fielder positioning and running between the wickets are three separate decisions with three separate failure probabilities. So the model splits into three layers.

Layer one is the delivery's hittability — line, length, pace, spin angle, and how it matches the batter's swing plane. Layer two is shot quality — timing, elevation, field angle. Layer three is the realised outcome — runs, dots, wickets. Each layer carries its own error bar, and I never drop the stadium-effect variable; the bounce in Sylhet, in Mirpur and the dew in Chattogram behave in three different ways.

This raises a question now circulating in Bangladesh's data circles: if someone can quietly edit this ledger afterwards, where does its testimony live? The raw tracking file, the scorer's app entry and the broadcast graphic can carry three different numbers, and the ordinary viewer has no way to verify any of them. That is where the blockchain-backed ledger idea earns its keep in cricket — once a ball's annotation is hashed, nobody can silently change the number sitting beside it. If the ledger lies, the entire process analysis becomes worthless.

Net run rate is not the first indicator in a regular season. In a play-off, decisions arrive in one match inside seven days; in a regular season they arrive across eight straight weeks, where form, injury, travel and bowler workload all fluctuate together. Across those eight weeks I read three layers separately: powerplay intent, middle-over spin pressure, and death-over execution.

The real powerplay indicator is intent, not boundaries. Fifty-eight runs in six overs or forty-one in six overs — both numbers look pleasant, but the ledger shows the difference in where the dots sit. A side that leaves 42 percent of deliveries in the powerplay carries a low intent score; even at 35 runs in six overs, that side will demand its price later, because boundary rhythm not built in the powerplay returns in the middle overs as slog-sweep risk. This season the top three sides' powerplay intent scores read 71, 64 and 62; the table order is not that order. That is the first crack.

The middle-over spin pressure index does the job of football's PPDA. In football, PPDA measures how much pressure is applied before an opponent's pass; in cricket I measure how many deliveries a batter concedes as dots out of his own footwork hesitation before being forced into a sweep or a charge. Across this season's top four spin spells, 96 deliveries produced 61 dots; 39 of those carry visible evidence of a back foot getting stuck in frame-by-frame logs.

Before publishing that number, one condition has to be attached: at least eight of those 39 saw the batter show intent toward cover and then abort the shot because square leg was up. The pressure therefore is not only the ball's quality — the field setting blocked that intent. Fail to separate the two causes and a spinner's numbers inflate while his captain believes he is unplayable.

The currency of the death overs is predictability, not the yorker. Across the last four overs I separate two things in a successful plan: the bowler-and-captain field pairing, and the bowler's back-up delivery. Pairings that produced at least two consecutive "safe" deliveries per over in the last four kept an economy under eight. Pairings that leaned purely on the yorker drifted into double figures per over whenever the back-up delivery failed.

One name keeps returning in my batter ledger — Soumya Sarkar. When I wrote about him for The Daily Star in 2026, I assumed the issue was shot selection. Eight years on, the data says something else: his powerplay intent score is the highest in his side, and the deliveries he leaves before being dismissed carry a hittability 0.04 lower than his team's average. He plays fewer gratuitous shots; rather, he takes on more pressure to strike balls that are not strikeable. The gap is small, but its coaching implication is not.

Another name surfaces often: Towhid Hridoy. In the first phase of the regular season his strike rate against spin read 128; against pace, 149. That gap is not about talent but about role. When a spinner bowls, he is holding an innings together; when a seamer bowls, he is the finisher. Run one batter through two roles and his numbers will never sit on a single line — nor is it fair to judge him on that line.

The team process table is updated weekly and published with its uncertainty attached. The figures below cover the first eight matches of the regular season, with names deliberately withheld:

| Team | Powerplay Intent | Spin Pressure Index | Death Economy | Process Rank | |------|-----------------|--------------------|--------------|--------------| | Team A | 71 | 0.68 | 8.2 | 1 | | Team B | 64 | 0.61 | 8.9 | 3 | | Team C | 62 | 0.72 | 9.4 | 2 | | Team D | 58 | 0.52 | 7.8 | 4 |

One caution is essential when reading this. Team D has the best death economy, but the weakest spin pressure index — it is surviving at the back end and not in the middle. In a league table these two kinds of sides sit side by side; in a play-off, the first survives and the second is knocked out.

Now the uncomfortable part, where my own model stops me.

Correlation is not causation. Anyone claiming that the process rank one side will lift the trophy skips three gaps inside the model. First, sample size: across eight matches and 960 deliveries, the confidence interval on the spin pressure index is wide enough that a 0.05 gap between two sides decides nothing. Second, toss and venue effects: a side batting second in six of eight matches will naturally show a better death economy, because the problem arrives before the dew. Third, my hittability score is video-based — camera angles sit beside the galleries in Sylhet and straight on in Mirpur. Change the angle and the score shifts slightly, and failing to subtract that shift from the entire list makes the analysis dishonest.

The scoreboard also deserves respect. Process neutrality is a trap. Assume a side winning implausible matches one after another is merely lucky and we miss what it teaches: clinical finishing, the habit of holding hard catches, the correct bowling change under pressure. From those, the definition of process has to be rewritten backwards from the ledger. Stop learning from results and the model does not grow — it wraps itself in its own arrogance.

The market and the process model belong in separate books. In franchise cricket a player's price is now set by tournament performance, where an eleven-match strike rate often settles a six-month contract. Six of those eleven matches in my ledger had rain-truncated inputs; two had pace-suppressing pitches. Price and process estimate can be made to meet on the same sheet of numbers, but one states a future and the other explains a past. House them together and nobody can be held responsible for the error.

Workload control is the most neglected ledger right now. In a regular season, sides that reduce back-to-back spells for their seamers and prefer chairs over bone-grinding four-over bursts see economy fall in the final two weeks, average pace drop by 2.1 kph, and dot-ball rate rise by four percentage points. These are my desk's calculations; not every franchise shares wrist-spread data. I treat them as decision evidence, not proof.

I built the first xG ledger in Sylhet, and that ledger rewrote the game's accepted history for me. A World Cup final gave me two truths — the scoreboard and the process. Empty stadiums taught me that silence has its own expected goals. What this season adds is the question of blockchain-like verifiability: who wrote the entry, when, and whether anyone changed it afterwards.

Before the regular season ends, the writer has exactly one luxury — time. The side that reads these eight weeks of ledger and changes its weakest layer before the play-offs will not merely climb the table; it will become a carrier of process. Who takes the title, the next six weeks on the field will decide. But the ledger has already written which processes can carry a trophy. The only question left is who forgets to read their own ledger on the way to the final four.