Workload Ledgers and Smart Contracts: Franchise Cricket's Invisible Injury Accounting

The Question Nobody Asks

On 7 February 2026, the men's T20 World Cup begins in India and Sri Lanka with twenty teams. In the four weeks before it, the world's franchise calendar blooms almost simultaneously — the Big Bash knockouts, ILT20, SA20, the PSL. A right-arm quick's January can be spent under four different medical teams at four different franchises, on four different workload spreadsheets. Then, from 7 February, he is told the new-ball spell is his.

The question is not about his reverse swing. The question is: who reconciles those four spreadsheets?

I started The Half-Space in 2026 because the game was speaking to me in two languages. In the press it spoke in results — who scored what, who took how many. In the franchise physio room it spoke in load — overs bowled, high-intensity sprints, hours slept. Nobody sits between the two languages as a translator.

Watching Manchester City through 2026-18, what stuck was not the beauty. Kevin De Bruyne created 106 chances and made 16 assists that season, but those numbers were not the cause of City's success; they were the output of a positional system built off the pitch, in the sports-science department's spreadsheets. — Root: 2026, dissecting Manchester City.

Cricket has not built that off-pitch system. The 2026 calendar exposes it as the sport's largest structural gap — and the first place where the word blockchain is genuinely relevant rather than decorative.

January's Arithmetic, February's Liability

Football's calendar looks chaotic but is sequential: league, cup, international window. There is at least a formal channel between UEFA competitions, club sports-science departments and national medical teams — club-block releases, capped minutes, shared GPS data.

Cricket's channel is informal. Verbal, a phone call, and almost always late. The SA20 physio does not know how many overs the same bowler sent down in ILT20 three weeks earlier, because that data lives on another company's server and there is no commercial reason to share it. To a franchise, a player is an asset; his injury data is competitive intelligence.

When I analysed the Bundesliga restart in 2026 across 83 matches, I found home-win percentage had dropped from 43% to 21% — my first serious work on crowd effects. But cricket's larger variable does not sit in the stands. It sits in the different physiological cultures of different leagues. One league gives a bowler two full rest days; another calls him for an optional session on a travel day. No central authority reconciles those cultures.

Data Whose Ownership?

An international quick's medical file now has at least five claimants: his board, his franchise, his insurer, his agent, and himself. Their interests conflict. The board wants him playing because the series revenue is theirs. The franchise wants him playing because it paid seven figures. The insurer wants risk reduced. The agent wants his client's market value intact. The player wants all of it — contract, selection, and a pain-free shoulder.

Governance has produced something strange: injury data is still true on an insurance claim form, but secret in selection meetings. The same MRI report is real in one room and absent in the next. Much of the commentary around Jasprit Bumrah's workload over recent years has not really been medical; it has been a political argument about data rights, one nobody is formally obliged to answer.

Take Bangladesh. Bowlers like Mustafizur Rahman, Taskin Ahmed and Nahid Rana move through an IPL season, franchise leagues, bilateral series and World Cup qualifiers inside one calendar year. The BCB medical staff do excellent work, but they depend on franchise courtesy for load information. Courtesy is not a system.

Reading the Gap: Half-Spaces and Inner Rings

I use football's half-space mapping in cricket for one reason: in both games, the decisive event happens where cameras are absent and responsibility is ambiguous. In football that is between the lines; in cricket it is the bowler's workload after the middle overs, in the seam between club and country.

The 2026 transfer window taught me that clubs reveal their souls in January and August. Van Dijk to Liverpool showed me how one signing can rewrite a league — after that £75m deal, Liverpool could defend a much higher line because the last line of risk had shrunk. France's 2026 triumph I read not as a burst of talent but as a controlled burn. — Root: 2026 transfer window / Van Dijk.

Cricket's transfer window runs on the same logic. A release clause and a wage bill say more about a franchise's squad philosophy than ten press conferences. But the same injury gap persists: medical assessment is rarely embedded structurally into cricket deals; it arrives late in the negotiation. Football signs players against historical injury-load models. Cricket still signs on the eye.

What Blockchain Actually Solves

Precision matters here. Blockchain does not heal injuries or prevent them. It is accounting technology: once written, a record cannot be altered, and anyone can verify who wrote or read it.

Three cricket applications look realistic to me. First, a co-operative workload ledger where boards, franchises and insurers append overs, ball counts, spell lengths and travel days to one hashed record. Anyone can contribute; nobody can amend. That distinction is the whole point. Second, smart-contract triggers: if a contract says a bowler exceeding 240 overs in a year automatically earns a 20% higher match fee, the 240th over posted to the ledger triggers payment — no review committee, no delay. Third, player-held data identity: medical records under the player's own key, granting time-limited access to named parties, so access ends when the franchise does.

All three are technically feasible and partially deployed. The obstacle is not technical.

The Oracle Problem

Here is what nobody wants to say. Blockchain guarantees immutability, not truth. A false entry, once written, does not stay false — it becomes permanent truth.

If an insurer submits incomplete data, or a franchise logs a fatigued session as "light fitness work", the system enshrines it forever. Software calls this the oracle problem: the bridge between ledger and physical world is built by a human, not a protocol.

That is no reason to discard the technology. It is a reason to stop treating it as a miracle. The real reform is institutional, not technological — a mandatory global workload registry, and a genuine off-season. While four leagues run simultaneously in January, no ledger saves anyone, because the physio will have no time to act on it.

I hold an unpopular view on football's back-three revival: it is not progress but a way for managers to dodge reputational risk, because an exposed back four demands personal accountability. Franchise cricket's blockchain pitch sounds similar. The league says it is bringing transparency; the real decision is cutting a month out of the calendar, and nobody wants that because the cost lands directly on broadcast contracts.

What to Watch Next

Three things from 7 February. First, in the opening fortnight of the 2026 T20 World Cup, watch spell length — not overs per match — for bowlers who played two or more franchises in January; the decay shows there first. Second, find one contract clause in the next auction or transfer window with a workload-based payment trigger; the trigger structure reveals whether a franchise treats a player as an asset or as inventory. Third, watch whether any board voluntarily publishes its players' workload data. The first to do so will not be making a tactical call. It will be making a structural statement — and until someone does, the arithmetic stays in four separate January spreadsheets, with the liability resting on a February shoulder.