A professional email puts the purpose in the subject line, addresses the recipient appropriately, explains the reason for writing, makes one clear request, and ends with a useful sign-off and signature. The format is simple; the judgment is deciding how much context the reader needs and exactly what they should do next.
In short: Use a specific subject, a greeting that fits your relationship, one or two short paragraphs for context and the ask, then a closing with your name. For a reply in an active thread, you can be briefer. Before sending, check the recipient, attachments, dates, and whether the request is clear.
The professional email format at a glance
Subject: [Specific topic or decision]
Hi [Name],
[Why you are writing and the minimum context the reader needs.]
[The specific request, decision, or next step, with a date if one matters.]
Thank you,
[Your name]
[Your role and company, if useful]
[Contact detail, if useful]
This is a starting structure, not a mandatory script. A message to a new client may need a sentence introducing you; a reply to a colleague in an active thread usually does not. The Boise State Writing Center recommends a specific subject, concise paragraphs, a respectful closing, and a signature. Its guidance also favors left-aligned text with blank lines between paragraphs.
If you meant a professional email address format, that concerns the sender's address. This guide shows how to format the message itself. For broader message-format basics and more examples, see Alore's email-formatting guide.
One complete example, with each line explained
Here is a fictional client email. Maya has already discussed a launch brief with Jordan, so she does not need to introduce the project from scratch. She needs approval of one section. The date is illustrative: Thursday, November 5, 2026. Replace it before using the message.
Subject: Approval requested: launch brief audience by November 5
Hi Jordan,
I’ve updated the launch brief to reflect Tuesday’s discussion. The revised version is attached; the audience section needing your approval is on page 2.
Could you reply “approved” for the audience section by Thursday, November 5? If you need changes, please comment on page 2 and reply with the marked-up brief by then so we can update the schedule.
Thanks,
Maya Chen
Operations Lead, Northstar Studio

- Subject: name the decision. Jordan can recognize the approval request before opening the email. Change the topic and date to match your own task.
- Greeting: fit the relationship. Maya uses Jordan's name without guessing a title. Choose “Hi,” “Hello,” or a more formal greeting based on context.
- Opening: give just enough context. The discussion and attachment explain why the message arrived. A new contact would need more orientation.
- Ask: specify the route. Jordan can reply “approved” or return the brief with comments on page 2 by the stated date. Name the action, channel and deadline in your own message.
- Sign-off: identify the sender. Maya gives her name and role. Add contact details only when useful.
The example is invented to show structure; it is not a tested campaign or a promise of a reply. If Maya had not actually attached the brief, the opening would be misleading. A final attachment check matters as much as polished wording.
Make the subject describe the reader’s job
“Quick question” leaves the recipient guessing. “Review requested: launch brief audience section” tells them what the message concerns. If there is a genuine deadline, add it: “Approval requested: launch brief audience by November 5.” Do not mark routine work “urgent” merely to attract attention.
Use the same topic language in the subject and body. This helps the recipient understand the message now and find it later. If the thread changes to a materially different topic, start a new subject rather than burying the new request under an old one.
Choose a greeting for the relationship
“Hi Jordan,” is professional for many ordinary workplace exchanges. “Hello Jordan,” is a slightly more neutral choice for a first contact. “Dear Jordan,” can suit a formal introduction, but a formal greeting cannot compensate for a vague request. Avoid guessing honorifics or pronouns. Boise State recommends using the name or form of address the person uses for themselves when you know it.
You may not need a new greeting on every short reply in an established thread. The University of Kansas Writing Center notes that later replies can become less formal while following the other person's pattern. A new topic or new recipient deserves a fresh, complete opening.
Give context, then ask for a concrete action
The body should answer two questions: Why am I receiving this? and What should I do? Context can be one sentence if the recipient was in the meeting. It may take more if the recipient is new to the issue. The University of Kansas Writing Center frames these as the context and the request, including any time limit.
Compare these requests:
Vague: “Please let me know your thoughts.”
Actionable: “Could you reply ‘approved’ for the audience section by Thursday, November 5, or return the brief with comments on page 2 by then?”
The second version tells the recipient what decision is needed, where to respond, and when. If approval is not the only acceptable outcome, say what alternative would help. Avoid piling unrelated asks into the same paragraph. For a multi-owner project request, short bullets can clarify who decides each item and by when.
Use blank lines between short paragraphs. The goal is scanability, not a fixed word count. A complex decision may need a link to a document and a concise summary in the email; the body should not become a second copy of the document.
Adapt the same format to the situation
First contact with a client or colleague
Suppose Jordan refers Maya to Avery, who now owns approval. Change the greeting to “Hello Avery,” and replace the opening with: “I’m Maya Chen, the operations lead on the Northstar launch project. Jordan suggested I send you the revised brief for audience approval. It is attached, and the audience section is on page 2.” Keep the request, addressed to Avery. Do not refer to Tuesday's discussion if Avery was not there.
Follow-up in an active thread
Keep the subject if the topic is unchanged. If Jordan has not yet decided, Maya can follow up in the same thread: “Hi Jordan, following up on the audience section on page 2. Could you reply ‘approved’ or send back the brief with your comments by Thursday, November 5?” She does not need to repeat the meeting history or reattach the same file unless the version changed.
A sensitive correction or delay
In a separate scenario, suppose legal review delays a brief before it is sent. State the change plainly, its effect, and the next step: “The brief is still in legal review, so I cannot send it on Thursday. I expect to send it Friday and will confirm the timing by 2 p.m. ET Thursday.” Do not present an uncertain delivery date as confirmed.
Close with the next step and an identifiable signature
The request should be in the body, where it is hard to miss. The closing can reinforce it briefly: “Thank you for reviewing this by Thursday.” Then use a sign-off such as “Thanks,” or “Best,” and your name. On a first contact, include your role and company so the recipient knows who is writing. Add a phone number only if a call is an appropriate route.
Avoid long signatures that push the request below a block of promotional copy. The signature is identification, not a substitute for context. The Boise State guide lists name, position, organization and a useful contact method as possible signature elements, depending on the sender's situation.
A 30-second check before you send
- Recipient: Is this the right person? Does anyone on CC need the message, and should any addresses stay private rather than appear in a group To/CC line?
- Subject: Would it tell the recipient what the email is about without opening it?
- Opening: Does the reader have enough context to understand the request?
- Ask: Is the action specific, with a real deadline and time zone where needed?
- Attachment or link: Is the promised file present, accessible and the right version?
- Tone and accuracy: Are names, dates, facts and commitments correct? Would the wording still make sense if forwarded?
The safest final test is to read the email as the recipient: could you act on it without asking what the sender meant? If not, revise the request before polishing the greeting.
The practical rule
Write the email so the recipient can identify the topic, understand why it matters, and take the next step. The familiar subject–greeting–body–closing structure gives you a place for each piece; the quality comes from making the request precise and supplying just enough context.






































































































