Injury updates — workload budgets, recovery windows, return-to-play ladders and the deck the player returns on

TL;DR. The injury-updates beat is the desk's medical-desk. Workload budgets, recovery windows, return-to-play ladders, the role share after return, and the deck the player returns on — all of it lands here. The desk's editorial rule is consistent: workload reads and injury reads are kept separate, two-source verification where possible, single-source disclosed for reported stories, and a closed list of inputs that decide whether a player is in the captain matrix on the next fixture. The beat exists to keep the fantasy player's calibration of player availability current across the season, with the medical and performance staff's framing of the read treated as primary.

Workload budgets — how the desk reads management-side constraints

A workload budget on this beat is a management-side constraint, not a medical-side injury. The constraint is published by the franchise or communicated privately to the player; the desk reads the constraint through the franchise's media note, the head coach's press conference, or a named source with direct knowledge of the constraint. The desk does not treat a workload budget as an injury update — the two are kept separate, and the captain matrix delta is calculated against the constraint rather than the injury.

Workload budgets come in three shapes on the injury-updates beat. The first is the fixed-share constraint — a bowler held to a fixed share of the innings (typically three or four overs) for a defined window, often during a back-to-back fixture cycle. The second is the role-share constraint — a bowler held to a specific role (powerplay only, death only, middle only) for management reasons, often during a workload rotation cycle. The third is the availability-window constraint — a player held out of the XI for a defined window (typically three to seven days) for rest, with no medical issue named.

The verification ladder on workload budgets is two-source where possible. The two sources are typically the franchise's media desk and the head coach's press conference; in cases where neither source is available, the desk holds the story. The held status is published at the top of the article until the source clears, and the correction note is dated when the story publishes. The desk's standing rule is that a workload budget is worse to misread than to hold — a player held to a fixed share who is read as a Tier-1 captain pick has direct consequences on the captain matrix and the user's fantasy team.

Recovery windows — the medical-side read

A recovery window on this beat is a medical-side read on the time it takes for an injured player to return to play. The recovery window is published by the franchise's medical staff, the player's representative, or a named source with direct knowledge of the medical update. The desk does not treat a recovery window as a workload budget — the two are kept separate, and the captain matrix delta is calculated against the recovery window rather than the workload budget.

Recovery windows come in four shapes on the injury-updates beat. The first is the soft-tissue window — a muscle strain or a ligament sprain, with a typical recovery of one to four weeks depending on the grade. The second is the bone-stress window — a stress fracture or a bone-bruise, with a typical recovery of four to eight weeks. The third is the impact-window — a concussion or a facial injury, with a typical recovery of one to two weeks under the league's concussion protocol. The fourth is the post-surgical window — a surgical repair with a defined rehab protocol, with a typical recovery of three to six months.

The verification ladder on recovery windows is two-source where possible. The two sources are typically the franchise's medical staff and the player's representative; in cases where neither source is available within 24 hours of the medical update, the desk holds the story. The held status is published at the top of the article with the medical update visible, and the correction note is dated when the recovery window is confirmed. The desk's standing rule is that a recovery window is a medical read, not an editorial read — the window is published as the medical staff has named it, with the desk's confidence level tagged separately.

The return-to-play ladder — how the desk tracks the comeback

The return-to-play ladder on this beat is the desk's framework for tracking a player's comeback from injury. The ladder has five rungs: medical clearance, on-field rehab, net session, practice match, and competitive return. Each rung is logged with a verification tag and a dated entry; the player's progression up the ladder is published within 24 hours of the rung being cleared.

The ladder's first rung is medical clearance. The franchise's medical staff signs off on the player's progression from rehab to on-field work; the desk publishes the medical clearance as confirmed once the franchise has communicated it. The second rung is on-field rehab — the player begins running, agility work, and low-intensity skill work on the outfield. The third rung is net session — the player bowls or bats in a controlled net environment with the franchise's coaching staff observing. The fourth rung is practice match — the player features in an internal practice match or a friendly fixture, with role-share read logged. The fifth rung is competitive return — the player is named in the playing XI for a competitive fixture.

