# How to Write a Formal Email: 8 Examples You Can Adapt Canonical URL: https://headwayskills.com/knowledge/communication/how-to-write-a-formal-email-example/ Markdown URL: https://headwayskills.com/knowledge/communication/how-to-write-a-formal-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 See how to write a formal email with 8 worked examples - job applications, professor emails, follow-ups, apologies and more, plus the structure behind them. ## Key facts - Title: How to Write a Formal Email: 8 Examples You Can Adapt - Category: Communication - Primary skill: Communication - Related skills: Professional Behaviors, Building Confidence - Primary keyword: how to write a formal email example - Source page: https://headwayskills.com/knowledge/communication/how-to-write-a-formal-email-example/ ## What this page covers - See how to write a formal email with 8 worked examples - job applications, professor emails, follow-ups, apologies and more, plus the structure behind them. - Practical guidance for how to write a formal email example - How this topic connects to Communication ## Detailed explanation A formal email follows the same six parts every time: a short, specific subject line; a greeting using the recipient's title and last name; an opening sentence that states your purpose; a brief body; a closing line that says what happens next; and a professional sign-off above your name. The examples below fill that shape in for eight situations you are likely to face. Most people don't look this up out of curiosity. There's a message sitting in a draft window — to a professor, a recruiter, someone two levels above you — and the real worry isn't the structure. It's whether "Dear" sounds stiff, whether the request is too blunt, whether the whole thing reads like a first-year wrote it. Worked wording settles that faster than rules do, so this is how to write a formal email case by case, with the sentences alongside the principle. ## What every formal email example has in common Career guides describe the same anatomy almost word for word, and that agreement is worth noticing: there is one standard, not competing schools, so learning it once removes most of the guesswork. The subject line carries the purpose in roughly seven words or fewer, written as a label rather than a sentence. Grammarly's guide uses "Leave Request," "Meeting Request," and "Customer Complaint" as the model forms. It has to be legible on a locked phone screen and findable in a search weeks later. The greeting is "Dear" plus title and last name — "Dear Professor Brown" — unless an established relationship or an explicit invitation permits a first name. Where you don't have a name, Indeed's guidance is to address the role instead: "Dear Hiring Manager," "Dear Team." The relationship sets the register, not your preference, and the reply that comes back shows you the level to match from then on. The opening states why you're writing in the first sentence or two, with one line of who you are only if the recipient doesn't know you. Busy recipients triage by skimming, so a purpose that first appears in paragraph three often isn't read at all. The body stays short. The template roundups converge on about 50 to 125 words for the body and under 200 for the whole message — considerably less than an anxious writer usually produces. Then a closing line naming what happens next, and a sign-off: "Sincerely" at the formal end, "Best regards" or "Kind regards" as the everyday professional middle. That's the half a template can hand you. The other half — how formal is formal enough for this particular person, how direct you can be, what to leave out — is judgment, and it carries over to every message you write after this one. If you've never had a reading on it, you can see [where your communication habits stand](https://assessment.headwayskills.com/) in a few minutes. ## Eight formal email examples ### 1. Requesting a meeting or call Subject: **Meeting Request: Q3 Handover**. Open with the purpose in one sentence — "I'd like to [arrange a short meeting](/knowledge/communication/effective-meetings/) to hand over the Q3 reporting before I finish on the 28th." Then offer two or three concrete times and, crucially, say how long you need. Naming twenty minutes rather than leaving it open is the most commonly skipped element, and it's what makes agreeing cheap for the other person. Close by making the next move obvious: "Would either of those work, or shall I send an invitation for a time that suits you?" ### 2. Applying for a job or internship Subject: **Application: Marketing Internship (Ref. 4127)**. Name the role and where you saw it in the first line, then give two or three sentences of the most relevant thing you've actually done — not a prose restatement of your CV, which is attached anyway. Close with a plain offer to talk. This is the one where CNBC's most-cited email failure hurts most: mentioning an attachment you didn't attach forces a follow-up message and undercuts the impression the email was written to make. Check the attachment before the wording. ### 3. Emailing a professor or lecturer Subject: **Extension Request — BUS204 Essay**. Put the course code in it; a lecturer may teach several hundred students. Then "Dear Professor Adams," one line identifying yourself by name, course and seminar group, and the request with a brief reason — not a paragraph of justification. UBC's Learning Commons notes that this is exactly the message students agonize over, worrying about sounding too casual or too formal. A fixed opening formula removes the decision entirely, which is the point of having one. ### 4. Thanking someone after an interview Subject: **Thank you — Junior Analyst interview**. [Three sentences is enough](/knowledge/communication/concise-communication/), sent within about a day: thanks for their time, one specific thing from the conversation that stayed with you, and a line confirming you're still interested. That specific detail is the whole job of the email — it's what separates a note the interviewer registers as yours from one that reads as a template pasted after every interview. Don't reopen a question you answered badly; the follow-up isn't a second attempt. ### 5. Following up when there has been no reply Reply inside the original thread rather than starting a new one, and wait about a week on anything non-urgent. Reference the first message and its date, restate the ask in a single sentence, and offer an easy out: "If this should go to someone else, could you point me in the right direction?" Don't apologize for following up, and keep the tone level — impatience is unmistakable in writing, and the silence usually means a full inbox rather than a decision. ### 6. Apologizing for a mistake at work Subject: **Correction — invoice 3391**. Lead with [what went wrong](/knowledge/confidence/learn-from-mistakes/), in the first sentence, before any explanation: "The invoice sent on Tuesday used last year's rate." Then the fix and when it will be done. Allow yourself at most one sentence of cause — the longer the explanation runs, the more it reads as a defense — and don't route the blame elsewhere. This is where the purpose-first rule is hardest to follow, because the instinct is to build up to the bad news rather than open with it. ### 7. Requesting leave or time off Subject: **Leave Request: 14-18 April**. State the dates, the total number of days, and what you've arranged for anything that would otherwise be waiting. Reference the organization's policy if there is one, since following it is half of what's being assessed. This is the most transactional of the eight and should be the shortest — well under a hundred words is normal, and padding it with justification tends to make a routine request look like a negotiation. ### 8. Raising a formal complaint Subject: **Customer Complaint — order 88214**. Facts first and in order: what was agreed, what happened instead, with dates and reference numbers. Then name the specific remedy you want, rather than leaving it to be inferred. Keep the adjectives out — the person reading it almost certainly didn't cause the problem, and a calm, factual account is what gets a complaint escalated rather than quietly filed. The restraint is the persuasion here. ## What makes the ninth one easier to write Notice what those eight don't settle. They give you the wording for eight situations; the ninth will be slightly different, and the judgment it needs — how formal, how short, how direct — has to come from somewhere other than a template. **Communication** is where most of that judgment lives. Main point first, a subject line that does its job, only the recipients who actually need it, a proofread before sending, a reply within a reasonable time — these are working habits rather than rules for one message, and email is simply where they show most plainly. Learn the habits instead of collecting templates and the wording questions start answering themselves, including in the situations no example anticipated. **Professional Behaviors** covers the register layer — how you address someone, how much formality a first contact deserves, what belongs in writing at all, how you refer to a third party in a message they might one day be forwarded. These are workplace etiquette: unwritten norms that feel like a minefield precisely because nobody sits you down and teaches them. They're learnable conventions, not instincts you either have or lack. **Building Confidence** is the one that decides whether the email gets sent. A draft that sits open for an hour usually isn't waiting on better wording; it's waiting on the writer feeling sure, which doesn't arrive by rereading. Confidence here is built by sending — deciding in advance when you'll press send, accepting the discomfort rather than trying to resolve it first, and letting the reps do the work. Almost every formal email that felt alarming to send is forgotten by its recipient within a day. That third one is the hardest to judge from the inside, which is a fair argument for not guessing. The **free** Work Skills Test scores it alongside the other eleven skills in the same set, so you can see [which skill to build first](https://assessment.headwayskills.com/) rather than working on whichever feels most visible. Some of this may already be how you work — checking the attachment before you send, rereading the opening line as the recipient will read it, resisting the urge to explain twice. The parts you haven't picked up yet are conventions rather than character; you can learn them and still sound like yourself in writing, which is the only version anyone actually wants to read. Written messages do last, though. They get forwarded, saved, and reread by people who weren't in the room, and the further you go, the more of your work reaches someone as an email before it reaches them as you. That's an argument for taking an honest reading of where you stand early, not for worrying about it. And you've already done the part most people skip: you looked up a model before sending rather than after a reply landed badly. ## Before you send the next one The wording is handled. What's left is the quieter question of which habits underneath it are already solid and which ones simply nobody taught you. The Work Skills Test is a **free** self-assessment of the twelve work skills that shape how things like this go — communication, professional behaviors and confidence among them. It takes about seven minutes, there's nothing to prepare, and it ends with a plain reading of where each one currently sits. There's no rush on it; the email in your draft window will go out fine either way. But when you'd rather practice a skill than look up another example, that's where to start. **[Take the skills test](https://assessment.headwayskills.com/)** *Free, takes about 7 minutes, nothing to prepare.* ## 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? See how to write a formal email with 8 worked examples - job applications, professor emails, follow-ups, apologies and more, plus the structure behind them. ### 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-write-a-formal-email-example/ Preferred summary: "See how to write a formal email with 8 worked examples - job applications, professor emails, follow-ups, apologies and more, plus the structure behind them." ## Change log - 2026-07-07: Content collection version published.