Introduction

Professional email is written communication that is clear, polite, and easy to act on. Even in chat-heavy workplaces, email remains the record for applications, schedules, external partners, and formal requests. A messy email can undo a strong resume or careful interview.

This lesson in Track 10 teaches structure, tone, subject lines, and etiquette. Accurate typing on TYPE10X Practice helps you send clean messages under deadline without flooding inboxes with typos.

Email is not old-fashioned—it is professional memory.

Learning Objectives

By the end of this lesson, you will be able to:

Decide when email is appropriate versus chat or meetings
Build a complete professional message from subject to signature
Manage recipients using To, CC, BCC, Reply, and Reply All
Attach files safely and describe what you need
Proofread for tone, clarity, and errors before sending

Main Lesson

When to use email

Email works well for:

Formal requests and applications
Messages that need a searchable record
Communicating with people outside your daily chat tools
Sharing documents with context
Non-urgent updates that several people must see

Use chat for quick clarifications. Use a call for sensitive or complex topics, then confirm by email if decisions must be documented—consistent with workplace communication.

The anatomy of a strong email

Subject line — Specific and scannable
Greeting — Appropriate to relationship
Opening purpose — Why you are writing in one sentence
Body — Facts, context, and asks in short paragraphs or bullets
Call to action — What you need and by when
Closing — Polite sign-off
Signature — Name, role/school, contact details

Subject lines that get opened

Weak: “Question” / “Important!!!” / “Hey”

Stronger:

“Internship application — Maya Chen — Marketing Assistant”
“Question: Saturday shift swap for March 12”
“Draft flyer attached — feedback needed by Wed 3pm”

Front-load keywords. Avoid ALL CAPS drama and clickbait.

Tone and wording

Professional tone is courteous and direct—not stiff, not casual slang.

Situation	Prefer	Avoid
Request help	“Could you please review…”	“Fix this now!!!”
Follow up	“Checking in on …”	“You ignored me”
Bad news	Clear facts + next step	Blame and sarcasm
Thanks	Specific appreciation	Empty flattery

Use complete sentences. Shrink emojis unless the culture clearly welcomes them. Mirror the other person’s formality level slightly downward only after trust is built.

Recipients: To, CC, BCC, Reply All

To — People who must act or directly answer
CC — People who should be informed (not necessarily act)
BCC — Hidden recipients; use carefully (privacy lists, avoiding massive reply storms)
Reply — Responds to sender
Reply All — Responds to everyone on the thread

Reply All only when everyone needs your answer. Accidental Reply All is a classic career embarrassment.

Attachments and links

Name files clearly before attaching
Mention the attachment in the body (“Attached: schedule.pdf”)
Check size limits
Prefer shared-drive links when policies require them
Never open unexpected attachments from unknown senders (connects to online safety habits)

Proofreading ritual (90 seconds)

Before Send:

Is the subject accurate?
Are the right people in To/CC?
Is the ask and deadline obvious?
Spell-check names and dates
Reread tone out loud once

Cold messages (applications, first contact) deserve extra care. So do emails written when you feel angry—wait and revise.

Templates you can adapt

Request:

Subject: Request — [topic] — [date needed]

Greeting → purpose → brief context → ask + deadline → thanks → signature

Thank-you after interview:

Subject: Thank you — [Role] interview — [Your Name]

Appreciate time → one specific discussion point → continued interest → contact info

Polite follow-up:

Subject: Follow-up — [original topic]

Reference prior email date → restate ask briefly → offer help → thanks

Key Definitions

Subject line — The title that summarizes the email’s purpose.
Call to action — The specific response or task you request.
CC — Carbon copy; visible informational recipients.
BCC — Blind carbon copy; hidden recipients.
Thread — A chain of related email replies.
Signature — Auto-included contact block at the end.
Netiquette — Courtesy norms for digital communication.
Tone — Perceived attitude of the writing.
Out of office — Auto-reply explaining absence and alternatives.
Confidential — Information that must not be forwarded widely.

