PROFESSIONAL EMAIL AND CORRESPONDENCE

Email is the paperwork of modern work. For most people in a hospital, a clinic, a school, or an office it is also the single largest writing task of the day — dozens of small documents, most drafted in under two minutes, each one permanent, forwardable, and in many settings legally discoverable. Chapter 1 asked who you are writing for and why. This chapter puts that thinking under pressure and at speed. You will learn to decide whether a message belongs in email at all, to write a subject line that survives a crowded inbox, to put your request where a hurried reader will actually find it, and to hold your tone steady when the stakes rise and sharpness is tempting. Every principle here arrives with a weak version and a stronger one, because email is a skill you build by revising real sentences — not by memorizing rules about salutations.

Section 1Should This Be an Email at All?

The channel-fit test

Most bad emails are not badly written. They are correctly written messages sent through the wrong pipe. Before you type a word, run four questions. How complex is the content? If the reader needs to hold more than three or four moving parts in mind at once, email will fragment it. How much emotion is in the room? Disappointment, blame, disagreement, and anything that touches someone’s competence or pay travels badly in text, because text strips the tone of voice that would have softened it. How fast do you need an answer? Email is asynchronous by design; if the answer is needed in ten minutes, email is a lottery ticket. Do you need a record? This is the question that pulls in the other direction, and it is why email survives.

Score those four honestly and the channel usually picks itself. High complexity plus low emotion plus a need for a record is email’s home turf. High emotion plus urgency belongs on a phone or in a hallway. High complexity plus high emotion — a performance concern, a staffing change, a mistake with patient consequences — belongs in a conversation followed by a short written summary. That last pattern is worth naming: talk first, confirm in writing. It gives you the humanity of the conversation and the durability of the record.

The test also protects you from a subtler failure. Some messages should not be sent at all. If you cannot state what you want the reader to do, you are not ready to write. The urge to send something — to look responsive, to move the problem off your desk — produces the emails that generate three replies and no decisions.

What email is uniquely good at

Email is not merely the default. It does four things no other everyday channel does as well. It is asynchronous, so a night-shift nurse and a day-shift manager can transact business without ever being awake at the same time. It is precise, because the writer can revise before sending and the reader can re-read. It carries payload — attachments, links, tables, and schedules that a phone call cannot deliver. And it produces a timestamped record, which matters enormously the day someone asks when a policy change was communicated and to whom.

That last property is the reason email persists despite every attempt to replace it. Chat is faster and warmer; chat is also a river. A decision made in a chat channel on a Tuesday is functionally gone by Friday. A decision confirmed by email is findable in three years by someone who was not in the room. When work has consequences — clinical, financial, contractual, disciplinary — the findability is not bureaucratic overhead. It is the point.

When email fails, and what to do instead

Email fails predictably. It fails at negotiation, because each round costs a day. It fails at anything requiring the reader to change their mind, because you cannot see resistance forming and adjust. It fails at urgent clinical communication, which is why organizations build paging, rapid-response, and read-back systems that deliberately bypass the inbox. And it fails at conflict, where the absence of a face invites the worst interpretation of every clause.

A practical rule: if a thread reaches a third round without resolving, the channel is wrong. Stop typing, pick up the phone, and then send one message that begins “Following up on our call — here is what we agreed.” You will spend four minutes and save four days.

Formal correspondence sits at the far end of the spectrum. A signed letter on organizational letterhead — a resignation, a formal complaint, a notice of a contract change, a reference — carries weight that an email body does not, because it signals deliberation and creates a clean document that can stand alone. In modern practice the letter usually travels as a PDF attached to a short, neutral email. Chapter 5 covers letter construction in detail; here the point is only that the letter is a channel choice, not a stylistic flourish.

Section 2The Anatomy of a Professional Email

Subject lines do real work

The subject line is the only part of your message that is guaranteed to be read. It is doing three jobs at once: it decides whether the message is opened now, later, or never; it becomes the label under which the message is filed; and it is the search term someone will type eighteen months from now when they need to prove what was communicated. Treat it as a filename, not a headline.

