Commanders Fans Have Every Right To Question David Blough After That Collapse

The Commanders' overtime defeat spotlighted rookie offensive coordinator David Blough's critical missteps and raised questions about his readiness for high-pressure situations.

The Commanders’ overtime mess against the Giants was ugly enough on the surface. But the loudest criticism landed on Dan Quinn and Jayden Daniels, while one of the biggest culprits stayed in the background: offensive coordinator David Blough.

Washington took a gamble by elevating Blough to offensive coordinator this offseason. He’s a rookie play-caller and has been viewed as a fast-rising coach with the kind of upside that could one day land him a top job. After what happened in Week 5, that future looks a lot less certain.

Quinn is the head coach, and Daniels is the quarterback who had to recognize the moment for what it was. But Blough is the one who had the primary communication responsibility on the field, and that mattered when the Commanders still had 55 seconds left and a chance to finish the job.

They took their time, but eventually a play was sent in. There was pre-snap motion, a hard count meant to sort out the coverage, and, according to Quinn, the first read was third-year tight end Ben Sinnott on an outside throw.

What came next was a clinic in how not to manage the clock.

Routes went out out, receivers and tight ends drifted downfield, and the offensive line was left without much to do. Daniels should have thrown it away once nothing unfolded the way it was supposed to.

A spike or a simple throwaway was the clear answer. Instead, the Commanders burned precious time and came away with nothing.

All Blough had to do was keep it simple.

Instead, he got too cute, and Washington paid for it. A more disciplined approach would have set up first-year kicker Drew Stevens for a 42-yard field goal at home to win the game. That wasn’t automatic, but it was well within range for someone with his leg strength.

He never got the chance.

Blough did not speak to reporters after the game, and he’ll have the right words when he faces the media on Friday before Monday Night Football against the San Francisco 49ers. But this was a major lapse in judgment, one he’d surely like back in a hurry.

The Commanders clearly believed in Blough when they made him the choice this offseason, and they still do. Quinn didn’t want to lose him when the Detroit Lions came calling, which says plenty about how Washington views him. But if he’s going to justify that faith, he has to handle moments like this much better.

And yes, plenty of blame belongs to others too.

Quinn isn’t calling plays, so it falls on him to read the situation and make sure everyone understands the plan. Daniels had all the time in the world to process the scoreboard and make a smarter decision. Blough, though, needed to stop chasing extra yards and instead give the Commanders a chance to win.

Instead, it was malpractice from everyone involved. Blough may sit in the shadows compared to Quinn, but that doesn’t erase his part in a fiasco that left Washington face down in the dirt.

Everyone can say it’s on them. In this case, though, words don’t carry much weight.

In Other News...

Commanders Report Card Reveals What Really Cost Them A Win In New York

A detailed look at Washingtons Week 5 trip to New York makes one thing clear: this was not just a game that slipped away, it was a game the Commanders let get messy in the margins. The report card found bright spots in the rushing offense and along the defensive line, while also showing how the passing game and protection left too much work for the rest of the team to cover.

Special teams and coaching also came under the microscope, because the tie with the Giants felt less like a clean finish and more like a lesson in game management. Washington had built enough of a cushion to control the afternoon, but the final verdict from the breakdown is that the Commanders issues in pass protection, secondary play and late-game decision-making added up at exactly the wrong time. [Read more 🡒]

Commanders Fans Are Still Questioning One Backfield Decision In The Tie

Jacory "Bill" Croskey-Merritt was one of the few bright spots in Washingtons 27-27 tie with the Giants, and the rookies work on the ground stood out even in a game that left plenty to sort through. He led the Commanders in rushing yardage and looked like the kind of back who could help steady an offense that needed a dependable spark as the afternoon wore on.

So it caught the eye when the backfield usage shifted late, with the Commanders leaning away from the runner who had been most effective. Rachaad White handled the rest of the carries while Croskey-Merritt stayed on the sideline, and the decision only added to the questions surrounding a game that already felt strange in the way it unfolded. [Read more 🡒]

Commanders Let A Winnable Game Slip Away With Brutal Late Mistake

For much of Sundays Week 5 meeting, Washington looked positioned to leave with a win after building a two-touchdown cushion in the fourth quarter. Instead, the Commanders wound up in a 27-27 tie with the Giants, a result that felt especially painful after New Yorks late surge and Jameis Winstons 326-yard, three-touchdown day kept the pressure on until the final whistle.

Washington still had a path to finish the job in the closing seconds, but a costly clock-management mistake erased the chance to line up a potential game-winning field goal. The Commanders will have to live with the missed opportunity after letting a winnable game slip away in a finish that left plenty of frustration on their sideline. [Read more 🡒]