Run an exception drill during virtual assistant onboarding

The meeting room's digital whiteboard displayed "VA Onboarding Phase 3: Competency Validation." Sarah, the onboarding lead, tapped her pen against the conference table. "We've covered all the standard operating procedures with our new virtual assistant, Alex. Their understanding of process flow and task execution is solid."

David, the department manager, nodded. "That's good. Alex is handling routine scheduling and data entry well. But what about the unexpected? We've all seen what happens when a VA encounters a request that doesn't fit neatly into a script. They either freeze, or worse, they make a judgment call with insufficient context, creating more problems than they solve."

Sarah scrolled through her notes. "Exactly. That's why I'm proposing we formalize an 'exception drill' as part of our remote onboarding. It's a structured simulation designed to test a virtual assistant's judgment and escalation process when faced with a situation outside documented procedures."

Maria, a senior virtual assistant who often helped with onboarding, chimed in. "I remember when I first started. A client once emailed me directly with an 'urgent' request for a report, bypassing their project manager. My instinct was to just do it because it sounded important. I didn't know the client had pending invoices and shouldn't receive new deliverables. It was a mess."

"That's the precise kind of scenario we need to prepare for," Sarah affirmed. "Our goal isn't to turn VAs into independent decision makers without oversight, but to equip them with the ability to identify an exception, assess its implications, and then apply the correct escalation and communication protocols. It's about testing their judgment beyond the standard procedure, and confirming they understand when to deviate from the script, and how to do it safely."

Evidence for a judgment drill

The need for an exception drill arises from common pitfalls observed in virtual assistant performance when procedures are insufficient for a given situation. While standard operating procedures (SOPs) are fundamental, they cannot anticipate every unique client request, internal conflict, or system anomaly. Relying solely on a VA's ability to follow explicit instructions leaves a significant gap in an organization's operational resilience.

Consider the frequent scenarios where VAs demonstrate excellent procedural compliance but struggle with ambiguity:

• Conflicting Instructions: A manager requests a task completed by end-of-day, but a separate, higher-priority project from another stakeholder has a conflicting deadline. The VA knows how to complete both tasks but lacks a framework for prioritizing conflicting directives.
• Unusual Client Requests: A long-standing client makes an informal request directly to the VA that contradicts an established company policy, such as sharing sensitive internal information or bypassing official approval channels.
• System Malfunction During Critical Task: A required software tool crashes in the middle of a time-sensitive process. The VA can't complete the immediate task but also doesn't know the alternative steps or who to contact for urgent support, beyond routine IT tickets.
• Information Deficiency: A task comes in with incomplete or ambiguous details, making it impossible to follow the standard procedure fully. A VA might guess, or stall, rather than proactively seeking clarification through an approved channel.
• Boundary Testing: A new team member or client attempts to push boundaries of the VA's role, asking for personal favors or tasks clearly outside the agreed-upon scope of work.

These situations are not failures of training on how to do a task, but failures in training on how to think about exceptions, how to identify when something isn't standard, and how to respond in a way that protects company interests and client relationships. The evidence points to a critical need for a structured method to evaluate and develop this specific type of judgment during onboarding.

Addressing disagreements about complexity

Introducing an exception drill often meets with initial pushback, primarily around perceived additional complexity and time commitment during onboarding. David articulated a common concern: "Won't this just add another layer of work for our onboarding leads? We're already trying to streamline the process."

Maria added, "And what if a new virtual assistant finds it overwhelming? We want them to feel supported, not immediately put on the spot with trick questions."

Sarah addressed these points by framing the drill as an investment rather than an overhead. "This isn't about creating 'gotcha' moments. It's about proactive risk mitigation. The time we spend facilitating this drill is significantly less than the time and resources required to fix an operational mistake caused by poor judgment later on. Think of the hours spent untangling a miscommunicated client deliverable or rectifying a process deviation that impacts compliance."

She continued, "Regarding it being overwhelming, the drill is designed to be a learning experience. It's a safe space to make 'mistakes' and learn the correct escalation and communication paths before they impact real work. We're not expecting perfection; we're testing their ability to recognize an exception and follow a structured response, which includes asking for help. It identifies where more targeted guidance is needed, making the rest of onboarding more efficient by focusing on true gaps."

The goal is not to test their ability to solve every problem independently, but their ability to identify a problem outside their defined scope, articulate the conflict, and escalate it appropriately, providing the necessary context to a decision maker. This structured approach reduces ambiguity and empowers the virtual assistant with a clear framework for handling the unforeseen.

A decision record

Decision Reference: OE-VA-ONBOARD-ED-001 Date: 2024-10-26 Decision Makers: Sarah Chen (Onboarding Lead), David Miller (Department Manager) Problem Statement: New virtual assistants, while proficient in following standard operating procedures, frequently lack a structured approach for handling requests or situations that deviate from documented processes, leading to operational inefficiencies, client dissatisfaction, or policy breaches. Proposed Solution: Implement a mandatory "Virtual Assistant Exception Drill" as a component of Phase 3 Onboarding: Competency Validation. Alternative Solutions Considered:

1. More Extensive SOPs: Dismissed. Impossible to document every conceivable exception; leads to unwieldy, unreadable documentation.
2. Ad-hoc Mentoring: Dismissed. Inconsistent learning experience, relies on reactive problem-solving rather than proactive skill assessment. Decision Criteria:

