For a rookie, Cam Ward’s debut against the Denver Broncos on September 7 couldn’t have gone much better. Delanie Walker praised his leadership, ESPN’s Dan Orlovsky said he was “blown away,” and honestly, we all were. But pump the brakes — because with the protection issues Tennessee is facing, there’s a real chance we don’t see the same Cam Ward we saw in Week 1 against the Los Angeles Rams tonight.

That’s because Tennessee will be without starting right tackle J.C. Latham this week, and Ward’s protection just got a whole lot weaker. Latham told reporters he won’t be playing after aggravating a hip injury against Denver. He tried to tough it out and return, but admitted, “Yeah,” when asked if he’d be sidelined — then added, “It made it worse.”

Let’s put things into perspective. Cam Ward went 12-of-28 for 112 yards — no touchdowns, no picks. But he was sacked six times and coughed up a late fumble on a strip-sack. The box score makes it clear where the real damage came from. It was the protection around him and the pressure he was constantly exposed to.

Those six sacks? They weren’t just bad luck; they were engineered. Denver pressured Ward on half of his dropbacks, one of the highest rates in the league last week. The tape backs it up too: the Broncos weren’t just coming off the edge, they were winning up the middle, collapsing the pocket from every angle.

And now, the same line that already struggled to keep him clean just got weaker. J.C. Latham logged 43 snaps before exiting, leaving Olisaemeka Udoh to step in for 12. The problem? On tape, Udoh was the one beaten on the sack that set up Ward’s costly fourth-quarter fumble. That can’t keep happening.

Tennessee managed just 133 total yards in Week 1 — and nearly matched that with 131 yards in penalties on 13 flags. Those self-inflicted wounds only cranked up the heat on Cam Ward. The blame’s split between rookie growing pains and a shaky offensive line… but without Latham, the scale tilts hard toward chaos.

And a tackle missing out on just one game reshapes everything. Protection calls change, pocket slides shift, and even the run-game timing gets thrown off. For a rookie like Cam Ward, that’s just extra noise when he’s already trying to process RPO reads and hot routes at NFL speed.

But to be fair…things aren’t looking too good over at Los Angeles either.

The Rams have problems of their own

Now flip the script. The Rams have their own issues up front, but they’ve still got Matthew Stafford under center — and he’s locked in. In Week 1, Stafford carved up Houston for 245 yards and a touchdown, guiding the Rams to a 14–9 win. That’s why there’s no doubt he’ll be starting on Sunday.

Yes, the Rams’ injury report read a lot like ‘crisis.’ Kevin Dotson and Steve Avila both left Week 1 with ankle issues, and Rob Havenstein missed a midweek practice with soreness. Three key starters are all missing practice at some point. That’s the “triple hit” we’re talking about.

Kevin Dotson was cleared to play Friday after limited practice, Steve Avila remains doubtful, and Rob Havenstein returned to limited practice work. Dotson might be the only one who will be suiting up. And Sean McVay has made it clear his focus is on keeping Stafford protected while adding any depth help he needs to get the job done.

And protection really is everything when it comes to Stafford. He can still produce MVP numbers when he’s healthy. But keeping him healthy is the biggest challenge Sean McVay will face this season. Need to keep that back upright. That’s the key to the playoffs.