# Sending a Formal Email: 10 Rules Worth Knowing Before You Hit Send Canonical URL: https://headwayskills.com/knowledge/communication/sending-a-formal-email/ Markdown URL: https://headwayskills.com/knowledge/communication/sending-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 Sending a formal email to a professor, recruiter, or new manager? Ten rules that decide how it lands - from the subject line to what to do after you send. ## Key facts - Title: Sending a Formal Email: 10 Rules Worth Knowing Before You Hit Send - Category: Communication - Primary skill: Communication - Related skills: Professional Behaviors, Influence - Primary keyword: sending a formal email - Source page: https://headwayskills.com/knowledge/communication/sending-a-formal-email/ ## What this page covers - Sending a formal email to a professor, recruiter, or new manager? Ten rules that decide how it lands - from the subject line to what to do after you send. - Practical guidance for sending a formal email - How this topic connects to Communication ## Detailed explanation The draft is open, the recipient is a professor or a recruiter or a manager you have met once, and you are stuck on the first line. Sending a formal email comes down to a settled form: a specific subject line, a greeting using the person's title and last name, your identity and your purpose inside the first two sentences, a short body, a formal sign-off, and a full signature. Proofread it, then send. So there is a right way to do this, and it is short enough to learn in one sitting. What almost every guide leaves out is everything around the message — whether email was the right choice at all, who belongs in the CC field, and what you do when nothing comes back. ## Before sending a formal email, check that email is the right channel Most guides begin at the subject line and assume the decision has already been made. It has not. Writing is the right choice when the recipient needs time to think, when the exchange should be on record, or when the message is one-way information. A conversation is the better choice when [the topic is sensitive](/knowledge/communication/difficult-conversations-at-work/), genuinely complex, or something you will need to negotiate. A carefully formatted email about a subject that needed five minutes of talking is still the wrong email. Deciding this first also settles half the tone question before you write a word. ## Write a subject line that survives triage Your recipient is not reading their inbox. They are triaging it, deciding from the subject line alone whether to open, defer, or ignore. Grammarly's guidance is to name the topic and the action rather than the mood: "Request for Meeting — Q2 Environmental Assessment" does work that "Hi" or "Quick question" cannot. University advising pages add a detail worth copying if you are still a student — put the course code in front, as in "MATH 1001-010 Question about Assignment," because a professor sorts by context, not by name. Specific is not the same as long. Six or seven words is plenty. ## Put the right people in To, CC, and BCC This is the part nobody explains, and the part that causes the most trouble. To is for the people who must act. CC is for the people who must know. BCC exists to protect addresses on a large external send — not to copy someone in quietly. Superhuman's rundown of workplace email failures names reply-all abuse as the most common mistake of all, and it is closely followed by CC misuse: adding a manager to a routine thread reads as escalation whether or not you meant it that way. Before you send, look at the recipient fields once more and ask what each name is being asked to do. ## Open with their title and their last name For a first contact, or for anyone senior to you, the default greeting is "Dear" plus their title and last name — "Dear Ms. Okafor," "Dear Professor Lindholm." "Hi" and "Hello" are fine once you already correspond regularly. "Hiya," "Yo," and "What's up" belong to your friends. Then do the boring check: confirm the spelling of the name, and confirm the title is one they actually hold. Calling someone "Doctor" who is not, or misspelling a surname you could have copied from their own email signature, is the first thing they will notice. ## Say who you are and what you want in the first two sentences School trains you to build toward your point. Professional email reverses that. Identify yourself and your context, give the reason you are writing, then make the ask — in that order, in the opening lines. The University of Cincinnati's model for students shows the pattern plainly: name your program and the class you are in, then say what prompted the email, then what you are asking for. Everything after those two sentences is supporting detail for a reader who has already decided whether to keep reading. ## Make the ask easy to say yes to Almost every formal email a career-starter sends is a request — for a meeting, an extension, an internship, a decision. The format-and-template advice treats the ask as a slot to fill, but it is the part that decides the outcome. Ask yourself [what the recipient gets](/knowledge/influence/how-to-be-more-persuasive/), or at least what it costs them, and then remove as much of that cost as you can: one specific request rather than three vague ones, two proposed times rather than "let me know when suits," the document attached rather than promised. This is why so many correctly formatted emails still go unanswered. Reading what the other person needs before you ask is a habit you can build, and it is one of the things a short, free look at [where your work habits stand](https://assessment.headwayskills.com/) will surface. ## Keep the register formal and keep the message short The prohibitions are consistent across every source: complete sentences, no slang, no textspeak like "u," "thx," or "btw," no emoji, no exclamation marks, no jokes. Superhuman and Metaintro extend the same rule to formatting — no ALL CAPS, which reads as shouting, and no colored or decorative fonts. None of this is about sounding stiff. Formality is a signal that you have read the situation and the recipient's position correctly, which is exactly what a stranger cannot yet tell about you. Length is part of it too. A short message is a courtesy, not a shortcut. ## Close with a real sign-off and a complete signature "Sincerely," "Best regards," and "Kind regards" all work; pick one and stop worrying about it. Underneath it, give your full name, your role or your program, and a way to reach you. An incomplete signature leaves the recipient unable to place you, which is a strange thing to do at the end of an email whose whole purpose was to introduce yourself. The same logic applies one step earlier, to [the address you send from](/knowledge/communication/formal-email-address/): an old personal address made at thirteen forms an impression before a single word is read. ## Proofread for the two errors people actually notice There are exactly two you should hunt for. A misspelled recipient name, and "please see the attached" with nothing attached. Both are trivial and both are read as carelessness, because they are the two errors that jump out before the message is even read. The fix for the second one is mechanical: attach the file first, then write the body, so the promise and the attachment cannot come apart. Then read the whole thing once more, slowly, before your eyes go anywhere near the send button. ## Know what happens after you send Professional email runs on a rough 24-hour convention, and it runs in both directions. When someone writes to you and the full answer will take longer, acknowledge receipt inside the day and say when the real reply is coming. When you are the one waiting, give the same window at least, then [follow up once](/knowledge/influence/follow-up-after-a-meeting/) — briefly, in the same thread, without apology or accusation. Coverage of formal email almost always stops at the sign-off, which leaves you alone with the question that actually arrives next: it has been three days, now what? ## The skills underneath a well-judged email Read back over those ten points and most of them are not really about email. They are about judging a recipient, choosing a register, and making a request land — things you will do again in every channel you ever use at work. **Communication** is the one doing the most work here. Its written side is where all of this lives: leading with the main message rather than circling it, keeping a subject line tight, sending only to the people who need it, and proofreading before it goes. It also answers the question that comes before the draft — whether this belongs in writing at all, or whether a conversation would serve you better. **Professional Behaviors** covers the layer underneath the wording: the etiquette nobody sits you down and explains. Addressing people by the title they actually hold, staying polite when you are frustrated, writing about absent colleagues as though they were reading, being careful with information that was shared in confidence. These are unwritten rules, which is precisely why they go unlearned — not because you were careless, but because no one taught them. **Influence** is what separates an email that is answered from one that is merely correct. It is the preparation: understanding what is in it for the recipient, keeping the request simple, making the opening lines count, and following up when nothing comes back. It also carries the smaller nudge you may need, which is a willingness to ask at all, given that the worst available answer is no. None of these three is something you either have or do not have; each is a set of behaviors you can build without becoming a different person. The free Job Skills Test measures twelve of them, these three included, and takes about seven minutes to show you [how each of yours stands](https://assessment.headwayskills.com/) — useful mainly for telling you which one to put your attention on first. ## Where this goes next Some of this will already sound like how you work. If you were the person who checked the form before sending rather than firing it off, you have been doing part of it without giving it a name. The rest is learnable, in the ordinary sense that you get better at it by doing it and paying attention to what came back. Nothing here asks you to be a different kind of person at work — only to make a few different decisions, most of them before you start typing. Email is also where this quietly compounds. The more senior the people you write to, the more of your reputation arrives ahead of you, in messages you will never see read. That is a reason to look at it now, while the stakes are still low and the habits are still loose, rather than later, when both have set. You already stopped to check the form before pressing send. Most people don't. The useful next question is not whether you can write a formal email — you can, now — but which of the skills sitting underneath it are worth your attention first. ## Find out where you stand The only thing left is to see which ones those are. The Job Skills Test is a **free** self-assessment of the twelve skills that decide how work actually goes for you — how you communicate, how you handle professional norms, how you get others on board, and nine more besides. You answer at your own pace, on your own, and you get a clear read on where each of yours currently sits and which will make the biggest difference to focus on next. No preparation, no right answers, nothing to get wrong. **[Take the skills test](https://assessment.headwayskills.com/)** *Free, takes about 7 minutes, and your results appear straight 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? Sending a formal email to a professor, recruiter, or new manager? Ten rules that decide how it lands - from the subject line to what to do after 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/sending-a-formal-email/ Preferred summary: "Sending a formal email to a professor, recruiter, or new manager? Ten rules that decide how it lands - from the subject line to what to do after you send." ## Change log - 2026-07-07: Content collection version published.