Email etiquette is the set of norms that make professional email communication clear, respectful, and effective. Key principles include writing descriptive subject lines, keeping messages concise, using appropriate salutations and sign-offs, responding within a reasonable timeframe, and avoiding all-caps, excessive exclamation marks, or overly casual language. Tone is notoriously hard to convey in text, so being explicit and courteous prevents misunderstandings.
Compare pairs of emails on the same topic — one well-written and one poorly written — and articulate specifically what makes each effective or not. Then rewrite the poor example.
You already know the mechanics of email — composing, sending, replying, forwarding, attaching files. Email etiquette is the layer on top of mechanics: the norms that determine whether your messages are perceived as professional, clear, and respectful, or as confusing and careless. The key insight is that email is asynchronous text — it lacks the vocal tone, facial expressions, and immediate feedback that make spoken conversation so forgiving of imprecision. The words have to carry all the meaning on their own, and the reader interprets them without context unless you provide it.
The subject line is the first professional signal your email sends. A subject like "question" or "hi" requires the recipient to open the message to understand what you want, then later search for it with no useful label. A subject like "Follow-up: Q2 budget approval needed by Friday" tells the recipient the topic, the action required, and any urgency — before they've opened anything. Treat the subject line as a one-sentence abstract of the message. Similarly, the opening lines should orient the reader quickly: who you are (if necessary), what you want, and why you're emailing this person — ideally within the first two sentences, before providing background or context.
Tone is where most professional email errors happen. Text lacks prosody — you cannot hear whether someone is being warm, neutral, or abrupt. A casually written sentence can easily read as curt or rude to someone who doesn't know you. The correction is not excessive formality, but explicit courtesy: "Would you be able to..." reads better than "Can you..."; "I appreciate your time on this" takes three seconds to add and costs nothing. Avoid sarcasm, which almost never lands as intended in text. Avoid all-caps, which reads as shouting. Limit exclamation marks in professional contexts; a string of them reads as performative. When in doubt, read your draft aloud — if it would sound abrupt or odd spoken to a colleague, revise it before sending.
The structural principle is: lead with the main point, then support it. State what you need in the first paragraph; put background and context after. One topic per email makes it easier for recipients to respond, file, and find messages later. Reply within a reasonable window — one business day is a common professional norm — but batch-checking email at set intervals rather than responding to every message the instant it arrives is both more productive and widely accepted. Finally, use Reply All deliberately: not everyone on the original chain needs every subsequent message, and indiscriminate Reply All is one of the most reliably annoying habits in any workplace. Think of each recipient field as a decision you're making, not a default you're inheriting.