Why Most VA Feedback Fails to Change Behavior
The most common form of feedback business owners give to their virtual assistants is reactive and vague: "This report doesn't look right," "Can you be more careful with emails?" or "This isn't what I asked for." These comments identify that something is wrong but provide no actionable path to fixing it.
According to a 2024 study by Gallup, 80% of employees who say they received meaningful feedback in the previous week report being fully engaged at work — versus only 40% who received no recent feedback. The same dynamic applies to VA relationships: quality feedback drives engagement, and poor feedback drives disengagement.
The templates below give business owners a framework for three distinct types of feedback: positive reinforcement, error correction, and improvement requests. Using the right format for the right situation increases the likelihood of behavioral change.
Template 1: Positive Reinforcement Feedback
Use this template when your VA does something well that you want repeated. Specific praise is far more effective than generic praise.
Subject: Great work on [Task Name]
Hi [VA Name],
I wanted to flag this specifically: [describe the task or output]. The part that stood out was [specific detail — e.g., "you caught the client's name error before the email went out" or "the report had the comparison column I had been asking for without me reminding you"].
This is exactly the standard I am looking for on [task type]. Keep doing this.
[Your name]
Why it works: Names the exact behavior, explains why it mattered, and signals what "good" looks like going forward. Takes 60 seconds to write and significantly reinforces the behavior.
Template 2: Error Correction Feedback
Use this template when a task was completed incorrectly or at a below-standard level. Separate the error from the person. Focus on the action and the correction needed.
Subject: Correction needed — [Task Name] [Date]
Hi [VA Name],
I reviewed [task name] and found an issue that needs to be corrected before [deadline/next use].
What happened: [Describe the specific error. Example: "The invoice tracker was updated with last month's figures rather than this month's totals in columns D–F."]
What needs to change: [Describe the correction. Example: "Please re-open the tracker, update columns D–F with the correct figures from the March invoices folder in Drive, and resave by 3:00 PM today."]
To prevent this next time: [Describe one process change. Example: "Going forward, please cross-check the invoice date against the month shown in the column header before saving."]
Let me know when the correction is complete.
[Your name]
What to avoid:
- Do not use "always" or "never" language ("You always miss details")
- Do not send error correction feedback when frustrated — wait 10 minutes
- Do not pile multiple corrections into one message; address each error separately
Template 3: Improvement Request Feedback
Use this template when performance is acceptable but you want to raise the standard. This is the most nuanced feedback type — it requires distinguishing between "wrong" (use Template 2) and "good but could be better."
Subject: Feedback + improvement request — [Task Type]
Hi [VA Name],
Your [task type] work this week has been solid. I want to share one area where I think we can level up the output.
Current state: [Describe what the VA is currently doing. Example: "The weekly client updates are accurate and sent on time."]
Target state: [Describe what improved looks like. Example: "The updates would be more valuable if they included the week-over-week change for each metric, not just the current figure. This gives the client context without them having to refer back to last week's report."]
How to get there: [Provide a concrete path. Example: "Starting next week, add a column called 'vs. Last Week' with a simple +/- number next to each metric. I have updated the template in Drive to include this column."]
This is not urgent, but I would like to see this format starting with next Friday's report.
[Your name]
Timing and Frequency Guidelines
- Positive reinforcement: Deliver within 24 hours of the work being completed. Delayed praise loses impact.
- Error correction: Deliver within the same business day if the error affects a deadline. Within 48 hours otherwise.
- Improvement requests: Deliver during or just before the weekly review call so there is time to discuss.
Avoid accumulating feedback and delivering it all at once in a monthly review. Feedback is most effective when it is timely, specific, and tied to a clear memory of the work being discussed.
Feedback Log Template
Maintain a simple log of feedback given. Review it monthly to identify patterns:
| Date | Feedback Type | Task/Area | Key Message | VA Response |
|---|---|---|---|---|
| Positive / Correction / Improvement |
If the same correction appears more than twice, it is a training or SOP gap — not a feedback gap. Escalate to a process update rather than sending a fourth correction message.
For business owners who want a professional team to manage VA communication standards and feedback cycles, Stealth Agents provides dedicated account management that includes regular quality review and coaching.
Feedback Template Checklist
- Positive feedback delivered within 24 hours of strong work
- Error correction separates behavior from person and includes a correction path
- Improvement requests describe current state, target state, and how to get there
- Feedback is specific — references a named task, date, or deliverable
- Feedback log maintained and reviewed monthly for patterns
Consistent, structured feedback is not a soft skill add-on. It is the management infrastructure that determines whether a VA relationship compounds in value or stagnates over time.
Sources:
- Gallup State of the Global Workplace Report, 2024
- Harvard Business Review, "The Feedback Fallacy," 2023
- SHRM Performance Feedback Best Practices, 2024