# How to Compose a Formal Email, From Subject Line to Follow-Up Canonical URL: https://headwayskills.com/knowledge/communication/how-to-compose-a-formal-email/ Markdown URL: https://headwayskills.com/knowledge/communication/how-to-compose-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 compose a formal email: what goes in the subject line, whether Dear is still the default, how formal is too formal, and when to follow up after silence. ## Key facts - Title: How to Compose a Formal Email, From Subject Line to Follow-Up - Category: Communication - Primary skill: Communication - Related skills: Professional Behaviors, Building Confidence - Primary keyword: how to compose a formal email - Source page: https://headwayskills.com/knowledge/communication/how-to-compose-a-formal-email/ ## What this page covers - How to compose a formal email: what goes in the subject line, whether Dear is still the default, how formal is too formal, and when to follow up after silence. - Practical guidance for how to compose a formal email - How this topic connects to Communication ## Detailed explanation You need to compose a formal email to a professor, a recruiter, or someone several levels above you, and it has been sitting half-written in your drafts while you delete the first line for the fourth time. To compose a formal email, write a short, specific subject line, greet the recipient by name, state your purpose in the first sentence, keep the body to two to four short paragraphs on a single topic, close with a professional sign-off and a full signature, and proofread before you send. That part is settled, and every guide on the first page of results agrees on it. The harder question, and the one you are actually stuck on, is how formal to be with this particular person. ## How do I compose a formal email from top to bottom? Six parts, in this order: subject line, greeting, purpose sentence, body, sign-off, signature. Grammarly's formal email guide lays out exactly that sequence, and the rest of the first page repeats it almost word for word, so there is no competing school of thought to weigh up. Set the body in block format: left justified, single spaced, a blank line between paragraphs, no indents. Hold the whole thing to one topic and one ask. If you catch yourself writing "also," check whether that "also" deserves an email of its own. ## What makes a subject line worth opening? Length and specificity. The guides converge on about ten words as the ceiling and roughly six as the target, with examples as plain as "Leave Request," "Meeting Request," or "Customer Complaint." Reply.io and Grammarly both recommend leading with an action word — Request, Update, Reminder, Invitation, Action Required — because it tells the reader what kind of message this is before they decide when to deal with it. That is what a subject line is for. It is triage, not a title. "Quick question" gives your recipient nothing to sort by, so it drifts down the inbox while more legible messages get answered. ## Is "Dear" still the formal default? Less often than you would think. A Wall Street Oasis poll of 95 finance professionals, reported by Prospeo, found 73 percent preferred "Hi," 12 percent "Hello," and only 16 percent "Dear." That is a small sample in a single industry, so it is not a rule — but it does show that "Dear" now reads as markedly formal rather than simply correct. Keep it for cover letters, academic and public-sector contacts, regulated or traditional industries, and first contact where you cannot read the culture yet. "Hello" sits comfortably between the two. Skip "Hey" unless they used it first. And if you do not have a name, spend two minutes finding one on a department page or LinkedIn; "To Whom It May Concern" is for when no named recipient exists, not for when you did not look. ## Where does my actual request go? In the first sentence. Every guide in the results says a version of the same thing: the purpose belongs in the opening line, or at the very latest the opening paragraph. If the recipient does not know you, introduce yourself in a clause — your name, your course or role, how you are connected to them — rather than a paragraph of background you are hoping will earn you the right to ask. Then two to four short paragraphs, none of them running past four or five sentences. Your reader is scanning to work out what is being asked of them, and if you make them hunt for it they will skim, guess, and answer a question you did not ask. ## How formal is too formal? Strict formal register means no contractions ("do not" rather than "don't"), title and last name, complete sentences, no slang or emoji, and a neutral tone even when the subject matter is frustrating. Treat that as the ceiling, not the target. Overshooting it reads as anxious rather than professional: stacked qualifiers, a paragraph of apology before the ask, "Please be advised that." The same guides that set those rules are consistent that clarity and restraint, not elaborate phrasing, are what register as formal. Keep the presentation quiet too — Arial, Calibri, or Times New Roman at 10 to 12 points, no color, no capitals for emphasis. Where to land between those two poles is a read on the person and the setting, and it is the one part of this that no template hands you. It is a skill rather than a knack, though, which means you can get a free read on [how your communication holds up](https://assessment.headwayskills.com/) in a few minutes rather than learning it from a message you cannot take back. ## Which sign-off should I use? "Kind regards" is the dependable choice for job applications, executives, and proposals, with "Sincerely," "Respectfully," "Regards," and "Best regards" all safe. Prospeo's analysis of email closings found that gratitude-based sign-offs outperform neutral ones, with "Thanks in advance" drawing a 65.7 percent response rate. Worth knowing, with one caveat: that figure comes from cold outreach, and "thanks in advance" quietly assumes a yes, which lands badly when you are asking someone senior for a favor. Under the sign-off, give your full name, your role or program, and a way to reach you. Someone who has to go looking for your details in order to reply is someone who replies later. ## What should I check before I hit send? Proofreading is the one step every guide treats as non-negotiable, and it works far better as a list than as a vague reread. Recipients: only the people who need it, not a defensive cc. Subject line: does it still match what the email turned into while you wrote it? The ask: in the first sentence, and only one of them. Names, titles, and the organization: spelled correctly. The attachment: actually attached. Then read the whole thing once as though it had arrived from a stranger, because a tone you intended as brisk can land as curt on someone who has no context for your mood. ## How long do I wait if there is no reply? Two to three business days before a first follow-up is the common recommendation from timetoreply and others — long enough to respect their inbox, short enough that your message is still findable. The specific cases are worth memorizing. A thank-you after an interview goes within 24 hours, without exception. A recruiter you have contacted gets three to five business days. If no timeline was given at all, a status check at five to seven business days is reasonable. And if they named a decision date that has now passed, wait a day or two, then ask. Silence is nearly always inbox volume rather than a verdict on you. ## What makes these judgment calls easier Read those answers back and almost none of them turns on vocabulary. Each one is a small read on the person receiving the message: how much formality they expect, how much of their attention you have earned, how long to leave them alone before asking again. That reading is what people are describing when they say someone is good at email. **Communication** does most of the work here, and its written side is narrower than it sounds — lead with the main message, keep the subject line concise, send only to the people who need it, proofread, reply in reasonable time. Those are the same moves the answers above keep circling back to. It also covers the decision that comes before any of them: whether this belongs in writing at all. Writing suits information, documentation, and giving someone time to think; anything sensitive or genuinely complicated usually goes faster in a conversation. **Professional Behaviors** are why formality exists in the first place. Being polite, replying when you said you would, writing about absent colleagues as though they would read it, and being careful with confidential material all show up inside an email — in the greeting, in the cc line, in what you decide to put in writing at all. None of that is deference to rank. It is the same respect extended to everyone regardless of title, which is also why an over-formal email to a senior colleague can land as awkwardly as an over-casual one. **Building Confidence** is the skill that matters at eleven at night with the message still sitting in drafts. Rewriting the same three sentences for an hour is not a writing problem; it is the discomfort of sending something you cannot take back. What helps is deciding in advance when you will write it and when it goes, letting the unease sit there instead of waiting for it to lift, and accepting a clear, imperfect email as finished. If you want to know which of those three deserves your attention first — email being one visible corner of the **twelve work skills** the framework treats as learnable rather than fixed — a short assessment will **[show you where you stand](https://assessment.headwayskills.com/)** across all of them. ## The part that carries forward Some of this will already be familiar. If you have ever cut a line because it sounded like you were apologizing for asking, or held off on a follow-up because it felt too soon, you were making exactly the call this article is about; you just did not have a name for it. That matters, because it means the gap is not a question of who you are. Nobody starts out good at writing to strangers who have authority over them. People get there by writing a lot of those messages and noticing what happened next, and you can do it in your own voice rather than adopting someone else's idea of what professional sounds like. The stakes also climb quietly. The email asking for a deadline extension becomes the email asking for a reference, a budget, a role. You went looking for the standard before sending rather than after, which is the useful instinct here, and it is the same one that makes the rest of these skills easier to pick up. What is left is finding out which of them would carry you furthest. ## Find out what to work on first The only thing left is to see where you are starting from. The Job Skills Test is a **free** self-assessment of the twelve work skills that carry the most weight in the first years of a career, communication among them. You take it on your own, at your own pace, and it gives you a read on where you stand across all twelve plus the two or three that would make the biggest difference to work on next. Run it before you send the message sitting in your drafts, and you will know whether the thing to build is the writing itself or the judgment underneath it. **[Take the skills test](https://assessment.headwayskills.com/)** *It is free, takes 7 minutes, and you see your results right away.* ## 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 compose a formal email: what goes in the subject line, whether Dear is still the default, how formal is too formal, and when to follow up after silence. ### Which Headway skill does this connect to? This guide connects primarily to Communication. It also relates to Professional Behaviors, Building Confidence. ### 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/confidence.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-compose-a-formal-email/ Preferred summary: "How to compose a formal email: what goes in the subject line, whether Dear is still the default, how formal is too formal, and when to follow up after silence." ## Change log - 2026-07-07: Content collection version published.