How to Write a Professional Email: Structure, Tone, and Examples

A professional email is not defined by stiff language or elaborate courtesies. It is a message that makes its purpose easy to understand and its next step easy to act on. A useful structure helps, but the right level of formality depends on your reader, relationship, and workplace norms. University writing centers consistently recommend clear subjects, courteous openings, concise bodies, and appropriate sign-offs; they also note that an ongoing exchange can be less formal than a first contact (Boise State University Writing Center; Purdue OWL; University of Wisconsin–Madison Writing Center).

Use this step-by-step structure

1. Decide what the reader should know or do

Before drafting, write down your main purpose in one sentence: request a meeting, share an update, answer a question, or confirm a decision. If the message has several aims, choose the main one and make secondary details support it. For a complex issue or sensitive discussion, email may not be the right channel; propose a call or use the organization’s approved process instead.

2. Write a specific subject line

Summarize the topic and, when useful, the requested action, project, or date. A helpful subject is brief but informative: “Approval requested: revised Q3 budget by May 14” tells the recipient more than “Quick question.” Boise State and Purdue both advise using a concise, meaningful subject so readers can identify the message’s purpose (Boise State University Writing Center; Purdue OWL).

Use an urgency label only when the matter genuinely needs prompt attention, and state the real deadline rather than manufacturing pressure. Keep the subject accurate if the thread’s purpose changes; start a new thread when an old subject no longer describes the message. Before sending, check the To, Cc, and Bcc fields: the subject cannot fix a message addressed to the wrong audience.

3. Choose a greeting that fits the relationship

For a first message or a formal relationship, use the recipient’s known title and name: “Dear Dr. Patel,” or “Dear Jordan Lee,” if you do not know the appropriate title. If you are unsure how someone prefers to be addressed, use their name as they provide it or check their signature or organizational profile. Avoid guessing a gendered title.

For a colleague you already know, “Hello, Maya,” or simply “Hi, Sam,” may feel natural. An existing thread may not need a repeated greeting in every short reply. The key distinction is not that one greeting is universally correct: “Dear” often signals more formality, while “Hi” can be professional in familiar, conversational settings. Boise State recommends a specific, friendly salutation and advises against assuming titles or pronouns (Boise State University Writing Center); Purdue notes that follow-up messages in an established conversation may omit a greeting (Purdue OWL).

4. State the purpose early

In the first one or two sentences, say why you are writing. If the recipient may not recognize your name, briefly identify yourself and the relevant context. For example: “I’m Lina Chen, the project coordinator for the Northstar launch. Could you review the attached timeline by Thursday?” This gives the reader both the request and the reason they are receiving it.

5. Add only the context needed to respond

Include facts that help the reader understand the request: a date, decision, brief background, or link to the relevant document. Use short paragraphs, with one main idea in each. If you have several questions, number them or use bullets so the recipient can answer them individually. Put deadlines beside the action they apply to. Do not bury the request at the end of a long history.

For instance, instead of “I was hoping that perhaps you might have time at some point to look at the attached draft,” write “Could you review the attached draft by Tuesday?” If the deadline is flexible, say so. Concision means removing material that does not help—not stripping out context the recipient needs. The Wisconsin and Boise State writing centers both recommend concise, direct messages with a courteous tone (University of Wisconsin–Madison Writing Center; Boise State University Writing Center).

6. Make the next step explicit

Say exactly what you want the reader to do, by when, and how to respond when that is not obvious. Compare “Let me know what you think” with “Could you confirm whether option A works by Friday?” The second version gives the recipient a concrete decision and a useful timeframe. If no response is needed, make that clear too: “For your information; no reply is necessary.”

7. Close courteously and include a signature

Use a sign-off that matches the relationship and the message: “Best,” or “Thanks,” for many familiar work exchanges; “Best regards,” or “Sincerely,” for a more formal note. Add your name, and include a role or contact details when the recipient needs them. A close can also acknowledge effort: “Thank you for reviewing this.” Boise State recommends ending respectfully and including next steps where relevant; Purdue notes that a signature block should contain contact information when a reply is expected (Boise State University Writing Center; Purdue OWL).

Adjust the tone without losing clarity

Professional tone is courteous, direct, and appropriate to the situation; it does not require inflated wording. With a new client, senior leader, or formal institution, use a more reserved greeting and spell out context. With a familiar teammate, a shorter greeting and more conversational phrasing may be suitable. Follow established team conventions, while retaining standard spelling and punctuation in either case (University of Wisconsin–Madison Writing Center).

For a request, “Could you send the figures by Wednesday?” is direct and polite. For a reminder, describe the needed action rather than accusing the reader: “A reminder that the approval is due Wednesday” is more constructive than “You still haven’t approved this.” For bad news, state the situation plainly, explain its practical effect, and offer a next step if you can. Avoid sarcasm, jokes that may be misread, all caps, and text-message shorthand in formal work messages; Purdue specifically cautions against jokes that may not land as intended and recommends standard spelling and punctuation (Purdue OWL).

Choose words for their precise meaning rather than swapping in a more formal-sounding near-synonym. For instance, “review” asks someone to examine something, while “approve” asks for authorization; the terms are not interchangeable. If you are uncertain about a word choice, consult the dictionary or synonyms guide, and explore writing and grammar resources for related guidance.

One complete professional email template

Subject: Review requested: Client onboarding checklist by June 12

Dear Morgan,

I’m updating the client onboarding checklist for the July rollout. Could you review the attached draft and confirm whether the support handoff steps are accurate by Wednesday, June 12?

If you suggest changes, please add comments in the document so I can incorporate them before the team review on Friday. The current version is here: [link to document].

Thank you for your help. Please let me know if that deadline is difficult to meet.

Best regards,
Riley Chen
Project Coordinator
Northstar Team

Replace the names, dates, role, and link with accurate details. Remove the line about comments if the reader should respond in another way, and do not attach or link material the recipient is not authorized to access.

Before you send: a concise checklist

• Does the subject accurately signal the topic or action?
• Is the message addressed to the right people, with Cc/Bcc used deliberately?
• Have you stated your purpose near the beginning?
• Is the requested action, deadline, and relevant context clear?
• Does the greeting, tone, and sign-off fit this relationship and situation?
• Have you checked names, dates, links, attachments, spelling, and punctuation?
• Is email an appropriate channel for this information, especially if it is sensitive?

Purdue cautions that email may be forwarded or seen by unintended readers and advises against sending passwords, payment details, or damaging sensitive information through ordinary email (Purdue OWL). Follow your organization’s secure channels and policies for confidential material. A final pause to check recipients and attachments can prevent a clear, polished message from going to the wrong place.