Write it for a stressed reader
Short numbered steps, exact commands and where the credentials live. Nobody reads prose while the site is down.
Decide the numbers in advance
How much data can you afford to lose, and how long can you be down? Those two answers determine backup frequency and architecture, and they are business decisions rather than technical ones.
Rehearse once a year
Restore into a scratch environment and time it. The rehearsal always finds something: an expired key, a missing dependency, a backup nobody had validated.
