The Commanders are paying for the same elbow twice, and the second bill is the one that can end their season.
Jayden Daniels starts Sunday against the Giants. Three weeks after dislocating his left elbow in Week 2. That's the news. What hasn't been argued is the price. ESPN reported this week that doctors around the NFL believe it is a matter of when, not if, Daniels injures that left elbow again, and that some of them believe he risks another dislocation. Read the wording. Not might. When.
This is the second dislocation of the same left elbow in 11 months. That number, not the three weeks, is the one Washington should be staring at.
The absence that already happened cost the Commanders three games of their starting quarterback. The cost of an absence is never just the games, though. It's the offense that gets shrunk while the starter watches, the red-zone install only he gets live reps on, the three weeks a staff spends managing a season instead of building one. Now they hand the ball back to a quarterback whose joint has failed twice inside a year of Sundays.
Here's where I land: Washington should have sat him Sunday. I would rather lose one divisional game in October than the quarterback.
The counterargument is real, and I'll state it properly. The Commanders are in a race, the Giants are a division opponent, and the medical staff in the building cleared Daniels after positive news on the elbow during the week. The doctors ESPN quoted anonymously haven't examined the joint. A team that sits a cleared quarterback every time an outsider frowns never plays him at all.
That's the strongest version of the other side. It still loses, because the risk here isn't generic soreness. Two dislocations of the same elbow in 11 months is a joint with a history, and the reported consensus outside the building is that it happens a third time. The asymmetry decides it. A win in Week 5 is one game. The starter is what the next several seasons are built on. Those two aren't close.
If it pops again, the job goes to Washington's backup. And that's the part of this I keep coming back to: the Commanders got three weeks to look hard at the alternative and their answer was to hand the ball straight back to the starter. My read is that tells you what they think of the room. Not that the backup is a disaster. That nobody in it has convinced the building, which is why there was never a real debate here.
Which part of the team gets worse if Daniels goes down mid-game? All of the offense, but it isn't a box-score drop, it's a margin drop. I can't put a number on it and I won't pretend to. What I can tell you is the shape of it: the install is Daniels's, so when the backup takes over in the second quarter the menu gets shorter, the protection gets more conservative, and Washington has to beat a defense that already knows it with fewer answers than it practiced with. That's why those three empty weeks mattered more than the standings showed.
So does this change the season? Plainly, yes, and not in the direction Washington wants. The Commanders are one awkward tackle from the same problem landing in a worse week.
Prediction, specific enough to be wrong: Daniels starts Sunday and finishes the game, and he still misses at least one of Washington's next four starts with a left elbow issue. If that happens, it will not be a three-week absence. A third event on that joint inside a 12-month window costs more time than the second one did, and Washington will spend those weeks learning that the schedule doesn't wait for a quarterback's elbow.
The one thing that would move me: a clear public statement from the doctors who actually examined Daniels, not the anonymous ones ESPN quoted, that his recurrence risk is no higher than any quarterback's. Show me that and I'll concede the start without argument. I don't expect to see it. Which is why I'd have taken the loss Sunday and kept the quarterback.
