Handoff Documentation and the Bus Factor
Ask a business who can restore their website if it breaks and you often get one name. That is a bus factor of one: the number of people who can disappear before the operation stops. Backups protect the files. Nothing protects the knowledge except writing it down.
The one page every business should have
A single document, stored where more than one person can reach it, containing:
- Where everything lives: registrar, DNS host, web host, CDN, email provider, analytics, and any connected service, with account owner and login location for each.
- Who has access to each of those, and who to contact for more.
- How to get the site back: where backups are, how to restore one, and how long it takes.
- What breaks regularly and how it was fixed last time.
- Support contacts for the host and any critical vendor, including account numbers.
- The routine: what maintenance happens, how often, and by whom.
Write it as instructions, not notes
The test is whether someone unfamiliar could follow it under pressure. "Backups are in the host panel" is a note. "Log into the host at this URL, go to Backups, choose the most recent, click Restore to Staging, wait about 20 minutes, verify the homepage and the contact form" is an instruction. Specificity is what makes the document worth having.
Keep it current with a trigger, not a schedule
Update it when something changes: a new vendor, a password rotation, a fixed incident, a person joining or leaving. Documentation kept on a quarterly review schedule is usually wrong by the time it matters; documentation updated at the moment of change stays accurate.
Then test it
Hand the document to someone who did not write it and ask them to perform one task from it, such as finding where the domain is registered or locating the most recent backup. Every place they get stuck is a gap. That exercise takes half an hour and converts a single point of failure into an ordinary operational risk.
