The Regular Season Is a Workload Ledger: Inside the IPL's Pace-Bowling Arithmetic

April 2, 2026. Ekana Stadium, Lucknow. The fourth ball of an over leaves the hand and the board flashes 156.7 km/h — the fastest delivery of that IPL season. Four days earlier at Mullanpur, on his IPL debut, he had touched 155.8 km/h and finished with 3 for 27. Seven wickets in two matches. The stands were busy memorising a new name.

Eleven days later, Mayank Yadav was off the field. A side strain. The rest of his tournament became a maybe. That same week the headlines carried the speed record; the injury sat in the bottom corner of the sports page. I read it the other way round. The ball was the headline. The calendar was the story.

From Liverpool I watch the IPL regular season as a ledger — every over, every flight, every recovery window entered in a column, with the sum worked out either in late May or in a scan report in the first week of the next season. In Russia I learned that the first tactical note is always about distance, not drama. Cricket enforces that rule harder, because distance here is measured twice: in kilometres and in maximum-effort deliveries.

Context: fourteen matches, thirteen venues, one invisible deadline

IPL 2026 began on March 22 and ended on May 26. Fourteen league matches per side, spread across seven weeks, across thirteen venues — Ahmedabad to Guwahati, Dharamsala to Visakhapatnam. Even before the knockouts, a team was playing two or three matches a week, with travel, practice sessions, media days and hotel-to-stadium transfers packed between them.

One feature of that season rarely made the discussion. The T20 World Cup began on June 1 in the United States and the West Indies. Every franchise fast bowler therefore carried an invisible deadline: he had to be fit by the last week of May, because the national team's tickets were already booked. Where there is no structural room to rest mid-season, injury and form end up bargaining at the same table.

Add the Impact Player rule, in place since 2026. In simple terms, it lets a side field an extra specialist. In practice, it reshapes how the bowling quota is distributed. The four-over cap has not moved; what has moved is whose hands those overs land in. The third and fourth seamer now carry duties that used to be shared with part-timers who have quietly left the eleven.

Core: the arithmetic of four overs, and the arithmetic outside them

Take the simple number first. A frontline quick bowling four overs sends down 24 balls. Perhaps twelve to fifteen of them are at maximum effort — the powerplay and the death overs. Across fourteen matches that is roughly 170 to 210 maximum-effort deliveries.

Now add the second sum, the one television never shows. Net intensity in a franchise season is not lower than match intensity. A quick bowls six to eight overs in the nets almost daily, and the pressure to push the speed gun is higher there, because that is where the coaching staff test the edge of a skill. My own ball-by-ball sheets cover 46 league-phase matches from 2026 and 2026, and match-day workload tracking counts match overs only. It does not count net overs. That is the first gap.

The travel sum is harsher still. Chennai to Delhi is about 1,700 kilometres; Kolkata to Mumbai more than 1,600. When two days separate two matches, it is called rest — but a flight, a hotel check-in, an optional session and a pitch assessment all fit inside it. Physically, those two days are never two days.

Mayank Yadav is the cleanest entry in this ledger. In IPL 2026 he played four matches and took seven wickets. Across those four he was the fastest bowler in the tournament, and across those four his body was demonstrating that a 21-year-old shoulder is not finished being built. My long observation is that quicks who mature physically ahead of their age get pushed into senior rhythms early, and the loan is repaid later with interest. In 2026 his body spoke the same language, though by then the message was no longer new.

The second entry is Jasprit Bumrah. In IPL 2026 he took 20 wickets in 13 matches for Mumbai Indians. Immediately after came the 2026 T20 World Cup, where he was Player of the Tournament with 15 wickets at an economy of 4.17. Then Test series from September to January — Bangladesh, New Zealand, Australia. He took 32 wickets in the Border-Gavaskar Trophy and was Player of the Series, but back spasms arrived in the Sydney Test in January and he could not bowl in the second innings. He was absent from the 2026 Champions Trophy.

Read that list and it is tempting to blame a league. I do not accept it. It is the output of a ledger in which the IPL was the most visible column while the largest entries sat before and after it. Bumrah's workload has been managed by the Indian board across an entire year — IPL, World Cup, Test Championship, ODI series. Four formats, three continents, one body.

One more thing stands out in my charts, and the cameras do not chase it. Lucknow's middle-overs spin block was a lesson in patience disguised as suffering. Between overs seven and fifteen, the share of overs bowled by spin is creeping up, because franchise coaches have understood that the real currency of a league season is not a seamer's speed but a seamer's availability. A side that absorbs pressure with spin through the middle keeps its frontline quick fresh for the death. Spin here is not the slow option. It is a load-bearing wall.

Contrarian: the real gap is in the nets, not the matches

The accepted line is that franchise leagues break bowlers. My reading is that the league is only the visible part. The risk is manufactured in the ten days before a season and the fortnight after it, when no tracking system is switched on. In pre-season camps quicks bowl their heaviest loads, because fitness testing, line-and-length drills and match simulation all run at once. At the end of a season a bowler leaves the franchise and walks straight into a national camp, because nobody left a gap in the calendar.

The second point is less comfortable. We pay a premium for 150 km/h — at the auction table, in the highlight reel, in the sponsorship deal. Recovery infrastructure is budgeted far lower at that same table. Sleep science, load-management software, the physiotherapist-to-player ratio: none of that sells an auction night. The auction table looks like a jigsaw puzzle with missing corners, and nobody wants to look at the corners.

The market rewards urgency, but the spreadsheet rewards silence.

This is also my objection to the Impact Player rule. It adds batting depth; granted. It also lets a side concentrate its bowling quota: three quicks can cover the powerplay and the death almost entirely, because a fourth bowler is carrying an extra slot. The consequence is that the fastest of those three absorbs the same duty every match. Less variation raises injury probability. That is physiology, not tactics.

Takeaway: what to count next season

In the next regular season, the first thing I will count is consecutive matches in which a single quick bowls four overs. If a bowler is taking powerplay and death overs in four straight games, that is a red flag for me regardless of the result. Second, I will write the travel leg between matches next to the scorecard. Third, I will watch whether boards and franchises agree on a defined off-ramp — a mandatory rest window before a world event, or a cap on net overs. Until that off-ramp exists, speed records should be read as advance notices of future injuries.

The last column of the ledger is the one nobody reads, because the numbers there accumulate in silence. Mayank Yadav's 156.7 km/h taught all of us to remember a name. If someone had written the flight kilometres and the net overs beside that ball, the following eleven days might have looked different. Next season, whenever a bowler touches 155, my first question will be about distance, not speed.