Email Writing Practice Test: Write Clear, Professional Emails
True / False
True / False
Select all that apply
Put in order
True / False
Select all that apply
Put in order
Select all that apply
Put in order
Put in order
Select all that apply
Five High-Impact Email Writing Habits This Quiz Reinforces
- Make the subject line do real work: include the topic + needed action + time cue (e.g., “Approve Q2 Budget Draft by Wed 3 PM”).
- Lead with purpose in the first two lines: state the reason for writing and the recipient’s role so the message is scannable on mobile.
- Write a single, unambiguous ask: use a verb + owner + deadline + time zone (and specify what “done” looks like).
- Control tone with word choice, not punctuation: replace exclamation points and vague “just checking” language with respectful, specific phrasing.
- Treat every email as a record: minimize sensitive data, name attachments clearly, and keep the thread easy to audit and forward.
Common Professional Email Errors That Create Delays, Rework, and Audit Risk
Most email problems aren’t “grammar issues”—they’re decision and documentation failures. These are the mistakes the quiz is designed to surface and correct.
Vague subjects that don’t route work
Mistake: “Quick question” or “Update.” Fix: include the project/topic + action + timing (if any). A good subject line prevents misfiling and speeds triage.
Buried or missing call-to-action
Mistake: explaining for three paragraphs and ending with a soft “let me know.” Fix: put the ask up front, then add only the context required to decide.
Ambiguous deadlines and approvals
Mistake: “by EOD,” “ASAP,” or “sometime tomorrow.” Fix: specify date, time, and time zone; define approval criteria (e.g., “Reply ‘approved’ or list changes”).
Tone mismatch and unnecessary heat
Mistake: sarcasm, all-caps, multiple exclamation points, or blaming language in a thread that may be forwarded. Fix: use neutral facts, one clear request, and a courteous close.
Sloppy threading and unclear references
Mistake: changing topics mid-thread, replying without quoting enough context, or using pronouns (“it,” “they”) with multiple possible meanings. Fix: start a new thread when the topic changes; name the document, version, and decision needed.
Attachment and recipient errors
Mistake: sending “final_v7_REALfinal.docx” or misusing CC/BCC. Fix: use a naming convention (project + date + version); sanity-check recipients before sending—especially when content is sensitive.
Bottom line: clear emails reduce cycle time, protect relationships, and lower the chance that a written record undermines you during audits, investigations, or disputes.
Clear, Professional Email Writing One-Page Reference (Print/Save as PDF)
Use this as a desk reference. You can print this page or save it as a PDF for quick review before high-stakes emails.
Core standard: the “5 Cs” quality check
- Clear: one topic, one primary outcome.
- Concise: cut throat-clearing (“Just reaching out to…”).
- Correct: names, dates, totals, file versions, links/paths (if used internally).
- Courteous: neutral tone; assume good intent.
- Complete: recipient has what they need to act (who/what/when).
Subject line formula (fast + specific)
- [Action] + [Object] + [Deadline/Timing]
- Examples: “Review Vendor Quote #218 by Tue 2 PM PT” / “Decision Needed: Training Schedule for April”
Body structure (BLUF + details)
- Greeting matched to relationship (formal for first outreach).
- BLUF (Bottom Line Up Front): why you’re writing + the ask.
- Context: 1–3 sentences or a short bullet list.
- Action items: bullets with owner + due date.
- Close: confirm next step; include signature block.
Clear call-to-action checklist
- Verb: approve, confirm, send, review, decide, sign.
- Owner: who must act (name or role).
- Deadline: include date + time + time zone.
- Definition of done: “Reply ‘approved’” or “Track changes in the doc.”
Editing pass (60 seconds)
- Cut filler: “I just wanted to,” “for your convenience,” “at this point in time.”
- Replace vague words: “soon” → “by Mar 23, 4 PM ET.”
- Scan for risk: remove unnecessary sensitive info; keep only what the recipient must know.
- Attachment check: correct file, clear name, referenced in the body, and included.
Real-World Email Scenarios: Write the Subject, Opening, and Ask
Use these drills to practice the same micro-decisions the quiz scores: subject line clarity, first-line purpose, tone, and an actionable close.
1) Status update with a deadline risk
You’re leading Project Atlas. A dependency slipped, and Friday’s deliverable may move by two business days. Draft: (a) a subject line, (b) a two-sentence opening that states impact, (c) one clear ask for stakeholders.
2) First-time outreach to a hiring manager
You’re following up after submitting an application. Draft a formal greeting, a one-sentence purpose statement, and a closing line that is confident but not pushy.
3) Clarifying an ambiguous request from your boss
Your manager emailed: “Can you handle the report?” Draft a reply that confirms scope (which report/version), deadline (date/time), and what format they want—without sounding defensive.
4) Getting approval on a document revision
You updated a policy draft based on feedback. Draft a subject line and a bulleted CTA that tells reviewers exactly how to approve (or request changes) and by when.
5) Replying in a heated thread
A client wrote an angry email blaming your team for delays. Draft a response that acknowledges the concern, states a neutral fact, and proposes a next step (meeting time window or specific information you need).
6) Sending files externally
You must send a spreadsheet to an external partner. Create a clean file name (project + date + version), write one sentence that describes what’s attached, and add a line that sets expectations for questions or confirmation.
Email Writing Glossary (With Usage Examples)
- BLUF (Bottom Line Up Front)
- A structure that puts the purpose and request at the top so the recipient can act quickly. Example: “BLUF: Please approve the attached draft by Mar 25, 2 PM ET.”
- Call-to-Action (CTA)
- The explicit action you want the reader to take, including the deadline and success criteria. Example: “Reply ‘approved’ or list changes by Wed 3 PM PT.”
- Thread hygiene
- Keeping one topic per email thread and starting a new subject when the topic changes. Example: changing from “Invoice Question” to “Contract Renewal” in the same thread is poor thread hygiene.
- CC (carbon copy)
- Visible recipients who should stay informed or contribute. Example: CC your project sponsor on a status update that affects schedule.
- BCC (blind carbon copy)
- Hidden recipients, typically used to protect privacy in mass emails or to prevent reply-all storms. Example: BCC a distribution list when emailing external attendees so addresses aren’t shared.
- Hedging
- Softening language that can reduce clarity or accountability when overused. Example: “I was just wondering if maybe you could…” → “Could you confirm by Tuesday?”
- Action items
- Bulleted tasks with an owner and due date to prevent back-and-forth. Example: “Action: Jordan to send revised quote by Mar 24 EOD ET.”
Authoritative Guides for Writing Clear, Professional Emails
- UW–Madison Writing Center: Advice for Students Writing a Professional EmailPractical guidance on tone, structure, and common professionalism pitfalls.
- Section508.gov: Email MessagesFederal accessibility-oriented tips that improve clarity, scannability, and usable formatting in emails.
- Digital.gov: An Introduction to Plain LanguagePlain-language principles you can apply to subject lines, openings, and action statements.
- National Archives: Top 10 Principles for Plain LanguageA concise checklist for writing that readers understand the first time.
- HHS HIPAA FAQ: Using Email to Discuss Health Issues With PatientsA compliance perspective on reasonable safeguards and avoiding unintended disclosures when email contains PHI.
Professional Email Writing FAQ: Clarity, Tone, and Risk-Control
What should a strong subject line include for professional work?
Include the topic and the intended action (if any), plus a time cue when timing matters. “Budget” is a topic; “Approve Q2 Budget Draft by Wed 3 PM ET” routes work. Avoid vague subjects (“Quick question”) because they slow triage, search, and recordkeeping.
How do I write a clear call-to-action without sounding demanding?
Be direct and respectful: verb + what + deadline + how to respond. For example: “Please review the attached draft and reply with ‘approved’ or edits by Mar 25, 2 PM PT.” Courtesy comes from neutral wording and reasonable deadlines—not from burying the ask.
When should I use CC vs BCC?
Use CC when people should be visibly informed or accountable in the thread. Use BCC to protect privacy in bulk messages (e.g., external attendees) or to prevent reply-all cascades. If someone’s involvement must be transparent for decision-making, CC is usually the better choice.
How formal should my greeting and closing be?
Match formality to relationship and risk. First-time outreach, external partners, or sensitive topics generally warrant more formality (“Dear Ms. Patel,” / “Sincerely,”). Internal, familiar threads can be lighter (“Hi Jordan,” / “Thanks,”) as long as clarity stays high.
How can email wording create compliance or legal problems?
Email is often a discoverable business record. Avoid unnecessary sensitive data, speculation, or emotionally loaded phrasing that can be forwarded or reviewed later. In healthcare settings, apply reasonable safeguards for PHI and minimize what you include in unencrypted messages. If you want to tighten verb tense consistency in emails, review Tenses Quiz: Test Your English Grammar Online for Free.