• Must assess judgment beyond procedural adherence.
• Must provide a safe, structured learning environment.
• Must identify specific areas for further coaching.
• Must be repeatable and standardized. Success Metrics:
• Reduced incidents of VAs making independent, unauthorized decisions on exceptions within first 90 days.
• Increased frequency of VAs appropriately escalating exceptions.
• Positive feedback from VAs on the clarity provided by the drill. Owner of Drill Process: Onboarding Lead (Sarah Chen) Review Cycle: Annually, or after significant changes to VA roles or company policy.

Worked example: the unofficial urgent request

Here is a typical scenario for an exception drill, designed to assess a virtual assistant's judgment and escalation process.

Scenario Setup:

The onboarding lead presents the following situation to Alex, the new virtual assistant:

"Alex, your primary task today is to process all outstanding support tickets. Our standard procedure states that all client communications and requests must be logged and managed through our CRM system, and that you should prioritize tickets by age, then severity.

"However, you just received a direct message in our internal chat tool from Mark Johnson, a high-value client. His message reads: 'Alex, I need the latest quarterly sales report from Q3 immediately. Can you pull it and email it to me directly? This is urgent for a presentation I have in 15 minutes. Don't worry about the CRM, just send it.'

"Assume you know how to pull the report from our reporting system. What is your immediate intended action, and what is your reasoning?"

VA's Initial Reaction (Common Failure Point):

A common initial response from a VA solely focused on speed and client satisfaction might be: "I would immediately pull the report and email it to Mark, then log it in the CRM afterward if I have time, since he said it was urgent."

This response, while well-intentioned, bypasses critical procedures: using the CRM for all communication, understanding the formal report request process, and potentially overlooking any internal holds or specific distribution protocols for high-value reports. It shows a failure to identify the conflict between urgency, client status, and established policy.

Facilitator Intervention and Correction:

The onboarding lead would then engage Alex with a series of questions:

• "You mentioned urgency. What is our standard process for urgent requests, and does this request fit that criteria?"
• "What are the potential implications of sending a report directly, outside the CRM, and without formal logging?"
• "Who typically approves the distribution of high-value reports, and have you confirmed Mark is on the approved distribution list for this specific report version?"
• "What would be the first step you'd take to ensure you are adhering to company policy while still trying to support Mark's urgency?"

Through this guided inquiry, Alex would be prompted to recognize the policy deviations and the potential risks. The onboarding lead would then clarify the correct approach:

Numbered Procedure for Exception Drill Response:

1. Acknowledge and Validate Urgency (VA): Respond to Mark's chat immediately, confirming receipt of his request and acknowledging the stated urgency. Do not promise direct fulfillment.
2. Identify Policy Conflict (VA): Recognize that the request bypasses the CRM and potentially other internal controls for report distribution.
3. Consult Internal Resources (VA): Briefly review the "Urgent Client Request" and "Report Distribution Policy" documentation, if available, or recall relevant training.
4. Formulate Escalation Plan (VA): Determine the appropriate internal contact for this specific type of exception (e.g., Mark's account manager, the compliance team, or the onboarding lead/direct manager).
5. Communicate and Escalate (VA): Inform Mark that while you understand the urgency, company policy requires all requests to go through the CRM for tracking and compliance. Offer to help him submit the request via the correct channel, or state you are escalating his urgent need to his account manager or your supervisor for immediate review and override approval, if possible.
6. Document the Interaction (VA): Log the entire interaction (Mark's request, your response, and any escalation) within the CRM or designated exception log, even if the request was made via chat.
7. Follow-Up (VA): Ensure the account manager or supervisor has addressed the urgent request, and confirm the resolution with Mark.

This process ensures that even under pressure, the virtual assistant adheres to principles of accountability, risk management, and proper communication.

The following table provides a framework for the VA's internal decision process during an exception drill:

Knowledge Consolidation: After the drill, Alex would be asked to summarize the key learnings, particularly the importance of structured escalation and the criteria for identifying an exception. This might involve adding a note to a personal onboarding journal or contributing to an internal FAQ for future VAs.

Frequently asked questions

When is the best time to run an exception drill?

The optimal time is after a virtual assistant has completed initial training on standard procedures and policies, typically in the final phase of onboarding before full independent task execution. This ensures they have a baseline understanding to compare against the exception.

How long should an exception drill take?

A well-designed exception drill, including the scenario presentation, VA response, facilitator's guided inquiry, and feedback, should typically take between 20 to 45 minutes per virtual assistant. The focus is on quality of interaction and learning, not speed.

What if the virtual assistant completely fails the drill?

A "failure" in an exception drill is a learning opportunity. It indicates a clear gap in judgment or policy understanding. The response should be constructive feedback, re-training on relevant policies, and perhaps a follow-up drill with a simpler scenario. It's an assessment, not a pass/fail test for employment.

Who should facilitate these drills?

The onboarding lead, a direct manager, or a senior virtual assistant with specific training in exception handling and company policy interpretation are ideal facilitators. They must possess a deep understanding of company procedures, escalation paths, and the virtual assistant's role boundaries.

Review your existing virtual assistant onboarding materials this week to identify three potential exception scenarios for your first drill.