The reader you're actually writing for
Most guidance on a letter of instruction quietly assumes a calm reader. Someone at a clean desk, coffee in hand, working methodically through your accounts and passwords like a project manager onboarding to a new tool.
That person does not exist.
The person who opens your instructions will have learned, hours or days earlier, that you are gone. They will be making funeral arrangements, fielding calls, and trying to remember whether they've eaten. And somewhere in that fog, they will be expected to keep your business — your servers, your customers, your incoming payments — from quietly falling apart.
If you write for the calm reader, you are writing for the wrong person. The single most useful thing you can do for a solo business is to write your handoff for someone whose mind is not working the way it normally does.
What grief actually does to the brain
This isn't a metaphor. Acute grief measurably changes cognition. The psychologist Mary-Frances O'Connor, who studies the neuroscience of loss, describes how the bereaved brain struggles with attention, working memory, and the kind of forward planning that feels effortless on an ordinary Tuesday. People in early grief routinely report that they can't concentrate, lose their train of thought mid-sentence, and forget conversations they had an hour ago. The everyday term is "grief brain," and it points at something real: the prefrontal regions that handle planning and judgment are taxed by the emotional load.
Stress compounds it. The relationship between arousal and performance — long described in psychology as the Yerkes–Dodson curve — means that beyond a certain point, more stress makes complex tasks harder, not easier. Simple, well-rehearsed actions survive high stress. Novel, multi-step reasoning does not.
So the cruel irony is this: the moment your business most needs clear-headed decisions is the exact moment the person in charge is least equipped to make them. Any handoff that depends on your successor figuring things out, weighing options, or improvising is a handoff built to fail.
Recognition is easy. Recall is hard.
There's a well-established distinction in memory research between recall — producing an answer from nothing — and recognition — confirming an answer when you see it. Recognition is dramatically easier and more robust under stress. It's why multiple-choice questions are easier than fill-in-the-blank, and why you can recognize a face you couldn't have described.
Good instructions lean entirely on recognition. Instead of "the hosting is with our usual provider," you write the provider's name, the login URL, the exact account email, and where the password lives. You are not asking your reader to remember or deduce anything. You are asking them to match: here is the screen you'll see, here is the button you'll click, here is what it should say when it worked.
Cognitive load theory, developed by the educational psychologist John Sweller, makes the same point from another direction: working memory is small and easily overwhelmed, so well-designed instruction strips away everything the learner doesn't strictly need. Every "you'll probably want to check whether..." you add is a coin spent from a nearly empty account.
Don't leave decisions. Leave decisions already made.
The most common failure in a letter of instruction is handing over choices instead of actions.
"Decide whether to keep the service running or wind it down." "Figure out which customers need refunds." "Talk to the accountant about the LLC." Each of these is a decision, and decisions are precisely what a grieving brain cannot reliably make. Decision fatigue is real even on a good day; under acute loss, the capacity to weigh trade-offs collapses.
So make the decisions now, while your mind is whole, and leave behind only the execution. Not "decide whether to keep the app running" but "keep the app running for 90 days, then email these customers using the draft below, then cancel these three subscriptions in this order." Not "handle the finances" but "the money lands in this account; here is who can legally access it and the document that gives them that right."
A useful test: read each line and ask, could a competent, exhausted stranger do this without phoning a friend? If the answer requires judgment only you possess, you haven't finished writing that line.
What belongs in the letter
The legal will handles ownership. The letter of instruction handles operation — the practical, often mundane knowledge that never makes it into legal documents but without which nothing can be done. At minimum, written so it can be recognized rather than recalled:
The first hour. What to do immediately, in order. Who to notify. What is time-sensitive — a domain renewal, a payment that will bounce, a certificate that expires. Put the things with deadlines at the very top, because attention is the scarcest resource your reader has.
The keys. Where the password manager is and how to open it. How to get past two-factor on the critical accounts. Where the recovery codes are. This is the chokepoint that strands most handoffs; everything else is academic if no one can log in.
The map. A plain-language list of every system that matters and what it does — hosting, domains, payment processor, email, code, customer data — in the language a smart non-expert understands, not your internal shorthand.
The money. Where revenue arrives, what it pays for, and who has the legal authority to touch it. Recurring charges that will keep hitting your card. The accountant's name and number.
The people. Customers who depend on you. A contractor who knows the codebase. Anyone owed a heads-up. Where appropriate, drafts of what to say to them, so your reader sends rather than composes.
Write it the way you'd talk to a friend across the table. Full sentences, no jargon, no assumed context. The warmth isn't decoration — a frightened reader reads a human voice more easily than a technical spec.
The letter that goes stale
The quiet enemy of every instruction document is time. You wrote it last year; since then you've changed your password manager, moved hosting, added a payment processor, and dropped a product line. The letter that was accurate in March is actively misleading by November — and misleading instructions are worse than none, because they send an exhausted reader confidently in the wrong direction.
This is the part willpower never solves. A document that lives in a drawer, or a Google Doc you mean to update, drifts out of sync the moment your real life moves on. The instructions have to live where your accounts and keys already live, so that updating the system updates the letter.
That coupling is the whole idea behind Heirloom. It keeps the vault, the beneficiaries, and the handoff instructions in one place, so the operational letter isn't a separate chore you forget — it's a byproduct of keeping your own records current, ready to reach the right person, written for the reader who'll actually open it.
You can't spare the people you leave behind their grief. But you can make sure that grief is the only hard thing they're carrying — that the business, at least, is a checklist and not a mystery. If that's the version of yourself you'd want to leave behind, you can start at heirloom.lumenlabs.works.