Should I Drop Mark Andrews?

Short Answer

Dropping Mark Andrews is most sensible when he sits behind another reliable tight end on your roster and a valuable waiver addition is available. It is riskier when tight end is thin on waivers, your league rewards the position, or you are reacting to short-term frustration. Weigh your league format, roster construction, and his current role before cutting him.

When It Makes Sense

  • Good fit: In shallow redraft leagues with short benches, where you start only one tight end and Andrews is stuck behind a clearly better starter, he can become a luxury bench piece rather than a necessity. If the waiver wire offers a running back, wide receiver, or quarterback with immediate starting opportunity, using his roster spot may raise your weekly scoring ceiling.
  • Good fit: You already roster two playable tight ends and your league does not use TE-premium scoring. When Andrews is your second or third option rather than a starter, the value of the player his roster spot is blocking often exceeds the small chance he returns to your lineup.
  • Good fit: There is objective evidence, not just frustration, that his role has shrunk. A notable drop in snap share, target share, or red-zone usage, or a change in quarterback, offensive scheme, or injury outlook, can justify moving on.
  • Good fit: You need an active starter for the upcoming week and Andrews is unlikely to play, while the waiver wire has a healthy tight end facing a favorable matchup.

When You Should Avoid It

  • Warning sign: You have no reliable replacement at tight end and the waiver wire is barren. Forcing yourself to start a low-floor streamer every week can hurt more than keeping Andrews on your bench.
  • Warning sign: Your league uses TE-premium scoring, deep benches, or keeper/dynasty rules. In those formats, proven tight ends carry extra value because replacements are hard to find and future assets matter more than a one-week roster spot.
  • Warning sign: You are cutting him after a single quiet game, a minor injury scare, or a tough matchup. Talent and role often rebound, and fantasy managers who panic-drop name players usually regret it later in the season.
  • Warning sign: You are near your league’s trade deadline and could get something back rather than nothing. Dropping a tradable asset without shopping it is usually poor roster management.

Pros and Cons

Pros

  • Reclaims a roster spot for a high-upside waiver claim at a position you actually start.
  • Removes the emotional temptation to keep starting an underperforming player based on name recognition alone.
  • Allows you to pursue a streaming strategy if you are comfortable managing weekly matchups.
  • Reduces dead weight on your bench during the playoff push, when every active spot counts.

Cons

  • Tight end is one of the scarcest positions in fantasy football; releasing a proven producer can easily backfire.
  • You may be dropping him at the low point of his trade value, wasting a usable asset.
  • A sudden injury to your starter could leave you scrambling if Andrews is no longer available.
  • A rival manager may claim him and benefit from a rebound in role or schedule, possibly using him against you.

Decision Checklist

  • Do I have a clearly better starting tight end, or will I be forced to start a waiver-wire replacement every week?
  • Is my league redraft, keeper, or dynasty, and does the format change how much bench depth and future value matter?
  • Am I seeing a sustained decline in role, targets, or snap share, or am I reacting to one bad box score?
  • Who is the best player I would add, and how likely is that player to outscore Andrews over the rest of the season?
  • Is there a trade market for Andrews, even at a discount, before I consider dropping him?
  • Would dropping him actually solve a starting-lineup problem, or am I creating a new one at a thin position?

Alternatives to Consider

Before you drop Andrews, explore a trade with a manager who is weak at tight end; even a modest return of bench depth or future draft capital is usually better than releasing a known player outright. If a trade is not possible, you can bench him and monitor snap counts, target share, and red-zone usage for another week or two. In redraft leagues with short benches, streaming tight ends by matchup is a viable alternative if the waiver wire offers decent options. In dynasty or keeper leagues, selling low on Andrews is generally preferable to dropping him, because tight-end production can rebound and retained assets matter more than a single-week roster spot.

Final Recommendation

Dropping Mark Andrews usually makes the most sense in shallow redraft leagues where he is buried behind another starting tight end and a clearly better waiver option is available. Hold or trade him in deeper leagues, TE-premium formats, or when the waiver wire is thin at tight end. The most important step is to separate a temporary slump from a lasting role change. For high-stakes leagues or large financial contests, consult current fantasy football analysts, expert consensus rankings, and team-reported injury updates before finalizing the move.

FAQ

Should I drop Mark Andrews?

It depends on your league depth, tight-end depth, and the waiver wire. In shallow leagues where he is not starting, dropping him for an immediate contributor can make sense. In deeper or TE-premium formats, holding or trading him is usually safer.

What should I consider before dropping Mark Andrews?

Compare his current role and target share to available replacements, check your league format, make sure you have a playable starter, and try to trade him before cutting him outright.

Is Mark Andrews droppable in all fantasy leagues?

No. Leagues with large benches, keeper rules, or premium tight-end scoring tend to make him more valuable to hold because replacements are scarce.

References

  1. NFL.com player news and injury updates
  2. ESPN Fantasy Football rankings and analysis
  3. FantasyPros expert consensus rankings
  4. Baltimore Ravens official team injury reports

Related Terms

Leave a Reply

Your email address will not be published. Required fields are marked *