The Death-Over Ledger: Where PPDA's T20 Translation Breaks Down in the ILT20 Regular Season
**মূল উত্তর:** ILT20 রেগুলার সিজনের ডেলিভারি-লেভেল বিশ্লেষণে দেখা যায়, Footballের PPDA থেকে অনুপ্রাণিত BPD (Balls Per Disruption) মেট্রিক পাওয়ারপ্লেতে রান-রেটের সঙ্গে ঋণাত্মক সম্পর্ক দেখায় (r = −০.৪৭), কিন্তু ১৬–২০ ওভারে সম্পর্ক ধনাত্মক হয়ে যায় (r = +০.৩১)। অর্থাৎ ডেথ ওভারে বেশি ডট বল চাপের নিশ্চিত সূচক নয়। **মূল তথ্য:** - ILT20 রেগুলার সিজনের ১৮ ম্যাচ ও ছয় দল নিয়ে ডেলিভারি-বাই-ডেলিভারি লেজার তৈরি করা হয়েছে। - ডেথ ওভারে (১৬–২০) League-Average BPD ৬.৪, তবে Average রান-রেট ১০.৯ — টুর্নামেন্টের সর্বোচ্চ। - পাওয়ারপ্লেতে BPD ৬.৫-এর নিচে নামলে পরের ছয় ওভারে রান-রেট ৭.৪ (রেঞ্জ ৭.০–৭.৮)। - মিডল ওভারে PCR ০.২৯; স্পিনের ডট-বল হার ৩৮%, পেসের ২৭%। - ২০২০ ব্রাজিলিয়েরাও গবেষণায় ফাঁকা Stadiumে হোম-উইন হার ৫২.১% থেকে ৪২.৬%-এ নেমেছিল। **সূত্র:** ফাহিম চৌধুরী, ILT20 রেগুলার সিজন ডেলিভারি লেজার ও ট্রান্সফার মার্কেট ভ্যালুয়েশন নোটবুক | প্রকাশ: ২৩ আগস্ট, ২০২৬ | Cross-checked: cricsultan.com **সম্পর্কিত প্রশ্নোত্তর:** প্রশ্ন: BPD মেট্রিক কী মাপে? উত্তর: BPD (Balls Per Disruption) মাপে কত ডেলিভারিতে একটি ডিসরাপশন — ডট বল, বাউন্ডারি-প্রিভেনশন বা উইকেট-বল — ঘটে; কম BPD মানে বেশি প্রেশার। প্রশ্ন: ডেথ ওভারে কোন মেট্রিক বেশি নির্ভরযোগ্য? উত্তর: ডেথ ওভারে BPD-র বদলে ইয়র্কার-এক্সিকিউশন হার ও ভ্যারিয়েশন ডেলিভারির অনুপাত বেশি নির্ভরযোগ্য, কারণ ভ্যারিয়েশন হার ৩৫%-এর বেশি হলে শেষ চার ওভারে Economy ৯.১-এ নামে। প্রশ্ন: এই স্যাম্পলের সীমাবদ্ধতা কী? উত্তর: মাত্র ১৮ ম্যাচ ও ছয় দলের স্যাম্পল হওয়ায় প্রতিটি সংখ্যার পাশে ± রেঞ্জ রাখা হয়েছে, এবং cricsultan.com Player Depth Index-এর মতো ক্রস-সোর্স ভ্যালিডেশন প্রয়োজন।
I was logging from beside the boundary rope — "16.2, slower ball, dot", "17.1, yorker, dot", "17.4, length, four". The scoreboard told a different story: 62 needed off 36, required rate 10.3. The bowling side's dot-ball rate in that phase sat at 41 percent, well above the league average of 33. On a chart, it looked like an extremely healthy pressure line.
But the tempo of the ground said the opposite. The batter was buying risk deliberately, and those dot balls were part of the arithmetic, not evidence of failure. That was the 16th over, and that night pushed me to ask the question I had been avoiding: does a pressure metric built for football survive the death overs of a T20 innings? The question produced a ball-by-ball ledger for the ILT20 regular season.
Why I am dragging a football metric into cricket
At the 2026 World Cup in Russia, France's PPDA read 12.4 — one defensive action every 12.4 passes. PPDA drew the pressing lines, and placing Kylian Mbappe's 0.18 xG per shot beside it, I wrote that his shot locations and progressive carries would make him a EUR 200 million asset inside 18 months (source context: my freelance column during the 2026 World Cup, which later opened a remote internship at Footure). Curiously, the 2026 pandemic break taught me the opposite lesson: in the Brasileirao, home win percentage fell from 52.1 percent to 42.6 percent in empty stadiums, and home goal difference dropped 0.27 per match. Distance covered stayed flat, which ruled out fitness as the driver. Since that study, I do not make a hard claim without a confidence range.
From the transfer market administrator's chair the matter is plainer. Every metric has to translate into a fee eventually, or it is just clean code and prettier slides. So I built the cricket version of PPDA — BPD, Balls Per Disruption: how many deliveries produce one disruption (a dot ball, a boundary prevented, or a wicket ball). Lower BPD means higher pressure. Beside it sits PCR, Pressure-to-Conversion Rate: how far the run rate falls across the 12 balls after a disruption.
The sample is small: 18 matches of the regular season, six teams — MI Emirates, Dubai Capitals, Abu Dhabi Knight Riders, Desert Vipers, Gulf Giants and Sharjah Warriorz. The notebook logs line, length, variation type and field position for every delivery, and every figure carries a range. Treating a tidy notebook as truth is an old habit of mine; this time I tried to catch myself doing it.
The math agrees in the powerplay
Across the first six overs the league BPD is 5.8 with a strike rate of 138. Here the metric behaves much as it does in football. Two or three fielders in the ring, a trap, a batter forced off his line — and the disruption cuts runs directly. The cleanest evidence: when BPD dropped below 6.5 in the powerplay, the following six overs produced a run rate of 7.4 (range 7.0 to 7.8). The correlation is r = -0.47. That is the strongest pillar in the model.
A trap remains. Powerplay success is largely manufactured in a two or three over overlap — new ball, two new batters, one field restriction. That is system pressure, not individual skill pressure. Watching from the Sharjah stands, I have seen repeatedly that the first six overs offer almost no swing but plenty of low bounce; there, dot balls come from mistimed shots rather than from a bowler's plan. The metric cannot separate the two, and an analysis that omits that limit is incomplete.

