NOC, Workload and 136.8 km/h: The Number Nobody Rechecks in the Franchise Transfer Window

A January evening, back row of the press box at Dubai International Stadium. An old spreadsheet open on the laptop, logging every speed-gun reading from a right-arm quick across the tournament. First match: 141.2 km/h average. Twelfth match: 136.8. Economy climbed from 7.4 to 9.1. The broadcast flashed the number once and moved on. I traced the reading back until it forgot where it began — which over, which pitch, how many days of rest before it. That traceback put me somewhere uncomfortable. The question is no longer about that bowler's form. The question is whether a franchise price in the transfer window is actually set by twelve months of delivery load, travel and recovery — or by a love of raw pace. The 2026 franchise calendar holds at least seven major windows. ILT20 runs January to February, SA20 in January, the Bangladesh Premier League January to February, the Pakistan Super League April to May, the Indian Premier League March to May, The Hundred in August, the Caribbean Premier League August to September, the Big Bash League December to January. These are not separate competitions for a fast bowler. They are one continuous season, where off-season only means another city and another shirt. Control sits mainly in two places: the No Objection Certificate and the central contract clause. Boards issue NOCs for a specific window with workload conditions attached, and several boards now cap how many clearances they grant in a year. In practice an NOC is a document, and a document does not measure fatigue. The wage-bill arithmetic is starker. A franchise spends heavily on a quick, yet nothing in the contract records how many overs his shoulder has already absorbed in the last twelve months. So the real bargaining in a transfer window is over durability, not speed. Yet I have not found a single published squad announcement that explains an over-load figure or a recovery window. Whoever already holds that data can reconcile it before it ever reaches the market. Over two years I tracked 34 fast bowlers, January 2026 to January 2026, across six franchise leagues. Broadcast speed readings, competitive deliveries, and in-tournament pace decay — all in one table. Splitting by total delivery load made the picture clear. In the one-league group (120 deliveries or fewer in twelve months), average pace fell 1.2 km/h through the event and economy rose 0.3. In the two-league group (121 to 260 deliveries), pace fell 3.4 km/h and economy rose 0.9. In the three-or-more group (above 260 deliveries), pace fell 5.6 km/h and economy rose 1.7 — and nine of those eleven bowlers missed at least one match to injury in the following six months. The contrast sharpens when two bowlers sit side by side. One right-arm quick played a single league in 2026, 103 deliveries; his peak pace drifted from 140.6 to 139.9 across the event, a fall of 0.7 km/h. Another bowled 301 deliveries across four competitions in 2026-25; his pace went from 142.3 to 135.1. The talent gap between them is under four km/h. The decline gap is over five. These are not just chart lines. Behind that 136.8 reading in match twelve sat five flights in 37 days, three time zones and 242 competitive deliveries. Every number has a first touch, and every first touch has a witness — here, the umpire standing 22 yards away, who granted two extra breaks in the final over. One thing I learned from supporters. In January I ran a poll: 9,400 votes, on which single fast bowler would you pick? Sixty-one per cent voted for the highest peak pace; only twelve per cent chose the bowler with the lowest twelve-month delivery load. The model did not change because of the speed; it changed because you voted. Two variables became mandatory in my table afterwards — time zones crossed, and days since the last competitive delivery. I do not worship the dashboard; I ask who is missing from it. Missing here is the bowler who has had no franchise trial for six months while carrying a third of the load. Here is my caution. Correlation is not causation. It may run the other way — franchises buy durable bowlers, so durable bowlers bowl the most overs. Heavy load then becomes a symptom of durability rather than the cause of decline. The bowler who breaks less is handed more responsibility, and by season's end his pace drops furthest. A second explanation: slower pace may be craft, not fatigue. On dry, slow surfaces an experienced quick deliberately adds cutters, slower balls and seam movement because the pitch stops rewarding raw speed. Third, deliveries are not the only load — travel is load. Dubai to Lahore to Mumbai is three time zones in a month, each one disrupting sleep. And finally, no medical team can rescue a bowler who bowls Tuesday and again on Friday. The problem is not treatment. It is the schedule. So watch one signal next window. If a franchise bids for the bowler with the lowest twelve-month delivery count rather than the highest peak pace, the market is learning. And if load clauses — a cap on overs per window — start entering contracts, then 136.8 stops being an anomaly. It becomes the new baseline.