The Hammer Sets the Price, the Shoulder Pays: Franchise Cricket's Invisible Workload Market

I opened the workload notebook and the auction changed shape.

November 2026, the Jeddah auction stage. The hammer fell on Rishabh Pant for 27 crore rupees, the highest single-player price in IPL history. At the table beside the dais, one team's analyst wrote three numbers into his notepad: 23, 18, 11. The first was the retention price of a finisher, the second a young spinner's fee, the third a serial number on an injury shortlist. Three numbers on a single page, and one of them wins nothing.

That night I did not sit down to write about record prices. I opened the ledger in the other direction — four seasons of workload data. Who bowled how many overs in how many days, how many flights, how many back-to-back T20s, how many consecutive days inside a hotel and a 22-yard strip. I sorted the rows until the story stopped hiding.

The price climbs on the arm; the bill arrives at the shoulder.

That is the least-disclosed truth of franchise cricket. We believe the auction window buys talent. In practice it buys workload, and workload has no rate card.

Context: windows, NOCs and the river of money

The modern cricket calendar turns on three wheels. Wheel one is the international fixture list, set by the Future Tours Programme. Wheel two is the franchise window — March to May for the IPL, January and February for the BPL, January for ILT20 and SA20, December and January for the Big Bash, August for the Hundred, July for Major League Cricket. Wheel three is the board's no-objection certificate and the clauses inside central contracts.

When three wheels spin at once, only one thing gets lost: control. No board can now say how many overs its centrally contracted fast bowler will deliver in a year, because the contract sits with the board while the overs sit with a league owner. One NOC, one flight ticket, and then a workload that arrives black-belted and unlisted.

Bangladesh complicates this further. The BCB is simultaneously the organiser and part-owner of the BPL and the regulator of the national side. One hand warms the tournament market by signing overseas stars; the other hand writes rest letters so those same stars can serve the national team. In the 2026-25 cycle, the debate around Mustafizur Rahman, Taskin Ahmed and Shakib Al Hasan was a symptom of that dual role, not a failure of individual discipline. The same institution is buyer and seller at once.

Inside the NOC system sits a gap nobody prints: workload data is not centralised. Every franchise knows how many balls its player bowled in the last two months. The BCB knows the load on its contracted players. The physio knows what the last scan of a shoulder said. These three databases never sit at one table. Decisions are made in the dark, by the sound of the hammer rather than the reading of a report.

Core 1: the hidden layer inside the price curve

Lay out five years of IPL auction data and a quiet pattern surfaces. In 2026 the highest fees went to finishers: Sam Curran at 18.5 crore, Cameron Green at 17.5 crore, Ben Stokes at 16.25 crore, Harry Brook at 13.25 crore. A year later in Dubai the picture inverted: Mitchell Starc at 24.75 crore, Pat Cummins at 20.5 crore. The biggest cheque of the cycle had moved to a fast bowler, the man who bowls month after month.

The 2026 mega auction bent again. The top two prices went to batters, Pant at 27 crore and Shreyas Iyer at 26.75 crore. But the flanking pattern is the story: Heinrich Klaasen was pulled into retention at 23 crore, while a fast bowler returning from injury, Mohammed Shami, settled at 10 crore. Starc himself slid from 24.75 crore to 11.75 crore.

The price curve is not a talent curve. It is a risk curve. Where risk is high, the hammer pauses. Starc's skill did not halve across two years. One thing moved — the invisible injury probability attached to his age. In the top-price list, batter dominance does not mean bowlers are undervalued for skill. It means bowlers are priced on two equations at once: quality, and availability. For batters the second variable is close to zero. For bowlers it is the primary term.

Core 2: how to actually measure workload

Workload is not distance covered or a basketball load index. Bowling is a stress-time curve; every delivery loads shoulder, elbow, lower back and knee at once. No single number tells the whole story. Still, I use a six-layer index.

Layer one: competitive overs per 30 days. Layer two: peak single-day load, such as a ten-over spell or a dense burst of 25 dot balls in four overs. Layer three: format switches — T20 back to Test, or the reverse. Layer four: travel and time-zone shifts, because Liverpool to Bengaluru or Dhaka to Cape Town scrambles the body clock. Layer five: the share of matches with under two days of rest. Layer six: injury history — what happened, how long the layoff was, how quickly the load was rebuilt afterwards.

Two bowlers can each deliver a hundred overs in a season. The first does it across four months, three continents and six format switches. The second does it in one league, in one time zone. The overs are equal. The load is never equal. On an auction table they sit in the same row.

I state my method limits in every piece. The index is an approximation, not a verdict. It simplifies the engineering model of the stress-time curve, ignores individual physiology, and does not separate the bodily cost of a slow ball from a reverse-swinging one. What it does is show where the data is missing — and that gap is the real story.

Core 3: what the injury ledger says

Cricket has no public injury register. No league or board publishes a centralised injury log. This is my biggest methodological problem, and I do not hide it. Still, match-by-match XIs and media reports generate a non-random pattern.

Three things recur. First, stress fractures arrive just after a load spike, never out of nowhere. Jasprit Bumrah's back stress fracture and Shami's ankle trouble each sit at the end of a rising overs line drawn well before the injury. Second, two fast bowlers with identical over counts do not carry identical risk. Mixed actions and heavy front-leg bracing load the back and knee differently. That variable never reaches the auction table, because it is hard to measure and hard-to-measure things price cheaper.

Third, the return period is the most dangerous window. Re-injury rates are highest in the first two months after a comeback, because two pressures meet: a body not yet ready for full load, and a team pushing a bowler back into rhythm quickly. Where those two collide, the second injury usually lands.

