Email Etiquette: 17 Rules for Clear Professional Messages

Quick guide

Make the subject line useful

A subject line should help the recipient decide what the message contains and whether action is required. “Question” and “Update” are too broad once an inbox contains hundreds of threads.

Keep the subject aligned with the conversation. If a thread changes from scheduling to contract approval, update the subject or begin a new thread so future searches remain useful.

• Action required: Approve Q3 budget by Aug. 28
• For review: Draft onboarding guide
• Meeting moved: Product review, 2 p.m. ET
• Decision recorded: Use option B for launch

Put the purpose in the opening lines

Readers should not need to reconstruct the request from a long background section. State why you are writing, then add only the context needed to make a decision.

For complex updates, use a compact structure: bottom line, relevant context, requested action, and deadline. A short bulleted list is often clearer than one dense paragraph.

Use To, Cc, Bcc, and Reply All deliberately

Put people responsible for action in To. Use Cc for people who need visibility but are not expected to respond. Bcc can protect recipient addresses in an external broadcast, but using it secretly in an ordinary conversation can damage trust.

Before selecting Reply All, ask whether every person needs the response. Removing necessary stakeholders can be just as disruptive as copying an entire organization.

• To — owns or directly receives the message
• Cc — needs awareness
• Bcc — receives a private copy, often for address privacy in broadcasts
• Reply All — use only when the response affects the whole group

Make requests specific and respectful

A polite request can still be direct. Name the action, owner, deadline, and required format. Replace “ASAP” with the actual business need when possible.

Tone depends on context and power. A sentence that feels efficient between close colleagues may feel abrupt in a first contact. Read the message once from the recipient’s position before sending.

• Write “Could you approve page 2 by noon Friday?” instead of “Thoughts?”
• Explain why a tight deadline exists when that context helps.
• Offer a realistic path to ask questions or renegotiate timing.
• Avoid fake urgency, excessive punctuation, and all caps.

Check names, links, files, and sensitive information

Attachment mistakes are common because the file is mentioned before it is added. Attach the file when you write that sentence, then verify its name, version, and permissions.

Autocomplete can select the wrong person. Before sending sensitive information, review every recipient and consider whether email is the appropriate channel.

• Confirm the recipient's name and title.
• Open each link and attachment.
• Use descriptive file names.
• Remove tracked changes or hidden comments when necessary.
• Do not email confidential data without approved protection.

Close with a clear next step

A closing should reinforce what happens next. “Thanks” is enough when the action is already clear; a more formal sign-off may fit a new relationship or external audience.

Avoid turning the signature into a billboard. Include the identity and contact details the recipient actually needs, and keep images and quotations from overwhelming short messages.

• Thanks — neutral and useful
• Best — concise and professional
• Kind regards — slightly more formal
• No sign-off — acceptable in a rapid internal exchange when context supports it

Final editing checklist