Retention Lists, Workload Clauses and Broken Bowlers: The Real Arithmetic of Asian Franchise Cricket

Before he took the ball for the final over he rolled his shoulder once, and the speed gun behind the bowling end caught the last number of its song: 129.4 kph. The same bowler, the same tournament, 141.2 fourteen days earlier. Nine matches in between. Read the scorecard by wickets and economy alone and those 11.8 kph are written nowhere. For me that is the real headline, because a scorecard does not count fatigue; it only counts outcomes.

Nine matches in fourteen days sounds dramatic, but in the Asian cricket calendar it is not unusual. National series, Asia Cup build-ups, domestic T20, and on top of that franchise auctions and retention lists. From Manchester I watch these windows every year, and the pattern is nearly always the same: the auction price makes the front page, the workload clause gets a footnote. Yet the number that decides whether a fast bowler's shoulder survives the next two seasons is not written on the pitch. It is written in a boardroom.

I think of Mirpur. On 22 March 2026, the Asia Cup final, a two-run defeat to Pakistan. In that final over an entire country held its breath at once. That density, that pressure, is the identity of cricket in this region. But identity has another side, the one that never makes the trophy photographs: how many matches the same bowler had to count before and after the final.

In my own tracking sheet I keep the last three seasons of Asian franchise and international matches apart. For every fast bowler I record three things: balls bowled inside a fourteen-day window, overs bowled, and how many consecutive matches he had to walk back to the bowling mark. The numbers are dry, but joined together they make a picture. Every number has a first touch, and every first touch has a witness. A bowler who has sent down more than ninety overs in fourteen days shows a clearly lower average speed in his last two matches than in his first two. This is not one or two men. On my sheet it is a pattern.

To find where the pattern comes from, I went backwards frame by frame through ball releases. I traced the ball back until the highlight forgot where it began. What I found is that the story of falling speed is not really a story about the ball. It is a story about recovery. Between two matches the bowler had no rest: there was travel, there were meetings, there was a session watching tape of the next opponent. The body had not yet paid off the load of the last match when the next match arrived with its demand.

This is exactly where I bring the audience in, because my model does not speak the truth on its own. Last year I ran a poll: is this drop in pace fatigue, or just a bad day? More than twelve thousand votes came in. The result split—some said fatigue, some said form. But the split is itself data. The model did not change because of the speed; it changed because you voted. After the poll I added two variables: rest days between matches, and travel load.

Then I added a section to the end of every scouting report and called it "fan objections". What the audience is asking gets written down separately. The habit is not new. In 2026, in due diligence on Manchester City's Ederson, City fans on Twitter asked whether the Portuguese league was too slow, and whether the statistics had been dressed up. I spent two weeks re-coding ten matches and added pressure-adjusted data. That is where I learned that a supporter's objection is not an obstacle to me. It is my error correction.

In cricket I am doing the same. Alongside ball-by-ball data I am adding "pressure-adjusted economy"—how much a bowler has conceded while bowling in hard situations. The number of a bowler who regularly takes the death overs and the number of one who gets the easy overs cannot be the same. Mustafizur Rahman has carried the death overs for years, and the pace of a bowler like Taskin Ahmed is a story not only of talent but of workload. On my sheet, bowlers who bowl more pressure overs also show higher fatigue rates and a higher chance of injury the following season.

Injury data matters here. Among Asian fast bowlers, soft-tissue injuries—hamstring, calf, side strain—often arrive on a particular rhythm: when workload spikes suddenly. Treating this as mere bad luck would be a mistake. If workload doubles inside fourteen days, the body has already priced that in. I do not worship the dashboard; I ask who is missing from it. And what is missing here is the bowler himself, the one whose body no one called a meeting about.

Now to the money, because in a transfer window money and the body often sit at the same table. Retention lists, release clauses, workload clauses—that is the real story, not the headline fee. If a franchise retains a fast bowler on a big sum but his contract carries no minimum rest condition, that contract is really buying risk. To me, more important than the release clause is how many matches he will be forced to rest, and who guarantees that rest.

A transfer rumour is a data point until it becomes a person. In the same way, a price is only a number until you know how much shoulder, how much hamstring, how many sleepless physio sessions sit behind it. In the Asian franchise market the relationship between price and load is not always linear, but the relationship exists—and not everyone wants to see it.

There is a comforting explanation here that I do not accept. It is said that the big teams have the best medical staff, so they can handle more matches. What I see says otherwise. Against the condition of two games a week, no medical team can work magic. A physio can speed up recovery and read a scan report, but he cannot buy time for bone and muscle. What the calendar has broken, an ice bag will not mend.

Here I am careful. There is a relationship between fatigue and injury, but a relationship is not a cause. A fast bowler losing pace does not mean he has picked up an injury—that cannot be said outright. He may have deliberately dropped pace and changed his line, the pitch may be slow, the match situation may demand it. Confusing correlation with causation is the biggest trap in my profession. So I keep one specific piece of evidence beside every claim, and one specific context beside every number.

From years of watching matches I can say that this context is what television loses. We see an over, a speed, a dismissal—but we do not see the fourteen-day picture. Those of us who sit with the data have a duty to show that picture. It is the work of making the arithmetic balance.

I remember 2026. Watching fifty Bundesliga matches in empty stadiums during Covid, I wrote that the home-win rate had fallen from 43.3 per cent to 32 per cent, and that referees had awarded fewer fouls against home teams. That was football, but the lesson holds in cricket: when the crowd is absent, one layer of the game changes. I started a weekly Zoom call called "Data & Fans" with thirty supporters from the two Manchester clubs. We did not only talk about statistics; we talked about feeling. Since then my writing has softened a little—from certain declarations towards shared questions.

Seen through diaspora eyes, it becomes clearer still. Watching Asian cricket from abroad, we see two things at once: the team's fight and the pull of home. The bowler playing nine matches in fourteen days is our son, our brother. When his shoulder breaks, a little of our memory breaks too. This is the point where my data and my emotion cannot be separated—so I write them side by side.

So what do I look for in the next window? The signal seems clear to me. A team that decides its retention on strike rate and economy alone is putting its money in the wrong place. The real competition is not for the trophy; it is for managing the calendar. The board that makes the workload clause real, the coach with the courage to sit his best bowler out for one match—they are the ones who will protect the balance sheet two seasons from now.

My model is not finished. Every week I add a variable and remove one. That work will never end, and that is fine. But one question remains: when the scorecard counts only wickets, who will count those 11.8 kph?