From time to time, you may notice that an owner in your league dropped someone from their starting roster who had already played (or started) their game for that week.
You might be wondering if this is a bug or intended by design.
The answer is that this is intentionally designed, and there is only one way for this to happen.
If the player being added was on waivers and cleared before the end of the football week, this is allowed. This is not allowed for any immediate free agent claims.
Let's say I put in a waiver claim (or FAAB bid) for Sammy Watkins on Friday, dropping Mohamed Sanu. Watkins' waiver countdown shows me that he'll clear waivers on Sunday at 2 p.m. EST.
However, the game that Sanu is playing in begins at 1 p.m. EST on that Sunday, and I have already started him in my lineup.
I won my waiver claim, and now, Sanu has been dropped from my roster during his game. Sanu's stats for his entire game are still counted for this week even though he is no longer on my team but is locked into my lineup. I cannot bench him or move him out. Sanu will have an "Off Roster" label appear next to his name.
It is also possible for me to now start Watkins this week, but only if his game has not yet started, and I also have the room elsewhere in my lineup to use him. Meaning, switching out another wide receiver or flex position.
The reasons we allow this to happen is as follows:
- This prevents even greater confusion and having to think about where you plan to put a player (starters vs bench) after they are used for a pending waiver claim.
- There is a minimal advantage gained by doing this. The mathematical advantage gained is no different than being able to drop a bench player after they played a game.
- Any advantage is off-set by a significant cost - your waiver position (or tiebreaker position in FAAB).
- Everyone has equal rights to that waiver.
As a result, we made a deliberate decision that all waiver claims, no matter who you drop, will be allowed and cleared at the time that the waiver clears.