Evaluating every interception thrown by Buffalo Bills QB Josh Allen

The dialogue around Buffalo Bills quarterback Josh Allen was exhausting in 2023.  While many ignored the fact that he was once again one of the league's best quarterbacks, finishing first in total yards and total touchdowns, as well as rushing for an NFL-record 15 touchdowns by a quarterback, they were quick to jump on him […]

Add as preferred source on Google
Jamie Germano/Rochester Democrat and Chronicle / USA TODAY NETWORK

The dialogue around Buffalo Bills quarterback Josh Allen was exhausting in 2023. 

While many ignored the fact that he was once again one of the league's best quarterbacks, finishing first in total yards and total touchdowns, as well as rushing for an NFL-record 15 touchdowns by a quarterback, they were quick to jump on him and point to his interception total.

Because why acknowledge that the Bills would be a dead in the water team without their Cyborg in 17 when you can be a pedantic stooge who metaphorically adjusts your monocle while saying "Well actually…" before attempting to explain that Josh Allen is actually not very good? Make it make sense.

In light of the never-ending nonsense surrounding Allen, I went back and watched each one of his 18 interceptions this season to see how many of them were bad decisions, bad throws, or had any real impact on the outcome of the game. To the surprise of no one who watches the Bills, the results paint Allen in a much better light than those who just sit and point at a box score.

Week 1 at New York Jets

Allen had three interceptions in this game, two of which were indefensible.

The first of which was basically an arm punt. It was third-and-eight from Buffalo's own 31. Allen uncorked a missile that was intercepted at the Jets' four yard-line. No harm, no foul.
Bad interception? No

The second pick was worse. It was second-and-eight and the Bills were up 13-6 in Jets territory, flirting with field goal range. Allen throws basically the exact same throw he did on the first interception, and it gets downed for a touchback. 
Bad interception? Yes

The final interception of Week 1 for Allen wasn't as bad as the second, but it was still ugly. Still leading 13-6, Allen had Dalton Kincaid for a first down underneath, but went over the top to Gabe Davis into tight coverage. He should have taken the layup.
Bad interception? Yes

Week 3 at Washington Commanders

The Bills were up 16-0 on Washington at the time of Allen's interception. It came on a bomb to Gabe Davis on third-and-20- the definition of a nothing interception. 
Bad interception? No

Week 5 vs. Jacksonville Jaguars (London)

Buffalo was trailing 11-7 on third-and-15 at their own 41 when Allen went deep for Stefon Diggs when it was picked off at Jacksonville's seven yard-line. The arm punts on third and long are a pattern that we will see again. If the Bills were close to field goal range, this would have been one that I'd be more critical of, but they are in their own territory on third and forever. Allen tried to make something out of nothing and pinned the Jaguars in their own territory- I'm fine with that. 
Bad interception? No

Week 6 vs. New York Giants

This was more a great play by the linebacker than a bad throw by Allen. The Bills were down 6-0 at the Giants' 46 yard-line. Allen had Dawson Knox over the middle breaking downfield. As he threw it, Bobby Okereke got a finger on the ball and caught it off the deflection. Again, it was more of a really nice play by Okereke than a bad decision by Allen. Sometimes you just have to tip your cap and move on. Plus, the Bills would win the game. Hindsight is 20/20, of course, but even so, this wasn't a bad play by Allen.
Bad interception? No

Week 7 at New England Patriots

This came on the Bills' first play from scrimmage, and it was a bad decision by Allen. He tried to fit the ball in to Dawson Knox, and it was read all the way for an easy interception. The Patriots scored on the ensuing drive to go up 10-0 and would end up winning the game. Granted, Allen gave the Bills the lead with under two minutes to play and the loss was not on him, but the early hole certainly didn't help matters.
Bad interception? Yes

Week 8 vs. Tampa Bay Buccaneers

This was the first play of the drive. Allen came off play action running a bootleg to his right, but was met with immediate pressure. He threw the ball and it was deflected at the line of scrimmage before being picked. In terms of classifying this throw, I'd lean that it wasn't a horrible interception. This is another one of those plays where you give credit to the defensive lineman for making a good play. Buffalo ended up winning, but I do understand those who would say just eat the sack there.
Bad interception? 50-50

Week 9 at Cincinnati Bengals

This was one of the uglier interceptions of the year for Allen. Buffalo was down 14-7 and he underthrew a ball 20 yards downfield on the left sideline to set the Bengals up in scoring position. 
Bad interception? Yes

Week 10 vs. Denver Broncos

This is the dictionary definition of "Not the quarterback's fault." Allen hits Gabe Davis directly in both hands over the middle of the field before bouncing right off his hands and getting picked.
Bad interception? No

This is the dictionary definition of "The quarterback's fault." Down 12-8, Allen underthrow Deonte Harty on the sideline and it was easily picked off by Denver.
Bad interception? Yes

Week 11 vs. New York Jets

The interception came on a heave on the final play of the first half- it meant nothing.
Bad interception? No

Week 12 at Philadelphia Eagles

This was a tremendous bait job by James Bradberry. Allen expected him to go deep with Gabe Davis, but he stayed in the flat and broke on the ball to pick it off. It was a great play by Bradberry, but Allen should have recognized it. The Eagles scored on the ensuing drive.
Bad interception? Yes

Week 14 at Kansas City Chiefs

The Bills were up 14-0, and this was an ugly pick. Allen had all day to throw and began running to his right before throwing across his body where the ball was picked off. He could have just thrown the ball away, and the Bills were approaching Chiefs territory. Bad decision by Allen. 
Bad interception? Yes

Week 16 at Los Angeles Chargers

This one was similar to the previous interception. Allen was running to his right and threw the ball downfield to his left, but underthrew Stefon Diggs and the ball was undercut. He should have just scrambled for a few yards here.
Bad interception? Yes

Week 17 vs. New England Patriots

This was a really good play design. Buffalo had the outside receiver run a post, while Dalton Kincaid lined up in the slot and ran a double move downfield. The deep safety made a great read once he saw Kincaid break up the field, and instead of sticking with the receiver, he broke towards Kincaid and met him at the ball for the pick. I can't knock the decision too much- it was a good decision, just a better play by the defense.
Bad interception? No

Week 18 at Miami Dolphins

The first of the two interceptions looks ugly on the surface, but it very clearly was a miscommunication between Allen and Gabe Davis (which isn't a rare occurrence with Gabe Davis). The classification of this depends on the player in which you give more of the blame.
Bad interception? 50-50

The second interception is another nothing interception. The Bills went for it on fourth down, no one was open, and Allen launched the ball to the end zone- basically just a punt. 
Bad interception? No

Out of all 18 of Allen's interceptions, only half of them were very obviously bad decisions that fall completely at the feet of Allen. The others were either arm punts on third and long for fourth down, great plays made by defenders rather than a bad decision, passes that were very catchable where Allen was let down by his receivers, or meaningless heaves at the end of the half.

Don't let box scores determine the narrative on a player. It's lazy, and it makes those who do so look foolish. Especially when discussing a player as special as No. 17.