MISS, BACK, and BYE: How FantasyOMatic Predicts Availability

An injury badge tells you a player is questionable, out, or on reserve. The lineup question comes next: when might that player become usable again, and which weeks should you plan to cover with someone else?

FantasyOMatic separates those questions. Official status remains official. Schedule remains schedule. Our model adds a clearly labeled return-timing estimate, then one availability engine carries that same answer into Rankings, Player Detail, My Team, Matchup Matrix, the browser extension, AI Coach, Podcast, and Call In.

The language is intentionally direct:

• OUT, IR, Q, D, and BYE are official or schedule facts.
• ≈ OUR ESTIMATE identifies FantasyOMatic's forecast.
• MISS means we expect the player to be unavailable that week.
• BACK is the first week our model allows the saved weekly projection to return.
• LOW, MED, or HIGH describes evidence strength, not certainty.

What the model predicts - and what it does not

The model predicts return timing after an injury has already been reported. It does not predict who will get hurt next. It does not diagnose an injury, read private medical records, or override a club's designation.

That distinction matters. If a player is officially OUT, FantasyOMatic displays OUT as the current fact. A future MISS W10 → BACK W11 · MED timeline is a separate model statement. The interface never quietly upgrades our estimate into an official return date.

Official reports, freshness, and roster eligibility

Current-season availability starts with official NFL injury reports, with official team reports used when the league source does not provide complete usable coverage. Game-day inactive lists add the final game-specific restriction when they are available.

A report must identify the right season, week, team, and player. FantasyOMatic keeps the source link and actual report date separate from the time it last checked the page. Checking an old report again does not make it a new report.

Players are matched through stable NFL profiles and exact roster identities, with birth-date corroboration when needed. Conflicting identities are held out for review. A similar name alone cannot assign an injury to a player.

Coverage can be current, legitimately before the first report is due, pending a required report, stale, or unavailable. Before reports are due, a verified active or elevated player may receive a conditional participation forecast. Once a report is due, missing evidence has a two-hour pending window before it is treated as stale. Source observations must be no more than six hours old, tightening to 30 minutes within two hours of kickoff.

A missing injury row does not clear a player to play. Practice-squad players, players with unknown eligibility, and players on restricted reserve lists do not become usable lineup options just because an injury table omits them. For a game already played, its dated report and inactive list remain evidence about that game, not a new statement about next week's eligibility.

The inputs behind the estimate

The current estimator starts with public weekly football information:

1. Primary injury - hamstring, knee, ankle, foot, concussion, shoulder, and more than 30 other normalized categories.
2. Position - the same injury can have a different football cost for a quarterback, running back, receiver, or tight end.
3. Practice participation - full, limited, or no practice can move the estimate when a usable report is available.
4. Time on the report - a first-week listing is different from an injury that has persisted for four weeks.
5. Game timing - a Thursday game has less recovery time; a Monday game has more.
6. Official status and reserve eligibility - OUT, Doubtful, Questionable, IR, PUP, and return eligibility constrain the result.

The injury-duration lookup uses historical NFLverse injury-report data from 2021 through 2024. Only stints that reached OUT or Doubtful at least once are included in the duration lookup, so a player who remained Questionable while playing every week does not distort missed-time medians.

In plain English, the calculation is:

historical injury duration × position × practice × game timing × time on report - time already elapsed

Official status then sets a floor. An OUT player cannot be transformed into an immediate return by one optimistic modifier. A short-duration Questionable estimate can remain playable, but its weekly projection may still be reduced.

Confidence is evidence strength, not a promise

The confidence badge is deliberately not a percentage. It scores three things: the size of the historical injury sample, whether practice information is usable, and whether multiple report weeks establish a direction.

• LOW usually means a small or unknown injury sample with little current evidence.
• MED means at least one meaningful evidence source is present.
• HIGH generally requires a large sample plus practice direction, repeat reports, or both.

Football recovery is not clockwork. Confidence tells you how much evidence supports the estimate; it does not guarantee the exact week.

Injury confidence and season calibration answer different questions

An injury-return badge describes the evidence behind one player's return estimate. It is separate from the Limited evidence (calibration week) message that describes the early-season ratings.

For the 2026 Week 1 historical starting snapshot, no current-season games have been incorporated. Season calibration requires three consecutive completed weeks starting with Week 1 to be included in successfully published current-season ratings. Historical seasons, an unplayed week, and an unpublished update do not count.

A HIGH injury-confidence badge does not mean season calibration is complete. During the calibration period, use extra caution with rest-of-season, playoff, and trade decisions as current roles and usage become clearer.

Historical example: Bucky Irving in 2025 Week 8

This example comes from an archived 2025 Week 8 testing snapshot, not the current 2026 rankings. In that snapshot, Bucky Irving carried an official OUT designation for a foot injury.

