How to Read an Injury Report Honestly

No other input in prop research moves numbers as violently as an injury report, and no other input is treated with less rigor. A single word on a team's official status list can redraw a slate: opportunity moves from one player to another, lines get pulled and reposted, and every projection built an hour earlier becomes a description of a game that will not be played. Which is exactly why the way most people read those reports is worth examining closely.

The core mistake is treating a designation as information about a body. It is not. It is information about a process. Teams publish statuses to satisfy league reporting requirements, and the categories are administrative buckets with league specific definitions, competitive incentives attached, and a history of being used loosely. A tag tells you that a question exists. It rarely tells you the answer.

A designation is an administrative category, not a probability

It is tempting to translate status words into percentages, and plenty of people do it out loud: this word means about half, that word means most of the time. Treat those translations with suspicion. The mapping differs by league, it differs by team within a league, it shifts when a league revises its reporting rules, and it responds to enforcement. A category that meant one thing three seasons ago can mean something noticeably different now, because the rules governing it changed rather than because players changed.

There is also an incentive problem baked in. Teams have competitive reasons not to advertise precisely how healthy someone is, and reporting requirements are written to constrain that without eliminating it. The result is a vocabulary that is genuinely informative at the extremes, where a player is ruled out or fully cleared, and genuinely murky in the middle, which is exactly where the research questions live.

So the honest use of a designation is as a prompt. It tells you which players need investigating and roughly how urgent the question is. What it does not do is finish the analysis, and any research process that stops at the tag has outsourced its most important judgment to a word chosen by someone with other priorities.

Two separate questions, and only one of them is tractable

Every injury situation contains two questions that people habitually collapse into one. First, does the player appear at all. Second, if he appears, is he limited. They are different questions with different evidence, different resolution times, and very different difficulty.

Availability is the tractable one. It resolves cleanly, it resolves publicly, and in most leagues it resolves before the game through lineup announcements, warm up reports, or an official inactive list. It is also binary, which means you can wait for it rather than estimate it. Waiting is not a sophisticated technique, but on this question it beats every sophisticated technique, because a resolved fact outperforms a good guess about that fact every time.

Effectiveness is where research goes to overreach. Suppose a player is confirmed to play while carrying something. How much slower is he? How many minutes does the staff plan to give him? Does the ankle affect his shooting or only his defense? Almost nobody outside the building knows, the player himself may not know until he moves, and the public evidence is thin: a few games of noisy production, some of which came under a different plan.

That does not make effectiveness unknowable, but it does make confident effectiveness claims a warning sign. The class of statements that begin with a precise fraction of a player's usual output, based on a nagging issue described in one sentence by a beat report, is where prop research most often stops being research. When the honest answer is that uncertainty widened and the center barely moved, that is the answer.

The second order effect is usually the bigger edge

Here is the shift that makes injury research productive rather than speculative. The hardest question is what an injured player will do. The most researchable question is what somebody else will do because of him.

When a player is out, his opportunity does not evaporate. Minutes, touches, shots, targets, plate appearances, and defensive assignments get redistributed, and the redistribution follows structure you can reason about: the backup at that position, the player who slides up in the batting order, the winger who inherits set pieces, the rotation piece whose minutes were capped only by the depth chart above him. That structure is often more predictable than the injured player's own status, and it is where a projection change is most defensible.

Redistribution is not proportional though, and assuming it is produces its own errors. Vacated usage tends to flow toward the players who already carried usage rather than spreading evenly, because coaches promote from the roles nearest the gap. Minutes and touches also come apart: a bench player can absorb a lot of minutes without absorbing much usage, which raises his rebound and defensive counting stats far more than his scoring. Knowing which of the two moved is the difference between a real projection change and a vague expectation that somebody will do more.

This is why injury research and role research are really one subject. What an absence does is create a temporary role change, and roles are the input that projections are most sensitive to, as the role changes article covers in detail. The corollary is unwelcome but important: the redistribution is temporary. When the injured player returns, the beneficiary's inflated recent numbers describe a job he no longer has, which is one of the most common ways a trailing sample lies.

Late breaking news rewards patience and punishes rumor

Injury information arrives on a schedule that is hostile to careful work. The most decisive updates land closest to the start, often within the final hour, sometimes during warm ups. That timing creates a genuine tension: the earlier you act, the more you are guessing, and the later you act, the more the market has already absorbed.

Resolve that tension in favor of patience, for a specific reason. Acting on an unconfirmed report is not an aggressive research posture, it is a wager on a rumor's accuracy, layered on top of the wager you already intended to make. You have added a second source of uncertainty that has nothing to do with the player's production and everything to do with the reliability of a sentence written by someone with an incentive to publish first.

Two practical habits follow. Distinguish sourcing tiers explicitly: an official team release is not the same thing as a national report, which is not the same thing as an aggregator repeating a national report, which is not remotely the same thing as an anonymous account claiming inside information. And watch the line as its own evidence stream. A number that moves sharply without any public news is telling you that somebody knows something, which is a reason to slow down rather than to chase, a pattern described in the line movement article.

• Confirm the status at the platform's own cutoff time, not when you started your research.
• Separate the availability question from the effectiveness question and answer them in that order.
• Name the specific teammate whose opportunity changes, and say whether it is minutes, usage, or both.
• Check what happens to the offer if the player is scratched. Void, settled, or stuck depends on the platform's rules.
• If availability is still unresolved when you must decide, treat that as a reason to pass rather than a reason to guess.

Know what happens to the offer if he does not play

An injury question is also a settlement question, and the two get researched separately far too often. If a player is scratched after an entry is placed, what happens to that leg depends entirely on the platform's rules: some void the leg and adjust the entry, some have different treatment for different products, and the treatment of a player who appears briefly and leaves differs again. Those mechanics are covered generally in the void rules article, and the specific text that governs your entry is the platform's own and can change without notice.

The same applies to rest, which is not an injury but produces the same research problem with a different label. Scheduled rest, load management, and the ordinary attrition of a compressed calendar all move availability without any medical news at all, and the patterns behind them are more predictable than injuries because they are planned. Rest and schedule spots is the companion question to this one, and on many slates it is the larger source of availability risk.

How Slateline handles availability, and what it refuses to invent

Slateline treats availability as a modeled input rather than a footnote. Where an engine has availability information for a sport, it enters the simulation as a probability that shapes the outcome distribution, and probabilities for player props are conditional on the player appearing, because an unplayed leg is not a loss, it is a different event. Where availability is genuinely unknown, the honest output is a wider distribution and a caution on the offer, not a confident number quietly built on an assumption.

Two things Slateline deliberately does not do. It does not publish medical opinions about specific players, because it has no basis for one. And it does not manufacture certainty about a lineup that has not been posted; when the lineup is unknown, that limitation is stated rather than hidden. What the engines do claim, and the record behind those claims, is public in the Model Room.

The practical close is the simplest sentence in this article. If availability is unresolved at your decision point, wait or pass. There will be another slate, the offer that requires a guess about a rumor is not the offer worth taking, and no research process is improved by acting before it has the fact it needs. Current boards are on the signal board. Keep the stakes recreational, and if the deciding stops feeling like research, the responsible gaming page and the National Council on Problem Gambling helpline are there.