How to end a message so people actually act on it

The last line of a message decides what happens next, so it should carry the ask: who does what, and by when. A sign-off is not an ending.

I have made the opposite case before, or it looks that way. Put the decision up top, where the preview pane catches it. Both hold. The first line is what gets read, the last line is what gets acted on, and a message carrying only one of them leaks somewhere.

Most messages end by running out of energy. The writer makes the case, feels the small awkwardness of asking for something, drops in a soft line to cover it, and sends. The reader reaches the bottom holding nothing.

Put the ask in the last line

End with the thing you want, written so plainly that the reader could act on it without scrolling back up.

Yes, that repeats you. One repeated sentence at the bottom is cheaper than making somebody climb back through your reasoning to work out what you were after.

Here is the test I use. If a person read only my final line, would they know what to do? When the answer is no, the message is ending in the wrong place, and the real ending is usually sitting two paragraphs up, where I first said what I needed.

A name and a real day have to be attached to it. I have made that case for meeting recaps and for follow-ups, and it holds for anything you send. "Can someone take a look" is addressed to nobody, and nobody is unreliable.

Past that, most endings sort themselves out by message type:

• A quick question ends with the question.
• A long update ends with the single decision you need.
• Information that needs nothing back ends when the information does.
• In chat, stop when the sentence stops, because the channel is already carrying the tone for you.

Sign-offs are an email habit that followed us into Slack, where they sit oddly. A one-line question wrapped in "hope the week is treating you well" and "thanks so much, really appreciate it" reads like a far larger favour than it is, and a wall of text gets sized up before it gets read.

Cut the line that asks for nothing

"Let me know if you have any questions" asks for nothing, so it tends to get nothing.

It sounds generous. What it does is hand the reader a small job: work out what you left out, then find the words for it. Most people will not take that job. They decide it is probably fine, or park it until later, which is the same as never.

Replace it with the one question you really have. "Does Tuesday work?" can be answered in a single word, and a single word is enough to unblock you.

The closers I delete on sight, and what goes in instead:

• "Let me know if you have any questions" becomes the actual question I have.
• "Thoughts?" becomes the one thing I want an opinion on.
• "Whenever you get a chance" becomes a day.
• "Happy to discuss further" becomes a time, or nothing at all.

While building Unvent I ran months of my own drafts through the tones, and the line I kept watching the Direct rewrite flatten was the last one. That is where my padding collects. I never soften the middle of a message. I soften the ask, because the ask is the part where somebody can say no.

Not every warm line is padding. "Thanks in advance" is fine by me, whatever the style guides say about presumption. It is three words and it is friendly. The trouble starts when the pleasant line replaces the ask instead of following it.

Writing upward, pick one and say so

When you are writing to someone senior, the last line should name the option you would take.

Laying out three choices and asking your manager to decide looks respectful. Mostly it moves the thinking upward while keeping your own hands clean, and the people who do it most are usually the ones with the clearest view of the answer.

Give them the easy job instead. Overruling a recommendation takes one sentence. Forming your opinion for you takes an afternoon they do not have, and it produces a worse opinion, because they are further from the thing than you are.

This is the part people argue with, and the worry behind it is always the same: what if I recommend the wrong one. Then you get corrected in writing by someone senior, which is the cheapest training on offer anywhere.

One kind of menu is worth handing over. When the question is which of your commitments gets dropped, only your manager can price that, and asking them to pick is the honest move rather than the lazy one. The line is whether you are closer to the answer than they are. On a tradeoff between their own priorities you are not. On the thing you have had your hands in all week, you are.

Write the last line first

If you cannot write the ending, you do not yet know why you are sending the message.

Write it first, then. One sentence: who does what by when. Build the context above it afterwards, and cut anything the reader would not need in order to say yes.

The button on the Unvent landing page says "Add to Chrome. It's free." I wrote that line before the paragraph that sits above it, which was the first time I had done it in that order on purpose. The paragraph then lost most of itself. Every sentence I had put there to warm somebody up was aimed at a reader who had already decided, and the ones that survived were the ones answering "what happens when I click this".

Writing towards an ending you already know is a different job from writing until you run out. The middle stops being a place to think out loud, and a good half of what I would have written turns out to have been for me.

A help request behaves the same way. It gets better the moment you know what its last line is.

When the ending will not come

A message whose last line will not come is usually a message you did not need to send.

You write the whole thing, the reasoning is fair, and then nothing will sit at the bottom of it. The honest read is that you did not want anything. You wanted to be seen handling it, or you wanted the discomfort out of your own head and into somebody else's inbox. Neither urge survives being written down as an ask.

The tell is the ending that keeps coming out as "anyway, just wanted to flag it". Flag it to whom, and for what. When a long and carefully reasoned message has nothing to put underneath it, the true ending is usually the one you did not want to type: I am annoyed and I would like you to know. That is worth saying out loud to somebody, or worth letting go of. It is not a message.

This is different from the draft you cannot bring yourself to send. That one has a real ask in it and fear on top. This one has no ask under the politeness at all, and it is better unsent than politely finished.