Read time: 10 min | Last updated: August 2026
Most email etiquette advice was written for a different inbox: one with twenty messages a day and time to craft each one. The average employee now receives 117 emails per workday and skims most of them in under a minute (the numbers are in our email statistics reference), which changes what good manners actually look like. Etiquette in 2026 is not about ceremony. It is about costing other people as little time and ambiguity as possible. These are the fifteen rules that still earn their place, organized so you can link or jump to any one of them.
The Short Answer
Address only the people who need to act, summarize the ask in the subject line, put the request in the first sentence, match your tone to the relationship, and reply (or at least acknowledge) within a business day. Almost every other rule is a variation on one principle: respect the reader's attention. If an email costs less of it, it is more polite, whatever the greeting says. And if your challenge is the blank draft rather than the manners, start with our guide to writing a professional email.
Addressing People Properly
1. Put action-owners in To, observers in CC
The To field is an assignment; CC is an FYI. When everyone is in To, nobody is sure who owns the reply, and when a decision-maker sits in CC, they rightly assume they can ignore the thread. If you need someone to act, put them in To and say so by name in the body. The mechanics and edge cases are covered in our CC vs BCC guide.
2. Use BCC for privacy, never for surveillance
BCC exists to protect recipient privacy in large lists and to let someone drop off a thread gracefully. Using it to secretly loop in a manager on a dispute is a trap: one "reply all" from the hidden reader exposes the move and burns trust with everyone on the thread. If a third party needs visibility, forward the thread to them separately and say you did.
3. Reply-all only when everyone needs your answer
Before touching reply-all, ask whether your message changes anything for every person on the thread. "Thanks!" and "Works for me" almost never do. The polite version is replying to the sender alone, or, when a group genuinely needs the outcome, summarizing it once when the decision lands rather than narrating your way there.
Subject Lines and Structure
4. Write the subject line as the summary, not the topic
"Q3 budget" is a topic; "Q3 budget: need your sign-off by Thursday" is a summary, and the second one gets opened, prioritized, and found again in search. If the thread's purpose changes, change the subject line to match. A useful test is whether the recipient could triage your email correctly without opening it. (Our free subject line generator scores yours against the same idea.)
5. One topic per email
Two asks in one email means at least one gets forgotten, because replies anchor on whichever point is easiest. If you need a decision and a favor, send two short emails; each can be answered, forwarded, and closed independently. This feels less efficient for the sender and is dramatically more efficient for everyone else, which is the actual etiquette.
6. Front-load the ask
State what you need, from whom, by when, in the first sentence or two; context comes after, for those who need it. Burying the request three paragraphs deep reads as considerate but functions as a puzzle. Readers skim, and a skimmed email with the ask on top still works.
Tone and Wording
7. Match formality to the relationship, and err formal on first contact
"Hi [Name]" is right for nearly all business email; "Dear" survives for genuinely formal first approaches, legal contexts, and some international correspondence. The reliable rule: open one notch more formal than you expect the relationship to be, then mirror whatever the other person does. They sign off with their first name, you may use it. They write two crisp lines, stop sending them five warm paragraphs.
8. Say something real, or skip the pleasantry
"I hope this email finds you well" signals template, not warmth. If you have a genuine opener (their launch, the last conversation, a shared deadline), use it in one sentence. If you don't, going straight to the point is not rude; it is a compliment to the reader's time. Warmth in email comes from specificity, not stock phrases.
9. Reread it as the recipient before sending
Sarcasm, urgency, and frustration all amplify in text, and short replies read colder than intended. One pass through the recipient's eyes catches most of it: would this line read as curt, blaming, or passive-aggressive if you received it mid-skim between meetings? When a thread is getting tense, the etiquette escalation path is a call, not a sharper email.
Replies and Timing
10. Acknowledge within a business day, even without the answer
Expectations are faster than most people think: internal colleagues commonly expect responses within hours, and half of all replies arrive within about 47 minutes (sources in our email statistics reference). You do not have to match that speed, but silence reads as a dropped ball. "Got it, I'll come back to you Thursday" costs ten seconds and converts an open loop into a commitment.
11. Reserve urgent for urgent
Priority flags, "URGENT" subjects, and same-day deadlines are a currency; spend them rarely or they stop working, and people start triaging your name accordingly. If something is truly urgent, email is usually the wrong channel anyway. Send the email for the record, then call or message.
12. Respect working hours with scheduled send
An email sent at 11 p.m. creates a quiet obligation, whatever your intent, and weekend email is now normal enough that boundaries need actively defending. Scheduled send exists precisely for this: write when it suits you, deliver when it suits them, especially across time zones and seniority gaps.
Mechanics and Formatting
13. Handle attachments like a professional
Name files so they make sense out of context ("Acme-Proposal-v3.pdf", not "final2.pdf"), mention every attachment in the body, and attach before you write the rest, because "you forgot the attachment" threads waste everyone's round trip. For anything over a few megabytes, send a link instead.
14. Format for the skim
Short paragraphs, one idea each, no walls of text, no rainbow of fonts and highlights, and exclamation marks in single digits. If your email needs headings and nested bullets to be understood, it usually wants to be a document with a two-line email introducing it.
15. Close deliberately
The sign-off is small but it is the last thing they read: "Best" and "Thanks" cover most situations, the closing line above it matters more than the sign-off itself, and mismatched formality (a breezy "Cheers!" on a formal apology) undercuts the message. The full decision tree, including how sign-offs should evolve over a thread, is in our guide to ending an email professionally.
Situations With Their Own Rules
Group threads reward restraint: answer only the question addressed to you, trim quoted history when it no longer adds context, and move sprawling discussions to a call or document once the third parallel sub-thread appears. Cold outreach earns replies through brevity and evident research; a stranger owes you nothing, so a short, specific, easily-declined ask is both more polite and more effective than a page of context. And in disagreements, email is for facts and decisions, not for winning; state your position once, offer the call, and never write anything you would mind being forwarded, because eventually it will be.
The Violations That Quietly Cost You
A few patterns do outsized reputational damage precisely because nobody tells you about them. The reply-all storm makes you memorable for the wrong reason once, and cautious readers forever after. The silent CC of someone's manager reads as escalation even when you meant it as transparency; say why every added name is there. Urgency inflation trains colleagues to discount you. The ghosted thread, where a clear question simply never gets an answer, outsources your disorganization to the other person's follow-up. And replying to a five-line question with one ambiguous word forces a second round trip that a full sentence would have prevented. None of these break a rule a style guide would catch; all of them show up in how people rank their inbox, which is where triage actually happens.
Frequently Asked Questions
How quickly should I reply to a work email?
Acknowledge within one business day, even if the full answer comes later. Internal expectations often run to within an hour for time-sensitive threads, so when you cannot engage, a one-line holding reply with a date beats silence.
Is it rude to send emails at night or on weekends?
The send time creates pressure even when you say "no rush," particularly downward in a hierarchy. Write whenever you like, and use scheduled send so it lands in the recipient's working hours.
Is "I hope this email finds you well" unprofessional?
Not unprofessional, just empty. A specific opener is better and no opener is fine. Reserve pleasantries for when you have a real one.
Should I reply to every email?
Reply to everything that contains a question, a request, or a genuine thank-you from someone senior or external. Mass mail, FYI-only CCs, and newsletters need no reply, and answering them creates noise of its own.
How formal should a work email be?
One notch more formal than the relationship, then mirror the other person. "Hi [Name]" with complete sentences and a clean sign-off is the safe default across almost every industry in 2026.
The Takeaway
Every rule above compresses to one habit: write the email that is cheapest for the other person to process. Right people in the right fields, the ask visible from the subject line, tone matched to the reader, replies that close loops instead of opening them. That standard is easy to hold at ten emails a day and genuinely hard at a hundred, which is where most professionals now live. It is also, not coincidentally, the part of the job an assistant can carry: Ayari triages what arrives, drafts replies that follow these rules in your voice, and briefs you daily on the handful of messages that need the human touch.