An empty state is one of the smallest surfaces in a product. A blank screen, an illustration maybe, and a sentence or two. In most apps it is an afterthought, a place to drop a cheerful line and a button. In a sensitive app, the empty state is one of the most emotionally loaded surfaces you have, precisely because there is nothing else on the screen to absorb the meaning. Every word is exposed.

At BlockWill, our empty states sit in places like a vault before any documents are added, a list of messages to loved ones before any are written, a beneficiary view before anything has been released. These are quiet moments that touch mortality directly. The microcopy in them can either steady a person or unsettle them. This is how we try to make it the former.

The empty state is not neutral

The first thing to accept is that a blank screen is never emotionally neutral in a product about death and inheritance. "You have no messages yet" reads very differently in a chat app than it does in a feature for leaving final words to your family. The same structure of sentence carries grief-adjacent weight here that it simply does not carry elsewhere.

So we never reach for the generic empty-state template. We write each one for the specific emotional context it lives in, asking what a person is likely feeling when they land on this particular blank screen, and what they need to hear.

Acknowledge, orient, invite

The pattern we use has three small parts, in order. Acknowledge where the person is, without melodrama. Orient them, so they understand what this space is for. Invite a single clear next step, gently, with no pressure.

For a vault with nothing in it, that is not "Nothing here yet. Add a file!" It is closer to a calm line that names what the vault is for (keeping the documents your family will need safe and reachable), followed by one clear, unhurried way to begin. The difference between those two is the difference between a screen that pokes at someone and one that holds them.

Calm beats clever

Microcopy culture rewards wit. Empty states are a favorite place for jokes and personality. In a sensitive app, that instinct is dangerous. A clever line about emptiness, when the subject is mortality, can land as flippant or even painful.

We choose calm and plain over clever every time. That does not mean cold or robotic. Warmth is welcome. But the warmth comes from clarity and gentleness, not from jokes. The voice we aim for is a steady person speaking quietly, not a brand performing cleverness.

Never pressure, never guilt

A lot of empty-state and onboarding copy works by manufacturing urgency. "Don't leave your family unprotected." "You haven't finished setting up." In a product about death, fear and guilt are especially easy levers to pull and especially wrong to pull. People do not need to be frightened into estate planning. They are already carrying the weight of the topic.

So our microcopy avoids guilt entirely. No countdowns, no warnings designed to provoke anxiety, no implication that the person is failing their family by not having finished. We state what a space is for and offer a calm way forward, and we trust the person to act in their own time.

Give the next step, always

Gentleness does not mean vagueness. A grieving or anxious person on a blank screen needs to know what to do next more than anyone, because they have the least spare energy to figure it out. So every empty state ends with exactly one clear, doable action, described plainly.

One action, not three. Clarity reduces load. When there is a single obvious next step, the empty state stops being a void and becomes a quiet doorway.

Write for the worst reading, not the best

When we review sensitive microcopy, we do not read it in a calm, focused state at our desks. We try to read it as the hardest-hit user would: distracted, grieving, scared, reading too fast. A line that is fine when you are relaxed can sting when you are raw. If a sentence could be misread as flippant, accusatory, or cold by someone in distress, we rewrite it, even if the cheerful reading is perfectly nice.

That habit, reading for the worst case rather than the best, is the single most useful discipline we have for this kind of writing.

Small surface, large responsibility

It would be easy to treat empty states as trivia, the last polish before shipping. In a sensitive product they are the opposite: a small surface carrying large responsibility, because they speak to people in their quietest and sometimes hardest moments with nothing else on the screen to soften the words. Getting them right is not decoration. It is part of the duty of care the whole product exists to honor.

Frequently Asked Questions

What is an empty state?

An empty state is what a screen shows before there is any content in it, such as a vault with no documents or a message list with nothing written. It usually contains a short piece of microcopy and a next step.

Why do empty states matter more in sensitive apps?

Because there is nothing else on the screen to absorb the meaning, so every word is exposed. In a product about death and inheritance, a generic or cheerful empty state can feel jarring or painful, while a calm one can steady the person.

What structure works for sensitive empty-state microcopy?

A three-part pattern: acknowledge where the person is without melodrama, orient them to what the space is for, and invite a single clear next step gently, with no pressure.

Should sensitive microcopy use humor?

Generally no. Wit and jokes, common in microcopy culture, risk landing as flippant when the subject is mortality. Calm, plain, and warm beats clever in these contexts.

Is it okay to use urgency or guilt to drive action?

No. Fear and guilt are easy to invoke in estate planning and wrong to use. Good sensitive microcopy avoids countdowns, warnings, and any implication that the person is failing their family.

How do you test sensitive microcopy?

Read it as the hardest-hit user would: distracted, grieving, reading too fast. If a line could be misread as cold, flippant, or accusatory by someone in distress, rewrite it, even if the calm reading is fine.

Further reading: