Skip to content

COVER THE SLATE

Explore CTS

Learn the game

We cover the slate so you don’t have to cover the entire internet.

Find your next read

Search a team, player, sport or strategy topic.

NFL Week 3 Usage Report: Roles, Risers & Workload Changes

NFL Week 3 usage report with workload trends, target and carry changes, injury context and the roles that matter moving into Week 4.

Published 4 min read Updated
PAST SLATE Sep 27, 2026
NFL Usage Report
Share on X
NFL Week 3 Usage Report September 29 2026

Three weeks gives us enough football to start separating real role changes from one-game noise. The key is context. A player gaining snaps because a teammate left in the first quarter is different from a coaching staff deliberately changing its rotation. This Week 3 report focuses on the usage that can actually carry forward.

Cam Skattebo is becoming the Giants feature back

This is one of the cleaner role changes of Week 3. New York had rotated its backs heavily through the first two games, then leaned much more heavily on Skattebo against Tennessee. He finished with 100 total yards while the Giants went run-heavy. Devin Singletary was inactive, so we should not pretend every Week 3 touch is permanent, but the broader change in how New York kept Skattebo on the field is more important than the box score.

Jeremiyah Love took control of Atlanta’s backfield

Love out-snapped Tyler Allgeier 56-31 and handled 26 touches to Allgeier’s six. His 77.8% rushing share was among the highest on the Week 3 slate. This was not an injury-created vacancy. It was a meaningful redistribution inside an active backfield, which makes it one of the strongest usage signals of the week.

Jahmyr Gibbs keeps earning true feature-back volume

Gibbs is averaging 26.7 touches per game through three weeks. That matters because the early-season question was never whether he was explosive. It was whether Detroit would consistently give him enough work to compete with the highest-volume backs. Through three games, the answer has been yes.

Brian Thomas Jr. is moving the wrong direction

Thomas played only 37.1% of Jacksonville’s offensive snaps in Week 3 and drew a 3.7% target share. The blowout against New England affected the game environment, but outside usage reviews also flagged the reduced role as a deliberate change after early-season drops. This is not a player we should describe as merely unlucky. His playing time now needs to recover before we treat him like the same DFS asset he was entering the season.

Brock Bowers returned, but Michael Mayer did not disappear

Bowers immediately commanded a 43.3% target share while playing 78.6% of the snaps. The interesting secondary signal is Mayer still playing 87.1%. That points toward Las Vegas using substantial two-tight-end personnel rather than simply replacing Mayer when Bowers returned. Bowers is the target monster, but Mayer’s field time remains meaningful.

Rashee Rice owns Kansas City’s passing-game volume

Rice drew nine targets and a 39.1% target share in Week 3. Travis Kelce only saw two targets, even though he converted them into 59 yards and a touchdown. The Chiefs can distribute touchdowns unpredictably, but Rice’s target concentration is becoming difficult to ignore.

Garrett Wilson remains the Jets target anchor

Wilson commanded a 36.1% target share in Week 3. Isaiah Williams played 89.4% of the snaps because Adonai Mitchell was out, but only drew two targets. That distinction matters. Williams’ playing time was injury-created and did not translate into meaningful volume, while Wilson’s target dominance remained intact.

Kenyon Sadiq earned a real opportunity, with injury context

Sadiq played 57.6% of the snaps and drew eight targets for a 22.2% target share. Mason Taylor was out, so this was clearly helped by injury. The useful takeaway is not that Sadiq permanently owns that role. It is that he performed when the opportunity arrived, which gives the Jets a reason to keep him involved even as the room gets healthier.

Jaylen Warren’s 90% snap game needs the injury label attached

Warren played 90.3% of Pittsburgh’s offensive snaps, the highest rate among running backs in the Week 3 usage review. Rico Dowdle was out. That makes the number useful for understanding Warren’s ceiling when the backfield is depleted, but not evidence that Pittsburgh has permanently moved to a 90-10 split.

Chicago’s passing usage is getting interesting

Monday night gave us another data point on Kalif Raymond and Luther Burden. Burden drew 11 targets, caught seven and scored, while Raymond led Chicago with 90 receiving yards. Caleb Williams was out and Case Keenum started, so quarterback context matters, but the target earning itself is notable. Burden’s involvement is especially interesting because it can survive a quarterback change if Chicago continues manufacturing touches for him.

What we are not overreacting to

  • Zay Flowers produced despite playing only 32.8% of Baltimore’s snaps because he entered as a game-time decision with a hamstring injury. That is not a normal workload baseline.
  • Ollie Gordon II handled 20 running-back touches after De’Von Achane suffered an ACL injury and Jaylen Wright was inactive. That is injury-created opportunity, although Achane’s long absence means the Miami backfield change now matters going forward.
  • Brycen Tremayne’s Carolina snap spike came after Jalen Coker left with a quad injury. Treat it as a contingency role until Coker’s timetable is clearer.
  • Jauan Jennings and Tai Felton gained Minnesota opportunity after Justin Jefferson left with an ankle injury. The next-step value depends on Jefferson’s availability.

CTS Week 3 usage takeaway

The strongest organic role changes are Skattebo’s move toward feature-back work, Love taking control of Atlanta’s backfield, Gibbs sustaining elite touch volume and Brian Thomas Jr. losing playing time. The strongest injury-driven situations to carry into Week 4 are Miami’s backfield after Achane’s ACL injury and any receiving changes tied to longer absences. Our Usage Board should show the raw numbers. Our analysis should explain why those numbers changed.