Most email delegation fails before it starts. You hand off your inbox to an assistant, they send a reply that doesn't sound like you, and you spend the next hour cleaning it up. The problem isn't the assistant. It's that you never gave them a real email response system to work from. Without documented preferences, even a great assistant is guessing. This guide covers exactly what to put in an email SOP so your assistant can handle your inbox with minimal back-and-forth.
What Should an Email Response System Include?
An email response system is a written document that tells your assistant how to handle your inbox. Think of it as an operating manual for your communication. It doesn't need to be long, but it does need to be specific.
The core components are:
- Priority senders: A list of people whose emails always get a same-day response, no matter what
- Categories to ignore or archive: Newsletters, automated notifications, cold outreach that doesn't meet a threshold
- Response time expectations: What counts as urgent, what can wait 24 hours, and what can wait a week
- Escalation triggers: The specific situations where your assistant should flag you before replying
- Tone and sign-off: How formal you are, what you call people, how you close emails
This document doesn't replace judgment. It builds the foundation so your assistant can exercise good judgment instead of defaulting to caution on every email.
How Do You Set Sender and Topic Priorities?
The most useful part of any email SOP is a clear priority framework. Not all email is equal, and your assistant needs to know the difference between a message from your biggest client and a newsletter from a vendor.
Start by dividing senders into three tiers. Tier one is anyone your assistant should treat as urgent: key clients, investors, your co-founder, direct reports, and anyone you've told them to watch for. Tier two covers important but not urgent contacts, like vendors, partners, and warm prospects. Tier three is everything else, including cold outreach, automated messages, and anything that can be batched or archived.
Do the same for topics. Requests that involve money, legal matters, or public commitments should always get flagged. Status updates and scheduling requests can usually be handled directly. Informational emails can often be archived with a brief acknowledgment.
According to Harvard Business Review, knowledge workers spend an average of 28% of their workday on email. A clear priority system is the fastest way to cut that number without missing anything that matters.
How Do You Document Your Tone and Drafting Style?
This is where most email SOPs fall short. People document what to respond to but not how. Then they read a draft their assistant wrote and think, "I would never say it that way."
The fix is to include a short style guide in your email system. It doesn't need to be elaborate. A few sentences covering your defaults goes a long way:
- Do you use first names or titles? ("Hi Sarah" vs. "Hi Ms. Chen")
- How formal is your default tone? (Casual and direct vs. polished and professional)
- What's your standard sign-off? ("Best," "Thanks," "Cheers")
- Are there phrases you always use or never use?
- How long should a typical reply be? (Two sentences or two paragraphs?)
Include two or three example emails you've written in the past. Real examples are worth more than any description. Your assistant can use them as a reference point when drafting replies.
Tools like River Executive Assistant learn your communication style over time, which means the drafts get sharper the longer you use it. But even an AI assistant benefits from an explicit style guide at the start.
How Do You Keep the System Updated?
An email SOP that's six months out of date is almost as bad as having none. Your priorities change, your client list changes, and your communication style evolves. The system needs to keep up.
The simplest approach is a monthly five-minute review. Scan the document and ask: has anything changed? New clients to add to tier one? Topics that should now trigger an escalation? Phrases that no longer sound like you?
You can also update it reactively. When your assistant handles something in a way that doesn't match your expectations, use that as a prompt to add a clarification to the SOP. Over time, the document gets sharper and the back-and-forth decreases.
Atlassian's guide to SOPs makes a useful point: the best operating procedures are living documents, not one-time projects. Build a habit of updating yours and it stays useful.
River Executive Assistant makes this easier by surfacing patterns in how you handle email, so you can spot gaps in your system without having to audit every thread manually.
Putting It Together
A good email response system doesn't take long to build. Most people can write a solid first draft in under an hour. Start with your priority senders, add your escalation triggers, document your tone with a few examples, and set basic response time expectations. That's enough to get your assistant handling 60-70% of your inbox without constant guidance.
The payoff compounds quickly. Once your assistant understands your system, you stop reviewing every draft and start only seeing the emails that actually need your attention. Whether you're working with a human EA or an AI tool like River Executive Assistant, the system is what makes delegation stick. Build it once, refine it over time, and your inbox stops being a daily burden.