Cross-Functional · Template · Beginner · Saves 20+ hours
Email Communication Standards
Standards for professional email communication.
What's included
- Email principles
- Format guidelines
- Response expectations
- Escalation protocols
- Templates for common situations
Best used when
- Training new employees
- Improving email culture
- Client communication standards
- Reducing email volume
Why this is Gold
Email represents you professionally. These standards ensure clear, effective communication.
The template
Overview
EMAIL PHILOSOPHY
The Enduring Power of Email
EMAIL AS A PROFESSIONAL COMMUNICATION TOOL
═══════════════════════════════════════════════════════════════
EMAIL IS NOT DEAD—IT'S EVOLVED:
┌─────────────────────────────────────────────────────────────┐
│ Despite Slack, Teams, and chat tools, email remains: │
│ │
│ • The primary channel for external communication │
│ • The formal record of decisions and agreements │
│ • The default for anything requiring documentation │
│ • The cross-organization communication standard │
│ • The most searchable archive of business communication │
│ │
│ EMAIL BEST FOR: │
│ ☐ External stakeholders (clients, vendors, partners) │
│ ☐ Formal announcements and documentation │
│ ☐ Asynchronous communication needing permanence │
│ ☐ Cross-company or cross-organization messages │
│ ☐ Legal/compliance-sensitive communications │
│ ☐ Detailed information requiring reference │
│ │
│ USE SLACK/CHAT INSTEAD FOR: │
│ ☐ Quick internal questions │
│ ☐ Informal team communication │
│ ☐ Real-time collaboration │
│ ☐ Ephemeral discussions │
└─────────────────────────────────────────────────────────────┘
THE EMAIL BURDEN:
Average professional receives 120+ emails per day
Average time spent on email: 28% of workday
YOUR GOAL: Make your emails easy to read, easy to respond to,
and easy to action. Respect people's inboxes.
EMAIL PRINCIPLES:
1. FRONT-LOAD THE ASK (Don't bury the lead)
2. BE SCANNABLE (Headers, bullets, whitespace)
3. ONE TOPIC PER EMAIL (Easy to file, reply, action)
4. MAKE ACTION CLEAR (What do you need? By when?)
5. RESPECT TIME (Shorter is almost always better)
COMPREHENSIVE EMAIL STANDARDS
Section 1: Email Structure and Formatting
EMAIL STRUCTURE FRAMEWORK
═══════════════════════════════════════════════════════════════
THE IDEAL EMAIL STRUCTURE:
┌─────────────────────────────────────────────────────────────┐
│ SUBJECT LINE: [TYPE] Topic - Key Detail/Deadline │
├─────────────────────────────────────────────────────────────┤
│ OPENING (Line 1-2): │
│ State your purpose/ask immediately │
│ "I'm writing to request X by [date]." │
│ "This email confirms our decision to..." │
├─────────────────────────────────────────────────────────────┤
│ CONTEXT (2-4 sentences): │
│ Brief background needed to understand the ask │
│ Only include what the reader needs │
├─────────────────────────────────────────────────────────────┤
│ DETAILS (if needed): │
│ • Bulleted for scannability │
│ • Numbered if sequence matters │
│ • Tables for comparison │
├─────────────────────────────────────────────────────────────┤
│ CLEAR ACTION: │
│ What you need from the recipient │
│ Deadline for response/action │
│ Next steps │
├─────────────────────────────────────────────────────────────┤
│ CLOSE: │
│ Thanks/appreciation │
│ Offer to discuss/help │
│ Signature │
└─────────────────────────────────────────────────────────────┘
SUBJECT LINE FORMULAS:
┌─────────────────────────────────────────────────────────────┐
│ [TYPE] Topic - Key Detail │
│ │
│ TYPES: │
│ [ACTION] = Response or action required │
│ [DECISION] = Decision needed │
│ [REVIEW] = Review and feedback requested │
│ [FYI] = Information only, no action │
│ [URGENT] = Time-sensitive (use sparingly!) │
│ [FOLLOW-UP] = Continuing a previous thread │
│ [APPROVED] = Sharing approval decision │
│ [CONFIRMED] = Confirming agreement │
│ │
│ EXAMPLES: │
│ [ACTION] Budget Proposal - Need approval by Friday │
│ [FYI] Q2 Results Summary - Highlights and Report │
│ [REVIEW] Marketing Plan v2 - Feedback by Tuesday │
│ [DECISION] Vendor Selection - Final choice needed │
│ [CONFIRMED] Meeting rescheduled to March 15 │
└─────────────────────────────────────────────────────────────┘
FORMATTING BEST PRACTICES:
┌─────────────────────────────────────────────────────────────┐
│ ✅ DO: │
│ ☐ Keep paragraphs to 2-3 sentences max │
│ ☐ Use bullet points for lists (3+ items) │
│ ☐ Bold key information and deadlines │
│ ☐ Include white space between sections │
│ ☐ Use headers for longer emails │
│ ☐ Number questions for easy inline replies │
│ ☐ Link to documents (don't describe them) │
│ │
│ ❌ DON'T: │
│ ☐ Write walls of text │
│ ☐ Use colored fonts or unusual formatting │
│ ☐ Bury the ask at the end │
│ ☐ Attach files when links work │
│ ☐ Write "per my last email" or passive-aggressive phrases │
│ ☐ Use all caps (reads as shouting) │
│ ☐ Over-use exclamation points!!! │
└─────────────────────────────────────────────────────────────┘
Section 2: Email Templates Library
EMAIL TEMPLATES
═══════════════════════════════════════════════════════════════
TEMPLATE 1: REQUEST FOR ACTION/INPUT
┌─────────────────────────────────────────────────────────────┐
│ Subject: [ACTION] [Topic] - Need by [Date] │
│ │
│ Hi [Name], │
│ │
│ I need your [input/approval/review] on [topic] by [date]. │
│ │
│ **Context:** [1-2 sentences explaining why this matters now]│
│ │
│ **What I need from you:** │
│ 1. [Specific ask #1] │
│ 2. [Specific ask #2] │
│ 3. [Specific ask #3] │
│ │
│ **Link:** [Document/Resource] │
│ │
│ Please reply by **[Date]**. If you need more time or have │
│ questions, let me know. │
│ │
│ Thanks, │
│ [Name] │
└─────────────────────────────────────────────────────────────┘
TEMPLATE 2: DECISION REQUEST
┌─────────────────────────────────────────────────────────────┐
│ Subject: [DECISION] [Topic] - Decision needed by [Date] │
│ │
│ Hi [Name], │
│ │
│ I need a decision on [topic] by [date] to proceed. │
│ │
│ **Recommendation:** I recommend **Option [X]**. │
│ │
│ **Options:** │
│ | Option | Pros | Cons | Cost | │
│ |--------|------|------|------| │
│ | A: ___ | ___ | ___ | ___ | │
│ | B: ___ | ___ | ___ | ___ | │
│ | C: ___ | ___ | ___ | ___ | │
│ │
│ **Why I recommend Option [X]:** [Brief rationale] │
│ │
│ **Full analysis:** [Link to detailed doc if needed] │
│ │
│ If I don't hear back by [date], I'll proceed with my │
│ recommendation. │
│ │
│ Thanks, │
│ [Name] │
└─────────────────────────────────────────────────────────────┘
TEMPLATE 3: PROJECT UPDATE
┌─────────────────────────────────────────────────────────────┐
│ Subject: [FYI] [Project Name] - [Week/Month] Update │
│ │
│ Hi [Name/Team], │
│ │
│ **TL;DR:** [1-2 sentence summary of status] │
│ │
│ **Status:** 🟢 On Track / 🟡 At Risk / 🔴 Blocked │
│ │
│ **Progress this [week/month]:** │
│ ✅ [Accomplishment 1] │
│ ✅ [Accomplishment 2] │
│ ✅ [Accomplishment 3] │
│ │
│ **Coming up:** │
│ • [Next milestone 1] │
│ • [Next milestone 2] │
│ │
│ **Risks/Blockers:** │
│ 🚧 [Issue] - [What we need to unblock] │
│ │
│ **No action needed** unless you have questions. │
│ │
│ Thanks, │
│ [Name] │
└─────────────────────────────────────────────────────────────┘
TEMPLATE 4: MEETING FOLLOW-UP
┌─────────────────────────────────────────────────────────────┐
│ Subject: [FOLLOW-UP] [Meeting Topic] - Notes and Actions │
│ │
│ Hi [Attendees], │
│ │
│ Thanks for meeting today. Here's a summary: │
│ │
│ **Key Decisions:** │
│ • [Decision 1] │
│ • [Decision 2] │
│ │
│ **Action Items:** │
│ | Action | Owner | Due | │
│ |--------|-------|-----| │
│ | [Task] | @name | [Date] | │
│ | [Task] | @name | [Date] | │
│ | [Task] | @name | [Date] | │
│ │
│ **Next Meeting:** [Date/Time] or "Will schedule separately" │
│ │
│ **Open Questions:** │
│ • [Question needing follow-up] │
│ │
│ Please reply if I missed anything or got something wrong. │
│ │
│ Thanks, │
│ [Name] │
└─────────────────────────────────────────────────────────────┘
TEMPLATE 5: INTRODUCTION/WARM HANDOFF
┌─────────────────────────────────────────────────────────────┐
│ Subject: Introduction: [Name A] <> [Name B] │
│ │
│ Hi [Name A] and [Name B], │
│ │
│ I wanted to connect you two. │
│ │
│ **[Name A]:** [1 sentence about who they are and why │
│ they're relevant to Name B] │
│ │
│ **[Name B]:** [1 sentence about who they are and why │
│ they're relevant to Name A] │
│ │
│ I think you should connect because [reason/shared interest] │
│ │
│ I'll let you take it from here. Moving to BCC. │
│ │
│ Best, │
│ [Name] │
└─────────────────────────────────────────────────────────────┘
TEMPLATE 6: ESCALATION EMAIL
┌─────────────────────────────────────────────────────────────┐
│ Subject: [URGENT] [Issue] - Escalation and Help Needed │
│ │
│ Hi [Name], │
│ │
│ I'm escalating [issue] because [why this needs attention]. │
│ │
│ **Situation:** [Brief description of what's happening] │
│ │
│ **Impact:** [Business impact if not resolved] │
│ │
│ **What I've tried:** │
│ • [Action taken 1] │
│ • [Action taken 2] │
│ • [Action taken 3] │
│ │
│ **What I need:** │
│ [Specific ask - decision, resource, intervention] │
│ │
│ **Timeline:** [When this needs to be resolved] │
│ │
│ Happy to discuss live if helpful. Please let me know how │
│ to proceed. │
│ │
│ Thanks, │
│ [Name] │
└─────────────────────────────────────────────────────────────┘
Section 3: Response Time and Etiquette
EMAIL RESPONSE STANDARDS
═══════════════════════════════════════════════════════════════
RESPONSE TIME EXPECTATIONS:
┌─────────────────────────────────────────────────────────────┐
│ Email Type │ Response Time │ Notes │
├─────────────────────────────────────────────────────────────┤
│ [URGENT] │ Same day │ Use phone for true │
│ │ │ emergencies │
│ [ACTION] with date │ By date │ Or acknowledge + │
│ │ │ negotiate │
│ Client/external │ 24 hours │ Even if just "will │
│ │ │ get back to you" │
│ Internal standard │ 24-48 hours │ Acknowledge quickly │
│ [FYI] │ None required │ Read when convenient │
│ CC'd emails │ None required │ Unless asked │
└─────────────────────────────────────────────────────────────┘
ACKNOWLEDGMENT CULTURE:
┌─────────────────────────────────────────────────────────────┐
│ If you can't respond fully, ACKNOWLEDGE: │
│ │
│ "Got it—will review and respond by [date]." │
│ "Received. I'll need until [date] to give this the │
│ attention it deserves." │
│ "Thanks for sending. Looping in [person] who can help." │
│ │
│ NEVER: Leave emails hanging with no response │
└─────────────────────────────────────────────────────────────┘
EMAIL ETIQUETTE GUIDELINES:
┌─────────────────────────────────────────────────────────────┐
│ TO vs CC vs BCC: │
│ │
│ TO: People who need to take action or directly respond │
│ CC: People who need to be informed (no action expected) │
│ BCC: Large distribution lists, or when protecting privacy │
│ │
│ REPLY vs REPLY ALL: │
│ • Default to REPLY unless everyone needs to see │
│ • Use Reply All sparingly on large threads │
│ • Remove people when thread becomes irrelevant to them │
│ │
│ FORWARDING: │
│ • Add context at top explaining why you're forwarding │
│ • Review thread for sensitive info before forwarding │
│ • Trim unnecessary earlier parts of thread │
└─────────────────────────────────────────────────────────────┘
PROFESSIONAL TONE:
┌─────────────────────────────────────────────────────────────┐
│ ✅ PROFESSIONAL │ ❌ AVOID │
├─────────────────────────────────────────────────────────────┤
│ "Thanks for sending this" │ "Per my last email..." │
│ "To clarify..." │ "As I already said..." │
│ "I wanted to follow up on..." │ "Just checking in │
│ │ AGAIN..." │
│ "I may have missed the reply" │ "You never responded" │
│ "Could you help me understand" │ "This doesn't make sense" │
│ "There seems to be a │ "You made a mistake" │
│ discrepancy" │ │
└─────────────────────────────────────────────────────────────┘
Section 4: Email Management
INBOX MANAGEMENT STRATEGIES
═══════════════════════════════════════════════════════════════
PROCESSING WORKFLOW:
┌─────────────────────────────────────────────────────────────┐
│ FOR EACH EMAIL, DECIDE: │
│ │
│ DELETE: Not needed, no action │
│ ↓ (If not deleted) │
│ DELEGATE: Someone else should handle │
│ ↓ (If not delegated) │
│ DO: Takes <2 minutes? Do it now │
│ ↓ (If takes >2 minutes) │
│ DEFER: Schedule time to handle, move out of inbox │
│ │
│ GOAL: Inbox is a to-do list, not a storage system │
│ Process to zero (or near-zero) daily │
└─────────────────────────────────────────────────────────────┘
FOLDER/LABEL STRUCTURE:
┌─────────────────────────────────────────────────────────────┐
│ RECOMMENDED FOLDERS: │
│ │
│ 📁 ACTION REQUIRED │
│ (Emails you need to respond to/work on) │
│ │
│ 📁 WAITING FOR │
│ (Sent and waiting for response) │
│ │
│ 📁 READ/REVIEW │
│ (FYIs to read when you have time) │
│ │
│ 📁 ARCHIVE (or search-based) │
│ (Everything else—trust search) │
│ │
│ Optional project-specific folders if needed │
└─────────────────────────────────────────────────────────────┘
BATCH PROCESSING:
┌─────────────────────────────────────────────────────────────┐
│ DON'T: Check email constantly │
│ DO: Process in batches │
│ │
│ RECOMMENDED SCHEDULE: │
│ • Morning: Process inbox, respond to urgent │
│ • Midday: Quick check, handle new urgent items │
│ • End of day: Final processing, clear inbox │
│ │
│ FOCUS TIME: Turn off email notifications │
│ Mark yourself as "Focusing" in calendar │
└─────────────────────────────────────────────────────────────┘
Email Quality Checklist
Before clicking send, verify:
| Check | Status |
|---|---|
| Subject line is clear and specific | ☐ |
| Purpose/ask is in first 2 lines | ☐ |
| Action and deadline are explicit | ☐ |
| Right people in To/CC (not over-distributed) | ☐ |
| Formatting is scannable | ☐ |
| Tone is professional | ☐ |
| Attachments are included (if mentioned) | ☐ |
| Signature is appropriate | ☐ |
| Read it aloud—does it sound right? | ☐ |
Frequently asked questions
What is the Email Communication Standards?
Standards for professional email communication.
Who is the Email Communication Standards for?
It is built for Cross-Functionals and their teams working on Meetings. The AI coach adapts it to your company, stage, and goals.
What's included in the Email Communication Standards?
5 working sections: Overview; Section 1: Email Structure and Formatting; Section 2: Email Templates Library; Section 3: Response Time and Etiquette; Section 4: Email Management.
How long does the Email Communication Standards take to use?
It saves roughly 20+ hours versus building from scratch. Our AI coach can tailor the template to your situation in minutes, then hand you a step-by-step plan.
Is the Email Communication Standards free?
Yes. You can read the full template and start getting coached through it for free. Sign in to save your tailored version and track your next steps.
How does the AI coach help with the Email Communication Standards?
The coach teaches you the framework, asks a few questions about your business, tailors the template to you, and gives you measurable next steps to execute.