# How to Send a Formal Email, From First Draft to Follow-Up Canonical URL: https://headwayskills.com/knowledge/communication/how-to-send-a-formal-email/ Markdown URL: https://headwayskills.com/knowledge/communication/how-to-send-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 How to send a formal email in eight steps: picking the right greeting, stating your purpose first, setting the tone, and what to check before you send. ## Key facts - Title: How to Send a Formal Email, From First Draft to Follow-Up - Category: Communication - Primary skill: Communication - Related skills: Professional Behaviors, Influence - Primary keyword: how to send a formal email - Source page: https://headwayskills.com/knowledge/communication/how-to-send-a-formal-email/ ## What this page covers - How to send a formal email in eight steps: picking the right greeting, stating your purpose first, setting the tone, and what to check before you send. - Practical guidance for how to send a formal email - How this topic connects to Communication ## Detailed explanation To send a formal email, give it a subject line that names your topic, open with "Dear" plus the recipient's title and last name, state your purpose in the first sentence, keep the body to one request in short paragraphs, close with a clear next step, and sign off with your full name and contact details. That much is settled convention. The part that actually stalls people is narrower. Whether "Dear Mr. Okafor" will read as stiff. Whether "Hi Sarah" will read as presumptuous. How much of your reasoning belongs in the message at all, and what to do when a week passes and nothing comes back. Those are judgment calls rather than formatting rules, and they follow a pattern once someone points it out. ## How to send a formal email in eight steps The steps below run in the order the message actually gets made, from the decision to write one at all through to the follow-up. Each depends on the one before it: you cannot write a useful subject line until you know your purpose. The formatting is the easy half; the sequence is where the judgment sits. ### 1. Decide whether email is the right medium Before you draft anything, check that this belongs in writing. Written messages suit documentation, one-way information, and anything the other person needs time to consider before responding. A conversation suits negotiation, complexity, sensitive news, and anything where you are building trust rather than transferring facts. Formality often pushes people the wrong way here. A message that feels intimidating to say out loud feels safer to type, so hard requests get sent by email precisely when a call would land better. If you are writing because you are [avoiding the conversation](/knowledge/communication/difficult-conversations-at-work/), notice that before you spend an hour on wording. ### 2. Settle your purpose and the reader's reason to care Almost every formal email is an ask: for a place, a meeting, a decision, an answer. Before writing a word, finish two sentences for yourself. What I want from this person is ___. [What is in it for them](/knowledge/influence/art-of-persuasion/) is ___. The second sentence is the one people skip, and it changes the whole message. A recruiter reading a speculative application is not evaluating your enthusiasm; they are deciding whether opening your attachment is worth ninety seconds. When you know what the reader is actually deciding, the email gets shorter and the ask gets more specific, which is most of the work. ### 3. Write a subject line that names the topic The subject line is how the recipient triages without opening. The guides that rank for this topic — Grammarly, Indeed, Mailchimp — converge on roughly six to nine words, or about 40 characters, and on the same requirement: state what the message concerns and why it warrants attention. Name the object and the action. "Application for the June marketing internship" works. "Quick question" does not, because it describes the size of your request rather than its subject. To someone who receives a high volume of mail, the subject line does more work than any other line in the message. ### 4. Choose the greeting and set your level of formality This is the step people search for, and the only one requiring real calibration rather than a rule. The convention is straightforward enough: when you have not met the recipient, or they hold a position of authority, use "Dear" with their title and last name — Dear Ms. Lindqvist, Dear Dr. Amaro, Dear Professor Bell. Indeed publishes a whole guide devoted to professional salutations and the ones to avoid, which tells you how often this single decision derails people. The calibration underneath it matters more than the list. Grammarly's guidance is the most useful thing in the mainstream coverage: start more formal than you think you need to, and let the register relax as the relationship develops. The reason is asymmetry. Being slightly too formal with someone who would have accepted "Hi Sarah" costs you almost nothing. Being too casual with someone who expected "Dear Ms. Chen" costs you their first impression, and you never find out that it did. Check the spelling of the name against their signature or their profile, not against your memory. If you cannot determine a gender or a preferred title, use the full name — "Dear Sam Whitfield" — rather than falling back on "Dear Sir or Madam," which reads as a form letter. If they sign their reply "Sam," you have your answer for the next message. Making that call is uncomfortable when you are new, because you are reading a person you have never met from a handful of signals. If that describes you, it is worth [checking how your communication reads](https://assessment.headwayskills.com/) more generally, since tone in writing is one of the few things colleagues assess you on before they have ever met you. ### 5. State your purpose in the first sentence, then keep to one ask Open by saying what you want. Context goes underneath it, not in front of it. The habit most early-career writers bring from school is the opposite — build the argument, then arrive at the request in the final paragraph — which mirrors how the thought formed rather than how it will be read. Then hold the message to one topic. Bundling three requests into one email reliably produces a partial answer: the reader handles the cheapest and the rest sit in a thread that now looks resolved. Formality in the body is mostly about what you leave out. No slang, no "Hey," no emoji, no abbreviations. The reason is not decorum but permanence. Formal emails are the ones that get forwarded up, saved into records, and read months later by people you never wrote to. Anything you would not want a senior stranger reading in a different mood does not belong in the message. Being formal is not the same as being ornate, though — long hedged clauses and inflated vocabulary read as caution, not competence. [Clear, brief and direct](/knowledge/communication/concise-communication/) is the register you want. ### 6. Close with the next step, then sign off properly The closing line tells the reader what happens next: what you would like them to do, or what you will do and when. "I would be grateful for your decision by Friday the 14th" gives them something to act on. "Thank you for your time" ends the message without ending the transaction. Then a formal sign-off — "Sincerely," "Best regards," "Kind regards" — followed by a complete signature: full name, role or program, organization, and a phone number or alternative contact. A signature that stops at your first name forces the recipient to work out who you are. ### 7. Run the pre-send check Four things. The recipient's name spelled correctly. The attachment actually attached, if you referenced one — writing "please see the attached document" with nothing attached is the most-cited mistake in the entire genre, and the fix is to attach the file first and write the sentence afterward. The recipient list: To for people who must act, CC for people who need to know, and a deliberate pause before any reply-all. Fourth, read it aloud. This is the proofreading method named most often across the sources that cover formal email, and its real value is not catching typos. Text that felt neutral while you typed it often sounds clipped or demanding when you hear it, especially in a short message written under time pressure. ### 8. Follow up if nothing comes back Nearly every guide on this topic stops at "send," which leaves the most common outcome unaddressed. Silence usually means your message arrived during a busy week, not that it was rejected. Wait several working days — not hours — then [reply in the same thread](/knowledge/communication/how-to-reply-to-a-formal-email/) rather than starting a new one, so the original message travels with the follow-up. Keep it to two or three sentences: restate the ask, note the date you first wrote, and make it easy to answer. One follow-up is standard; a second, after another week, is defensible when a real deadline is attached. Beyond that, the answer is usually no. ## The skills that make the next one easier to send Reading those steps back, very little of the difficulty was ever about writing. It was about reading a person you cannot see, deciding what they need in order to say yes, and judging how much distance to keep in the process. Which is why the same email is genuinely hard at twenty-two and unremarkable at thirty — the underlying behaviors get practiced, not inherited. **Communication** is the skill doing most of the work here. Its email components map straight onto the steps above: lead with the main message, keep the subject line concise, include only the recipients who need to be there, proofread, and reply in reasonable time. It also covers the decision that comes before all of them, which is whether to write at all or to have the conversation instead. Adapting to the receiver — the calibration in step four — sits in the same place. **Professional Behaviors** are the norms a formal email quietly tests, because email is where they are most visible and most permanently recorded. Politeness as a default, appropriate restraint with humor, handling confidential information deliberately, and writing about absent colleagues as you would with them in the room. That last one stops being abstract the moment a thread is forwarded. None of it is innate polish; these are conventions, and conventions can be learned. **Influence** — the kind you earn and then apply — is what separates an email that is correctly formatted from one that gets acted on. Preparing means working out what is in it for the recipient before you draft — step two. Pitching means keeping it simple and making the opening count. Persisting means the follow-up in step eight, which is where a surprising share of requests are actually won, and which almost nobody is taught. None of the three is something you either have or lack. Each is a set of behaviors you can practice deliberately, starting with the next message you send. The free Work Skills Test gives you a read on where yours currently sit — [which one to build first](https://assessment.headwayskills.com/) is rarely the one people expect — along with the other nine it covers. ## What changes as the stakes go up Some of this may already describe how you work. If you have ever rewritten a greeting twice, or deleted a paragraph because the reader did not need it, you have already been making the judgment these steps formalize. Written messages also carry more weight the further you go. As your responsibilities grow, an increasing share of the people whose opinion affects you will have never watched you work; your emails become most of the evidence they have. That is worth understanding early rather than discovering late, and it is entirely within reach without becoming a different person. By working through a process for something most people treat as obvious, you have already done the part that usually gets skipped. The useful next step is seeing where the rest of your work skills currently stand. ## Get a read on your work skills The only thing left is to find out. The Work Skills Test is a **free** self-assessment of your work skills that shows you where you stand across all twelve of them — including the communication and professional behaviors behind everything above — and which ones would make the most difference to you right now. It takes about 7 minutes, and you can work through it on your own, whenever it suits you. What you get at the end is a clear picture of your strengths and the gaps worth closing, with no obligation to do anything further with it. **Take the skills test** Free to take, and you'll be done in about 7 minutes. ## 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 send a formal email in eight steps: picking the right greeting, stating your purpose first, setting the tone, and what to check before you send. ### 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-send-a-formal-email/ Preferred summary: "How to send a formal email in eight steps: picking the right greeting, stating your purpose first, setting the tone, and what to check before you send." ## Change log - 2026-07-07: Content collection version published.