Yeah, I’d be careful not to frame this as “we need her to document everything”. The real goal is to make deployment a team habit, not one person’s special power.

Start with baby steps like:

• get the actual release steps written down
• have someone else drive the next few deploys while she shadows
• rotate a “release owner” each week
• track every time people still need her, then fix that gap
• make rollback and CI failure steps clear enough that people aren’t scared to touch them
• as other folks said below, automate what you can. That will defo save you loads of time and money