A strong subject line names the topic, and where relevant the action and the date. It front-loads the distinguishing word, because inbox previews truncate at roughly forty to sixty characters on a phone. “Question” is not a subject line. Neither is “Quick follow-up,” which describes the writer’s intent rather than the reader’s business.

Salutation, sign-off, and the signature block

Openings signal how you see the relationship, and getting them wrong is cheap to fix and expensive to ignore. “Dear Dr. Ramirez,” is correct for a first contact with someone senior or external. “Hi Dr. Ramirez,” is correct for the fourth message in an established working relationship. “Hey” belongs to peers you know. No salutation at all is fine inside a fast-moving thread and reads as brusque when it opens one.

Etiquette guides genuinely disagree about “Dear.” Some treat it as the safe default in any professional first contact; others argue it now sounds stiff or faintly antique outside formal letters and legal correspondence, and that “Hello” is the modern neutral. Both positions are defensible, and the honest answer is that the norm varies by industry, country, and generation. The reliable move is to mirror: read how your correspondent opens their messages and match one notch more formal until invited otherwise.

Names deserve care. Use the credential the person uses for themselves — if the signature block says Dr. Chen, write Dr. Chen, and do not downgrade a physician, a doctorally prepared nurse, or a professor to Ms. or Mr. because you assumed. Spell the name correctly; it is in the message you are replying to. When you do not know a gender or an honorific, the full name works cleanly: “Dear Alex Whitfield,”. “To Whom It May Concern” should be a last resort, and thirty seconds on a staff directory usually eliminates the need for it.

End with a sign-off and a signature block. “Best,” “Thanks,” “Regards,” and “Sincerely,” are all serviceable; “Sincerely” carries the most formality and is right for letters and first contacts with strangers. The block underneath should give your full name, your role, your unit or department, your organization, and one reliable phone number. This is not decoration. A reader who needs to call you at 4 p.m. about your own message should not have to look you up.

The first sentence is the whole email

Many readers see the sender, the subject, and the first line and decide everything from there. That first line is therefore load-bearing, and it is routinely wasted on throat-clearing. “I hope this email finds you well” is not offensive; it is simply empty, and it pushes the actual content below the preview fold on a phone.

Compare two openings to the same message. Weak: “Hi Dr. Ramirez, I hope you had a great weekend! I wanted to reach out because I have been thinking about the discharge packet situation and I know things have been really busy on the unit lately…” Stronger: “Hi Dr. Ramirez — I need your sign-off on the revised discharge packet by Thursday so printing can start Friday. Two items need your decision; both are below.” The second version is not colder. It is more respectful of a reader who has ninety other messages, and it tells them in one line whether this is theirs to act on.

Warmth still belongs in professional email; it just belongs after the point, not in front of it. “Hope the move went smoothly” lands better in sentence three, once the reader knows what they are being asked to do.

Section 3Writing the Ask: Structure That Gets Action

Bottom line up front

BLUF — bottom line up front — is a structural discipline borrowed from military and government correspondence. It inverts the shape most of us learned in school. Academic writing builds toward a conclusion; workplace writing leads with it and then supplies the support underneath, so a reader can stop reading the moment they have what they need. The busiest, most senior readers stop earliest. That is the design assumption.

In practice BLUF means the first two sentences answer three questions: what is this about, what do you want from me, and by when. Everything after that is evidence, context, and courtesy. If the reader is a subject-matter expert who will need the reasoning, the reasoning still comes second — experts skim to the conclusion and then read the support, which is exactly the order BLUF gives them.

There is one honest exception. When the news is genuinely bad or the request is genuinely unwelcome, a single sentence of context before the point can prevent the reader from reacting to a headline out of nowhere. That is a buffer, and it should be one sentence, not one paragraph. Section 4 develops the technique. Outside of that case, lead with the point.

Name the actor, the action, and the date

A request that does not name a person, a verb, and a date is a wish. “Please advise” is the classic offender: it puts the burden of figuring out the question onto the reader. “Someone should look into this” guarantees that no one will, because diffusion of responsibility is not a character flaw, it is arithmetic. If a message goes to six people and names none of them, each reader reasonably assumes one of the other five will handle it.

