Every Cam Ward 3rd down throw from Sunday. - Protection...inconsistent - Intermediate/deep throws arguably worst of his career - Playcalling wasn't particularly helpful Some thoughts in the thread below of how there's blame to go around. 1/x

First third down. Scheme problem here. I don't know if this is poorly designed, or poorly executed. When a blitzer comes free there's typically a built in "hot". Cam looks for Robinson, but the spacing with Helm eliminates the read. No answer to the blitz. 2/x

Next third down. The result is positive, but the process is negative. Play design creates an open receiver (Robinson) on the quick out. Cam just doesn't cut it loose. 3/x

This play felt like them giving up on chasing the first down, and just hoping to improve field position for the field goal. Cam makes the only throw available, and executes the play as intended. 4/x

Again - free blitzer comes. And, again no built in answer. Not sure where the protection blame falls here, but Pollard needs to find the free rusher. Still, even if he does, this is so slow developing with awful spacing, and guys aren't running open. 5/x

Correct read on this one. Poor throw, though admittedly a difficult one. 6/x

Likely an alert throw here. Cam sees single coverage and tests it. 1. I don't love this decision given the situation, and there's still a shaded safety. That's a tight window. 2. Cam put multiple deep sideline throws out of bounds. Have to give your WR a shot. 7/x

I thought this was a good read by Cam, and these types of plays suit him. He feels space well. This angle makes it looks like a fastball, but this should have been caught by Spears. 8/x

Mixed bag on this one. You'd like to see Cam cycle and find Ridley settling in the middle of the field. Protection is good here. That said, hard to fault him playing point guard and finding the open man. 9/x

Don't love the play call. Poor protection. There's no good answer here for Cam. Routes are too slow developing. The seam looks semi open, but that receiver isn't looking for the ball. 10/x

Much like the play from earlier. Intention here is just to pick up a few yards. Not to get the first down. Executed as designed. 11/x

This one is definitely bothersome. The pressure eliminates the combination read to the field (Tate does come open). But, when he scrambles, Ridley is open and behind the corner. Cam cuts this loose 10/10 times last year, yet doesn't here. 12/x

Too little too late, but one of the best throws of the day for Cam. Tight window. Away from the safety. 13/x

All in all - plenty of blame to go around. Separate of these plays, I felt like when Cam was at his best the team was spread out and playing with pace. Splits somewhat agree with this. (h/t @SumerSports) 14/x

Blame to go around. I actually expected Cam to look worse, but there were some bright spots. Same goes for the OL. Not great, but felt much worse during the game. If I had one take away, it would be that Cam seems most comfortable with the quick game. Start there. 15/15

They’re not really asking him to make any difficult throws, even when they’re playing from behind, they don’t really trust him.

On the bright side, there were nine QBs rated worse. 🤣

@JustinM_NFL The playcalling wrongly assumed he could make those plays.

Some of the crossers were awful. Just running into each others coverage and no way to throw to either crosser. Weird.

Honestly looking at this feed objectively, the WR’s weren’t open and the scheme didn’t particularly help all while having free rushers in his face

@MikeHerndonSk1 That 2nd to last one where he’s staring at Ridley who’s wide open deep down the left is very concerning. I don’t understand why he didn’t throw that ball. College Cam is ripping that without hesitation

😂

Dropping backwards in the pocket is infuriating