Elijah Mitchell’s Kansas City Stint Ends With More Questions Than Carries
Elijah Mitchell is officially a free agent. After clearing waivers on Monday, the veteran running back is now free to sign with any team willing to take a chance on him. But whether there’s another chapter to be written in his NFL career-or if the Kansas City stop was the last page-is anyone’s guess.
What’s not up for debate, though, is how strange his time with the Chiefs turned out to be.
Let’s rewind. When the new league year kicked off, Kansas City wasted no time making moves.
General Manager Brett Veach quickly added two former 49ers to the roster. The first was offensive tackle Jaylon Moore-a logical pickup, considering the team’s ongoing search for stability at the tackle position.
Then came the signing of Mitchell. That one raised eyebrows.
On paper, Mitchell’s one-year deal worth up to $2.5 million wasn’t a blockbuster by any means. But the timing was curious.
Signing a depth running back on the second day of the league year? That’s usually reserved for players expected to contribute, not ones still trying to recapture past form.
Mitchell hadn’t been a significant factor on the field since 2021. Injuries had taken a toll, and his production had dropped off-under 300 rushing yards in each of the last two seasons, and not a single snap played in 2024.
If this was a low-risk flyer, it sure didn’t feel like one. It felt like a move made with intent-like the Chiefs saw something worth investing in early. But that vision never materialized on the field.
Once Mitchell arrived in Kansas City, the enthusiasm seemed to fade. Quickly.
Andy Reid’s staff never gave him a real shot. Mitchell was a healthy scratch in every game but one.
That’s not just disappointing-it’s costly. Many of his contract incentives were tied to simply being active on game day, bonuses that never had a chance to kick in.
Even as the Chiefs’ backfield struggled, Mitchell remained on the sidelines. Isiah Pacheco missed time with injuries.
Brashard Smith didn’t exactly seize the moment either. And yet, Mitchell never got the call.
The Chiefs often went away from the run altogether, and when they didn’t, the results were inconsistent at best.
It’s not just that Mitchell didn’t play-it’s that he never felt like part of the equation.
His release with a couple of games left in the regular season caps off a head-scratching tenure. Now, Mitchell is back on the open market, and you can’t blame him if he’s wondering what exactly went wrong in Kansas City.
Why the early investment if there was never a plan to use him? Where was the disconnect between the front office and the coaching staff?
He’s not the only one likely asking those questions. Players like Josh Uche and Jalen Royals-others who’ve found themselves caught in the strange in-between of roster decisions and actual playing time-might be watching this unfold with more than a little interest.
For Mitchell, the hope is that another opportunity comes along. He’s still just 26, with flashes of potential that once made him a key piece in San Francisco. But wherever he goes next, it’s clear he’ll be looking for more than just a contract-he’ll be looking for clarity, consistency, and a chance to actually contribute.
Because in Kansas City, he never got that chance.