Montgomery (coach's decision) is inactive for Sunday's game against the Steelers, Jamison Hensley of ESPN.com reports.
One day after acquiring Montgomery from the Packers on Tuesday, coach John Harbaugh suggested the running back could have a role on offense right away for the Ravens in Week 9. Though Montgomery practiced with his new team from Wednesday through Friday, the Ravens decided he could benefit from more time to get familiar with the playbook. Though Gus Edwards will dress as the No. 3 running back Sunday, it would be surprising if Montgomery didn't displace him for those duties following the Ravens' Week 10 bye. Montgomery, an accomplished pass catcher who began his career as a receiver, could eventually unseat Javorius Allen for the top change-of-pace role behind starter Alex Collins.
Acquired from the Packers on Tuesday in exchange for a 2020 seventh-round pick, the versatile Montgomery is expected to ultimately settle in as the third back on the depth chart behind Alex Collins and Javorius Allen, with the potential to move up in the pecking order if he shines in his initial opportunities with his new team. The Ravens probably won't ask for much from Montgomery this weekend, however, as the 25-year-old's main focus for the next few days will be getting up to speed with the Baltimore playbook. If Montgomery proves to be a quick study and impresses the coaching staff in practices Wednesday through Friday, he could be active ahead of Gus Edwards as the Ravens' No. 3 back once Sunday arrives.
It's been a tough season for Montgomery, who has been usurped by both Aaron Jones and Jamaal Williams in the Packers backfield. The final straw in Green Bay seemingly was his lost fumble on a kickoff return this past Sunday after the Rams took a late 29-27 lead, all but ensuring Aaron Rodgers wouldn't have a comeback attempt. With the move to Baltimore, there doesn't seem to be much room for work, either, behind Alex Collins and Javorius Allen. At the very least, Montgomery has a chance at a fresh start with unrestricted free agency on the horizon this offseason.
Montgomery had two carries for six yards and one reception for two yards in Sunday's loss to the Rams. He also lost a fumble on a kick return late in the game.
Montgomery's role appears to have changed significantly coming out of the Packers' Week 7 bye, as he was on the field for just six plays Sunday after averaging 24 snaps over the Packers' first six games. That could have led him to try and make a play late in the game, when he brought a kick out of the end zone and fumbled at a point where a simple touchback would have given the Packers' offense a chance at a game-winning drive. Head coach Mike McCarthy said afterward Montgomery was instructed not to return the kick, and according to SI's Michael Silver, his teammates were none too pleased with Montgomery's decision to do otherwise. That leaves Montgomery's hold on a roster spot a bit tenuous moving forward, but there is not an obvious replacement for him in the backfield. It seems likely Montgomery will stick around because of that, but based on how things went Sunday, he could be stuck in an insurance role moving forward, with Aaron Jones being the top running back and Jamaal Williams taking most of the snaps Jones does not receive.
Montgomery had four carries for 12 yards and a touchdown and two receptions for 10 yards in Monday's victory over the 49ers.
Montgomery's first touchdown of the season came from two yards out, but he actually caught the ball on the edge on a backwards pass from quarterback Aaron Rodgers, so it was hardly a spot where he was operating as a goal-line back. He continues to work in a three-back rotation with Aaron Jones and Jamaal Williams and all three are splitting the snaps fairly evenly, but given that Montgomery has not led the crew in snaps in any game this season and Jones is averaging 5.9 YPC, he should be considered the third option at the position heading into the Packers' Week 7 bye.
|13||12/2/18||@ ATL||1:00 pm|
|14||12/9/18||@ KC||1:00 pm|
|16||12/22/18||@ LAC||8:20 pm|
|2015||Green Bay Packers||6||3||3||14||4.7||9||0||0||0|
|2016||Green Bay Packers||15||6||77||457||5.9||61||3||5||20|
|2017||Green Bay Packers||8||5||71||273||3.8||37||3||1||13|
|2018||Green Bay Packers||7||0||26||105||4.0||16||1||0||6|
|2015||Green Bay Packers||6||3||15||136||9.1||31||2||1||0||6|
|2016||Green Bay Packers||15||6||44||348||7.9||24||0||1||0||19|
|2017||Green Bay Packers||8||5||23||173||7.5||23||1||3||0||8|
|2018||Green Bay Packers||7||0||15||170||11.3||43||0||2||1||5|
|2015||Green Bay Packers||6||7||218||31.1||46||0||2|
|2016||Green Bay Packers||15||18||366||20.3||40||0||1|
|2017||Green Bay Packers||8||0||0||---||0||0||0|
|2018||Green Bay Packers||7||10||210||21.0||27||0||0|
|2015||Green Bay Packers||6||0||0.0||0||0||0||0||0.0||0||0||0|
|2016||Green Bay Packers||15||1||1.0||0||0||0||0||0.0||0||0||0|
|2017||Green Bay Packers||8||0||0.0||0||0||0||0||0.0||0||0||0|
|2018||Green Bay Packers||7||0||0.0||0||0||0||0||0.0||0||0||0|
|Year||Team||G||Fum||Lost||Fum Forced||Own Rec||Opp Rec||Yds||Tot Rec||TD|
|2015||Green Bay Packers||6||0||0||0||0||0||0||0||0|
|2016||Green Bay Packers||15||2||1||0||0||0||0||0||0|
|2017||Green Bay Packers||8||0||0||0||0||0||0||0||0|
|2018||Green Bay Packers||7||2||1||0||0||0||0||0||0|