Will Shipley currently costs almost nothing. One projection source had him valued at 2.2 fantasy points for both Week 4 and Week 5, the kind of number that reflects a bench stash, not a roster priority. His season line backs that price up: nine carries for 28 yards, four catches for 24 yards, zero touchdowns, 3.1 PPR points per game, RB65 overall through four weeks. By any conventional measure, Shipley is replacement level.
The gap between that price and his actual value opened up in the span of one half of football. Saquon Barkley left Philadelphia's Week 4 game with a hamstring injury on the first series. Tank Bigsby, the presumed next man up, later exited himself with an undisclosed issue. For a stretch of that game, Will Shipley was the last running back standing on the Eagles' roster. That is not a stat line. It is a role that did not exist a week earlier, and it is the entire reason Shipley is worth a roster spot this week even though his numbers do not yet justify one.
The Backfield Behind Saquon Barkley
Barkley remains Philadelphia's lead back and the engine of this offense when healthy. Behind him, Tank Bigsby was the Eagles' notable offseason addition at the position, making the initial 53-man roster as the clear primary backup. Dameon Pierce signed in free agency in late March but did not survive final cuts; Philadelphia also waived Jordan Mims and Carson Steele on August 30, clearing out depth that never stood ahead of Shipley to begin with. Shipley himself made the 53-man roster that same week, with coverage describing a strong summer, a valued backup role, and a retained special-teams job — plus the explicit note that he could see a larger offensive share if either Barkley or Bigsby went down.
Jalen Hurts remains the starting quarterback, unchanged from last year, which matters because it means the passing-game environment around any Eagles back is familiar rather than new. What has changed is the play-caller: Sean Mannion was finalized as offensive coordinator in March, with Bobby King coaching quarterbacks and Nick Sirianni still the head coach. A new coordinator calling the same quarterback's run game is a wrinkle worth watching, but it is not the reason Shipley matters this week. The reason is that Bigsby, not Shipley, was the back the Eagles signed to be the clear second option — and after Week 4, that depth chart got tested in real time.
What Week 4 Actually Showed
When Barkley left early against the Rams, it was Bigsby and Shipley who split the work, and reporting described the two backups playing a near-even amount of snaps the rest of the way. Shipley's box score from that stretch was modest — six carries for 23 yards, no catches on his one target — but he also returned three kickoffs for 65 yards, a reminder that his special-teams role is real and gives him a floor even in games where he barely touches the ball on offense. The useful signal from Week 4 is not the yardage. It is that when Philadelphia's top back went down, Shipley was on the field immediately, not watching from the sideline.
The Math If Both Backs Sit in London
Shipley was removed from the injury report on October 2 after dealing with a foot issue earlier in the week, and the expectation at that point was that he would continue in his usual depth role. Then Barkley's hamstring and Bigsby's undisclosed issue both surfaced in the same game. RotoWire's reporting made the contingency explicit: Bigsby had been working ahead of Shipley after Barkley's exit, but if both top backs are unavailable, Shipley could take on the lead role against the Jaguars in London. That is a real, named scenario, not speculation — it is the specific outcome that turns a $0 waiver claim into a potential three-down workload for a week.
Bigsby Already Has the Edge
The strongest case against adding Shipley is that the pecking order has already been settled, and not in his favor. NBC Sports reported that Shipley will assume second running back duties, with Bigsby perhaps working in more on offense after the mini-bye — language that puts Bigsby, not Shipley, in position to absorb Barkley's work if the hamstring lingers. FantasyPros was even more direct, saying Shipley is expected to continue to play his usual depth role in the week ahead and beyond. Add the foot issue that only just cleared the injury report, and the counter-argument writes itself: this is a committee's third wheel, not a lead back in waiting, and the 3.1 PPG season average is the accurate reflection of his current value.
That argument is honest and it is mostly right about the baseline. It is wrong about the tail. Depth charts do not need Shipley to pass Bigsby for Shipley to matter — they only need Barkley and Bigsby to both be compromised at the same time, which already happened once, in the same game, within a matter of series. A player one game-script away from lead touches in an offense that still runs through its running backs is not the same asset as a true dead-roster-spot handcuff, even if the two look identical in a season-long points column.
Add Him for Insurance, Not for Starts
The tiebreaker here is opportunity cost, not projection math. Shipley is priced like a player who will not matter, and in most weeks he will not. But the Eagles just showed, in real time, how fast that changes in this specific backfield — one hamstring and one undisclosed issue away from Shipley fielding a real workload, with a retained special-teams role as a floor even when he doesn't. In deeper leagues, or any roster already invested in Barkley, that is worth a free waiver claim this week. In shallower leagues, it is fine to wait and see whether Barkley's hamstring or Bigsby's issue costs either back a game before using the spot. Either way, the instruction is specific: add Shipley as backfield insurance behind Barkley, not as a streaming start, and revisit the claim only if Philadelphia's Week 5 injury report in London actually removes one or both backs ahead of him.