How do I write an email subject line that tells people what I need?
Quick answer
Write the subject line around the next action you need from the recipient: name the topic, say what they should do, and include a deadline only if there is a genuine one. For example, “Please approve the draft proposal by Thursday” is clearer than “Proposal” or “Urgent.” Keep the wording specific and concise; put background, options, and context in the email itself.
The question, the details, the next step.
I often write subjects like “Quick question” or “Project update,” but then people may not know what I need. What should I include?
Start with the recipient’s next action, then identify the topic. A useful pattern is: “Please [action] [specific item] [by date, if needed].” That lets someone scanning their inbox understand both what the message concerns and whether they need to do something.
For example:
- “Please review the draft agenda”
- “Choose a launch date for the new brochure”
- “Confirm the room setup for Friday’s workshop”
If you do not need the recipient to act, say what the email is about instead: “Update: workshop room is confirmed.” “Quick” or “urgent” does not explain the request, so use those words only if they genuinely help convey timing—and be clear about the actual deadline.
How specific should I be? I don’t want the subject to become a whole sentence or repeat the entire email.
Include enough detail to distinguish this request from other work, but save the explanation for the body. A project name, document, decision, or event can make a short action much clearer.
Compare:
- “Feedback needed” — the reader cannot tell what to review.
- “Please review the spring event invitation” — the item and action are clear.
- “Please review the spring event invitation and rewrite the introduction, check all dates, suggest three alternate headlines, and send your edits…” — too much for a subject; put those details in the email.
A practical test: could the recipient identify the task from the subject alone, without guessing which file or project you mean? If not, add the missing identifier. You do not need to put every instruction, reason, or piece of background there.
What if I need a reply by a certain time? And what if I’m asking, not assigning a task?
Add a date or time when it is real and relevant to the recipient’s decision. Be concrete rather than relying on “ASAP” or “urgent.” For example, “Please confirm the catering count by Tuesday, 3 p.m.” gives a clear request and deadline. If the deadline is flexible, do not make it sound fixed; you can explain the preferred timing in the message instead.
For a question, make the topic and the kind of answer easy to spot:
- “Could you recommend a printer for the event flyers?”
- “Which of these two meeting times works for you?”
- “Please confirm whether the revised title is approved.”
A question mark can help, but it is not essential. The important part is making clear whether you need a recommendation, a choice, confirmation, review, or another specific response.
Could you show me how to improve a vague subject, and give me a quick check I can use before sending?
Suppose you are emailing a colleague about a draft schedule and need their feedback before you share it with a group. “Schedule” names the topic but not the request. “Thoughts?” signals a question but leaves the topic unclear. A more useful subject is:
“Please review the draft schedule by Wednesday”
That wording identifies the action, the item, and the genuine deadline. If Wednesday is only a preference, use “Please review the draft schedule” and explain the timing in the email body. If you only want to inform the colleague that the schedule is ready, use “Draft schedule is ready for the team.”
Before sending, check that the subject names the topic, makes the needed action—or lack of action—clear, and states a deadline only when one applies. Then remove details the body explains better.
A practical checklist
Name the specific project, document, event, or decision.
State the action you need, such as review, choose, confirm, or reply.
Add a deadline only if it is genuine; make it concrete when appropriate.
Keep background, multiple instructions, and explanations in the email body.
Check that the subject does not imply urgency or a task you do not actually mean.
A few more useful answers
Should I put “Action required” in the subject?
Use it only when the recipient really needs to act, and pair it with the specific task: “Action required: approve the event budget.” By itself, it does not tell them what to do.
Is it okay to use a question as the subject?
Yes, if it makes the topic and response clear, such as “Which meeting time works for you?” For a more involved request, a direct action phrase may be easier to scan.
What if the email includes several different requests?
Lead with the main action or decision needed, and put the other requests in the message. If they are separate tasks for different people or deadlines, separate messages may make each request clearer.