Build every ask with three slots filled: who does it, what exactly they do, and when it is due. Add a fourth slot when the request is nontrivial: what happens if the date slips. “If I do not have the roster by Wednesday, I will publish the schedule with the current assignments and correct it next cycle” is not a threat. It is information that lets the reader prioritize honestly.

Be equally explicit when you need nothing. “No action needed — sharing for awareness” at the top of a message is one of the highest-value sentences in professional writing. It saves every recipient the cognitive work of scanning for a hidden obligation.

Format for a reader who is scanning

Nobody reads workplace email the way they read a novel. They scan in an irregular sweep, catching the first words of paragraphs, anything bold, anything numbered, and anything that looks like a date. Formatting is therefore not decoration; it is a map that tells the eye where to land. Chapter 4 develops document design fully. For email, four habits carry most of the value.

First, keep paragraphs to one idea and roughly two to four lines on a phone screen. A ten-line block reads as a wall and gets deferred. Second, use a short labeled list when you have three or more parallel items — questions, options, deadlines, attachments. Third, bold sparingly and only on the load-bearing element: a date, a deliverable, a decision. Bold everything and you have bolded nothing. Fourth, put the details a reader might need but might not read below a visible break, so the top of the message stays clean.

Two things to avoid. Do not use ALL CAPS for emphasis; it reads as shouting to most readers and is harder to decode. And do not rely on color alone to carry meaning, since colleagues with color-vision deficiency, and anyone reading a printed or plain-text copy, will lose the distinction entirely. Emphasis should survive being read aloud.

A worked example, annotated

Here is a complete revision. The original is realistic — polite, competent, and still guaranteed to generate two clarifying replies before anything happens.

Before. Subject: Schedule. Body: “Hi everyone, I hope you all had a good weekend! I wanted to touch base about the summer schedule since we are getting close and I know a lot of people have questions. There are still some gaps we need to fill and I would love to get everyone’s input on how to handle the weekend coverage since that seems to be where the biggest issues are. Also there is the training day that we still need to figure out. Please let me know your thoughts when you can. Thanks so much!”

After. Subject: Action by Wed 5/6 — claim a summer weekend shift (3 open). Body: “Hi all — three weekend shifts are still open for June. Please claim one by Wednesday 5/6 by replying to me directly with your preferred date. Open: Sat 6/6, Sun 6/14, Sat 6/27. If fewer than three people volunteer, I will assign the remainder by rotation order and post the final schedule Friday 5/8. Separate email coming today about the July training day — nothing needed from you on that yet. Thanks, Priya.”

Notice what the revision does. It splits two topics into two emails, so each has one subject line and one deadline. It names the action, the date, and the consequence of silence. It routes replies to one person rather than inviting a reply-all storm. And it tells recipients explicitly that the second topic requires nothing yet, which prevents a wave of “what about the training day?” messages.

Section 4Tone, Register, and Repair

Register: how formal, and how would you know

Register is the level of formality a piece of writing adopts, and email demands more conscious control of it than almost any other genre because the same person may write to a patient’s family, a physician, a vendor, and a friend from nursing school within the same ten minutes. Three variables set the dial: distance (how well you know the reader), power (whether they are above, below, or beside you), and weight (how consequential the message is). Raise the formality when any one of the three goes up.

Register lives mostly in small choices. Contractions, sentence fragments, and first names lower it; full forms, complete sentences, and titles raise it. “Can you send that over?” and “Would you be able to forward the completed form by Friday?” ask for the same object and describe two different relationships. Neither is correct in the abstract; the first is right for a peer and slightly careless for a hospital’s general counsel.

The failure mode nobody warns you about is over-formality with people you work beside daily. A message that opens “Dear Ms. Okafor, I am writing to inquire regarding…” to a colleague you had lunch with reads as a signal that something is wrong — that you are creating a record, or that you are angry. Formality carries information. Use it deliberately.

The politeness dial and when softening backfires

Politeness in email is mostly built from hedges and softeners: “I think,” “maybe,” “just,” “a little,” “when you get a chance,” “sorry to bother you.” These are not errors. They are the linguistic equivalent of not standing too close, and stripping them all out produces messages that read as curt or even hostile. The problem is dosage, not existence.

