Start Tony Pollard or David Montgomery? Week 7

Updated Oct 21, 4:21 PM ET. Locks at kickoff, graded after. Week 8 answer posts Tuesday.

Latest

Oct 21, 1:43 PM ET: Jawhar Jordan: Listed Out (Undisclosed) (Sleeper injury feed)

Start Tony Pollard over David Montgomery

Start

Tony Pollard

RB · TEN · vs CLE

Market projects: 13.6; fantasy pts
CLE D vs RB: 16.1; 2nd fewest to RBs (2026)
Upside: Moderate; 55 of 100 at RB
Snap share: 55%; Through Week 6
Target share: 8%; Through Week 6

Sit

David Montgomery

RB · HOU · vs NYG · Questionable

Market projects: 10.0; recent weeks avg
NYG D vs RB: 21.6; 15th most to RBs (2026)
Upside: Moderate; 61 of 100 at RB
Snap share: 46%; Through Week 5
Target share: 4%; Through Week 5

Should I drop Tony Pollard for David Montgomery?

Yes, on the rest of the season. David Montgomery projects 105 market-implied PPR points from Week 7 through Week 17 (10.5 a game over 10 games), Tony Pollard 99 (9.9 a game over 10 games). For Week 7 the call starts Tony Pollard over David Montgomery. So make the move after his Week 7 game. David Montgomery is listed questionable.

Parlae may earn a commission from price links.

David Montgomery rookie cards

Make this call for your own roster

Sync your league and My Team sets this week's lineup for your actual roster, spot by spot. Free, no account.

Sync my league

Sleeper ESPN Yahoo

Or get it by email

Tuesday 8am ET: one email with what moved on the board and who is worth a claim.

Free. One a week, one tap to stop.

Our Week 7 call

Start Tony Pollard over David Montgomery in Week 7.

Market-based projections have Tony Pollard at 13.6 points and David Montgomery at 10.0, a gap of 3.6. Tony Pollard's number is scaled up from a partial market: not every stat the position needs is posted yet, so the rest is estimated from what is. No player market is posted for David Montgomery this week yet, so his 10.0 is the average of his market-based projections in Weeks 4 and 5 (10.2 and 9.8); the call is rebuilt when his market posts. Drafters take Tony Pollard at ADP 68 and David Montgomery at 52.

What the market projects

Player markets imply 13.6 fantasy points for Tony Pollard, with 90 percent of the markets a RB needs posted.

The market-based projection for Tony Pollard is 68 rushing yards and 0.6 touchdowns (10 and 13 market sources).

No Week 7 player market is posted for David Montgomery yet. His market-based projections were 10.2 and 9.8 points in Weeks 4 and 5, an average of 10.0, which stands in until his Week 7 market posts.

That puts Tony Pollard 3.6 points ahead of David Montgomery on these projections.

Week 7 matchups

Tony Pollard and TEN host CLE on Sunday at 1:00 PM ET.

CLE allowed 16.2 fantasy points a game to RBs this season over 6 games, the 2nd fewest in the league.

Running backs ran for 99 yards and 0.2 touchdowns a game against CLE and caught passes for 18 more yards.

David Montgomery and HOU host NYG on Sunday at 1:00 PM ET.

NYG allowed 21.6 fantasy points a game to RBs this season over 6 games, the 15th most in the league.

Running backs ran for 108 yards and 0-1 touchdowns a game against NYG and caught passes for 22 more yards.

By points allowed to the position, David Montgomery has the softer matchup.

Injury status

Tony Pollard is not on the injury report.

David Montgomery is listed as questionable with a groin injury.

Usage before Week 7

Through Week 6, Tony Pollard played 55 percent of TEN snaps, took 67 percent of the carries, drew 8 percent of the targets and had 41 percent of the red zone chances.

Tony Pollard, Week 3 against NYG: 32 of 60 snaps, 17 carries for 74 yards, 4 targets and 4 catches for 22 yards.

Tony Pollard, Week 4 against BAL: 34 of 64 snaps, 16 carries for 48 yards, 4 targets and 2 catches for 2 yards, 1 touchdown.

Tony Pollard, Week 5 against HOU: 30 of 63 snaps, 14 carries for 52 yards, 1 target and 0 catches for 0 yards.

Tony Pollard, Week 6 against IND: 35 of 46 snaps, 19 carries for 76 yards, 1 target and 0 catches for 0 yards.

Through Week 5, David Montgomery played 46 percent of HOU snaps, took 45 percent of the carries, drew 4 percent of the targets and had 28 percent of the red zone chances.

David Montgomery, Week 2 against CIN: 42 of 80 snaps, 6 carries for 10 yards, 2 targets and 2 catches for 14 yards.

David Montgomery, Week 3 against IND: 34 of 54 snaps, 11 carries for 33 yards, 2 targets and 2 catches for 15 yards.

David Montgomery, Week 4 against DAL: 31 of 55 snaps, 10 carries for 24 yards, 0 targets and 0 catches for 0 yards.

David Montgomery, Week 5 against TEN: 9 of 66 snaps, 5 carries for 11 yards, 0 targets and 0 catches for 0 yards.

Their 2025 seasons

In 2025, Tony Pollard played 17 games for TEN and scored 185.8 PPR points, 10.9 a game, finishing RB23.

He ran 242 times for 1082 yards and 5 touchdowns, and caught 33 of 41 targets for 206 yards.

He was on the field for 62 percent of the offense's snaps in the games he played.

In 2025, David Montgomery played 17 games for DET and scored 166.9 PPR points, 9.8 a game, finishing RB27.

He ran 158 times for 716 yards and 8 touchdowns, and caught 24 of 29 targets for 192 yards.

He was on the field for 37 percent of the offense's snaps in the games he played.

Their other Week 7 calls

Locks at kickoff, graded after. When the start/sit engine grades week 7, the call and the result appear on the public record, wrong ones included.

Drop or keep

Should I drop Tony Pollard for David Montgomery?
Yes, on the rest of the season. David Montgomery projects 105 market-implied PPR points from Week 7 through Week 17 (10.5 a game over 10 games), Tony Pollard 99 (9.9 a game over 10 games). For Week 7 the call starts Tony Pollard over David Montgomery. So make the move after his Week 7 game. David Montgomery is listed questionable.
Should I drop David Montgomery for Tony Pollard?
No. Keep David Montgomery: he projects 105 market-implied PPR points from Week 7 through Week 17 (10.5 a game over 10 games), Tony Pollard 99 (9.9 a game over 10 games). For Week 7 the call starts Tony Pollard over David Montgomery. David Montgomery is listed questionable.