# Sample: How to Write a Formal Email, Step by Step Canonical URL: https://headwayskills.com/knowledge/communication/sample-how-to-write-a-formal-email/ Markdown URL: https://headwayskills.com/knowledge/communication/sample-how-to-write-a-formal-email.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 A full sample formal email plus the eight steps behind it: subject line, salutation, the one-ask body, sign-off, and how to judge the right level of formality. ## Key facts - Title: Sample: How to Write a Formal Email, Step by Step - Category: Communication - Primary skill: Communication - Related skills: Professional Behaviors, Influence - Primary keyword: sample how to write a formal email - Source page: https://headwayskills.com/knowledge/communication/sample-how-to-write-a-formal-email/ ## What this page covers - A full sample formal email plus the eight steps behind it: subject line, salutation, the one-ask body, sign-off, and how to judge the right level of formality. - Practical guidance for sample how to write a formal email - How this topic connects to Communication ## Detailed explanation To write a formal email, follow a fixed sequence: a specific subject line, a formal salutation, an opening stating who you are and why you are writing, a short body built around a single request, a closing line naming the next step, a professional sign-off, and a check of recipients and attachments before you send. A sample shows you the shape of it; the sequence is what lets you produce your own. That sequence is not really in dispute. Grammarly, Mailchimp, Indeed, and Saleshandy all publish near-identical versions of it, which is why format is the easy half. What a sample cannot give you is the judgment underneath it: whether "Hello" or "Dear Ms. Okafor" is right for this person, and what belongs in the paragraph a template leaves blank. Both are below, with a complete worked example. ## How to write a formal email in eight steps The published sequences run seven steps, in that order because each element constrains the next: you cannot settle a sign-off before you have settled a greeting. One step has been added in front of them, because every version found starts at the subject line, which is in practice the last part you can write well. ### 1. Decide the one thing you want, and what the recipient gets Before you open a draft, write two sentences somewhere else: the single action you want the recipient to take, and [why responding is worth their time](/knowledge/influence/whats-in-it-for-me/). Neither goes in the email. They exist to make the rest of it writable, because the subject line compresses the first and the body has to earn the second. No published sequence includes this step, and that is a structural gap rather than an oversight: a template can supply every part of a formal email except the part specific to you. Skip it and you get a message that is formatted correctly and gives the reader nothing to act on. ### 2. Set the formality from the recipient, not from your habits The most usable rule in circulation comes from Superhuman: use a formal email any time you reach out to someone in [a professional setting](/knowledge/professional-behaviors/how-to-be-professional-at-work/) for the first time. It is blunt, but it is decidable, which most formality advice is not. The rest describes formality as a spectrum without telling you where on it you stand. After the first exchange, read the reply instead of guessing. If they signed off with a first name, a first name is now available to you. If they kept "Kind regards," keep yours. Matching the register of the thread beats any general rule, because it is evidence about this person rather than an average. This is the one step no sample can take for you, and where people who follow a template closely still come unstuck. If you are unsure how your written habits land at work more broadly, it is worth [checking where your communication stands](https://assessment.headwayskills.com/): a judgment you can measure and improve, not a knack you either have or do not. ### 3. Write the subject line Length guidance contradicts itself inside the same set of results. Superhuman recommends one to five words; Saleshandy recommends around 40 characters, or six to nine. Neither cites research, and the disagreement is useful information: length is not the variable that matters. What both sides agree on is specificity plus an action cue. "Question" is a topic. "Interview availability — Thursday or Friday?" names the thing and the decision. Write it after step 1, since it is a shortened form of an ask you have already settled. ### 4. Choose the salutation The greeting is the most-cited failure point in formal email, and it is read before anything else, which is why an otherwise careful message can land badly. The workable map has three tiers: - "Dear Mr./Ms. Okafor," for a first contact or a genuinely formal one, where you know the name - "Hello Amara," when you are uncertain — the safe middle - "Hi Amara," once a working relationship already exists "Hey," "Hiya," and "What's up" are ruled out everywhere. If you do not know which title someone uses, address them by full name, "Dear Amara Okafor," rather than guessing at Mr. or Ms. ### 5. Open with who you are and why you are writing Both belong in the first two sentences, ahead of any background. This is the point the sources are most unanimous about: context must not precede purpose. The instinct under uncertainty runs the other way, toward explaining how you found their address, apologizing for the interruption, and reaching the point in paragraph three. The reason is mechanical. Someone scanning on a phone reads two or three lines before deciding to act, defer, or ignore. If your purpose sits in line eight, that decision has already been made without it. ### 6. Write the body around a single ask Spark puts the body at 50 to 125 words, [shorter than most first drafts](/knowledge/communication/concise-communication/) by someone anxious to seem thorough. Thoroughness reads as competence to the person writing and as work to the person receiving. Several sources specify one ask per email, and the mechanism is worth understanding rather than simply obeying. A recipient acts on the first request and defers the rest, so a second ask does not double your chances; it lowers the odds on the thing you actually needed. If you have two requests, send two emails. ### 7. Close with the next step, then sign off State what happens next, or what you are asking for and by when. Then use a sign-off that reads as formal without sounding starched: "Kind regards," "Best regards," or "Sincerely," followed by your full name and, where relevant, your role. The sign-off has to match the salutation from step 4. "Hi Amara," closing with "Sincerely," reads as two different people writing one message. Mismatched pairs are a quiet version of the tone drift that appears in every list of unprofessional emails. ### 8. Proofread, then check recipients, Cc, and attachments Every source puts proofreading last, and the better ones define it as more than spelling: check the To field, check the Cc field, check that the file you referenced is genuinely attached. The ordering is not arbitrary. This is the only step covering errors you cannot correct after sending — a typo is survivable and often unnoticed, and a confidential message in the wrong To field is neither. ## A sample formal email you can adapt The sequence assembled into one message: a recent graduate following up on a job application, writing to someone they have never met. **Subject:** Application follow-up — Junior Analyst, ref. 4821 Dear Ms. Okafor, My name is Daniel Reyes. I applied for the Junior Analyst position on August 12 and am writing to ask whether the role is still open. I spent my final year working with the same reporting tools your team uses, and I have attached a one-page summary of that work in case it is useful at this stage of the process. If the position has already been filled, I would still be glad to know, so I can stop watching for a reply. Kind regards, Daniel Reyes The sentence about the attachment is the only one a template could not have supplied. It exists because of step 1: it answers what the recipient gets. ## What actually makes an email read as unprofessional The error lists published by Mailchimp, Superhuman, and Clean Email converge on the same set, and it is worth checking a draft against, because these are not the mistakes most people brace for: - Emojis and texting shorthand, such as "u" for "you" - Excessive exclamation points - Casual greetings in a first contact - [Hedging phrases](/knowledge/confidence/lack-of-confidence/) such as "I think," "maybe," and "I guess," which quietly withdraw the request as you make it - Tone drift: opening formally, then turning casual halfway down None of these is a grammar error. They are register errors, which is why you can follow a template correctly and still produce something that reads wrong, and why spell-check will not flag one of them. ## The skills that make the next one easier Notice how little of the above was really about writing. The sequence took minutes to lay out; the parts that took longer were the judgment calls about how formal to be, what the reader gets, and what to leave out. Those recur in every professional message you send. **Communication** covers the written-channel rules specifically: lead with the main message, keep the subject line short, copy only the people who need to be there, proofread before sending. What makes those a skill rather than a checklist is that they transfer. The instinct that front-loads an email also front-loads a status update, a message to a client, a request to your manager. Learn the sequence once and you stop hunting for a fresh template every time the situation shifts. **Professional Behaviors** settles the register question the format cannot. Politeness, keeping out of writing what should not be in writing, and describing people as though they were in the room are the standards that tell you whether "Hi" reads as warm or careless with this recipient. None of it is a matter of character. Nobody arrives knowing where the line sits in a workplace they only just joined; these are norms you read from the context, and they can be learned like anything else. **Influence** is what fills step 1. Working out what is in it for the other person, keeping the ask simple, being straight about the drawbacks rather than overselling, and taking a small yes when a full one is unlikely: these turn a correctly formatted email into one that gets answered. It is persuasion in the plain sense rather than pressure, which matters here, because an email that leans on a stranger fails on its first line. These three are rarely developed evenly in the same person. Someone whose emails are formatted immaculately but never get replies has a different problem from someone whose asks land well but whose register reads too casual for the room. **Communication is one of twelve work skills** measured by the free Work Skills Test, with the other two above among them, and it will tell you [which gap is yours](https://assessment.headwayskills.com/) instead of leaving you to guess. A gap you can name is one you can practice. Some of the eight steps probably described things you already do without having a name for them, which is worth registering rather than skipping past: it means you have been picking this up from the work around you. The rest are simply the next few to learn, and learning them asks nothing of who you are. You do not have to become a more formal person; you have to make a few decisions differently, and keep making them. Writing also does not matter less as you go. The further along you get, the more of your judgment reaches people in written form before they ever meet you. You went looking for how to write a formal email properly instead of pasting the first template you found, and that instinct is most of what separates people who get better at this from people who keep second-guessing each draft. What is missing is a read on where you are starting from. ## Find out where your work skills stand The Work Skills Test is a free self-assessment of the skills you actually use at work. You answer questions about how you tend to operate, and it scores you across all twelve, communication and professional behaviors and influence among them, then shows you where you are already strong and where a little deliberate practice would make the most difference. There is nothing to prepare and nothing to read first. Take it whenever it suits you, and the next email that matters will be easier to judge. **[Take the skills test](https://assessment.headwayskills.com/)** *Free, takes about 7 minutes, and you can do it in one sitting.* ## 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? A full sample formal email plus the eight steps behind it: subject line, salutation, the one-ask body, sign-off, and how to judge the right level of formality. ### 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/sample-how-to-write-a-formal-email/ Preferred summary: "A full sample formal email plus the eight steps behind it: subject line, salutation, the one-ask body, sign-off, and how to judge the right level of formality." ## Change log - 2026-07-07: Content collection version published.