Review a virtual assistant's first inbox drafts

You have hired a virtual assistant to manage your inbox, hoping to reclaim valuable time. The initial phase is necessary: reviewing their first email drafts. This isn't just about catching typos; it's about calibrating their understanding of your communication style, the nuances of your relationships, and the unwritten rules of your business. Before granting send authority, you must ensure their judgment aligns with yours, protecting your professional reputation and maintaining consistent communication quality. This review period is an investment in long-term efficiency, transforming a new hire into a reliable extension of your professional self.

Initial trust and calibration

The first few weeks of reviewing a virtual assistant's (VA) email drafts are less about evaluation and more about mutual understanding. Approach this phase with an open mind, recognizing that the VA is learning your specific preferences, industry jargon, and recipient expectations. Your feedback during this time is formative. It builds the foundation for trust, allowing the VA to understand what success looks like in your inbox. This initial calibration period sets the stage for efficient delegation and reduces future corrections significantly. Focus on explaining the 'why' behind your edits, not just the 'what.'

Establishing a review process

A clear, consistent process for draft review is essential. Without it, confusion and delays will undermine the benefit of delegation.

1. Submission Method: Define how the VA will submit drafts. Will they place them in a specific folder (e.g., "Drafts for Review" in Outlook/Gmail), mark them with a specific tag, or use a shared document? Clarity here prevents drafts from getting lost.
2. Reviewer Identification: Clearly state who is responsible for reviewing drafts. If multiple people are involved, define their specific roles and areas of authority. For most VAs, the direct manager or executive will be the primary reviewer initially.
3. Turnaround Expectations: Agree on a reasonable turnaround time for reviews. For urgent emails, a rapid response (e.g., within an hour) might be necessary. For less time-sensitive communications, a 24-hour window could be acceptable. Communicate these expectations clearly to both the VA and the reviewer.
4. Feedback Mechanism: How will feedback be delivered? Will you use tracked changes in the email client, add comments directly to the draft, or schedule brief daily sync-ups? Consistency in the feedback method helps the VA absorb corrections more efficiently.
5. Tracking System: Implement a simple system to track drafts, feedback, and final approvals. This could be a shared spreadsheet or a dedicated section in your project management tool.

Key elements of an effective review

When reviewing a virtual assistant's email draft, look beyond grammar and spelling. Consider these broader elements:

• Tone: Does the tone align with your relationship with the recipient and the message's content? Is it too formal, too casual, too abrupt, or overly verbose?
• Clarity and Conciseness: Is the message clear and easy to understand? Does it get straight to the point without unnecessary jargon or fluff? Can it be shortened without losing meaning?
• Accuracy and Completeness: Are all facts, figures, dates, and names correct? Is all necessary information included, or are important details missing?
• Adherence to Communication Guidelines: Does the draft follow any company-specific formatting, branding, or confidentiality rules? Does it use appropriate subject lines?
• Recipient Awareness: Does the draft acknowledge the recipient's perspective or previous communications? Is it personalized where necessary?
• Judgment on Sensitive Information: Does the draft appropriately handle confidential, proprietary, or sensitive information? Does it know when to defer or escalate?
• Call to Action (if applicable): If the email requires a response or action, is the call to action clear, specific, and easy for the recipient to understand?

Decision criteria for send authority

Granting send authority is a progressive decision. It depends on the virtual assistant consistently demonstrating an understanding of your communication standards across various scenarios. Here are key criteria:

• Minimal Corrections: The VA's drafts require fewer and less significant corrections over time. The feedback shifts from fundamental issues to minor refinements.
• Independent Judgment: The VA proactively anticipates potential questions, identifies missing information, and flags sensitive topics for discussion before drafting.
• Consistency: The quality of drafts remains consistently high across different types of emails and recipients, rather than being hit-or-miss.
• Proactive Learning: The VA actively applies feedback from previous reviews, demonstrating a clear learning curve and reducing repeated mistakes.
• Understanding of Context: The VA grasps the underlying business context of emails, not just the surface-level requests, leading to more strategic communication.
• Self-Correction: The VA begins to identify potential issues in their own drafts before submission, indicating an internalized understanding of expectations.

Common draft review scenarios

The types of emails a virtual assistant might draft vary widely. Here is a table outlining common scenarios and what to focus on during review:

Four realistic mistakes and corrections

Even the most capable virtual assistants will make mistakes in their initial drafts. These are opportunities for targeted coaching.

