Fantasy football managers know that every lineup decision can make or break a week, and choosing the right players to start or sit is where championships are won. With the 2026 NFL season underway, matchups, stats, and trends are more important than ever. From favorable matchups and scoring trends to players you should avoid in tough spots, my weekly positional start and sit guide is built to give you an edge.
Want your start/sit questions answered within minutes? Join the Blitz Community for free fantasy football advice all season long.
Running Backs to Start
Cam Skattebo, RB (NYG)
Cam Skattebo hasn’t delivered the breakout season I expected, but his workload remains encouraging. Through five games, he’s rushed for 294 yards and one touchdown on 81 carries while adding 10 receptions for 79 yards. He’s averaging just 3.6 yards per carry and has scored only once, making his lack of explosive plays particularly frustrating. Against Washington in Week 5, Skattebo rushed 13 times for 59 yards and caught two passes for 12 yards, but a lost fumble hurt his fantasy production. Skattebo has fumbled four times through five games, although his costly overtime turnover against Washington was the first he actually lost. Ball security is becoming a concern, but the Giants haven’t significantly reduced his workload, as he’s handled at least 15 touches in every appearance.
New Orleans gives Skattebo an excellent opportunity to turn that volume into meaningful fantasy production. The Saints rank 27th in defensive EPA per play and have allowed 133.4 rushing yards per game to running backs, along with a 48.9% rushing success rate. Opposing backs are averaging 3.8 yards after contact per carry, the third-most in the NFL, while seven running backs have already scored double-digit fantasy points against this defense. That matters for Skattebo because he’s struggled to consistently create additional yardage on his own, averaging just 2.0 yards after contact per attempt. The matchup should provide more opportunities to get into the second level, and his involvement in the passing game gives him another way to contribute. I’m expecting Skattebo to deliver one of his better performances of the season, making him a strong RB2 with legitimate RB1 upside.
Dameon Pierce, RB (PHI)
Dameon Pierce suddenly finds himself in position to lead Philadelphia’s backfield after a brutal stretch of injuries. Saquon Barkley has missed time with a hamstring injury, Tank Bigsby is on injured reserve following core muscle surgery, and Will Shipley suffered a partial plantar fascia tear against Jacksonville that is expected to sideline him for multiple games. Pierce stepped into the lead role after Shipley exited in Week 5, finishing with 11 carries for just 14 yards while catching two of five targets for negative two receiving yards. That production was obviously disappointing, but Philadelphia’s offensive line has also been dealing with significant injuries. The situation has become even more concerning with Jalen Hurts ruled out for Week 6 after a superficial blood clot was discovered in his calf. Tanner McKee is expected to start against Carolina, creating additional uncertainty about Philadelphia’s offensive efficiency. Pierce hasn’t been a regular featured back in several seasons, but the opportunity to handle a substantial workload makes him difficult to ignore.
Carolina presents an appealing matchup for whoever leads Philadelphia’s backfield, allowing 25.6 fantasy points per game to running backs, the fifth-most in the NFL. The Panthers rank 21st in defensive EPA per play and have struggled to consistently limit opposing rushing attacks. With McKee replacing Hurts, Philadelphia could lean more heavily on its running game to take pressure off its backup quarterback, potentially creating additional carries for Pierce. Barkley’s availability remains the deciding factor after he missed Wednesday’s practice. If Barkley is ruled out, I’m comfortable starting Pierce as a volume-dependent RB2 or flex option, although Carson Steele could also see opportunities. If Barkley returns without restrictions, Pierce belongs back on the bench.
Rhamondre Stevenson, RB (NE)
Rhamondre Stevenson has quietly put together consecutive strong fantasy performances, and his role could become even more valuable with TreVeyon Henderson dealing with an ankle injury. Stevenson rushed 13 times for 64 yards and a touchdown against Las Vegas in Week 5 while adding three receptions for 21 yards, giving him another performance with at least 17 PPR points. Through five games, he’s averaging 11.4 carries, 45.4 rushing yards, 3.8 receptions and 22.2 receiving yards per contest. That receiving involvement has been particularly important because New England hasn’t consistently generated explosive rushing plays. However, Henderson isn’t the only other running back who could affect Stevenson’s workload. Corey Kiner impressed against Las Vegas, rushing six times for 52 yards while adding a seven-yard reception. Henderson’s absence wouldn’t necessarily leave Stevenson with the entire backfield, although his established passing-down and scoring-area roles still make him the preferred fantasy option.
The Jets are another favorable opponent for Stevenson, allowing 21.7 PPR fantasy points per game to running backs. New York ranks 10th in defensive EPA per play, but that overall ranking hides some significant problems against the run. The Jets rank 29th in defensive rushing EPA and have allowed significant production to opposing fantasy running backs this season. That weakness is particularly appealing for Stevenson because New England should be able to establish a more balanced offensive approach rather than relying exclusively on Drake Maye. Henderson’s ankle injury could also create additional opportunities for Stevenson, particularly in passing situations and near the goal line, even if Kiner continues receiving carries. I’m viewing Stevenson as a strong RB2 with top-12 upside if Henderson remains sidelined.
Tony Pollard, RB (TEN)
Tony Pollard hasn’t been particularly exciting for fantasy football, but his workload has remained relatively dependable despite Tennessee’s offensive struggles. Through five games, he’s averaging 13.6 carries for 54.6 rushing yards while adding 2.4 targets and 1.6 receptions per contest. His 4.0 yards per carry isn’t particularly concerning, but he’s scored only one rushing touchdown and hasn’t consistently contributed enough as a receiver to offset Tennessee’s limited scoring opportunities. Pollard handled 14 of the Titans’ 17 running back carries against Houston in Week 5, demonstrating that he remains the clear leader of the backfield. Unfortunately, Tennessee managed just three points in that loss and is averaging a league-low 11.6 points per game. That’s a significant problem for a running back who relies heavily on rushing volume and touchdown opportunities, especially with the Titans’ offensive line struggling to consistently protect the quarterback and sustain drives.
Indianapolis presents one of Pollard’s better matchups of the season, allowing 24.6 PPR fantasy points per game to running backs, the sixth-most in the NFL. The Colts rank 26th in defensive EPA per play and 31st in defensive rushing EPA, making them one of the league’s least efficient defenses against the run. They also allowed Jaylen Warren to generate 188 scrimmage yards and two touchdowns in Week 5, demonstrating how vulnerable this defense can be when opposing backs receive consistent opportunities. However, Tennessee’s offensive limitations make Pollard far from a guaranteed start. If the Titans fall behind early, his rushing volume could disappear, and this offense hasn’t demonstrated that it can consistently create scoring opportunities even against weaker opponents. I’m willing to trust Pollard as a lower-end RB2 or flex because of the matchup and his established role, but his limited receiving involvement and Tennessee’s struggling offense significantly cap his ceiling.
Running Backs to Sit
Woody Marks, RB (HOU)
Woody Marks is one of the more interesting running backs entering Week 6 because his workload could increase dramatically following David Montgomery’s groin injury. Montgomery exited Houston’s Week 5 victory over Tennessee and didn’t return, allowing Marks to take over the backfield. He finished with 15 carries for 62 yards while catching four passes for 23 yards, giving him 85 scrimmage yards in his most productive performance of the season. More importantly, Marks played 95.7% of the offensive snaps over the final three quarters after Montgomery exited, handling all 13 running back carries during that stretch. He also posted a 66.7% route participation rate and an 11.5% target share during those three quarters. Those usage numbers are encouraging, and Montgomery’s absence from Wednesday’s practice suggests Marks could be positioned for another substantial workload. With Montgomery considered week-to-week, Marks is one of my favorite waiver-wire pickups because of his potential value beyond Week 6.
However, Jacksonville is about as difficult a matchup as Marks could draw for his first opportunity to lead Houston’s backfield, particularly with the game being played in London. The Jaguars rank fourth in defensive EPA per play and fourth in defensive rushing EPA, while allowing the second-fewest fantasy points per game to running backs. They’ve also surrendered the second-lowest explosive run rate, fifth-lowest rushing success rate, and fewest yards after contact per attempt to opposing backs. That creates a difficult environment for a Houston offense that has struggled to consistently establish its running game, even when Montgomery has been healthy. Marks’ potential receiving involvement provides some PPR upside, and I’m interested in his rest-of-season value if he maintains a featured role. However, there’s a difference between being a valuable waiver-wire addition and being someone I’m comfortable starting immediately against one of the league’s strongest defensive fronts. He’s a volume-dependent flex option rather than a preferred Week 6 starter.
Omarion Hampton, RB (LAC)
Omarion Hampton’s usage has become one of the most frustrating developments in fantasy football, particularly after entering the season with expectations of becoming a featured running back. Through five games, he’s averaging 14.6 carries for 54.2 rushing yards while contributing very little as a receiver, with just five catches for 35 yards on the season. His role became even more concerning against Denver in Week 5, when he played only 31.7% of the Chargers’ offensive snaps while handling 41.2% of the team’s rushing attempts. Hampton averaged just 2.4 yards per carry in that game and ran only two routes, demonstrating how limited his involvement has become outside of early-down rushing situations. Kimani Vidal and Keaton Mitchell have taken on larger roles, particularly in passing situations, leaving Hampton without the dependable three-down workload fantasy managers expected.
Kansas City makes that declining workload even more concerning, ranking eighth in defensive EPA per play and eighth in defensive rushing EPA. The Chiefs have allowed the eighth-lowest rushing success rate, fewest yards before contact per attempt, and third-lowest missed tackle rate to opposing running backs. That’s a difficult combination for Hampton, particularly when the Chargers haven’t consistently given him opportunities to contribute as a receiver. Los Angeles has also struggled offensively, creating the possibility that another negative game script could push more snaps toward Vidal and Mitchell. Hampton still has the talent to generate explosive plays, but I’m not willing to rely on that upside when his snap share and receiving involvement have become so limited. He’s a touchdown-dependent flex option rather than a dependable RB2, and I’m keeping him on the bench in traditional leagues.
Jeremiyah Love, RB (ARI)
Jeremiyah Love has been one of the biggest disappointments in fantasy football through five weeks, particularly after entering the season with enormous expectations as the third overall pick. He’s rushed for 245 yards and one touchdown on 67 carries, averaging just 3.7 yards per attempt while adding 11 receptions for 36 yards. His Week 5 performance against Detroit was especially concerning, as he managed only 22 yards on 12 carries and finished with a season-low 2.2 fantasy points. Love has now scored fewer than eight fantasy points in three of his last four games, and his rushing efficiency hasn’t shown meaningful improvement. More importantly, he’s dealing with an ankle injury that appears to be affecting his workload. Over the last two games, Love has averaged just 13.5 touches and 38.5 scrimmage yards while playing 47% of Arizona’s offensive snaps. Tyler Allgeier has remained involved, preventing Love from establishing the featured role fantasy managers expected.
The Rams present an interesting matchup because their overall defensive performance has been considerably better than their rushing efficiency. Los Angeles ranks 11th in defensive EPA per play, but 24th in defensive rushing EPA, suggesting there are opportunities for opposing backs to generate production on the ground. The Rams have allowed the highest rushing success rate, ninth-highest explosive run rate, and eighth-most yards before contact per attempt to running backs, so this isn’t an impossible matchup for Love. However, his declining workload and ankle injury make it difficult to trust him even in a potentially favorable situation. Love has not practiced to open the week, and his receiving involvement has also fallen significantly, with just a 19.4% route share and 2.4% target share over the last two games. If Love cannot play, Allgeier could move into the starting role. Even if Love is active, I’m not comfortable relying on a running back who isn’t consistently healthy, efficient or heavily involved in his offense. Until his ankle improves and Arizona commits to giving him a larger role, he’s a risky flex option rather than a player I’m comfortable starting.
