How to Write an Email Subject Line Colleagues Open

Your colleague gets somewhere between 60 and 120 emails on a normal workday, and they decide which ones to open by reading a line of six or seven words. If your email subject line says "Quick question" or "Update", it sits in the pile with everything else, and your request waits a day it did not need to wait. This guide shows how to write an email subject line that tells the reader what you need, how urgent it is, and whether they can deal with it in two minutes.

I have spent years reviewing internal email for teams that complained nobody read their messages. The body was rarely the problem. The subject line was.

What a good email subject line does at work

Marketing advice about subject lines is mostly about curiosity: make people want to click. Internal email works the other way. Your colleagues will open your message eventually; the question is whether they open it at the right time and know what to do once they do.

A useful work subject line answers three questions before the email is opened:

What is this about? The project, client or document, named specifically.
What do you need from me? A decision, a review, information, or nothing at all.
By when? A real day or time, not "ASAP".

Compare "Budget" with "Q1 travel budget: approve by Thursday noon". The second one can be sorted, prioritized and even answered from a phone notification. That is the standard to aim for.

A simple formula you can reuse

Most strong internal subject lines fit this pattern:

[Action needed] + [specific topic] + [deadline if any]

Some examples from real teams I have worked with:

Weak subject line	Stronger version
Question	Need your call: vendor A or B for the March event
Update	FYI: Henley account renewal signed, no action needed
Meeting	Moving Tuesday design review to 3pm, reply if that fails
Draft	Review by Friday: two page onboarding draft, sections 2 and 3
Urgent!!	Today by 4pm: sign the printer contract so delivery holds

Notice what the stronger versions avoid. No exclamation marks, no capital letters for emphasis, no vague nouns standing alone. They are longer, typically 40 to 60 characters, and that is fine. Most desktop inboxes show about 60 characters and phones about 35 to 40, so put the most important words first.

Prefixes that save everyone time

Agreeing on a small set of prefixes with your team is one of the cheapest communication fixes there is. It takes one short meeting and pays back every day. Common ones:

ACTION: the reader needs to do something.
DECISION: you need a yes, no, or choice between options.
FYI: information only, no reply expected.
EOM: end of message. The whole content is in the subject line, so the email body is empty. "EOM: Call with Ortega moved to 2pm" saves an open entirely.

Keep the list to four or five. A team with twelve prefixes has simply invented a new language nobody remembers.

Why "short and catchy" is the wrong rule for internal email

Plenty of guides tell you to keep subject lines under five words. That rule comes from sales and newsletter email, where open rates are the goal and long lines get cut off on phones. For a colleague, short usually means vague. "Thoughts?" is short. It is also useless, because the reader has to open it to learn whether it matters.

My counter-rule is this: be as long as needed to make the email skippable when it is not urgent, and impossible to miss when it is. A 55 character subject line that lets someone decide without opening is worth more than a 12 character one that forces an open. The only real limit is that the action and topic should appear in the first 35 characters so they survive a phone screen.

The other overrated rule is "always personalize". Adding the reader's name to an internal subject line ("Maria, quick favor") feels warm the first time and manipulative the fifth. Use the name when the email goes to a group and one person has a specific job; otherwise leave it out.

Fixing subject lines in long threads

Threads drift. An email titled "Website launch plan" becomes, three weeks and 40 replies later, a conversation about who pays for photography. The subject line is now lying to everyone.

When the topic changes, change the subject. Many teams use the pattern "New topic (was: Website launch plan)" for one reply so people can still find the history. After that, drop the old part.

A few rules for threads that I recommend to every team:

One email, one request. If you need a decision and a document review, send two emails with two subject lines.
Update the deadline in the subject when it moves. "Review by Friday" that is now due Monday creates confusion and missed work.
Add "RESOLVED" at the front once the question is answered, so late readers do not reopen it.

If your thread is going nowhere and you need a nudge, the structure in our guide on writing a follow up email after no response pairs well with a sharper subject line.

A two minute check before you hit send

Read only your subject line and ask:

Could someone act on this without opening the email?
Is the deadline a real date or time?
Would it still make sense in a search six months from now?
Does it contain a word the reader would actually search for, like the client or project name?

If the answer to two or more is no, rewrite it. Searchability is underrated. Months later, someone will type "Henley renewal" into their inbox, and a subject line called "Re: Re: Fwd: Hi" will never show up.

A good subject line also sets up the body. Once you know the one action you need, the email itself tends to get shorter and clearer. That is the core idea behind the email that gets answered in one reply, and the opposite pattern is unpacked in the email that gets ignored and why.

Frequently asked questions

How long should an email subject line be for work?

Between 40 and 60 characters works well for most internal email. That is long enough to name the topic, the action and the deadline. Put the key words in the first 35 characters so they still show on a phone.

Should you write URGENT in an email subject line?

Rarely. If everything is marked urgent, nothing is. Write the actual deadline instead, such as "Today by 4pm", which tells the reader exactly how urgent it is without shouting.

Is it rude to send an email with no body?

Not if your team understands it. Adding "EOM" at the end of the subject line signals that the whole message is there. Agree on it as a team first, then it becomes one of the fastest ways to share small updates.