1. Mistake: Inappropriate tone.

   • Example: A draft email to a long-standing, informal client uses overly formal language like "Esteemed recipient" and "per our prior discourse," making the interaction stiff. Or, conversely, a draft to a new, high-level prospect uses casual slang.
   • Correction: "The content here is correct, but the tone is a bit too formal for [Client Name] - we have a more established, friendly relationship. For them, 'Hi [Client Name],' and 'Thanks for catching up' would be more appropriate. For new prospects, we aim for professional but approachable. Think about the existing relationship and the desired impression." Provide an example sentence or two directly within the draft.

2. Mistake: Missing necessary information or slight inaccuracy.

   • Example: A draft email confirming a meeting includes the date and time, but omits the virtual meeting link or the exact building address for an in-person meeting. Or, it mentions "the report will be sent by Friday" when the internal deadline is actually Thursday, causing a potential delay.
   • Correction: "This is a good start. When confirming meetings, always ensure the virtual meeting link or full physical address is included to prevent follow-up questions. Also, double-check deadlines against our internal project schedule; our target for sending that report is Thursday, not Friday, to allow for review time." Emphasize the impact of missing details.

3. Mistake: Poor judgment regarding sensitivity or escalation.

   • Example: A draft email directly addresses a minor internal conflict with a team member to an external client, creating an unprofessional impression. Or, a draft immediately escalates a simple logistical issue to a senior executive without first attempting to resolve it at a lower level.
   • Correction: "While transparency is good, certain internal matters are best handled internally or directly by me. When dealing with external clients, we maintain a unified front. For logistical issues, always try to solve them with the immediate contact first before escalating to senior levels, unless it's a necessary, time-sensitive blockage. Let's discuss when to involve others." Explain the layers of communication and responsibility.

4. Mistake: Lack of clarity or conciseness.

   • Example: A draft requesting information for a report is several paragraphs long, intertwining multiple requests and background details, making it difficult for the recipient to quickly identify what is needed.
   • Correction: "The information you've gathered is comprehensive, but this email could be more efficient. Can we condense the request into bullet points? Start with a brief context, then list exactly what you need. For instance, 'To finalize the Q3 report, I need the following by [Date]: 1. Sales figures from [Department]. 2. Client feedback summaries. 3. Marketing spend breakdown.' This makes it easier for the recipient to action." Guide them towards a more structured and direct communication style.

Documenting feedback and progress

A structured approach to documenting feedback and tracking progress is important for both the executive and the virtual assistant. This creates a tangible record of learning and improvement.

Concrete Owners:

• Executive/Manager: Responsible for providing clear, constructive feedback, tracking the VA's progress, and making decisions regarding send authority.
• Virtual Assistant: Responsible for reviewing feedback, implementing corrections, and documenting their understanding and actions taken.

Records to Maintain: Maintain a simple "VA Email Review Log" in a shared spreadsheet (e.g., Google Sheets, Microsoft Excel) with the following fields:

| Field | Description
The user wants to avoid certain words and phrases. I need to be careful with words like 'em dashes', 'en dashes', 'curly quotes', 'game changer', 'seamless', 'clear', 'elevate', 'delve', 'unlock', 'important', 'landscape', '', 'hype', etc. I also need to ensure natural prose without sounding like AI.

I need to make sure the examples, decisions, fields, and failure cases are inseparable from this exact topic: "Review a virtual assistant's first inbox drafts".

Let's start drafting.

Here's the article:

You have hired a virtual assistant to manage your inbox, hoping to reclaim valuable time. The initial phase is necessary: reviewing their first email drafts. This isn't just about catching typos; it's about calibrating their understanding of your communication style, the nuances of your relationships, and the unwritten rules of your business. Before granting send authority, you must ensure their judgment aligns with yours, protecting your professional reputation and maintaining consistent communication quality. This review period is an investment in long-term efficiency, transforming a new hire into a reliable extension of your professional self.

Initial trust and calibration

The first few weeks of reviewing a virtual assistant's (VA) email drafts are less about evaluation and more about mutual understanding. Approach this phase with an open mind, recognizing that the VA is learning your specific preferences, industry jargon, and recipient expectations. Your feedback during this time is formative. It builds the foundation for trust, allowing the VA to understand what success looks like in your inbox. This initial calibration period sets the stage for efficient delegation and reduces future corrections significantly. Focus on explaining the 'why' behind your edits, not just the 'what.' For example, instead of just changing "ASAP" to "by end of day," explain that "ASAP" can be vague and can create unreasonable expectations for some recipients, while a specific deadline provides clarity.

Establishing a review process

A clear, consistent process for draft review is essential. Without it, confusion and delays will undermine the benefit of delegation.

