Logo

The Steelers made a dreaded “clerical error” when they listed their quarterback depth chart on Monday.

That’s according to head coach Mike Tomlin, who clarified the situation on who will be backing up Mitchell Trubisky for the season opener against the Bengals on Sunday.

Where the depth chart originally listed Mason Rudolph as the backup and rookie Kenny Pickett as third string, it will actually be flip-flopped, with Pickett backing up Trubisky.

“It was a clerical error,” Tomlin told reporters on Tuesday. “That’s how the depth chart was listed at the start of training camp, so the cut and paste component was the cut and paste component. I know you were hoping for a little bit more colorful explanation, but it is what is. That’s what happened.”


  Mike Tomlin cited a “clerical error” in their QB depth chart mixup. Getty Images Mike Tomlin cited a “clerical error” in their QB depth chart mixup. Getty Images

  Rookie QB Kenny Pickett will back up Mitch Trubisky in the Steelers’ opener against the Bengals on Sunday. Getty Images Rookie QB Kenny Pickett will back up Mitch Trubisky in the Steelers’ opener against the Bengals on Sunday. Getty Images

Tomlin had high praise for Pickett’s trajectory.

“Really pleased with the growth and development of Kenny,” the coach said. “I thought the acceleration of his development really took off once we started coming into stadiums. I thought that he grew and grew at a really fast pace once we got into stadiums.”

Tomlin also reserved a compliment for Rudolph, who has apparently handled the depth chart demotion with grace.


  Mason Rudolph is the third string QB despite being listed as the backup on the Steelers’ depth chart Monday. Getty Images Mason Rudolph is the third string QB despite being listed as the backup on the Steelers’ depth chart Monday. Getty Images

“I’ve got so much respect for Mason Rudolph,” Tomlin said. “He didn’t blink. He didn’t pout about reps or what groups he was running in. He just made plays.”

Comments
anonymous profile image
Powered by RoundtableBuilt on infrastructure designed for real-time media. Learn more at RTB.io.© Roundtable 2026. By using this site you agree to the Terms of Use and Privacy Policy