What Is the NBA Injury Report? Out, Doubtful, Questionable Explained

The report is a game-specific record of participation information supplied by teams. It brings a player name together with a current status and a reason, under a team and matchup. That combination matters: an isolated name or injury phrase cannot tell you which game the entry concerns or when the information was recorded. Read the row in its full context before comparing it with another page.

An entry can concern injury, illness, rest or a different availability reason. The existence of a row therefore does not establish that someone has a new injury. Conversely, the absence of a visible row in an excerpt is not proof that a player is healthy. You may be looking at a selected sample, a partial team submission or an earlier version of the file. The scope of the document should be visible beside any summary count.

A participation report is also distinct from a roster and a starting five. A roster describes membership. The report describes availability for a specified game. A starting lineup identifies the five selected to begin. Those layers can be displayed together, but no one layer should silently stand in for the others. An Available player may still be a reserve, and an Out player does not automatically name the replacement starter.

There are three useful questions to ask of any injury summary. What is the document’s scope? Which game date does the row describe? What evidence supports the displayed status? A concise card can answer those questions without reproducing an entire PDF. If one answer is absent, the reader should not assume it from a nearby fixture or a current calendar date. A short, clearly bounded excerpt is more reliable than a broad headline that hides which teams or files were actually covered.

The source rules describe a standard deadline of 5 p.m. local time on the day before a game. For the second game of a back-to-back, the listed deadline is 1 p.m. local time on game day. These are team reporting deadlines, not promises that every public website will show the same data at precisely that minute. A team submission still has to appear in the file or feed a reader is using.

The game-day report window is normally 11 a.m. to 1 p.m. local time. For a game scheduled at 5 p.m. or earlier, the rules describe an earlier 8 a.m. to 10 a.m. window. Local time in these filing rules is different from the ET labels used in the public report and our schedule cards. Keeping the two clocks separate prevents an apparent discrepancy that is simply a time-zone difference.

Files can be revised during the day. A deadline is therefore not the end of the availability story, and a later status must retain its own file time. The source dossier observed report filenames on a fifteen-minute grid; that observation is not a guarantee that every possible filename exists or that a new player decision occurs every fifteen minutes. The time on the file is evidence about that document, not a universal refresh promise.

Out indicates that the report lists the player as not participating in the specified game. Doubtful, Questionable and Probable preserve different official levels of uncertainty or expectation. Available indicates availability in that source version. These labels should be reproduced as labels; this site does not attach invented percentages to them or turn them into a probability model.

Available is particularly easy to overread. It is not a guarantee of minutes, a starting role or a particular performance. It may appear after an earlier concern, but one file alone does not prove the sequence of prior statuses. To say that someone changed from Questionable to Available, both relevant source versions must be present and matched to the same game and player.

The March 27 example on this site contains two Out and three Available entries. Those are sample counts, not league totals. The buttons on the archive widget simply filter the five selected rows. A reader looking for tonight’s absences needs a report attached to tonight’s game date, not a larger-looking number extracted from an unrelated historical file.

Pending and Source delayed are publication states used by this site. They are not extra official injury designations. Pending means the required information has not been published here. Source delayed would mean an expected source could not be refreshed. Neither state should be interpreted as an official judgment about a player’s condition.

The reason field adds context to the status. An Injury/Illness entry can identify a body part and a description, as in the historical Achilles and ACL examples. Other rows may use G League Two-Way, G League On Assignment or Not With Team. These descriptions explain different reasons for an availability entry; they should not all be summarized as injuries.

A team-level Not Yet Submitted marker has another meaning again. It says that the team’s information was not supplied in that source version. It is not a player-level diagnosis, an Out designation or an all-clear. If a table is empty because the team has not submitted, the correct summary is missing team coverage rather than zero unavailable players.

Keep the original level of detail. A short reason field does not contain a full medical assessment, rehabilitation plan or return-to-play decision. The reporting layer should not expand it into an unsupported story. A reader comparing names across files also needs the matchup, team and timestamp so a similar name or a changed team assignment is not accidentally merged into the wrong record.

Start with the report timestamp and game date. Then identify the matchup and team before reading a player’s current status and reason. Game Time is labeled ET in the source format. The page number describes the document’s pagination; it does not establish that a clipped screenshot or selected table contains all entries for a team.

A useful reading sequence is date → matchup → team → player → status → reason. Only after those fields are matched should you compare the row with another file. A later timestamp may contain an unchanged status, a corrected reason or a newly submitted team section. Those cases have different implications and should not be collapsed into a generic updated badge.

The selected sample here is deliberately smaller than the full PDF. Its link leads to the dated excerpt, where the five entries and the file time are visible. That makes it suitable for understanding the format without pretending that the excerpt covers every NBA game that day.

A daily report page belongs to a fixed game date. Its schedule context, source timestamp and rows should be retained together, while later versions may add a clearly described change. The intended ingestion process checks for new files and compares matched rows instead of generating new information from a timer.

In the present preview, the historical sample is fixed and opening-night report coverage is Pending. The automatic report pipeline is not running. We avoid displaying an automatic updated-at label that could make the same old source appear fresh after a page reload.

When complete source coverage exists, a daily summary can count statuses within the intended slate and link to each team. Missing submissions must remain visible in that process. A source outage should preserve the last known timestamp or show an explicit empty state; it must not erase uncertainty or convert missing rows to healthy players.