A useful subject line does more than announce that an email exists. It gives your future self a quick clue about what the message concerns and why it mattered. “Update” may make sense while you are writing, but weeks later it could refer to almost anything. A short project or topic label paired with the message’s purpose makes scanning easier. The goal is not to squeeze every detail into the subject: it is to provide a readable signpost, then put the explanation and decisions in the message itself.
The useful bits
- Name the project or topic, then state the message’s purpose.
- Keep details that distinguish the email; move the rest into the body.
- Treat subjects as scanning aids, not guaranteed search or sorting rules.
Build a subject around two clues
Start with the topic a reader is likely to recognize: a project, event, client matter, or recurring process. Add the purpose of this particular message, such as requesting approval, sharing a decision, or confirming a date. Together, those clues answer two quick questions: “Which conversation is this?” and “What is this message about?”
A simple pattern is “Topic — purpose.” It is a writing aid, not a rigid rule. Use the wording your team already recognizes, and put the most identifying words early enough to see while scanning.
Harbor launch — review draft timeline Harbor launch — decision on opening date Quarterly planning — request for budget input
Choose a purpose that says what changed or is needed
Purpose words are most helpful when they describe the action or information in the email. “Review draft,” “confirm date,” and “share decision” set clearer expectations than “update” or “question.” If you need a response, say what kind of response in the subject when you can do so briefly. If the message is only informational, avoid wording that makes it sound like a request.
Be accurate about the body. A subject that says “Approval needed” is misleading if the email is only a preliminary discussion. Likewise, “Final schedule” should not label a draft that may still change. Match the subject to the message’s actual status and ask.
Product guide — approve revised outline Office move — confirm preferred desk date Support handoff — share current status
Keep the line readable, not exhaustive
A subject should help someone decide whether to open a message, not reproduce the whole message. Include the project and the main purpose; leave background, multiple sub-questions, and supporting details in the body. If a subject needs several commas, a chain of parenthetical notes, or multiple requests, it is probably carrying too much.
Use a distinctive detail only when it separates this message from similar ones. For example, a phase name or a meeting date may help; a long list of every attachment and participant usually does not. Prefer familiar terms over internal shorthand that a future reader may not remember.
Too crowded: Atlas — draft v3 — comments from design and sales — approve by Friday — see attached notes Clearer: Atlas — approve draft by Friday
Use a consistent pattern where repetition helps
For an ongoing project, a repeated topic label can make related messages easier for people to scan together. Pick a name people will recognize and use it consistently: “Atlas rollout,” for instance, rather than alternating among “Atlas,” “new system,” and “rollout project.” Then vary the purpose so each subject still tells the messages apart.
Consistency does not mean every email needs the same formula. A routine note may need only a topic and a purpose. A sensitive or unusual message may need more precise wording. Avoid adding tags or labels simply because they look systematic; include them only if recipients understand what they mean.
Atlas rollout — share training dates Atlas rollout — request access review Atlas rollout — confirm launch decision
Make a quick edit before sending
Before sending, imagine seeing the subject alone in a crowded inbox later. Can you identify the topic? Can you tell whether the sender is asking for something, reporting something, or sharing a decision? If not, replace vague wording or add the missing clue. Check that the subject does not promise more certainty or urgency than the message supports.
- Topic or project is named in recognizable terms.
- Purpose is specific and matches the email body.
- Only the most useful distinguishing detail is included.
- The line remains easy to read at a glance.
Check usefulness without assuming search behavior
After sending, you can confirm that your convention is working for human scanning by reviewing a few related messages: do their subjects make the project and purpose clear without opening each one? You can also ask a recipient whether the wording helped them distinguish a request from an update. If it did not, adjust the wording for future messages.
A consistent subject can support scanning, but it cannot guarantee how a mail service will sort, group, index, or return a message in search. Search and display behavior can depend on the service and its settings. Keep important decisions and details in the message body as well, and use search when needed rather than treating a subject convention as a filing guarantee.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction