Reset or recover password

Jared in QA locked himself out and needs password recovery now; reset access for his account and send the recovery link to his work email. Verify his identity by confirming last project name and manager approval, then force a password change on next sign-in and document the reset for compliance.

Before I send the reset steps, make the process painless for Jared but secure: put the recovery link up front, explain what identity proof I need him to provide (last deployed branch and manager confirmation), show how to create a strong password, and note how to re-enable any integrations that break after a reset. Flag common pitfalls so Jared doesn't get stuck at 3 a.m.

Jared says he can't reach the recovery email on file because it's his old personal address. I don't know whether he can prove identity to IT, and I worry about social-engineering risks if I accept weak proof. HR is slow. What's the safest fast path to restore his account today so he can run tests without compromising security — manager attestation, video call verification, or temporarily granting a scoped account?

Across teams we keep getting account lockouts where recovery goes to personal addresses people no longer access. That delays work and creates help-desk choke points. Which habit or policy change would most reduce these incidents — enforced recovery email checks at onboarding, quarterly reminders, or forcing corporate email only for recovery — and how do we implement it without overburdening new hires?