NOCs, Wage Bills and the 22nd-Over Speed Drop: A Reliability Filter for Asia's Cricket Market

There is a spreadsheet on my laptop I call “Speed Decay”. Across three seasons I hand-coded more than a hundred matches from Asia's franchise leagues and bilateral series, keeping four columns only: the speed reading, the over number, the delivery type, and how many balls that bowler had sent down in the previous seven days. The cruellest column is the fourth-spell average drop.

In the stands at Mirpur the verdict is always the same: “He got the money and went soft.” The spreadsheet says something else: one hundred and forty-plus deliveries in six days, a red-eye flight, two timezones, and a No Objection Certificate with a date on it.

Every number has a first touch, and every first touch has a witness. This piece is an attempt to find those witnesses — and to answer the question that dominates every Asian cricket window: who is actually moving, and how much of it is contract, how much is source-based noise.

I have traced highlights back until they forgot where they began. A speed-gun graphic clipped and shared ten thousand times usually leads back to a tired neck in the 22nd over. Transfer rumours deserve the same discipline: where did the claim originate, who said it, what was paid for it, and where is the paperwork.

The release clause is not the story. The NOC is.

Football's transfer window runs on release clauses, agent fees and sell-on percentages. Cricket has none of that architecture. Three things control this market: the board-issued No Objection Certificate, the franchise wage bill and retention list, and the overlap of league calendars.

An NOC is the gate. A player needs his home board's permission to appear in a foreign league; that permission carries a validity window, a deadline, and often conditions — return by a date, cap the number of matches, rest in a specific format. A refused NOC does not just cost a player a contract; the franchise loses squad balance.

This is where cricket differs from football. In football, two clubs negotiate. In cricket, a third party sits in the middle — the national board — holding two weapons: the calendar and the NOC. Used together, they can move a market price sharply without a single ball being bowled.

Asia's calendar is uniquely messy. The Bangladesh Premier League in December and January, the UAE and South Africa leagues in early January, the Pakistan Super League in April and May, the IPL from March into May. Above all of that sits the ICC Future Tours Programme and World Cup preparation series. For a fast bowler this can mean two hundred-plus competitive deliveries a year, much of it inside airports.

The franchise calculation is brutally simple. A cricketer is a four-week asset. The franchise wants that asset working for those four weeks; the risk of breakdown is carried not by the franchise but by the player's knee, shoulder and next ten years. In contract language this is a liability shift, and it is bounded by NOC dates and insurance clauses.

I do not worship the dashboard; I ask who is missing from it. What is missing here is the domestic first-class calendar and the contracting architecture of women's cricket.

A four-tier reliability filter

Tier One: registered reality. The contract is filed with the league, the board NOC is issued, the dates exist. Tier Two: process underway. Terms agreed, NOC requested but not granted — the greatest risk here is timing. Tier Three: interest, trials, visas. Tier Four: source-based claims, which I weight at three per cent, because unverifiable claims are possibilities, not information.

Every claim then gets a reliability score: tier weight × recency × the alignment of both parties' interests. A claim that suits two franchises is likelier true; a claim leaked for one party's convenience invites suspicion.

Pricing comes down to five variables: age curve, injury history, twelve-month bowling load, availability window, and fit with the overseas quota. The last is never admitted but controls price most. Within each league's overseas limit, an all-rounder and a specialist quick are not the same commodity.

The weakest variable is workload. In my own coding, the fourth-spell decline shows up in two ways: fewer balls at full pace, and less repeated yorker length. The stronger evidence, though, is not the drop but its variance. Bowlers with low seven-day loads drop sharply in one spell but not consistently. Bowlers with high loads decline smoothly — meaning the injury is not arriving suddenly but building quietly, before the medical staff can see it.

A transfer rumour is a data point until it becomes a person. When I can hear the phone calls, the medical date, the school run in a different timezone, the analysis changes.

Fan objection, as a formal error-check

In July 2026 I built a pass-origin map on Ederson's move to Manchester City. City fans on Twitter objected: the Portuguese league is slower. I spent two weeks re-coding ten Benfica matches and added pressure-adjusted numbers. Since then every scouting report carries a mandatory section: fan objections.

The objection here is credible: the domestic first-class calendar may be the real killer, not the franchise leagues. So the model now carries “domestic calendar density” as a separate variable, with a heavier weight.

Women's cricket: the dashboard that does not exist

When I go looking for the same workload data on a women's player, it is absent. There is no ball-by-ball domestic log, no consistent speed archive, no public workload record. Yet Bangladesh's women now play regularly at world level and are entering franchise negotiations.

What is measured gets priced; what is not measured gets priced on eye-test. Men's cricket has a correction mechanism. Women's cricket does not yet. The NOC structure compounds this: conditions are less transparent, contracts shorter, an agent's downside larger. A board that treats women's league participation as a threat to the international calendar is writing an asset-depreciation ledger.

The poll that rewrote the weights

After the February world event I ran a poll: which should weigh more — injury history or twelve-month workload? Roughly ten thousand votes split almost evenly, workload slightly ahead. The comments mattered more. Many voters argued both variables measure the wrong thing: what should be counted is high-intensity deliveries and death-over net overs.

So the model changed. Load was split into total deliveries and high-intensity deliveries. The model did not change because of the speed; it changed because you voted.

The contrarian angle

Correlation is not causation. Workload correlates with speed decay, and the third variable is calendar density. My structural view: the killer is not any single tournament but the density. No medical team can fully rebuild a body between two matches a week; an excellent medical team does not prevent injury, it reduces severity.

The second counter-intuition is about the market itself. We assume franchises avoid long deals because of injury risk. I think the logic runs the other way: losing a star mid-tournament is not something insurance can repair. So they prefer short, renewable, conditional deals — and the condition is not written in the contract, it is written in the NOC date.

What I will watch next

Four signals, in order: NOC notification dates rather than contract dates; retention lists, because a name left out is already circulating; domestic calendar density, because that sets December's workload starting point; and the volume of published women's contracts. Not one player's glory — an infrastructure returning.

What my dashboard cannot hold is a wedding anniversary, a mother's surgery, a daughter changing schools. Before I read the NOC, I ask whose door this contract closes and whose light it switches on.