The subject line has one job, and it’s not a summary
The body of your email can explain, soften, and add context. The subject line can’t — it has to survive a half-second scan on a phone screen, wedged between a calendar notification and a newsletter. Its only job is to answer one question for the reader: should I open this now, or later?
Non-native writers tend to fail this in two opposite directions, and both come from the same instinct: treating the subject line like a sentence instead of a signpost.
The first failure is over-explaining. You want to be polite and complete, so the subject becomes a mini-paragraph: “Question regarding the formatting of the Q3 report and also about the deadline extension.” By the time the reader’s inbox truncates it at “Question regarding the formatting of the Q3 rep…”, the actual ask is gone.
The second failure is under-explaining — going so generic that the subject carries no information at all: “Question.” “Hello.” “Doubt” (a direct translation from languages where duda or dúvida just means “question,” but reads strangely flat in English). These get opened last, if at all, because they look like every low-priority email in the inbox.
The fix for both is the same: front-load the ask.
Front-load the ask
Put the specific thing you need in the first 40 characters — roughly the point where mobile inboxes cut subject lines off. Everything after that is a bonus the reader may never see.
Before: “Regarding the client presentation for next week’s meeting” After: “Can you review 3 slides before tomorrow’s call?”
The “after” version tells the reader three things instantly: what you need (a review), how much it costs them (3 slides, not 30), and when (before tomorrow). The “before” version tells them a topic exists. A topic is not an ask.
A useful test: if you deleted everything in your subject line except the first six words, would the reader still know what to do? If not, move the verb and the object to the front.
When to put a deadline in the subject
A deadline in the subject line is a strong signal — use it when it’s real and near. “by Friday,” “before the 3pm call,” “end of day” all tell the reader how to triage the email against everything else competing for their attention.
Don’t add a deadline when there isn’t one, or when the real deadline is weeks out. “Contract review — need by end of month” for something you could easily discuss next week just trains the reader to discount your deadlines the next time you have a genuine one. Deadlines in subject lines are a limited resource. Spend them on things that are actually time-boxed.
A good rule: if the task can wait more than a few days, leave the deadline out of the subject and put it in the first line of the body instead, where it reads as planning rather than pressure.
Why “URGENT” usually backfires
“URGENT” in a subject line works exactly once per relationship. After that, the reader either learns you mean it — or learns you don’t, and starts opening your urgent emails last, since they’ve learned “urgent” from you means “normal.”
The instances where it actually helps are narrow: something is broken right now, someone needs to approve a wire transfer in the next hour, a client is on the phone waiting for an answer. In those cases, a specific deadline does more work than the label itself: “Need approval before 2pm — client waiting” beats “URGENT: Approval needed” because it tells the reader exactly what “urgent” means here, rather than asking them to trust your judgment about your own priorities.
If you’re not sure whether something qualifies, it doesn’t. Use the deadline instead of the label.
Three scenarios, rewritten
Asking a favor
Before: “Small request” After: “Can you introduce me to someone on the design team?”
Following up
Before: “Following up” (the third email in a row with this exact subject) After: “Following up: still need the vendor contract signed”
Repeating “Following up” with nothing else forces the reader to open the email just to remember what they’re following up on. Naming the thing again costs you three words and saves them a click.
Sharing a document
Before: “Document” or “Files” After: “Q3 marketing report — feedback needed by Wednesday”
“Document” tells the reader nothing they can act on. The rewrite tells them what it is, what you need from them, and by when — which is also, not coincidentally, the three questions every subject line should answer.
A short checklist before you hit send
- Does the ask appear in the first 40 characters?
- Is there a real, near deadline — and did you name it instead of just flagging urgency?
- Would “URGENT” survive being replaced by an actual time?
- Could a stranger tell what you need from the subject alone, without opening the email?
If you’re drafting the email itself in Copynote, the same tone-control pass you’d run on the body works on a subject line too — worth a quick check before sending, since a subject that sounds right in your head doesn’t always land the same way in English.