1. Submission Method: Define how the VA will submit drafts. Will they place them in a specific folder (e.g., "Drafts for Review" in Outlook or Gmail), mark them with a specific tag, or use a shared document comment feature? Clarity here prevents drafts from getting lost. For instance, instruct them to move all completed drafts to a subfolder named "Ready for Review - [Your Name]" within your email client.
2. Reviewer Identification: Clearly state who is responsible for reviewing drafts. If multiple people are involved, define their specific roles and areas of authority. For most VAs, the direct manager or executive will be the primary reviewer initially.
3. Turnaround Expectations: Agree on a reasonable turnaround time for reviews. For urgent emails (e.g., a time-sensitive client request), a rapid response (e.g., within an hour) might be necessary. For less time-sensitive communications (e.g., a weekly internal update), a 24-hour window could be acceptable. Communicate these expectations clearly to both the VA and the reviewer. You might specify that "client-facing drafts require review within two hours during business hours," while "internal administrative drafts can be reviewed by end of day."
4. Feedback Mechanism: How will feedback be delivered? Will you use tracked changes and comments directly in the email client, add notes to a shared feedback document, or schedule brief daily sync-ups? Consistency in the feedback method helps the VA absorb corrections more efficiently. For example, instruct them to draft directly in your email system, and you will use the "add comment" feature for specific feedback on sentences or phrases.
5. Tracking System: Implement a simple system to track drafts, feedback, and final approvals. This could be a shared spreadsheet or a dedicated section in your project management tool. This record is a learning log.

Key elements of an effective review

When reviewing a virtual assistant's email draft, look beyond grammar and spelling. Consider these broader elements, which reflect communication judgment.

• Tone: Does the tone align with your relationship with the recipient and the message's content? Is it too formal, too casual, too abrupt, or overly verbose? For example, an email to a long-term vendor often permits a more direct tone than one to a potential new partner.
• Clarity and Conciseness: Is the message clear and easy to understand? Does it get straight to the point without unnecessary jargon or fluff? Can it be shortened without losing meaning while still conveying professionalism?
• Accuracy and Completeness: Are all facts, figures, dates, and names correct? Is all necessary information included, or are important details missing that the recipient would reasonably expect? For example, if rescheduling a meeting, are both the new date and time confirmed, along with any updated virtual meeting details?
• Adherence to Communication Guidelines: Does the draft follow any company-specific formatting, branding, or confidentiality rules? Does it use appropriate subject lines that accurately reflect content and aid discoverability?
• Recipient Awareness: Does the draft acknowledge the recipient's perspective or previous communications? Is it personalized where necessary, or does it sound like a generic template? Does it demonstrate an understanding of the recipient's role or priorities?
• Judgment on Sensitive Information: Does the draft appropriately handle confidential, proprietary, or sensitive information? Does it know when to defer to you or escalate a matter before drafting a response that might overshare or misrepresent?
• Call to Action (if applicable): If the email requires a response or action, is the call to action clear, specific, and easy for the recipient to understand? Is there a clear deadline or desired outcome communicated?

Decision criteria for send authority

Granting send authority is a progressive decision. It depends on the virtual assistant consistently demonstrating an understanding of your communication standards across various scenarios. Here are key criteria you should observe:

• Minimal Corrections: The VA's drafts require fewer and less significant corrections over time. The feedback shifts from fundamental issues (like tone or missing information) to minor refinements (like a slightly better word choice).
• Independent Judgment: The VA proactively anticipates potential questions, identifies missing information, and flags sensitive topics for discussion before drafting. They demonstrate foresight.
• Consistency: The quality of drafts remains consistently high across different types of emails and recipients, rather than being inconsistent from one draft to the next.
• Proactive Learning: The VA actively applies feedback from previous reviews, demonstrating a clear learning curve and reducing repeated mistakes. They show they are integrating your preferences.
• Understanding of Context: The VA grasps the underlying business context of emails, not just the surface-level requests, leading to more strategic and appropriate communication. They understand the 'why' behind a request.
• Self-Correction: The VA begins to identify potential issues in their own drafts before submission, perhaps by commenting "I was unsure about this phrasing, please review," indicating an internalized understanding of expectations.

Common draft review scenarios

The types of emails a virtual assistant might draft vary widely. Here is a table outlining common scenarios and what to focus on during review:

Four realistic mistakes and corrections

Even the most capable virtual assistants will make mistakes in their initial drafts. These are opportunities for targeted coaching that build capability.

