The planned vacation request is a message you get to polish. This is the other one. Your dad is in the hospital, or the school just called, or you woke up and knew, the way you sometimes just know, that you cannot do this today. At a big company there's a procedure for this moment. At a small one there's you, a phone, and a boss who is a specific human being whose Tuesday you're about to change.
The wrongness people default to here comes in two flavors, and they're opposites.
The first is the over-explainer. Because there's no formal sick day system, no category to file this under, the message tries to build its own justification: three paragraphs of medical detail, the timeline of the emergency, an apology per line, evidence that this is real and you're not faking. It comes from a decent place, and it does two bad things. It hands your boss information they didn't need and now can't unknow, your health specifics are yours, and it frames the whole event as a trial where you're the defendant. You are not on trial. Something happened. Employees are humans and humans have Tuesdays like this.
The second flavor is the vanisher, the person so uncomfortable with the ask that they send "not coming in today" at 6:12am and go dark. Technically informative. But at a small company your absence isn't an abstract headcount change, it's a specific pile of things that now sit somewhere, and a message with no handles on it forces your boss to guess at all of them. The vanisher isn't rude, usually. Just overwhelmed. The result reads rude anyway.
The working message is four sentences and follows one rule: name the category, not the contents.
Morning Dave. I have a family emergency and won't be in today, possibly tomorrow too, I'll know more by tonight. The Hendricks proposal is done and in the shared folder; the only thing time sensitive is the 2pm vendor call, which Priya has context on if it can't move. I'll check messages this evening and update you.
That's the whole architecture. The category ("family emergency," "a health issue," "a personal matter I need to deal with") gives your boss what they need for planning without opening your life for inspection. You do not owe symptoms, diagnoses, or the nature of the crisis, and a boss who demands them is telling you something about the company. The time horizon ("today, maybe tomorrow, update tonight") is the piece people forget and the one small company owners need most, because they're not staffing a department, they're personally rearranging a day. The handoff line covers the one or two things that break without you, which at a small company you know better than anyone. And the update promise closes it so nobody has to chase you.
Two harder cases inside this.
The mental health day, the one where nothing happened except that you're at the end of something and need a day before you break. You're allowed. Do not manufacture a stomach bug; a fake illness is a small lie you'll maintain forever, and "I'm sick" is anyway true in every way that matters. "I'm not well today and won't be in. Everything's covered as of last night; I'll be reachable for anything urgent." Sick is sick. The category system protects this day exactly as well as it protects the flu, which is the point of using categories.
And the multi day crisis, where you genuinely don't know when you're back. Don't promise dates you'll have to walk back. Give rhythm instead of an endpoint: "I'll update you every morning by 9 so you can plan the day." An owner can work with a rhythm. What breaks trust isn't a long absence, it's silence with no next update in sight.
One more thing, for the version of you reading this in advance rather than mid-crisis: the emergency message is a hundred times easier at companies where you've already normalized the planned kind. If asking for a Tuesday in October feels like a trial, asking at 6am from a hospital hallway will feel impossible. Build the normal now. The crisis message will inherit it.