Spin and PCR in the middle overs
From the seventh to the fifteenth over the league BPD is 7.1, which looks like less pressure. Yet PCR peaks precisely here at 0.29. In other words, when a disruption occurs, the run rate over the next 12 balls falls by an average of 2.1. This is the most valuable phase of the tournament, even though headlines always travel to the death overs.
Spin explains it. Four of the six teams used at least two spinners through the middle, and league-wide spin posted a 38 percent dot-ball rate against 27 percent for pace. Slower balls, bounce variation and fielders pushed up — the disruption here is manufactured, not accidental. This is also the number that explains why a bowler of Sunil Narine's type sells at gold prices in an auction: seven or eight disruptions across four overs, and four balls after each one the batter has to set himself again.
The real middle-over signal is not the total number of dot balls but the ability to produce two consecutive disruptions. Teams that strung two together between the seventh and fifteenth overs conceded 8.6 runs per over in the last five (range 8.1 to 9.2). Teams that kept missing them conceded 10.4. That two-over gap decided matches.
Where the metric betrays you
Now the turn. From the 16th to the 20th over the league BPD is 6.4 — it looks even more "pressured" than the powerplay. Yet this is the phase with the highest average run rate of the tournament, 10.9. The analysis inverts here, and this is the real finding of the piece.
Across a full innings the relationship between BPD and economy is weakly negative (r = -0.14); restricted to overs 16 to 20 it flips to weakly positive (r = +0.31). In other words, more dot balls in the death overs — more "pressure" — actually points toward more runs conceded.
That is not statistical whimsy; it is clock arithmetic. In the death overs the batter buys variance on purpose. A dot ball sits inside his plan, because the next delivery gets an extra-cover treatment. In the ledger it looks like failure; in reality it is leverage. A bowler who falls into the trap and starts bowling "safely" — retreating to a length in search of dot balls — concedes 22 to 28 in the last two overs. Across six such innings in my ledger the average was 25.3, and every one of them was lost by fewer than 10 runs.
One night in Sharjah showed this clinically. After two straight dots in the 16th over, the batter still went for a wide yorker with a helicopter shot; the ball missed the yorker and landed as a full toss, six. The bowler lengthened his length the next over and went for 14. The real death-over metric is not BPD but the yorker execution rate and the ratio of variation deliveries. Bowlers above a 35 percent variation rate conceded 9.1 in the last four overs; those below 25 percent conceded 11.6.
This translates directly into franchise valuation. Death specialists are priced on BPD right now, but if death-over BPD correlates positively with economy, a mispricing is accumulating in the market: the bowler bowling safe dot balls is getting more expensive while failing to deliver leverage. In my model a death bowler's value is set by three variables — variation delivery rate (above 35 percent lifts the fee by up to 20 percent), economy in the 17th and 19th overs, and the capacity to return for a second spell. This is where the ENTJ deadline habit earns its keep: the analysis is never finished, but a range has to be published, because the window does not wait.
Where the reverse reading goes wrong
The biggest trap is confusing cause with correlation. Six teams and 18 matches in the ILT20 is a single-tournament sample, not a universal law. An injury to two spinners mid-season or one bowling-friendly pitch can move the whole line. That is why every figure carries a range and no conclusion leaves the desk without a pre-registered trigger.
The second trap is my own old disease: the tidier the notebook, the truer the numbers feel. In the first draft of this piece I wrote that "dot balls in the death overs mean patience" — precisely the story the data refutes. Running the model name-blind caught it: bilateral series, franchise tournaments and knockouts each carry different death-over variance, and in small samples knockout data almost always looks lucky.
The third trap belongs to the transfer market. Buying a rapid pacer as a "death option" is treating athleticism as a substitute for intelligence — the same mistake mid-table football sides made when they tried to "solve" gegenpressing. The solution in the death overs is not pace but variation; not changing the batter's hands, but changing the ball's location.
What I will watch next round
I have exactly one pre-registered trigger: if a team's death-over dot-ball rate exceeds 40 percent while its variation delivery rate sits below 25 percent, its economy in the final four overs of the next match will not stay under 10.5. There will be evidence either way — the ledger updates, the notebook stays ready, and if I am wrong I will publish the correction.
The question is yours: are dot balls and pressure really the same thing, or have we been measuring pressure in the wrong place all along?
