Subject lines people actually open at work

A subject line at work has one job: tell the reader what the message needs from them before they open it. Name the topic, name the action, and add the deadline if one exists. Everything else is decoration.

This sounds obvious. Then you open your own sent folder and find "Quick question", "Following up", and "Hello" doing the work of labels on a filing cabinet.

A label, not a headline

Work subject lines are labels, and labels fail when they try to be headlines. A headline exists to create curiosity. A label exists to make curiosity unnecessary.

Curiosity gaps work in marketing because the reader owes the sender nothing, so attention has to be baited. Your coworker already owes you a read. Baiting a reader you already have does not create interest. It spends patience.

Clever subject lines at work are a tax on people who were going to open your mail anyway. I stopped writing them entirely, including for good news.

Put the action in the line

The subject should classify the message: what kind of response it wants, and by when. The colon pattern does this best.

• Approve: vendor contract, need a yes by Thursday
• Decision needed: keep or fold the beta list
• FYI only: postmortem notes, no action
• Question: who owns the staging keys?

It is ugly. Use it anyway. The reader is triaging a stack of messages between two meetings, and the ones that classify themselves get handled first. The elegant unlabeled message gets opened last, read halfway, and marked unread for a better hour that never comes.

"Urgent" is not an action. If the deadline is in the line, the urgency is already visible. If it is not, "urgent" is just volume.

Name the owner when you write to a group

A message to five people with a subject like "Feedback needed" is a message to nobody. Shared responsibility in a subject line rounds down to zero, because each reader can reasonably decide the other four have it covered.

Put the owner in the line: "Sam: sign-off needed on the venue contract". The other four still get the context, and exactly one person feels the tap on the shoulder. If you cannot name an owner, that is not a subject line problem. The message itself does not know who it is for yet, and it is cheaper to work that out before sending than to discover it through a week of silence.

The first sentence finishes the subject

Your subject line and your first sentence get read as one unit, because inboxes and phone notifications print them side by side. Write them as a pair.

The subject names the ask; the first sentence carries the detail that makes it answerable. So do not spend sentence one repeating the subject, and do not spend it warming up. Extend it. "Approve: vendor contract, need a yes by Thursday" followed by "Same terms as last time except the support tier" has done its whole job before the message is even opened.

Long messages have their own failure modes, and I have written about the fix separately. The subject-plus-first-line pair is upstream of all of it: it decides whether anyone gets far enough to skim.

Rename the thread when the topic drifts

When a thread outgrows its subject, change the subject and keep the trail: "Budget owner for the offsite (was: lunch options)". Almost nobody does this, which is part of why it works.

Threads drift. The one that started with lunch logistics is now carrying a budget decision, and its subject line is lying about the contents. Every later search and every forwarded copy misfiles that decision under "lunch options". Renaming costs four seconds, and I would call it the highest-leverage habit in workplace email.

Write for the person searching later

Subject lines are how messages get found again, so put the searchable nouns in: the client's name, the project's real name, the invoice number.

The person searching is often you, months from now, trying to find the thread where the terms got agreed. "The thing we discussed" defeats that search on purpose. "Acme renewal: revised terms" wins it. Write the subject for someone who has forgotten everything about this message except one noun, because that is exactly who will be looking for it.

Real dates age better than relative ones here. "Offsite agenda, 14 June" still means something after three forwards. "Next week's agenda" means nothing by the time anyone searches for it.

Subjects that make the reader do the work

A few standards fail on contact, all for the same reason: the reader must open the message to learn why it exists.

• "Quick question" hides the question, and the question is rarely quick.
• "Hello" puts a greeting where the topic should be.
• "Following up" names neither the thing nor the need.
• The empty subject gets filed by guess, and the guess is "later".

The problem with all four is cost, not manners. Each one moves the work of classification from the person who knows the answer onto the person who does not, and it does that to everyone on the thread at once.

Label the message, then send the message

A subject line is also a test of the message underneath. If you cannot label the email in one line, it is usually two emails, and the failed label just told you where to cut.

My own habit is to type the honest label first and the body second, and to let Unvent handle the register of the body right there in the compose box. The subject never needs a tone. It needs a noun and a date. Save the craft for the sentences underneath; the line at the top should read like it was written by someone with somewhere to be.