Coaching & Scheme
Carolina Told Us It Would Be a Committee. Week 1 Told Us Otherwise.
Dave Canales talked about a Carolina committee, but Chuba Hubbard dominated the meaningful Week 1 work. Canales’ coaching history suggests fantasy managers should take that usage seriously.
Carolina spent the offseason giving fantasy managers reasons to worry about Chuba Hubbard's workload.
Then Week 1 happened.
Hubbard finished with 10 carries, three receptions, 87 total yards and two touchdowns.
More importantly, the usage underneath the fantasy points looked like a feature back.
That's where Dave Canales' history becomes important.
The First-Half Split Wasn't Close
Jonathon Brooks was healthy enough to play in Week 1.
That did not create an even backfield.
Hubbard led Brooks 25-6 in first-half snaps and controlled the valuable situations before the game got away from Carolina.
For the full game, Hubbard played 69% of the offensive snaps.
Through three quarters, before Carolina began giving away late work, Hubbard had played 77% of the snaps, run a route on 63% of the team's pass plays and handled 71% of the carries.
Those are feature-back numbers.
The final box score makes the backfield look closer than it actually was when the game was competitive.
Dave Canales Has Done This Before
This is the part that makes the Week 1 usage more believable.
Canales has repeatedly leaned on one primary running back.
In Tampa Bay in 2023, Rachaad White handled a massive workload and finished as a top fantasy back.
In Carolina in 2024, Hubbard became the feature back and finished as RB13.
Even last season, when the Panthers eventually shifted toward Rico Dowdle, the important lesson was the same: Canales was willing to ride the back he trusted.
The name changed.
The structure did not.
That's why the preseason “committee” language should not outweigh what Carolina actually did in a real game.
Brooks Still Matters
This does not mean Jonathon Brooks is irrelevant.
Brooks turned five touches into 62 total yards in Week 1.
That efficiency is going to keep him involved.
If he continues producing explosive plays, Carolina has every reason to increase his workload.
But there is a big difference between “Brooks deserves touches” and “this is a 50-50 committee.”
Week 1 gave us no evidence of the second statement.
Hubbard handled early downs.
He was involved in the passing game.
He was trusted near the goal line.
That's the combination fantasy managers care about.
Why Week 2 Matters
Carolina gets Atlanta next.
The result matters less to me than whether the Panthers repeat the deployment.
If Hubbard again plays around 70% of the snaps and controls the high-value touches, we should stop treating the backfield as an unresolved competition.
One week can lie.
Two weeks of the same role, especially when that role matches the coach's history, becomes much harder to dismiss.
The other thing to watch is Brooks' route participation.
If Carolina wants to expand his role, passing downs are one of the easiest places to see it.
If Hubbard continues dominating those snaps too, his PPR floor becomes significantly stronger.
The Fantasy Decision
Hubbard should be started as a legitimate fantasy RB2.
I would not sell him simply because Brooks looked explosive on limited touches.
If anything, the offseason committee fear may have created a value window that Week 1 began to close.
Brooks remains a strong bench hold because his talent is obvious and his contingent upside would be enormous if Hubbard missed time.
But right now, the backfield belongs to Hubbard.
The FF Draft Boards Take
Coach comments are useful.
Actual usage is better.
Carolina told us to prepare for a committee.
Then Dave Canales used Chuba Hubbard exactly like the feature backs he has trusted in previous offenses.
Hubbard controlled the meaningful snaps, routes, carries and scoring opportunities.
Brooks is talented enough to earn more work.
Until that actually happens, fantasy managers should trust what Carolina showed us on the field rather than what it told us before the season.
