Bucky Irving's late-season role changed in a way fantasy drafters can actually use. Tampa Bay gave him real carries, enough passing-down access, and a backfield job that looked more stable by the closing sample. That doesn't make him automatic. It makes him the back in this Chase Brown, Alvin Kamara, and Irving pocket whose workload can still grow.
Here is the call we can grade in January: if all three stay near these publish-day prices, draft Irving at or after pick 22, make Brown fall past pick 24 before clicking, and save Kamara for pick 100 or later in PPR builds. That's the move because Irving is the only one of the three who combines a current first-team depth-chart slot, a high-confidence projection profile, and a role that can still expand without needing his offense to change identity.
The board is doing two jobs. It separates the backs by price, and it separates them by what has to happen for the pick to pay off. Irving needs Tampa Bay to keep him on the field for early-down work and enough two-minute or checkdown snaps. Brown needs Cincinnati to keep feeding a back while Joe Burrow, Ja'Marr Chase, and Tee Higgins are still the center of gravity. Kamara needs the Saints' passing role to rebound while the roster is already treating him more like a specialist than an unquestioned centerpiece.
That is why the first click goes to Irving. The easiest mistake at this turn is drafting the most recent headline instead of the back whose football job gives you the best return path.
Why Irving is the better swing
What worked last year for Irving was the late shift from change-of-pace touches to drive-level involvement. In FFN's role data, he finished the closing sample with 18 carries per game, a 59.7 percent snap share, and a strong recent-volume profile. Week 18 against Carolina is the moment that keeps this from being a spreadsheet argument: Tampa Bay ran 38 times, Irving handled 26 carries, and he played 63 percent of the offensive snaps.
That is a real usage picture. A back doesn't need every third-down snap to matter when the offense is comfortable letting him close drives, keep the run game honest, and catch enough short-area throws to avoid empty rushing weeks. Irving's latest logged game only included two targets, but the broader sample still showed passing-game access, and the publish-day projection gives him 52 targets beside 208 rushing attempts.
The current depth chart matters, too. Irving is listed as Tampa Bay's RB1, with Kenneth Gainwell and Sean Tucker behind him. That doesn't guarantee a feature role, but it does mean the draft case isn't built on a vague hope that a veteran gets pushed aside. The job is already pointed at Irving. Now we are asking whether the Buccaneers keep enough of the receiving and red-zone work attached to him.
Tampa Bay's team profile keeps the case honest. The Buccaneers threw on 61.4 percent of plays last season and used a 59.6 percent red-zone pass rate, so this isn't a 1990s bell-cow setup. If Irving becomes a 12-touch back in an offense that still wants Baker Mayfield throwing near the goal line, the price gets thin fast. But if the late-season carry volume holds and the short targets stay in his weekly menu, pick 22 is playable. We don't need a miracle. We need the role that already showed up to survive August.
Pick 18 RB board
| Player | Publish-day Context | Football Reason | Draft Action |
|---|---|---|---|
| Bucky Irving | RB17, overall rank 29, ADP 22 | Lead Tampa Bay back with late-sample carry growth and enough target access to matter | Draft after the early anchor tier if your build needs an upside running back |
| Chase Brown | RB14, overall rank 25, ADP 18 | Lead Cincinnati back in a pass-first offense, with the cost already charging for the late-season rush spike | Take only if he slips past pick 24 or your first pick gave you a safer floor |
| Alvin Kamara | RB44, overall rank 133, ADP 119 | Passing-game projection still helps, but the snap trend and depth chart make him a later PPR patch | Target around pick 100 or later, not in this turn |
Brown is playable, but the price is less forgiving
Brown's case is not fake. Cincinnati's depth chart lists him as the RB1, and the Bengals offense creates the right kind of backfield math: spread looks, light boxes, checkdown outlets, and scoring chances attached to an elite passing core. In the broader tracked window, Brown averaged 15.7 carries and 4.3 targets late in the sample. That's not empty volume.
Week 18 against Cleveland is the Brown argument in one box score shape. He had 13 carries and 6 targets while Cincinnati produced 142 rushing yards, and he turned that mixed workload into a strong fantasy day. The important part isn't only the points. It's that he can matter without Cincinnati becoming a run-first offense. He can live on red-zone work, outlets, and defenses that can't load up against the backfield.
The problem is the entry point. On the publish-day standard board, Brown is RB14 with an ADP of 18, while FFN's internal rank sits lower and the value label flags the cost. His projection still deserves respect: 242 rushing attempts and 68 targets is a real workload. But that projection is exactly why the pick is dangerous. At 18, you're paying for the role to stay solved in an offense that can score perfectly well without forcing 20 touches to its back.
So make Brown a fall rule, not a fade. If he reaches the back half of the second round, he fits builds that already have an anchor or need a usable RB with weekly touchdown access. If he is your first running back in the middle of the second, the pick asks for too much precision: the Bengals need to stay pass-friendly, Brown needs to hold the goal-line work, and the target share can't leak enough to turn him into a touchdown-dependent RB2. That's a lot to demand before the third round starts.
Kamara is a later PPR patch
Kamara is the name most likely to make a drafter feel safer than the role actually is. The projection still sees the receiving value: 75 catches and 99 targets on the publish-day profile. In full PPR, that kind of usage can still cover bye weeks, smooth out bad touchdown luck, and give a roster a flex option when the Saints are chasing points.
But the old Kamara label is doing more work than the current setup. New Orleans now lists Travis Etienne ahead of him on the RB depth chart, with Kamara second and younger backs behind them. The role data is also warning us not to treat the name like a locked-in weekly snap base. In the closing sample, his snap share fell by 20.3 percentage points compared with the prior tracked window, and his latest logged game showed only 11 offensive snaps.
That doesn't make Kamara useless. It changes the job. He shouldn't be asked to solve the pick 18 decision because that pick needs a player who can anchor a weekly backfield plan. Kamara is a later PPR solution for rosters that waited at running back, need pass-catching cover, and can live with the Saints offense being uneven. New Orleans finished last season with negative passing EPA and negative rushing EPA averages, so every touch has to work harder than it would in Cincinnati or Tampa Bay.
The news context also requires restraint. Today's digest flagged a discovery-only Kamara uncertainty note and specifically said no move has happened. Treat that as a reason to keep the price down, not a reason to write him off. If he opens camp with clear passing-down work and the depth chart settles in his favor, the pick 100 line may be too conservative. Until then, the better use is simple: PPR patch, not early-round answer.
What would change the call
For Irving, the key camp signal is passing-down trust. If he takes the first two series, stays on the field when Tampa Bay has to throw, and still gets the short-area targets, he belongs in that post-anchor RB pocket. Failure case: Gainwell owns the hurry-up work or Tucker starts taking goal-line snaps, turning Irving into a thinner rush-volume bet instead of a second-round target.
For Brown, the question is not whether he is good. He is. It is whether Cincinnati keeps giving him the kind of inside-the-10 and outlet work that makes a pass-first offense good for fantasy backs. If those touches are visible in camp and his ADP cools into the back half of round two, he becomes a much easier click. If the price stays at 18, the bet is already charging for the best version.
For Kamara, role clarity decides the line. If he is second on the depth chart but still owns the two-minute and hurry-up work, he can beat a pick near 119 in PPR. If the snaps stay in the 30 to 45 percent range, the receptions won't be enough to carry him through the Saints' weaker offensive environment.
The better answer is the back whose role can still grow, not the back whose price already assumes the role held. That is Irving in this fork. Take him after the early anchors, let Brown come to you only if the board blinks, and keep Kamara for the later PPR build where one receiving spike week can actually help instead of disappoint.
Go deeper on Bucky Irving.
Compare plans with FFN rankings, projections, and player context in one workflow.