In FFN's Week 1 data, Jalen Coker drew 9 targets and caught 8 passes. That target volume matters because receiving opportunities can remain useful when touchdowns fluctuate. We view Coker as a lineup option when volume is the priority, but his single result establishes a usage watch rather than confirmed multiweek heat.
Players getting hot
Our opening lineup card favors players whose results came with pass attempts, carries, targets, or multiple scoring paths. No current-season week-over-week role trend is available for this group. We need another workload sample before calling any of them persistently hot.
| Usage Watch | Observed Workload | Lineup Move |
|---|---|---|
| Caleb Williams (CHI) | Per the Week 1 box score, Williams had 29 pass attempts and 10 carries. | Start him when we need both passing and rushing paths; pivot if the rushing work contracts. |
| Kenneth Walker (KC) | Per the Week 1 box score, Walker had 23 carries and 6 targets. | Keep him in the lineup while both sources of opportunity remain intact. |
| Jalen Coker (CAR) | Per the Week 1 box score, Coker had 9 targets and 8 receptions. | Use him when target volume matters, but choose another receiver if those opportunities contract at ATL. |
| Isaiah Likely (NYG) | Per the Week 1 box score, Likely had 8 targets and 8 receptions. | Consider him when the alternative's target role is uncertain; move away if his targets fall. |
Caleb Williams reached his opening result through passing and rushing usage. The FFN Week 2 ranking lists Williams as QB17. We can pursue that dual-path ceiling when our alternative depends almost entirely on passing, while recognizing that his opening scoring rate may not repeat.
Kenneth Walker received work as a runner and receiver. He is RB9 in the FFN Week 2 ranking and faces IND. We are keeping Walker in lineups. His carries provide the foundation, while targets offer another route to half-PPR production if the rushing result is less explosive.
For Jalen Coker, the lineup argument at ATL begins with opportunities rather than an established trend. Managers with an established high-volume receiver can wait for confirmation. Rosters short on target access can use Coker, then reassess if the next box score shows a meaningful decline.
Isaiah Likely converted every supplied opening target into a reception. The FFN Week 2 ranking has Likely at TE16. Treat him as a conditional tight end play at LAR, with his next target total determining whether he remains usable over an alternative with a less uncertain role.
Regression/volatility candidates
The bench lever is not automatic for these players. We are looking beyond the bright opening scoreboard and isolating performances that become harder to repeat if touchdowns decline or opportunities narrow.
| Volatility Candidate | Observed Result | Failure Path |
|---|---|---|
| Caleb Williams (CHI) | Per the Week 1 box score, Williams scored 37.3 half-PPR points with 4 total touchdowns. | His result can fall if rushing scores disappear and passing volume does not compensate. |
| Derrick Henry (BAL) | Per the Week 1 box score, Derrick Henry scored 34.8 half-PPR points with 3 rushing touchdowns. | Lower touchdown conversion would expose his limited target involvement. |
| Jalen Coker (CAR) | Per the Week 1 box score, Coker scored 29.8 half-PPR points with 2 receiving touchdowns. | His ceiling contracts if targets fall or fewer receptions become scores. |
| Isaiah Likely (NYG) | Per the Week 1 box score, Likely scored 23.8 half-PPR points with 2 receiving touchdowns. | His result becomes fragile if target volume declines and scoring recedes. |
Caleb Williams remains playable because his carries create an additional route to fantasy production. Our concern is the concentration of scoring, not the absence of usable volume. Choose another quarterback when protecting floor matters more than pursuing Williams's passing and rushing ceiling.
Derrick Henry recorded 24 carries and 1 target in FFN's Week 1 data. That workload keeps him in our lineup against NO even if the opening touchdown total proves unsustainable. The rushing volume remains the central support because his receiving opportunity was small.
Jalen Coker and Isaiah Likely each paired their supplied targets with multiple scores. Neither has current-season multiweek evidence behind that performance. Their targets remain actionable, but we should downgrade either player if the next game removes the volume beneath the touchdown production.
Bold predictions
The goal-line play sheet gives us aggressive calls without requiring a new workload assumption. We are extending specific passing, rushing, carry, or target signals from the opening box score while accepting the risk attached to touchdown forecasts.
| Bold Call | Observed Support | Prediction |
|---|---|---|
| Josh Allen (BUF) | Per the Week 1 box score, Allen had 334 passing yards and 2 rushing touchdowns. | In Week 2, Allen produces 4 total touchdowns vs. DET. |
| Kenneth Walker (KC) | Per the Week 1 box score, Walker had 23 carries and 173 rushing yards. | In Week 2, Walker scores 2 total touchdowns vs. IND. |
| Christian Watson (GB) | Per the Week 1 box score, Watson had 8 targets and 147 receiving yards. | In Week 2, Watson catches 2 touchdowns at NYJ. |
Josh Allen demonstrated that his fantasy scoring can come through his arm and legs. That combination supports our aggressive call. We start Allen confidently unless an availability change removes one of those scoring paths.
Kenneth Walker's prediction leans on touches, while Christian Watson's call depends on targets producing explosive results again. Watson is WR7 in the FFN Week 2 ranking. When choosing between these bold calls, we trust Walker's carry volume more than Watson's target-based touchdown outcome.
Closing weekend posture
At the final lineup screen, check final practice participation and the injury report before games lock because current practice information was not supplied. Watch whether Coker and Likely retain their targets and whether Williams and Walker preserve their multiple usage paths. Our recommendations hold unless availability changes or the next workload loses the opportunities supporting the call.