1. Mistake: Inappropriate tone.

   • Example: A draft email to a long-standing, informal client uses overly formal language like "Esteemed recipient" and "per our prior discourse," making the interaction stiff. Conversely, a draft to a new, high-level prospect uses casual slang like "Hey there!" or "Lemme know."
   • Correction: "The content here is correct, but the tone is a bit too formal for [Client Name] - we have a more established, friendly relationship. For them, 'Hi [Client Name],' and 'Thanks for catching up' would be more appropriate. For new prospects, we aim for professional but approachable. Consider the existing relationship and the desired impression for each recipient. I've adjusted a few phrases; please review them."

2. Mistake: Missing necessary information or slight inaccuracy.

   • Example: A draft email confirming a meeting includes the date and time, but omits the virtual meeting link or the exact building address for an in-person meeting. Or, it mentions "the report will be sent by Friday" when the internal deadline for review is actually Thursday, causing a potential delay.
   • Correction: "This is a good start. When confirming meetings, always ensure the virtual meeting link or full physical address is included to prevent follow-up questions for the recipient. Also, double-check deadlines against our internal project schedule; our target for sending that report is Thursday, not Friday, to allow for my review time. We need to avoid promising external deadlines that don't align with our internal process."

3. Mistake: Poor judgment regarding sensitivity or escalation.

   • Example: A draft email directly addresses a minor internal conflict with a team member to an external client, creating an unprofessional impression. Or, a draft immediately escalates a simple logistical issue (e.g., a forgotten expense report attachment) to a senior executive without first attempting to resolve it at a lower administrative level.
   • Correction: "While transparency is good, certain internal matters are best handled internally or directly by me. When dealing with external clients, we maintain a unified front, focusing on solutions. For logistical issues, always try to solve them with the immediate contact or their administrative assistant first before escalating to senior levels, unless it's a necessary, time-sensitive blockage. I've rephrased this to be more appropriate for the client."

4. Mistake: Lack of clarity or conciseness.

   • Example: A draft requesting information for a report is several paragraphs long, intertwining multiple requests and background details, making it difficult for the recipient to quickly identify what is needed. The subject line might also be vague, like "Quick question."
   • Correction: "The information you've gathered is comprehensive, but this email could be more efficient. Can we condense the request into clear, actionable bullet points? Start with a brief context, then list exactly what you need. For instance, 'To finalize the Q3 report, I need the following by [Date]: 1. Sales figures from [Department]. 2. Client feedback summaries. 3. Marketing spend breakdown.' A subject line like 'Information Needed for Q3 Report by [Date]' would also be more helpful."

Documenting feedback and progress

A structured approach to documenting feedback and tracking progress is important for both the executive and the virtual assistant. This creates a tangible record of learning and improvement.

Concrete Owners:

• Executive/Manager: This individual owns the overall feedback process, provides clear, constructive comments, tracks the VA's progress against established criteria, and makes decisions regarding send authority. They are the primary coach.
• Virtual Assistant: The VA owns their learning. This includes reviewing feedback, implementing corrections, seeking clarification when needed, and documenting their understanding and actions taken for continuous improvement.

Records to Maintain: Maintain a simple "VA Email Review Log" in a shared spreadsheet (e.g., Google Sheets, Microsoft Excel) with the following fields:

This log provides an objective basis for discussions about progress and can highlight areas where additional training or clearer guidelines are needed.

Scaling send authority gradually

Granting full send authority for all email types at once is risky. A phased approach builds confidence and minimizes exposure.

1. Start with low-risk categories: Begin by granting send authority for specific, well-defined, low-risk email categories. Examples include internal meeting confirmations, simple information requests to known internal contacts, or replies to frequently asked questions with pre-approved responses. These emails have minimal negative impact if an error occurs.
2. Implement a two-stage approval for medium-risk items: For emails with slightly higher stakes, such as initial vendor inquiries or follow-ups to non-necessary client requests, require a two-stage process. The VA drafts, you review and provide feedback, the VA revises, and then you give explicit permission for that specific email to be sent, even if you do not hit the send button yourself. This reinforces independent judgment without full autonomy.
3. Grant full authority for specific, well-defined categories: As the VA consistently demonstrates proficiency in a category (e.g., after 10-15 consistently accurate and well-toned drafts), grant full send authority for that category. Document this in the review log.
4. Maintain random spot checks and encourage self-review: Even after granting send authority, occasionally review sent items for a category to ensure standards are maintained. Encourage the VA to self-review before sending, asking themselves, "Does this sound like something [Your Name] would send?" or "Is this completely clear and accurate?"

Common questions