How to read an injury report

Why the wording is strange

An injury report is written by a team that would prefer its opponent knew less, published under a rule that requires it to say something, read by bettors who move money on every syllable, and filtered through a medical privacy law. Nobody in that chain has a straightforward incentive to be plain.

The result is a dialect. “Day-to-day” is not a diagnosis. “Questionable” is not a probability anyone computed. Learning the dialect is most of what separates a reader who panics at a Wednesday practice report from one who does not.

The designations, roughly translated

Leagues define these differently and enforce them unevenly, but the working translations hold up:

• Out — will not play. The one unambiguous word on the page.
• Doubtful — historically plays well under a quarter of the time. Treat as out until told otherwise.
• Questionable — genuinely uncertain, and the designation teams use most strategically. Roughly a coin flip, with wide variation by club.
• Probable, where it still exists — plays almost always; several leagues dropped the label because it carried no information.
• Day-to-day — a description of the schedule, not the injury. It can precede one missed game or fifteen.
• Load management / rest / personal — not an injury report at all, and often the most honest line on it.
• Placed on injured reserve — a roster transaction with a minimum number of games attached. The number is the news.

Who is actually telling you

Sourcing matters more here than anywhere else in sports coverage, because the incentives to leak early and be wrong are enormous. A player's own agent, the team's official account, a national insider, and an aggregator account with a logo for an avatar are four very different levels of evidence being presented in the same format on the same screen.

The reliable pattern is a named reporter with a beat, attributing to a person — “per the team”, “according to a source with knowledge of the situation” — and then a team confirmation within hours. The unreliable pattern is a post that cites another post, which cites a third post, all within four minutes.

If a report cannot be traced to someone with a name and a phone number, it is a rumour with good graphic design.

Timelines are ranges, and the range is the story

“Four to six weeks” is not a prediction of five. It is a span that usually assumes nothing goes wrong, and the published version tends to be the optimistic end of what the medical staff believes.

Two things follow. First, the return date that gets written into headlines is a best case being reported as a schedule. Second, when a player misses that date, it is usually not a setback in any medical sense — it is the original number having been the floor.

What an injury actually costs a team

The instinct is to subtract the injured player from the team. The truer accounting is to subtract the difference between that player and whoever replaces him, across the games he misses.

A team losing a star with a capable backup for three weeks may lose less than a team losing a solid starter whose replacement is not a professional-grade option. This is why analysts talk about replacement level at all, and why the injury that decides a season is often the second one at the same position rather than the first.

Reading one without over-reacting

• Check the designation, then check who the source is, in that order.
• Wait for the team's own statement where one is coming; it is usually hours, not days.
• Ask who replaces the player, not only who is out.
• Treat any timeline as a floor.
• Ignore practice-participation reports on Wednesdays. They are the least predictive and the most written about.

Most injury news resolves itself within forty-eight hours into something duller than the first report. Waiting is nearly free, and it is the single habit that most improves what you believe about a team's season.