The subject line is the message
For a large share of your readers, the subject line is all they will ever read, and it is what they will search on in six months when they need to find this. A subject that describes the topic is doing half a job; one that carries the ask and the date is doing the whole one.
| Weak | Better | What changed |
|---|---|---|
| Quick question | Approval needed: Q3 vendor contract, by Fri Sep 12 | Names the action, the object and the date |
| Following up | Still need: headcount for the Denver office | Says what is outstanding instead of describing the email |
| Meeting | Moved: design review now Thu 2pm, same room | Delivers the whole change without the body being opened |
| Update | FYI only, no action: migration finished, no downtime | Tells a busy person they can stop reading |
| Re: Re: Fwd: Re: budget | Budget v4 — decision on line 12 | A thread that changed topic four times should get a new subject |
| URGENT — please read | Blocking: build broken since 9am, need someone on it today | States why it is urgent instead of asserting that it is |
Conventional prefixes save people time when you use them consistently: Action needed, Decision needed, FYI, Blocking, and EOM at the end of a subject line when there is no body at all. If your team does not use them, one person starting is usually enough.
Put the ask in the first two sentences
The instinct is to build context first and arrive at the request at the bottom, on the theory that leading with the ask is abrupt. It is not abrupt; it is considerate, because it lets a reader who cannot help route the message immediately and a reader who can help start thinking. Background goes underneath, where the people who need it will find it.
A complete request has three parts, and mail that omits any of them generates a round trip: what you want, who you want it from, and when. "Can someone look at the invoice discrepancy" has none of them. "Priya — can you confirm whether invoice 4471 was paid twice, by Thursday close of business? Details below" has all three, and it can be answered from a phone.
Deadlines need dates. ASAP, end of week, soon and when you get a chance are not deadlines — they are hopes, and they are interpreted differently by every person who reads them. Write "Friday Sep 12, 5pm ET" and include the time zone if anyone on the thread is elsewhere. If it is genuinely not urgent, say that too, because unmarked requests default to urgent in the reader's head and that is a cost you are imposing without meaning to.
To, cc, bcc, and the reply-all problem
| Field | What it means | Practical rule |
|---|---|---|
| To | You are expected to do something or answer | If more than three people are in To, most of them will assume someone else has it. Name the owner in the first line. |
| cc | Awareness only, no action | People in cc should be able to archive without reading. If you need something from them, move them to To. |
| bcc | A hidden copy | Legitimate for a large announcement so nobody harvests the list, and for gracefully dropping people from a thread — say "moving Jan to bcc" in the body. Using it to secretly loop in a manager is a trust problem, not an email problem. |
| Reply | Back to the sender only | The default for most answers |
| Reply all | Back to everyone, forever | Read the recipient list before you type, not after you send. "Thanks" to sixty people is the smallest example of the failure mode; the large one is a candid opinion about a person who turns out to be in cc. |
Two habits prevent most reply-all damage. Write the body first and fill in recipients last, so an unfinished thought cannot escape. And if your client offers an undo-send delay, set it to the maximum — thirty seconds of regret has retrieved more mail than any apology has fixed.
When a thread has drifted into a decision between two people, take it off the wider list and send a short summary back when it is settled. Threads with twelve people and forty replies are how organizations lose things.
Assume it will be read by people it was not sent to
Mail written to a work account can be forwarded in one click, quoted out of context, produced in a legal matter, read by an administrator, or shown to the person you were writing about. None of that requires anyone to behave badly. It is simply what a durable, copyable, searchable record does over time.
The practical filter is not complicated: do not write anything you would not want read out loud, to the person it concerns, in a room you are also in. Frustration, sarcasm, a joke at a colleague's expense, and a candid assessment of somebody's competence all survive far longer than the mood that produced them. If a message is genuinely sensitive, have the conversation and send a short factual note afterward summarizing what was agreed.
The same applies to speed. If a message makes you angry, write the reply, save it as a draft, and do not send it until the next morning. This advice is old because it works.
Attachments, formatting and the small stuff
Attach the file before writing the sentence that mentions it. Name it usefully — "Q3-forecast-v4-2026-08-28.xlsx" rather than "final_final.xlsx" — because your reader will download it into a folder of thirty other files. Say in one line what it is and what you want done with it. Large files belong in a shared drive with a link and the right permissions checked; sending a 40MB attachment to eight people is a small act of vandalism against everyone's storage.
Formatting is a courtesy, not decoration. Short paragraphs, a blank line between them, bold on the deadline and the ask, and a bulleted list when there are genuinely discrete items. A wall of text gets skimmed, and skimming a wall means the middle is lost. Skip the colored fonts, the inspirational quote in the signature, and the read receipt, which most people find faintly hostile.
A signature needs your name, role, organization and one reliable way to reach you fast. A signature generator will build one; the discipline is deleting most of what it offers.
The three hard emails
| Type | Shape that works |
|---|---|
| Saying no | Decline in the first line, give one real reason, offer the alternative if you have one, stop. "I can't take the Denver review — I'm committed to the audit through the 20th. Ravi knows the file and may have room." Long apologetic preambles read as negotiable and invite a second ask. |
| Apologizing | Name the error plainly, say what you are doing about it, give a date, and skip the explanation of how it happened unless it is genuinely relevant. "The report went out with last month's figures. Corrected version attached, and I've added a check to the process before the next one." No "sorry for any inconvenience", which reads as a form letter because it is one. |
| Chasing | Short, factual, no edge. Reply on the original thread so the history is right there. "Checking in on the vendor approval — still need it by Friday to hold the price." Two follow-ups is usually the point to switch channels: a chat message or a two-minute call resolves what a fourth email will not. |
Across all three, the tone rule is that written English reads colder than you intend by roughly one step. A message that feels neutral to you can land as curt. Adding a human first line — a genuine one, not "hope you're well" — costs six words and prevents a surprising amount of friction. Cut the hedging in the other direction too: "I was just wondering if maybe you might possibly have a chance to" is six words of apology in front of a simple request.
Timing, time zones and when email is the wrong tool
Sending at 11pm is a message about your working hours whether or not you mean it as one, and for a manager writing to a report it lands as an expectation. Schedule it for the morning; every major client can do this. Across time zones, write the date and hour with a zone attached, and let a meeting time finder or a time zone converter do the arithmetic rather than doing it in your head at the end of a long day.
Email is the wrong tool for anything requiring back-and-forth to reach a decision, anything emotionally loaded, anything genuinely urgent — nobody is watching an inbox during a fire — and anything that would take four exchanges to clarify. Two rounds without convergence is the signal to pick up the phone. It is also the wrong tool for a running conversation, which is what chat is for, and for a permanent decision record, which belongs in a document that people can find without searching a mailbox. If you are working across a distributed team, the remote work setup guide covers where each of those lines usually falls.
Set an out-of-office with a return date and a named person to contact in the meantime. "Limited access to email" tells the reader nothing they can act on.
Before you send
Six seconds, in this order: does the subject line carry the ask and the date; is the request in the first two sentences; is there a real date rather than ASAP; is the owner named; is the attachment attached; and is the recipient list what you actually intended, particularly if you arrived here by hitting reply all. That check catches nearly everything that goes wrong with work email, and it is faster than the recall you would otherwise be attempting ninety seconds later. When the mail in question is an application or a note to a hiring manager, the stakes on the subject line and the first two sentences go up rather than down — interview preparation and the resume guide deal with the rest of that exchange.
Take the last message you sent and rewrite its subject line as if the recipient will read nothing else: not "Following up" but "Still need: signed W-9 from Acme, by Sep 12." That one line, done habitually, will get you more answers than any other change you make.
Questions people ask
What makes a good work email subject line?
It carries the action, the object and the date, so that a person who reads nothing else still knows what you need. "Approval needed: Q3 vendor contract, by Fri Sep 12" does work that "Quick question" never will. It also has to survive search six months later, which is why threads that have drifted onto a new topic deserve a new subject rather than a fifth "Re: Re:". Consistent prefixes like Action needed, FYI and Blocking help readers triage at a glance.
When should I use cc versus bcc?
cc means awareness only — anyone in it should be able to archive the message without doing anything. If you actually need something from a person, they belong in To, with their name in the first line. bcc has two legitimate uses: a large announcement where you do not want to expose everyone's address, and dropping people off a thread, which you should announce in the body ("moving Jan to bcc"). Using bcc to quietly copy someone's manager is a trust problem that email etiquette cannot fix.
How do I write a follow-up without being annoying?
Reply on the original thread so the history is attached, keep it to two sentences, restate the specific thing outstanding and the date, and leave any edge out of it. "Checking in on the vendor approval — still need it by Friday to hold the price" is complete. After about two follow-ups, the problem is usually the channel rather than the wording: a chat message or a short call will resolve what a fourth email will not.
Is it really a problem to send work email at night?
It sends a message about working hours whether or not you intend one, and from a manager to a report it lands as an expectation even with "no rush" attached. Nearly every mail client can schedule delivery, so write when you want and send in the morning. Across time zones, put an explicit zone on every date and time you state, and let a converter do the arithmetic rather than working it out tired.
How careful do I have to be about what I put in writing at work?
Careful. Anything sent to a work account can be forwarded in one click, quoted without its context, read by an administrator, or produced in a legal matter, and none of that requires anyone to act in bad faith. The workable filter is whether you would be comfortable having it read aloud, to the person it concerns, with you in the room. If a message is genuinely sensitive or you are angry, have the conversation instead and send a short factual summary of what was agreed.