Workplace Email Etiquette: The Unwritten Rules, Written Down

By the maker of Manners · Updated July 2026

Nobody teaches email. You absorb it — from a manager's clipped one-liners, a colleague's five-paragraph updates, and that one thread where someone hit reply-all and the whole floor watched. Yet email is where most of your professional reputation quietly forms. The rules below aren't about stuffiness; they're about the same principle that governs all etiquette: make things easier for the person on the other end.

The subject line is a promise

A good subject line tells the reader what the email is and what it needs before they open it. "Quick question" promises nothing; "Question: approval needed on Q3 budget by Friday" lets a busy reader triage honestly. Three habits cover most cases:

• Lead with the noun, not the pleasantry: the project, the decision, the date.
• Signal the ask when there is one — "for review," "action needed," "FYI only."
• Update the subject when a long thread changes topic. Replying "Re: Holiday party" with a contract question buries it forever.

Greetings and sign-offs: match the register

Email greetings work like the tone settings in the Manners app — Everyday, Polished, Formal — and the polite choice is the one that matches the relationship, not the fanciest one available.

Two cautions. Don't guess at nicknames — write to "Jonathan" until he signs off as "Jon." And when in doubt between two registers, start one step more formal; people will invite you down to casual, but nobody enjoys inviting you up.

Tone: warm, brief, and unambiguous

Text strips out your voice, so neutral words read colder than you meant them. The fix is not exclamation marks everywhere; it's structure and one deliberate line of warmth. A workable pattern for almost any message: one sentence of context, the ask or answer stated plainly, then details in bullets if needed, then thanks.

Watch for the three classic tone traps:

• False cheer that hides the point. If the answer is no, say no kindly — "We won't be able to take this on this quarter" — rather than burying it under enthusiasm the reader has to decode.
• Apology inflation. "Sorry to bother you!" three times per email teaches people your requests can be ignored. Reserve apologies for actual missteps.
• Sarcasm and irony. They almost never survive transit. If a line could be read two ways, one of those ways will be chosen — usually the worse one.

Reply timing, and the polite holding reply

You don't owe anyone an instant answer, but long silence on a direct question reads as dismissal. If a real answer needs time, send the two-line holding reply — it costs twenty seconds and preserves the relationship:

And when you do reply later than you should have, resist the paragraph of penance. One clean line — "Apologies for the slow reply" — then straight to the substance. Overexplaining a late reply makes the reader manage your guilt, which is the opposite of courtesy.

CC, BCC, and reply-all

• To means "I need something from you." CC means "you should know this is happening." Mixing them up is how five people ignore a request meant for one.
• Adding someone's manager to CC mid-thread is an escalation. Sometimes escalation is warranted — but know that's what you're doing, and prefer saying so plainly: "Adding Priya for visibility."
• Reply-all is for information the whole list genuinely needs. "Thanks!" to forty people is not that. Reply to the sender alone whenever in doubt.
• BCC is for mailing lists and for quietly dropping people out of a thread ("moving the team to BCC to spare inboxes") — not for secretly looping someone into a sensitive exchange, which tends to surface at the worst moment.

The polite follow-up

Following up feels pushy, so people either don't (and the work stalls) or they do it passive-aggressively ("Per my last email…"). The etiquette is simple: a follow-up after a reasonable interval is not rude — it's diligence. Keep it short, assume good faith, and make the next step effortless:

One follow-up per interval, not three. If the second nudge goes unanswered, change the channel — a quick message or a word in person — rather than sending a third email into the void.

Small rules that spare everyone

• Answer every question you were asked, in order. Half-answered emails generate whole new threads.
• Attach the file before writing "attached." (Write the attachment line first; it's the only reliable cure.)
• Proofread names. Misspelling the recipient's name in an otherwise perfect email is the typo they'll remember.
• Send during working hours when you can; schedule-send exists so your midnight catch-up doesn't set an expectation of midnight replies.
• Know when to stop emailing. If a thread passes three rounds without converging, propose a call — that's not defeat, it's etiquette.

More guides: politely decline an invitation · modern dining etiquette · tipping around the world