# How to Write a Professional Email: An Example of Every Type You'll Send Canonical URL: https://headwayskills.com/knowledge/communication/how-to-write-a-professional-email-example/ Markdown URL: https://headwayskills.com/knowledge/communication/how-to-write-a-professional-email-example.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving communication at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer How to write a professional email, with a worked example of each of the five types you actually send at work: requests, follow-ups, updates, notices, apologies. ## Key facts - Title: How to Write a Professional Email: An Example of Every Type You'll Send - Category: Communication - Primary skill: Communication - Related skills: Professional Behaviors, Influence - Primary keyword: how to write a professional email example - Source page: https://headwayskills.com/knowledge/communication/how-to-write-a-professional-email-example/ ## What this page covers - How to write a professional email, with a worked example of each of the five types you actually send at work: requests, follow-ups, updates, notices, apologies. - Practical guidance for how to write a professional email example - How this topic connects to Communication ## Detailed explanation There is a particular kind of stuck that comes with an empty compose window and a name in the To field you would rather not disappoint. You rewrite the first line, delete it, and start again. A professional email has five parts: a specific subject line, a greeting matched to the relationship, an opening sentence that states your purpose, a short body carrying the supporting detail, and a closing with a clear ask and your signature. Lead with the point, and keep paragraphs under five sentences. That frame is settled; almost nobody disagrees about it. What the guides rarely say is that the frame is the easy half — what you are really deciding is which kind of email this is. ## The parts of a professional email, with an example Every part of the frame answers a question the reader asks in order, which is why the order is fixed. The **subject line** answers "is this for me, and does it need me now." Smartlead's format guide puts the useful range at roughly three to seven words, because anything longer gets cut off on a phone. The contrast that recurs across the guides is between a line like "Update" and one like "Request for feedback on Q3 report by Friday" — the second names the topic, the action, and the timing before the message is even opened. The **greeting** is a matching decision, not a formality contest. Overloop and Mailchimp both land on "Hi [First name]" as the default for most workplace messages, with "Dear Ms. Lopez" held back for first contact or a formal setting. Use the name. And if you are job-hunting from an address you made at fifteen: the student guides at Prepory and MsCareerGirl put this near the top for good reason — your address is read before the subject line, and [firstnamelastname@ is the convention](/knowledge/communication/professional-email-address/). The **opening line** states why you are writing. Superhuman and monday.com both describe this as an inverted pyramid — point first, context after — so that a reader who skims still leaves with the message. It is the habit most often broken by people new to work email, who narrate the background first and arrive at the ask in the final sentence. The **body** carries only what is needed to act. Indeed's guidance is that paragraphs rarely run past four or five sentences, and there is a practical reason: long emails get postponed rather than read. A message that looks like work to open is work the reader does later. The **closing** names what you want and by when, then signs off with your name and role. An email with no ask is the commonest reason a reasonable message gets no reply — the reader cannot tell whether one was expected. Put together, that is a complete professional email: > **Subject:** Feedback on survey draft by Thursday > > Hi Daniel, > > Could you review the attached customer survey draft and send me any changes by Thursday? We share it with the client on Friday morning. > > The two questions in section three are the ones I'm least sure about — if you're short on time, those are the ones worth your attention. > > Thanks, > Maria Bruun > Insights team ## Five types of professional email, and an example of each Here is the part the anatomy guides skip. The frame holds no matter what you are writing, so it cannot be what makes one email easy and the next one hard. What changes is the job the body has to do, and that depends on which type of message this is. It matters because readers sort before they read. As altFtool's breakdown of email types describes it, people drop incoming messages into mental buckets — urgent, important but not urgent, informational, ignorable — and then decide what to open. A message that does not signal its category in the subject and first line gets sorted by guesswork, and the guess is usually downward. ### The request email This one asks somebody to do something they have not agreed to yet: review a draft, approve a spend, make time, give an opinion. It is the only type that has to carry both a deadline and a reason, because the reader has no prior commitment to act on. Vagueness is fatal here — "let me know your thoughts" gives the reader nothing to schedule. Name the task, name the day, and make the effort as small as you honestly can. The example above is a request email: Daniel knows what to read, by when, and where to look first if he is busy. ### The follow-up email Nothing has come back, and you have to [raise it again](/knowledge/influence/follow-up-after-a-meeting/) without sounding like an accusation. This category is taught in its own right — the career services offices at the University of Wyoming's Haub School and Hardin-Simmons both publish whole collections of follow-up templates for every work situation, so it carries conventions of its own. The post-interview thank-you belongs here too. Restate the ask compactly, offer an easier version of it, and leave the reader an unembarrassed exit. > **Subject:** Following up: survey draft > > Hi Daniel, > > Checking in on the survey draft I sent Monday. No pressure if it's still in the queue, but I'd need it by midday tomorrow to hold the client deadline. > > A two-minute verbal reaction works just as well as written comments, if that's quicker. > > Best, > Maria ### The status update You send this so that nobody has to ask. It is the only type with no real call to action, which is why people write it badly — with nothing to ask for, they ramble. The structure that solves it is the one the format guides describe for status and confirmation messages: what is done, what is in progress, what happens next. Three headings, and the reader is current in fifteen seconds. > **Subject:** Survey project: week 2 > > Hi Priya, > > Where things stand: > > - Done: questions drafted, reviewed by Daniel > - In progress: client feedback, expected Friday > - Next: pilot with ten respondents, week of the 22nd > > Nothing is blocked. I'll flag it here if that changes. > > Maria ### The informational email A process change, a schedule, a piece of shared knowledge — one way, no reply needed. The failure mode is length, and it is worse here than anywhere else: a reader who cannot tell what they owe you will hold the message open and come back to it later. Say in the first line that no action is required, then give the detail underneath. > **Subject:** New expense process from October 1 > > Hi all, > > From October 1, expense claims go through Concur instead of the shared spreadsheet. Nothing to do today. > > Your login arrives separately this week, and the one-page guide is attached. The spreadsheet stays open for September claims until the 10th. > > Questions to me. > > Maria ### The apology or correction The hardest of the five, and the one where instinct misleads. The instinct is to explain at length, and length reads as defensiveness. [Own the error plainly](/knowledge/communication/how-to-write-a-formal-letter-of-apology/), lead with the fix rather than the reason, and stop. The more serious the mistake, the shorter and flatter the message — and this one, more than any other, gets forwarded. > **Subject:** Correction: figures in yesterday's report > > Hi Priya, > > The revenue table I sent yesterday used August figures instead of September. That was my error. The corrected version is attached; the totals in section two are the only numbers that change. > > I've added a check to the process so it doesn't happen again. > > Maria Five types, one frame. Any template online is a worked instance of one of these, which is also why templates run out: the situation you are in is rarely the one somebody wrote a sample for. What carries over is the judgment underneath — knowing which type you are writing and what it owes the reader. If nobody has ever checked that judgment against anything, it is worth seeing [how your writing lands](https://assessment.headwayskills.com/); nobody tells you when an email reads as curt or unclear, they just reply a little more slowly. ## What the examples are really made of Read back over the five and notice how little of the difficulty was in the wording. Choosing the deadline, holding your tone in the follow-up, resisting the urge to explain yourself in the correction — none of that is writing. It is a set of habits, learned rather than inherited. **Communication** does most of the visible work. Its email principles are the ones this article keeps circling: main message first, a short specific subject line, only the recipients who need it, proofread, answer in reasonable time. Sitting above them is a call the compose window never prompts you to make — whether this should be an email at all. Writing suits one-way information and anything that needs a record; anything sensitive, complicated, or up for negotiation is a conversation that will go worse in text. **Professional Behaviors** covers the layer email tests hardest, because tone does not travel and messages get forwarded without warning. Writing about an absent colleague as though they were reading over your shoulder, treating a junior recipient exactly as you would a senior one, keeping confidential material out of a channel that copies itself endlessly. It also names what to avoid: the passive email that never states its point, the sharp one written while annoyed, and the quiet manipulation of CC'ing somebody's manager as pressure. **Influence** decides whether any of it works, because you almost certainly cannot compel the recipient to act. The pattern applies anywhere you are asking rather than instructing: work out what is in it for the reader before you write, keep it simple, earn attention in the opening line, ask plainly instead of hinting, and follow through on what you said you would do. Over a couple of years, that is how a junior person becomes known as someone whose emails get opened first. None of the three is a knack you either have or don't. The free Job Skills Test looks at how you actually operate across **twelve work skills** — those three among them — and returns a ranked read, so instead of assuming email is your problem you can see [which skills to build first](https://assessment.headwayskills.com/). ## The emails you haven't had to write yet Read the five types again and you may find two or three of them already come easily, while one — often the correction, sometimes the follow-up — is the one you rewrite five times before sending. Which one that is tells you more about your starting point than any template can. Nothing here asks you to write in a voice that isn't yours; it asks that calls you currently make on reflex start getting made on purpose — a change in habit rather than character. The stakes do climb. Asking a colleague for a deadline extension is a different weight from asking a director for a budget, and both arrive sooner than you expect — but they are built from the same five parts you have just read through, learned the same way. You went looking for a worked example instead of guessing and hitting send, which is the step most people skip. ## Where your skills actually stand The only thing left is to find out. The Job Skills Test is a **free** self-assessment of the skills you use at work: you answer questions about how you genuinely operate rather than how you would like to, and it scores you across all twelve — communication, professional conduct, and influence among them. What comes back is ranked: the skills already working in your favor, and the one or two worth deliberate attention over the next few months. Seven minutes, and the next time you open a blank compose window you will know which part deserves the most thought. **[Take the skills test](https://assessment.headwayskills.com/)** *Free, seven minutes, and your results appear the moment you finish.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? How to write a professional email, with a worked example of each of the five types you actually send at work: requests, follow-ups, updates, notices, apologies. ### Which Headway skill does this connect to? This guide connects primarily to Communication. It also relates to Professional Behaviors, Influence. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/knowledge/professional-behaviors.md - https://headwayskills.com/knowledge/influence.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/communication/how-to-write-a-professional-email-example/ Preferred summary: "How to write a professional email, with a worked example of each of the five types you actually send at work: requests, follow-ups, updates, notices, apologies." ## Change log - 2026-07-07: Content collection version published.