Skip to main content

Commissioner Injury Management: Bench Players Vs. IR Spots

Injuries create manager frustration.

If your platform has IR spots, clarify the rule: Can teams stash injured players for free? Or does every player (injured or not) take a bench spot? Different rules, different league dynamics.

The IR Question

No IR spot (traditional):

  • Injured players still take a bench spot
  • Incentivizes dropping injured players quickly
  • Rewards managers who chase waiver pickups fast

IR spot (modern, ESPN standard):

  • Injured players go to IR
  • Team can fill their spot with a healthy player (15 roster + 1 IR = 16 active)
  • Removes penalty for injuries (team doesn’t lose depth)

The Rule Decision

Choose one and document it in your constitution:

Option 1: “No IR spot. Injured players take a bench spot.”

  • Simple rule
  • Fair (everyone faces same constraint)
  • Penalizes teams with injuries (realistic)

Option 2: “IR spot allowed. Only players on team’s IR list can go there.”

  • More complex rule
  • Less fair to lucky teams (fewer injuries)
  • More forgiving (encourages depth building)

Clarifying “Injured”

If you use IR spots, define injured:

  • Player on team’s official Injured Reserve
  • Player labeled “Out” or “Questionable” (not “Day-to-day”)
  • Player with 4+ week expected absence

Bad definition: “Any player I think might be injured” (too broad, exploitable)

The Roster Constraint Problem

Without IR spot:

A manager’s RB1 gets injured (season-ending). They drop him, add a waiver pickup. Their roster depth stays intact (15 spots, 1 injured drop).

With IR spot:

Same manager puts RB1 on IR, adds a waiver pickup. They have 16 active players (15 bench + 1 IR). Advantage: They get free depth.

Is this fair? Not really. Unlucky team (injured player) gets more depth than lucky team (no injuries).

The Practical Approach

Most modern leagues use IR spots (ESPN, Yahoo default to this).

Best practice:

  1. Adopt IR spot rule (standard now)
  2. Clarify the “Out/Questionable” threshold (only Out players, not Questionable)
  3. Enforce consistently (once a player is ruled Out, IR-eligible)

The Dispute

Manager says: “My RB is ‘Questionable’—can I put him on IR?”

You say: “Only ‘Out’ players can go on IR. ‘Questionable’ means he might play. Keep him on your bench.”

How to avoid: Define in your constitution: “Only players labeled ‘Out’ by the platform can be placed on IR.”

The Worked Example

Week 5:

  • Manager A’s RB1 is labeled “Out for 4-6 weeks” (ACL)
  • Manager A puts him on IR
  • Manager A adds a waiver pickup with the freed roster spot
  • Roster is now: 15 bench + RB1 (IR)

Week 9:

  • RB1 is still on IR (recovery ongoing)
  • Manager A hasn’t removed him (leaves him there for future flexibility)
  • This is allowed (player is still Out)

Week 13:

  • RB1 is cleared to play (returns from IR)
  • Manager A must move him to active roster (or drop him)
  • IR spot is now free for another injured player (if needed)

The Payoff

Clear injury rules:

  • Prevent disputes (“Can I stash him on IR?”)
  • Create fairness (everyone knows the rule)
  • Streamline management (commissioners don’t have to make judgment calls weekly)

Living guide — updated each preseason. Related: commissioner fundamentals · league constitution.