Too many hedges around a real requirement create genuine ambiguity. “I was just wondering if maybe you might have a chance to look at the incident form sometime this week if you get a moment” does not communicate that policy requires the form within 72 hours. The reader is not being obtuse when they deprioritize it; you told them it was optional. The fix is to hedge the relationship and stay firm on the requirement: “Sorry to add to your week — the incident form is due to Risk by Thursday at 5. Can you get it back to me by Wednesday so I can review it first?” That sentence is warm and unmistakable.

You will encounter confident advice, particularly aimed at women, to delete “just,” “sorry,” and exclamation points entirely on the grounds that they undercut authority. The evidence is genuinely mixed. Some studies of workplace language find hedged requests are rated as less confident; others find the same softeners increase perceived warmth and cooperativeness with no credibility cost, and several researchers argue the advice misdiagnoses a bias problem as a writing problem. What holds up across the disagreement is narrower and more useful: hedge the interpersonal frame, not the factual content, and never let a softener obscure a deadline or a safety issue.

Bad news, refusals, and apologies that work

Three hard messages recur in every workplace. Each has a reliable shape.

Bad news takes a one-sentence buffer, the news stated plainly, a brief reason, and a forward path. “Thank you for the detailed proposal — the committee reviewed it carefully. We are not funding the equipment request this cycle; the capital budget closed at the end of March. The next cycle opens in September, and I would be glad to review the proposal with you in August so it is ready.” Notice that the reason comes after the news rather than before it. Long preambles do not soften bad news; they make the reader anxious, then annoyed at having been made to wait.

Refusals should decline the request, not the person, and should be specific about what you are declining. “I cannot cover Saturday” is clean. “I do not think I will be able to make that work, unfortunately” invites a second ask. Where you can, offer one alternative — a different date, a smaller scope, another person — but do not manufacture one that you cannot deliver.

Apologies in professional email are frequently botched in one of two directions. The non-apology names no wrong: “I am sorry you were frustrated” assigns the problem to the other person’s feelings. The over-apology is self-focused and asks the injured party to provide reassurance: “I feel awful, I have not stopped thinking about it, I am so embarrassed.” The version that works has four parts and is short: name what happened, take the part that is yours, state the correction, and state the prevention. “The discharge instructions I sent Tuesday listed the wrong follow-up date. That was my error. I called the family this morning and corrected it, and I have added a date check to the template before it prints.” Note also that in clinical and legal contexts, organizations often have specific policies about written apologies related to patient events — follow your risk-management guidance, and route those communications through the required channel.

Writing when you are angry

The most damaging emails in most careers are sent within ninety seconds of reading something infuriating. Text is uniquely dangerous here because it removes every repair mechanism a conversation has: no pause, no tone, no chance to see the other person flinch and walk it back.

Two mechanical safeguards work better than resolve. First, write the angry draft with the recipient field empty, then leave it for an hour. Most of the time you will delete it and send four sentences instead. Second, apply the forwarding test: assume this message will be read aloud by someone you respect, in a room you are not in, six months from now. That is not paranoia. Forwarding is one click, and workplace email is routinely produced in investigations, grievances, and litigation.

When you must address a conflict in writing, strip the interpretation and keep the observable. Not “you clearly do not care about the deadline,” which claims access to someone’s motives, but “the report was due Monday and I have not received it; I need to know today whether it is coming.” Facts are hard to argue with. Attributed motives are all anyone will remember.

Section 5Threads, Recipients, and Risk

To, CC, BCC, and reply-all: who is in the room

The recipient fields are a governance system disguised as a form. To means you are asking this person to act or respond. CC (carbon copy) means you are informing this person and expecting nothing from them. BCC (blind carbon copy) means you are sending a copy the other recipients cannot see. Used casually, these fields quietly reshape who is accountable and who feels surveilled.