Examples

Example 1: Clear internship email

Subject: Application for Summer Library Assistant — Jordan Lee

Body states role, availability, and that resume/PDF is attached; ends with thanks and phone.

Example 2: Bad subject rescue

From “pls read” to “Need projector confirmation for Friday workshop by noon.”

Example 3: Reply All restraint

A 20-person thread announces a room change. One person Reply-Alls “Thanks!” Create noise; a private Reply is better.

Example 4: Deadline clarity

“Please send your paragraph edits by Thursday 5pm so I can compile the final packet Friday morning.”

Real-World Scenarios

Scenario A — Wrong attachment

Sam sends an old resume draft. He follows up quickly with the correct file and a short apology. Fast correction beats silence.

Scenario B — Emotional send

After a tense shift, Nia drafts a heated complaint. She waits overnight, removes insults, states facts, and proposes solutions. The revised email gets help.

Scenario C — Missing ask

A manager receives a long story with no question. He replies “What do you need from me?” The sender learns to put the ask near the top.

Tips

Tip: Put the main ask in the first short paragraph, then add details.

Tip: Keep a personal swipe file of strong emails you have sent for reuse.

Tip: Warm up with five minutes of typing practice before writing important application emails.

Warnings

Warning: Do not put passwords, ID numbers, or highly sensitive data in ordinary email unless required by a secure process.

Warning: Forwarding private threads without permission can break trust and policy.

Did You Know

Did you know: Many professionals decide whether to open an email based only on subject line and sender name.

Did you know: A polite follow-up after several business days is normal; daily pestering is not.

Common Mistakes

Blank or vague subject lines
No clear ask or deadline
Reply All for personal thanks
Forgetting the attachment you mentioned
Typos in the recipient’s name

Interactive Exercise

Email Clinic (15 minutes)

Rewrite this message into professional form:

“hey can u send me the thing for the project my teachr needs it idk when thx”

Add a real subject, greeting, purpose, clear ask, deadline, closing, and signature.

Practice Questions

When is email better than chat?
What belongs in a strong subject line?
What is the difference between CC and BCC?
When should you avoid Reply All?
List three proofreading checks before sending.

Mini Challenge

Send (or draft for teacher review) three emails: (1) a meeting request, (2) a polite follow-up, (3) a thank-you after a conversation. Score each on subject clarity, structure, tone, and ask.

Summary

Professional email succeeds when subject, structure, tone, and recipients are intentional. Make the ask obvious, keep records clean, and proofread before you send. These written habits reinforce broader workplace communication and support smoother teamwork.

Student Checklist

[ ] I can structure a complete professional email
[ ] I write specific subject lines
[ ] I understand To/CC/BCC and Reply All judgment
[ ] I can attach files with clear naming
[ ] I completed the email clinic rewrite

Teacher Notes

Provide before/after email samples for analysis.
Run a blind subject-line contest: which get opened?
Practice Reply All scenarios with visible consequences.
Require peer proofreading for application emails.
Connect to online safety when discussing phishing-style fake “urgent” emails.

FAQ

Q: How formal should greetings be?

Start with “Dear Ms. Rivera,” or “Hello Mr. Okonkwo,” for first contact. “Hi Team,” works for familiar groups.

Q: How soon should I follow up?

Often 3–5 business days for non-urgent requests, unless a deadline requires sooner.

Q: Are emojis okay?

Usually avoid them in formal external email. Follow team culture for internal chat-like tools—not the same as email.

Q: What if I send to the wrong person?

Send a brief correction/apology quickly. If sensitive content was exposed, notify a supervisor or IT according to policy.

Q: What should I learn next?

Continue to Teamwork Skills to apply communication inside groups.

Related Lessons

Next Lesson CTA

You can now write email that is clear, polite, and actionable. Next, practice collaborating with others under deadlines: continue to Teamwork Skills.

Professional Email