How to Give Feedback to a Virtual Assistant
See also: How to Hire a Virtual Assistant, VA Code of Conduct Template, How to Onboard a Virtual Assistant
Feedback is the primary tool for making a virtual assistant better at their job. But most feedback given in VA relationships is either too vague to act on ("This isn't quite right"), too delayed to be useful (three weeks after the problem started), or never given at all because the business owner quietly corrects the work themselves.
Effective feedback is specific, timely, and focused on the output rather than the person. This guide covers when, how, and what to say - with real examples tied to common VA tasks.
Step 1: Give Feedback Immediately, Not at the Monthly Review
The most common feedback mistake is saving it for a scheduled review. By the time a monthly check-in arrives, the VA has produced three more weeks of work in the same pattern you meant to address. Early feedback is more effective because it:
- Stops a bad habit before it becomes entrenched
- Gives the VA a chance to improve on the very next task
- Signals that you pay attention to quality, which raises the overall standard
Aim to give feedback within 24 hours of reviewing work. For high-stakes deliverables, give it the same day.
Step 2: Be Specific About What Needs to Change
Vague feedback is worse than no feedback. It tells your VA you weren't happy but gives them nothing actionable to change.
Vague: "This email reply doesn't sound right." Specific: "This email reply sounds too formal for our brand. We don't say 'Dear [Name]' - we use first name only. We also avoid passive voice ('It has been decided') - use active voice ('We've decided'). Here's an example of a reply in our tone: [link]."
Vague: "The research report is too long." Specific: "The research report should be no more than one page - five to seven bullet points per company, not paragraphs. The competitor funding section doesn't need the full investor history, just the most recent round. Here's the format I'd like going forward: [example]."
Vague: "You missed something in the calendar." Specific: "I noticed you accepted the Thursday 2pm meeting with Acme Corp, but I have a hard block on Thursdays until 4pm that I mentioned in the onboarding doc. Going forward, please check my blocked time list (linked in the calendar SOP) before accepting any meetings. If you're unsure, hold the meeting as tentative and check with me first."
The key elements of specific feedback: what was wrong, what correct looks like, and how to avoid the same mistake going forward.
Step 3: Use the SBI Feedback Model for More Complex Issues
For larger or more sensitive feedback conversations - quality that has consistently missed the mark, communication problems, or patterns of behavior - use the Situation-Behavior-Impact (SBI) framework:
Situation: Describe the specific context. "Over the last three weeks, in the weekly newsletter process..."
Behavior: Describe the observable action (not interpretation or personality). "...the subject lines have been submitted after the Thursday noon deadline in two of the three weeks, without advance notice."
Impact: Explain the effect. "This pushes the send time for the newsletter to Friday afternoon, when our open rates are significantly lower, and I'm left scrambling to approve last-minute."
Then ask for their input: "Can you tell me what's causing the delay, and what we can put in place to make sure this is consistently on time?"
This approach is direct without being accusatory. It focuses on actions and results, not character judgments, and it invites the VA into the problem-solving process.
Step 4: Give Feedback in Writing, Then Confirm Understanding
For anything more than a quick one-liner, feedback should be in writing - in a Slack message, a comment in your project management tool, or a shared Google Doc. This creates a record and gives your VA something to reference when they're completing the next version of the task.
After giving written feedback on a task, ask your VA to confirm they understand it: "Does that make sense? Any questions before you revise?" A simple confirmation prevents the awkward situation where a VA nods along but didn't actually understand what to change.
For recurring tasks, ask them to update the relevant SOP to reflect the change. "Can you update the calendar scheduling SOP to include the blocked-time rule we discussed?" This closes the loop and makes the feedback permanent.
Step 5: Balance Corrective Feedback with Positive Acknowledgment
Many managers only give feedback when something is wrong, which means their VA only hears from them about their mistakes. This creates a dynamic where the VA becomes anxious about every submission and stops taking any initiative that might draw criticism.
Balance corrective feedback with specific, genuine acknowledgment of what's working:
"The research report format you used this week was exactly right - the bullet point structure was clean and easy to scan. The only change needed is to include the LinkedIn URL for each contact in column D."
"Thanks for catching that double-booking in my calendar and resolving it without asking me - that's exactly the kind of judgment I need."
Positive feedback also serves as instruction: it tells your VA what to keep doing, not just what to stop.
Step 6: Real Feedback Examples for Common VA Tasks
Calendar management: "I noticed you scheduled two meetings back-to-back with no buffer. I need at least 15 minutes between calls to prepare and debrief. Please update the scheduling SOP to reflect this - a note that says 'minimum 15-minute gap between any two scheduled calls.'"
Inbox management: "Three emails in the 'Escalate' folder this week could have been handled with our standard template - the vendor rate question, the speaking inquiry, and the product demo request. Can you review the email response guide? If you're unsure which template applies, flag it with a one-line note explaining your thinking and I'll clarify."
Content or writing tasks: "The blog post draft is a good start - the structure is right and the research is solid. Two things to revise: the intro is 120 words but should be 60 maximum, and the conclusion is missing the CTA we discussed. Here's the CTA language to use: [paste text]."
Research tasks: "The competitor analysis missed three companies that are directly relevant - I've listed them below. Going forward, for this type of research please search both 'HR software' and 'workforce management software' since some competitors use different category terminology. Please add these three to the existing sheet."
Common Mistakes to Avoid
Fixing the work yourself without giving feedback. Your VA learns nothing, the pattern continues, and you've just given yourself extra work permanently.
Giving only end-of-month feedback. Recency bias means you'll focus on the last few things rather than the most important patterns. Give feedback as close to the work as possible.
Making it personal. "You're disorganized" is a personality judgment. "The task tracker hasn't been updated since Monday" is an observable fact. Stick to behaviors and outputs.
Cushioning feedback so much the message is lost. You can be direct and kind at the same time. The feedback should be unmistakably clear, even if delivered with warmth.
Only giving feedback, never asking for it. Ask your VA periodically: "Is there anything that would make it easier for you to do this task well? Are there areas where you feel unclear on what I'm looking for?" This surfaces blockers you might not see.
Ready to Find Your Virtual Assistant?
Stealth Agents places virtual assistants who respond well to feedback and improve quickly. Pair their VA matching with the feedback system in this guide and you'll build a strong, high-performing working relationship.
Find your virtual assistant at Stealth Agents