# Formal Business Email Format: Every Part, and Why It's There Canonical URL: https://headwayskills.com/knowledge/communication/formal-business-email-format/ Markdown URL: https://headwayskills.com/knowledge/communication/formal-business-email-format.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 The formal business email format in ten parts - subject line, greeting, body, the ask, sign-off and signature - plus how formal to be with each recipient. ## Key facts - Title: Formal Business Email Format: Every Part, and Why It's There - Category: Communication - Primary skill: Communication - Related skills: Professional Behaviors, Influence - Primary keyword: formal business email format - Source page: https://headwayskills.com/knowledge/communication/formal-business-email-format/ ## What this page covers - The formal business email format in ten parts - subject line, greeting, body, the ask, sign-off and signature - plus how formal to be with each recipient. - Practical guidance for formal business email format - How this topic connects to Communication ## Detailed explanation Most people looking up the formal business email format are staring at a half-written draft, unsure whether it reads as professional or just stiff. A formal business email has ten parts: the sender address, the subject line, the recipient fields, the salutation, the opening line, the body, the ask, the sign-off, the signature block, and a final check before sending. Each part carries information the recipient uses to decide how, and how quickly, to respond. The structure itself is settled — you can learn it once and reuse it. What the templates rarely explain is what each part is actually doing, and that is where most drafts go wrong. ## What goes into a formal business email format The ten parts below run in the order the recipient encounters them, starting before your first sentence. Two of them — the address you send from and the fields you put recipients into — are decided before you write a word, which is why they are so often left out of format guides entirely. ### 1. The address you send from The very first thing a recipient sees is not your subject line but your sender name and address, rendered in their inbox list. A personal address built around a nickname, or a display name left as an unconfigured default, undermines an otherwise correct email before it is opened. Email guides list checking your sender identity among the non-negotiables for exactly this reason. Use your work or study address where you have one, and make sure the display name is your full name. ### 2. The subject line The convention is consistent across guides: roughly six to ten words, or about forty characters, and specific rather than clever. The subject line is a triage instrument. Your recipient uses it to decide whether to open your email now or leave it until Thursday, so "Question" and "Following up" push you down the queue while "Invoice query — order 4471, needs approval by Friday" does not. This is the one place where formal business email runs directly counter to marketing email: curiosity gaps and clickbait subject lines are rewarded in campaigns and read as evasive in professional correspondence. ### 3. The recipient fields: To, CC, and BCC Who goes where is a formatting decision, and it carries meaning. To is for the people who need to act. CC signals informational inclusion — you are keeping someone in the loop without asking them for anything. BCC hides addresses from each other and, as TechTarget's [etiquette guidance](/knowledge/communication/email-writing-etiquette/) puts it, should be used sparingly and mainly for groups of recipients who do not know one another. The practical risk for a newer colleague runs in both directions: CC-ing a manager onto a routine request can read as escalation, while leaving a stakeholder off can read as going around them. ### 4. The salutation This is the choice most people hesitate over, and it is the one element where the guidance is genuinely about calibration rather than a fixed rule. Use "Dear Mr./Ms. [Last name]," for first contact and for senior recipients. When you do not have a name, a role-based greeting such as "Dear Hiring Manager," is the neutral option — not "To whom it may concern," and never "Hey." Robert Half's guidance is to start more formal than you think necessary and relax as the relationship establishes, moving to "Hello [First name]," once you are corresponding regularly. The relaxation runs one way; you do not tighten back up. ### 5. The opening line Within your first two sentences, the recipient should know who you are and why you are writing. This is a separate job from the greeting, and it is the part writers skip most often, because the context is obvious to them and invisible to the reader. If there is any chance the recipient does not immediately place you, say how they know you before you say what you want. One sentence covers it: your name and role, or the meeting, application, or shared contact that connects you. ### 6. The body One topic, main point first, short paragraphs of one or two sentences, and bullets when several items genuinely need to be covered. Formal recipients are often reading on a phone between meetings, so a request buried in the fourth paragraph is a request that does not get handled on the first read. The one-topic rule has a consequence worth noticing: when you have two unrelated things to raise, the correct fix is two emails, not a longer one. ### 7. The ask One explicit request per email, stating what you want the recipient to do and by when. Nearly every guide lists a single clear call to action as a non-negotiable, and then leaves the hardest part unaddressed: [how to phrase a request](/knowledge/influence/how-to-be-more-persuasive/) so it is specific enough to act on without reading as demanding. The pattern that works is to name the action, attach a date, and offer an alternative — "Could you approve the attached by Thursday? If that timing is difficult, let me know and I'll adjust the schedule." A softened, vague request is not more polite; it just makes more work for the person answering it. ### 8. The sign-off A short courteous line, then a standard closing: "Sincerely," or "Best regards,". Sources are consistent on what to keep out — slang, exclamation marks, emojis, and anything affectionate; Robert Half identifies over-familiarity as the most common sign-off error. Proton's guidance on ending emails makes the same point about matching the closing to the relationship rather than to your mood on the day. Because it is the last thing read, an incongruent sign-off recolors the whole message retrospectively, which is a lot of weight for two words to carry. ### 9. The signature block Full name, job title, organization, and a way to reach you by another route. Exclaimer's signature guidance treats this as functional infrastructure rather than decoration, and that is the right way to think about it: the block lets the recipient identify you, place you in an organization, and pick up the phone if email is not working. Newer professionals most often omit the job title - precisely the field an external recipient uses to work out what you can decide. ### 10. The check before you send Verify tone, the spelling of the recipient's name, pronouns, any facts you have stated, and whether the attachment you mentioned is actually attached. Reading the email aloud once catches tone problems and missing attachments more reliably than a spell-checker will. Mailchimp's rundown of unprofessional emails singles out misspelling the recipient's name as the error that does the most damage, because it reads as inattention regardless of what you intended. Then there is the part that comes after: the professional norm for replying to a formal thread is within twenty-four to forty-eight hours, same day when the matter is urgent. ## How formal should a business email actually be? The format is fixed; the register inside it is not. The same ten parts carry a first approach to an external client and a routine note to a colleague you email weekly, and the difference lives almost entirely in the salutation, the sign-off, and how much scaffolding you put around the request. The useful default is to match the formality of the last message you received, and to start a notch above that when you have nothing to match. If they write in full sentences with a formal closing, mirror it until they relax first. That calibration is a judgment call rather than a rule, and it is the part of [workplace writing](/knowledge/communication/business-writing/) nobody teaches — which is why it is worth [reading how you come across](https://assessment.headwayskills.com/) rather than guessing. It is a learnable judgment, not a fixed trait, and getting a read on where yours currently sits takes less time than drafting the email you are stuck on. ## The skills underneath a well-written email Reading back through those ten parts, the pattern is that almost none of them are really about layout. Choosing a subject line that helps someone triage, deciding whether to CC a manager, phrasing a request so it can be answered in one pass — these are judgment calls about other people, and they show up far beyond email. **Communication** is the closest fit, and email is one of its named territories: lead with the main message, keep the subject line concise, include only the recipients who need to be there, proofread, and reply within a reasonable window. It also covers a decision the format itself cannot make for you — whether email is the right medium at all. Written messages work well for documentation, for one-way information, and when the other person needs time to think. For anything sensitive, genuinely complex, or likely to turn into a negotiation, a conversation does the work that no amount of careful formatting will. **Professional Behaviors** is what makes "formal" mean something other than arbitrary rule-following. Professional etiquette covers being polite, responding as expected, handling confidential information appropriately, and writing about absent colleagues as though they were in the room. Once you see the format that way, it stops being a set of hoops: a specific subject line and a correct name spelling are how respect for someone else's time becomes visible in a medium where they cannot see your face. **Influence** is the skill behind item seven, the ask. Most formal business emails want something, and the ones that get it tend to share the same features: they are simple, they make clear what is in it for the recipient, they acknowledge the drawbacks rather than hiding them, and they are followed up on when the reply does not come. None of that is pressure or clever wording — it is the ordinary way a request earns a decision when you have no authority to compel one. None of these are things you either have or don't. They sit among twelve work skills the framework treats as learnable, and the free Job Skills Test is a quick way to [see which ones need attention](https://assessment.headwayskills.com/) — including the ones you have never had reason to think about. ## Where this shows up in your own work Some of this may already match how you handle your inbox — the pause before hitting send, the second look at a name, the instinct that a particular message would go better as a call. Those instincts are the skill, arriving before the vocabulary for it does. The rest is learnable in the ordinary way, by noticing which choices land and adjusting the next one. You do not have to become a different kind of writer to do it; the same judgment that made you check the conventions before sending is the judgment the rest of it runs on. What tends to be true is that these calls get consequential rather than less so as your work touches more people — a badly aimed request costs more when there are five of them a week and a client on the other end. That is a good reason to know where you currently stand, rather than finding out from a reply that never arrives. ## Find out where your skills stand The format is the easy part; knowing which of the underlying judgment calls you already make well is the useful part. The **free** Job Skills Test is a short self-assessment of your work skills — it shows you where you stand across all twelve, and which ones would make the biggest difference to how your emails, requests, and conversations land right now. Work through it once, then apply what it flags to the next email you have to send. **Take the skills test** Free, 7 minutes, and your results appear as soon as 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? The formal business email format in ten parts - subject line, greeting, body, the ask, sign-off and signature - plus how formal to be with each recipient. ### 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/formal-business-email-format/ Preferred summary: "The formal business email format in ten parts - subject line, greeting, body, the ask, sign-off and signature - plus how formal to be with each recipient." ## Change log - 2026-07-07: Content collection version published.