Every job I've had eventually turns into the same question: "what happens when I'm not here?"
At Everise, it was training material that had to work for a new hire who'd never met me. At Beauties of the Beasts, it's a volunteer showing up on a Saturday I'm not scheduled, needing to know exactly how to handle a reptile intake without guessing. In caregiving, it's the next person taking over a client's care plan and needing to know what actually works for that person, not just what's in a generic template.
So I write everything down. Not because I don't trust people to figure it out — because "figuring it out" under pressure, with a scared animal or a distressed client in front of you, is a bad time to be improvising.
What good documentation actually does
A SOP that survives contact with reality is short, specific, and written for someone who is stressed and in a hurry. Not exhaustive. Not clever. Just correct, and fast to scan.
I test mine by handing them to someone who's never done the task and watching where they get stuck. If they have to ask me a question the document should have answered, the document is wrong — not the person.
It's not just paperwork
The caregiver assignment tracker I built started as a spreadsheet formula flagging anyone left unassigned past 7 days. That's documentation too, just automated. Same instinct: don't rely on someone remembering to check. Build the thing that checks for you.
If you're building a team or a system and it only works because you're personally holding it together, it's not actually built yet.