The desk's return-to-play read on the captain matrix follows the ladder. Until the player reaches the net-session rung, the captain matrix excludes the player from the differential pool. From the net-session rung onward, the player is added back to the differential pool with a confidence tag tied to the rung cleared. From the practice-match rung onward, the player is added back to the captain pool with a confidence tag tied to the role share logged in the practice match. The matrix is updated within 24 hours of each rung being cleared.

Role share after return — what changes for the player and the XI

The role share after return is the read on what changes for the player and the franchise's XI once the player is back from injury. The role-share read is published after the practice-match rung is cleared, with the role share logged across the first two competitive fixtures. The desk does not assume the role share returns to the pre-injury level — the share may be lower (a workload budget while the player builds match fitness), higher (a role expansion while the franchise tests the player in a new position), or unchanged (the franchise returns the player to the same role).

The role-share framework has three layers. The first is the role itself — what the player is asked to do in the XI on the return. The second is the role share — the over count or the batting position the player occupies, compared to the pre-injury share. The third is the consequence — the captain matrix delta on the player's return, the role share delta on the player being replaced during the injury, and the impact on the franchise's squad shape. Each layer is sourced independently; the desk does not publish a role-share read that names only the role without the share or the consequence.

Role-share reads have a longer shelf-life than other injury-update stories. A role-share read on a returning bowler affects the captain matrix for the next six to ten fixtures; a role-share read on a returning batter affects the captain matrix for the next three to six fixtures. The desk tracks the long-tail consequence of each role-share read in the franchise desk and updates the captain matrix on the relevant fixtures across the window.

The deck the player returns on — the venue and surface read

The deck the player returns on is the read on the venue and surface conditions for the player's first competitive fixture back from injury. The deck read is published the morning of the fixture and sized against the player's pre-injury role share, the workload budget (if any), and the franchise's selection pattern. The deck read is one of three inputs that decide the captain matrix on the player's first fixture back; the other two are the workload budget and the practice-match role share.

The deck read has three layers. The first is the venue — the stadium, the surface type (red soil, black soil, drop-in), and the typical chase ceiling at the venue. The second is the surface — the grass cover, the moisture level, the expected turn for the spinners, and the expected pace and bounce for the quicks. The third is the conditions — the dew forecast, the temperature, the wind, and the expected DLS risk. Each layer is sourced from the desk's pre-toss read on the venue and from the match officials' pitch report.

The desk's read on the deck is updated the morning of the fixture and locked at the toss. If the deck reads in the player's favour (a flat deck for a returning batter, a green deck for a returning quick), the captain matrix promotes the player to the differential pool; if the deck reads against the player (a slow deck for a returning quick, a two-paced deck for a returning batter), the captain matrix demotes the player to the held-read pool. The deck is one of three inputs; the matrix is locked against all three together, not against the deck alone.

What we don't know — the held-read rule on injury updates

The held-read rule on this beat is the desk's standing discipline when an injury update cannot be confirmed against the verification ladder. The desk publishes the held status and the reason for the hold; the held status is not a permanent state — the desk re-checks the ladder every 24 hours and updates the article when the ladder clears. The held-read rule exists for two reasons: reader trust (a wrong injury update has direct consequences on the captain matrix) and the medical read (the medical staff's framing is treated as primary, not the desk's inference).

The held status on an injury update names the reason for the hold, the verification rung the update is currently at, and the next check time. The reader can size the hold against the same rungs the desk is using; the desk does not hold a story for a reason the reader cannot see. The transparency on the hold is the desk's editorial commitment to the injury-updates beat.

Frequently asked

How does the desk verify an injury update?

We verify with at least two independent sources, or an official franchise or league communication, before publishing an injury update as confirmed. The verification window is logged in the correction note if the story changes; single-source stories are tagged reported.

Does the desk publish projected availability on injured players?

Yes. When the franchise has communicated a projected return window, we publish it as reported with the source named. When the projection is the desk's own (built from net-session reads, rehab-phase updates, and management notes), it is published as projected with the inputs named.

How are workload reads different from injury reads?

A workload read covers a bowler being held to a fixed share for management reasons; an injury read covers an actual medical issue. The two are sometimes related, sometimes not. The desk labels each separately and tracks the captain matrix delta for each.

---

Editorial note. This page is part of an independent newsroom. The sources are listed in the editorial footer; the verification tag is confirmed unless otherwise stated; the correction note at the top is the latest version of the page.