FantasyOMatic combined the historical foot-injury duration, his running back position, his time on the injury report, and the current status. The resulting public timeline was:

W8 OUT · W9 BYE · W10 MISS · W11 BACK · MED

Week 9 is the important part. Tampa Bay had no game, so BYE wins. The system does not relabel a schedule fact as an injury estimate. Week 10 is the scheduled pre-return game, so it becomes MISS. Week 11 is the modeled return boundary, so it becomes BACK.

This is also why FantasyOMatic never describes a MISS or BYE as a zero Player Rating. Bucky's opponent-neutral talent still exists. What disappears is the Week Rating and projected fantasy points for a week in which he is not expected to play.

What changes across the product

One structured timeline drives every decision surface:

Rankings and Player Detail

The Player Rating remains visible as the neutral talent baseline. An unavailable current or future week shows status instead of a numeric Week Rating or projected points. The player page can still explain the injury, estimate, confidence, and expected return boundary.

My Team, Dashboard, Compare, and Fix Byes

Lineup tools suppress unusable weekly output, reduce remaining-season availability, and surface replacement timing. Compare can still show long-term talent, but it cannot pretend an expected missed game is startable.

Matchup Matrix

The Matchup Matrix (All-Pro) keeps schedule evidence separate from player availability. When verified opponent-defense evidence exists, Matchups Only can show that evidence even during a player's MISS week. Apply Player Ratings hides an unavailable weekly rating. Schedule Edge is independent of the player's injury; Player Outlook reflects expected missed games.

During the 2026 Week 1 historical bootstrap, opponent-defense strength is unavailable. The Matrix and extension withhold unsupported matchup boosts, penalties, and opponent-strength ranks. A fantasy D/ST scoring rating is not evidence of how difficult that defense is for an opposing quarterback, running back, receiver, or tight end. Subtracting Player Rating from Week Rating does not establish that evidence either.

You can still use the schedule and supported player outlook. An unavailable defensive signal does not mean the matchup is neutral; it means FantasyOMatic cannot yet support that claim.

AI Coach, Podcast, and Call In

AI Coach (All-Pro) and Podcast with Call In (Hall of Famer) receive the same structured availability rules. Hall of Famer adds AI Coach companion memory. Return timing must be presented as FantasyOMatic's estimate. Advice checks reject unsupported timing claims, unusable weekly values presented as startable, and reserve eligibility presented as guaranteed activation.

New advice is checked against the ratings and availability evidence it uses. A saved episode or call keeps the evidence from when it was recorded. If ratings or availability have changed, the page identifies that older context. A later Call In may use newer evidence than its parent episode, and that difference is identified. Check current rankings before acting on saved audio.

Early-season calibration cautions also apply to advice, with stronger caution for ROS, playoff, and trade decisions.

How missed games affect remaining value

BYEs and projected absences are not the same calculation.

A BYE is excluded from the scheduled-game average because no game exists. A scheduled MISS remains a zero-effective-output game inside the remaining horizon. FantasyOMatic then tracks how many games are expected to be available and applies that availability to rest-of-season and playoff decision signals.

This lets the product say two true things at once:

• The player may still be talented when healthy.
• The player's usable remaining value is lower if games are expected to be missed.

The same availability rules at every refresh

The historical example illustrates the rules that current updates must preserve: a BYE stays a BYE; an unavailable week does not leak a usable Week Rating or projected points; and BACK marks the first week the supported weekly output can reappear.

Recoverable starting values are retained so that clearing an injury can restore the forecast. Rechecking unchanged reports must not add the same backup-opportunity boost again or gradually inflate future projections.

Kickers follow their own player availability. Fantasy D/ST remains schedule-only for this player-availability treatment. Neither rule supplies missing opponent-defense evidence.

What the model still cannot know

Transparency includes the boundaries:

• The estimator supports multi-day practice trajectories, but ordinary current ingestion supplies the latest supported practice status. Do not assume every estimate includes a complete Wednesday-through-Friday progression.
• The historical duration table is intentionally reviewed and versioned; it is not silently retrained every week.
• Repeated same-body-part injury is not yet a separate recurrence feature.
• BACK means weekly output may reappear. It does not promise a full snap count or official activation.
• Public reporting and roster eligibility can change after FantasyOMatic's latest scheduled refresh. Complete report coverage is not a guarantee of participation.

These are reasons to label the estimate, not reasons to hide it.

How to use the signal

Start with the official status. Then read the timeline and confidence together. A MED estimate that spans two scheduled games should change roster planning more than a generic red badge, but it should never be treated as medical certainty.

Use Rankings to see which weekly values remain usable, open Player Detail to inspect the full availability story, and use My Team (All-Pro) to identify the actual roster decision created by the absence.

The product rule is simple: availability is a status, not a talent score.