Every Ball Is a Block: How the Regular-Season Ledger Tells the Truth Before the Table Does

Every Ball Is a Block: How the Regular-Season Ledger Tells the Truth Before the Table Does At Mirpur on Friday night, the scoreboard read 78 for 1 at the ten-over mark, chasing 165. The broadcast win-probability graphic said 31 percent. My laptop ledger said 58 percent. Same match, same ball, a 27-point disagreement — and the disagreement was not an error. It was two different questions. The graphic was asking who has played better so far. My ledger was asking what happens over the remaining 60 balls if the fielding side gets its one working weapon into the right overs. That is roughly what happened. The six overs after the tenth produced 29 dot balls, three wickets, and a middle-overs spinner who split his four-over quota into two distinct spells — flat in the first, pushed through in the second. The scoreboard narrated an unexpected defeat. The ledger narrated an appointment. I built the first xG ledger in Sylhet, and the numbers rewrote the game; in cricket the same principle runs ball by ball, where every delivery is a block and every over is a chain, and the chain cannot be edited retroactively. The regular season offers a luxury that knockout cricket destroys: time. In this season's table, the top four teams sit five points apart, but their net run rates are separated by 0.23. Across the ten matchdays that remain, that table will not move on run rate. It will move on the discipline of conserving deliveries. I have watched this game for 34 years from radio cabins, television commentary boxes and, more recently, from a ledger — and the thing you notice first at the ground is the weight of the weather; the thing you notice after you leave is how little of it the scorecard understood. Every row in my ledger carries five columns: delivery type, line-and-length bin, batter position, match phase, and a dot/boundary/wicket flag. This season to date: 42 matches, 9,864 legal deliveries, 1,107 boundaries, 3,482 dot balls. Two junior writers at the Sylhet desk log shot coordinates for every match, because the scorecard never tells you whether the ball was outside off or pitched on leg. A spreadsheet is a monastery, and I take vows in columns and rows — but the first vow is to publish the assumptions. So here are the assumptions. This ledger measures decisions, not talent. Boundary data is reliable; explaining the cause of a dot ball requires video. The error band runs at plus or minus 1.8 percentage points per match, slightly wider against senior pacers, slightly narrower in dew-affected second innings. A ledger that does not record its own error bars is not a ledger; it is a press release. The first finding: in the powerplay, position is set not by run rate but by the ratio of dot balls. There are at least two roads to 55 off six overs — 27 dots and four sixes, or 16 dots and nine fours. The scoreboard says 55 either way, but these are two different kinds of cricket. In my dataset, teams keeping their powerplay dot rate below 38 percent have won 11 of 17 matches, or 64.7 percent. Teams above 45 percent have won five of 14. Their six counts are almost identical — 63 against 58. The difference sits in accounting, not aggression. There is a subtler thing I have watched repeatedly from the stands. A powerplay dot is not a zero; it is a free extra matchup handed to the bowler at the other end. Four dots in five balls eventually drags the sixth bowling option into the attack, and by then the field is set at deep midwicket. A side that eats 36 percent dots in the powerplay is effectively carrying a handicap that never appears in the run-rate column. The second finding is the most valuable row in my ledger: the wicket actually falls two balls early. Of the 213 middle-overs wickets (overs 7 to 15) in this sample, 131 — 61.4 percent — were preceded by at least one dot ball from the same bowler out of the same length bin within the previous two deliveries. The mechanism is not complicated. After two dots, scoreboard pressure rises, the required rate speaks, and the batter selects a shot outside his natural game — cross-bat, sweep, or the lofted flick. The catch goes to mid-off, the credit goes to the fielder, and the ledger files it as an event from two balls earlier. This is why I log how spinners split their spells, because the split is a structural decision rather than a skill. For bowlers who push it flat in their first two overs and then bring the pitched-up delivery in their last two, the conversion rate from pressure-dot to wicket runs 1.6 times the league average. Silence and uncertainty are data; the difference here is not the ball, it is the setup. I do not chase results; I interrogate the process until it confesses — and in the middle overs the process confesses in one sentence: make the batter play a necessary shot first, then make him play an unnecessary one. The third item I call the fifth-bowler tax. Teams that bat a specialist at seven and bowl a part-timer at six concede 9.7 runs per over between overs seven and fifteen. Teams that field five genuine bowlers concede 7.9. That is roughly 11 runs across six overs — wider than the margin in a typical match. The cost is booked in the grandstand; the invoice arrives in the points column. The World Cup final gave us two truths: the scoreboard and the process. I was on a live data desk for the 2026 football final, where France won 4-2 but the model recorded 2.1 against 1.8, and one side's pressing number invited the other to own midfield. On that ledger France won on execution, not on control. Cricket translates the same lesson into different units while keeping the principle intact: the scoreboard asks who won, the ledger asks who was going to. The fourth finding is short and about home advantage. In Sylhet this season, chasing sides have won 58 percent of second innings; in Dhaka, 46 percent. The pitches are not that different. What differs is night dew and a ball that grows heavier in the sprint. Ignore that and the home-advantage calculation tilts the wrong way. Empty stadiums taught me that silence has its own expected runs — during the pandemic years, home advantage in my model erased roughly two-thirds of itself, which means it was never a story about the pitch. Now the market bridge. The transfer market is not a bazaar; it is a probability engine with agents. Bangladesh's auction prices strike rate and pace, because those are visible in columns. The middle-order batter who shaves seven and a half percentage points off his dot rate, or the left-arm spinner who converts middle-overs pressure into wickets, is routinely underpriced by that engine. Auction rooms still look at highlight reels more than at ledgers, which is precisely where the inefficiency lives. A spreadsheet is a monastery, and a monk's hardest test is the night he begins to doubt his own ledger. My doubt arrives from three directions. The first is statistical, and it points straight back at my opening finding. Correlation is not causation. Teams that are ahead can afford dots; teams 30 behind cannot. Powerplay dot rate is therefore partly an outcome as much as a cause. My error band around that 11-of-17 record is plus or minus 12 percentage points, which means a large slice of the gap may still belong to luck. The second doubt concerns my own eyes. I log deliveries; I do not log decisions. When a batter chooses one of four possible shots after two dots, the ledger records the choice but not the three roads not taken. Half the evidence for my belief that middle overs are won by setup lives outside my data, inside the video. The third doubt is deliberate discipline about markets. Market-implied probability and model probability are different animals, and neither should be dressed in the other's clothes. The price on a second innings contains dew, reputation and crowd mood — three things invisible in my ledger. And on a night with no dew, my model is at its worst. Three signals will reach the table before the results do. First, powerplay dot rate: at least one of the two bottom sides will jump, because their position comes from a dot rate that has sat above 42 percent for five straight matches, not from weak batting. Second, the spinner's spell shape: sides that never give their primary spinner three overs in one block are converting fewer chases past 140. Third, the team sheet at number seven. The night a side replaces a part-time sixth bowler with a genuine fifth, the fifth-bowler tax disappears from the invoice — and it shows in the table that same night, not three weeks later. The number burning brightest in my ledger right now belongs to no batter. It is a question: the regular season is the rare condition in which results give process no time to answer, and that is exactly where the ledger does its work. Watch which side agrees to give up the comfort of a sixth bowling option.