My rule follows: I do not rate a returning player before ten matches. In ten matches the workload is not yet legible, and the price set there is hope, not evidence.

Core 4: the young-player premium bubble

A second distortion sits on the auction table. A few crore for a player with fewer than fifty top-flight games is now routine, because an unformed talent invites an unlimited ceiling in the buyer's imagination. The experienced player has a known ceiling and therefore a known price. Uncertainty sells at a premium because the buyer can imagine the future.

My position is blunt: paying crore-scale money for someone with fewer than fifty top-flight games is naked gambling. Repetition is the base of evaluation, and repetition takes time. On a small sample we are measuring possibility, not production. The blame, though, belongs to the system, not the player. Scouting departments are forced to judge an entire market on tiny samples. A young Bangladeshi who hits two destructive innings in four BPL games can double or triple his fee while his first-class average is still under fifty. The market is not discovering talent; it is buying the shadow of talent.

Core 5: Bangladesh's different arithmetic

In Bangladesh the workload question sits elsewhere, because the institutional distance between franchise cricket and the national team is small. The BCB is selector, BPL organiser and, in many cases, a partner of franchise owners. Decisions taken at two different tables land on a single calendar.

The BPL runs in January and February. Bilateral series sit either side. International league windows cut across. Lay out Mustafizur Rahman's 2026 calendar day by day and the T20 bowling stream barely stops — IPL, international series, league again. Taskin Ahmed's case is subtler because his role shifts: sometimes four overs with the new ball, sometimes four at the death. Same over count, entirely different physical cost.

Bangladesh's problem is not a talent deficit. It is a data void. No central record shows who bowled how much. The physio's report sits in the club locker, the board file sits in an office, the franchise sports-science spreadsheet sits on its own server. Three files are never read together. So decisions get made with half the data and full confidence.

There is a straightforward fix that is not technically hard: a shared, verifiable workload ledger. Every over, every flight, every physio note in one register that boards and franchises read together. Nobody can hide from it and nobody can later deny overloading a player. When the data stops being blocked, everyone can read the same story — and that is the actual reform.

Core 6: retention, release clauses and the wage bill

Every transfer-window checklist starts with a name and ends with a warning. The name takes the headline; the warning sits in a hidden column. IPL retention lists make the duality visible. Retention prices are paid per match, but they are built on the previous season's performance, which was produced in a fixed window. A team that retains its star is buying the past, not the future. A release clause or a trade window never reads workload data.

The BCCI's newer rules, requiring centrally contracted players to appear in domestic cricket and to file injury reports on schedule, are an attempt to close exactly this gap. The rule disciplines less than it de-blocks information.

The wage bill sharpens the point. A large share of a squad's salary goes to five or seven players; the rest is filled at base price. When the first-choice fast bowler breaks down, the replacement is a less experienced bowler whose own workload has never been audited. An injury to one player therefore transfers weight down the queue. The underused bowler suddenly doubles his overs and joins the list four to six weeks later. That chain reaction is franchise cricket's least-discussed structural risk.

Core 7: three countries, three load models

The biggest myth about load management is that it is a cultural habit. It is an institutional arrangement, and each board has built a different one.

England's model rests on central contracts and a written rotation culture, capping how many matches a contracted quick plays in a summer. It costs them — a key seamer sits out, a series can slip. It also saves them from a bowler collapsing after ten straight games.

India's model is more centralised from the other pole: the IPL is the centre of the economy, and the national team is that economy's biggest user. Load instruments are therefore administrative — letters, directives, policy. The 2026 changes made this explicit. But however strict the administration, the calendar does not change, and the hardest question remains: who is accountable for the player outside a central contract?

Australia takes a middle path, aided by geography. The Big Bash is a domestic season; a player returning home to play it avoids multi-continent travel. Under similar formal rules, the natural load is lower. This is a reminder that geography and calendar matter as much as policy.

Models that account for geography and calendar lose fewer players than models that rely on discipline alone. Load cannot be lowered by decree. It falls when travel falls, when format switches fall, and when a player can play in one place in one season.

The contrarian turn: correlation is not causation

Now the other side, so readers do not over-believe my rows.

First, workload is never the sole cause of injury. Age, action, type of load — new ball versus death overs — pitch, and even family stress all contribute. My notebook draws one variable; the others stay dark.

Second, injury data is private, incomplete and biased. No franchise wants to look fragile, so injury language is permanently cautious. Any load-injury relationship therefore rests on partial inference.

Third, rest under the banner of load management often becomes a commercial concession. Some players are rested before their own league; others after an international window. The announcement is equal; the calendar is not.

Fourth, small-sample overreach. Drawing system-level conclusions from twenty fast bowlers in one season is my own limitation, which is why I call every load claim provisional until it survives three seasons and two competition contexts.

Last, a counter to my own transparency argument: if the market does not price workload, what does opening the data achieve? This much — the labour becomes visible. Player welfare does not always register in market arithmetic. Sometimes transparency is not charity; it is accounting.

Takeaway

I rebuilt the 2026 calendar and the numbers sharpened in my hand. An injury is not an accident; the data about it is simply not in the room, and that absence is the biggest cost. However smooth the press release, injury is a calendar product — bought often, wanted never.

The spreadsheet did not cheer, but it remembered. From the 2026 T20 World Cup to the next IPL auction, every bend in the calendar asks the same question: who is bowling the overs, and who is paying for them. If workload one day takes its own column on the auction table, cricket will have found something it has kept hidden — the player's account.