Two abuses are worth naming. Putting a supervisor in CC to add pressure is widely read as escalation, and it damages relationships even when it works. If the situation genuinely needs a manager, say so openly: “I am copying Dana since this affects the unit budget.” One clause of explanation converts a power move into a courtesy. The second abuse is using BCC to let a third party quietly watch a conversation. It feels efficient and it is a trust bomb: if the BCC recipient replies-all by reflex, everyone learns they were being observed. Two uses are clean. The first is sending to a large list so that recipients cannot see each other’s addresses, which is a privacy protection. The second is announced rather than hidden: moving someone off a thread once their part is finished — “moving Dana to BCC” — which works precisely because you said so.

Reply-all deserves its reputation. Before you use it, ask a single question: does every person on this list need this sentence? “Thanks!” to forty people is forty interruptions. Reply-all is right when the answer corrects a factual error others received, when it prevents duplicate work, or when the thread is a genuine group decision. It is wrong for acknowledgments, jokes, side questions, and anything about one person’s performance.

Forwarding, quoting, and the permanent record

Forwarding is the most underestimated risk in email, because it moves words you wrote for one audience into another audience’s context without your knowledge. Before you forward, scroll to the bottom of the chain. Old messages accumulate: a candid assessment of a vendor, a salary figure, a colleague’s medical absence, an early draft with errors in it. Trim the thread to what the new reader needs, and add one line of framing so they know why they have it: “Forwarding for the equipment specs in the last message — earlier discussion trimmed.”

The permanence cuts both ways, and the constructive side matters more day to day. Email is where you document that a decision was made, that a concern was raised, and that a task was handed off. If you raise a safety concern verbally and nothing changes, a short factual follow-up — “Confirming our conversation this morning: I reported that the second glucometer is reading 20 points high, and you asked me to take it out of service and notify biomed, which I have done” — protects patients, protects you, and creates the record that makes systemic problems visible. Write those messages neutrally, without blame, and stick to what you observed and what you did.

Confidentiality and the mis-sent message

Address auto-completion is a leading cause of everyday confidentiality breaches. You have two contacts named Sarah, one internal and one at a vendor, and the message meant for the first goes to the second. In healthcare, sending PHI (protected health information) to the wrong recipient is an impermissible disclosure that must be assessed and, unless the risk of compromise is shown to be low, reported under HIPAA’s breach notification rule. Education records are protected differently: FERPA restricts disclosure of student records without consent and requires the institution to record the disclosure, but — unlike HIPAA — it contains no breach-notification requirement, so any duty to notify students comes from state breach law or institutional policy rather than from FERPA itself. Many organizations also impose their own rules on financial and personnel data.

Practical protections are unglamorous and effective. Type the recipient last, after the message is written, so a stray keystroke cannot send a draft. Verify the full address, not the display name — auto-complete shows you the name it has decided you meant. Follow your organization’s rules on encryption and secure-send tags rather than improvising. Use the minimum identifying information the message actually requires; a medical record number alone is often enough where a name plus a date of birth is not, though the number is itself PHI. And never put confidential detail in a subject line, which is visible in notification previews on unlocked phones and on shared screens.

If you do send in error, act immediately: notify your supervisor or privacy officer, do not rely on a recall function that works only inside your own organization and only sometimes, and follow the incident process. Speed matters more than composure here, and the cover-up is always more damaging than the mistake.

Attachments, follow-ups, and closing the loop

Say what the attachment is and why it is attached, in the body: “Attached: revised fall-risk protocol (PDF, 6 pages). Changes are in section 3.” Name files so they make sense on someone else’s desktop — “FallRisk_Protocol_v3_2026-03-14.pdf” rather than “final final FIXED.pdf”. Send PDFs when the document should not change and an editable format when you want edits back. Attach the file before you write the body, or attach it the moment you first mention it; the forgotten attachment is the most common reason anyone sends a second email.

Follow-ups should be brief, dated, and free of grievance. “Following up on my 3/2 request” plus a restatement of the ask plus a new date is the entire genre. Do not write “as I mentioned twice already”; it adds nothing except a record of your irritation. Escalate on a schedule rather than on emotion: a follow-up after a few business days, a second with a named consequence, then a phone call, then a manager — and tell the person before you involve their manager.

Finally, close loops. When someone does what you asked, say so briefly, and when a thread ends, mark it: “Received — nothing further needed. Thanks.” This costs six seconds and prevents the follow-up asking whether anything arrived.

Words worth knowing