Share
You send a correction, they say "got it," do the same thing next week, you send the same correction. This loop costs more time than doing the task yourself. The problem isn't the VA — it's that the feedback isn't landing in a format that creates lasting change. Here's how to give feedback that actually sticks.
How to Give Feedback to a Virtual Assistant: Why Most Feedback Doesn't Work
Text feedback is the default, but it often fails for complex corrections. "The report format isn't right" means six different things depending on the reader. A VA who got that note last week and spent 20 minutes trying to figure out what you meant — and guessed wrong — is not ignoring your feedback. They just can't see what you see.
The three feedback killers: vague language without examples, feedback sent days after the problem occurred, and corrections that don't update the SOP. Fix all three and you'll see a different VA.
The Loom Method: Show, Don't Tell
For any feedback that requires showing what correct looks like — use Loom. Record your screen. Pull up the output. Narrate exactly what's wrong and what you want instead. Show the correct version. Total time: 2–4 minutes. Total clarity: complete.
A VA who watches a 3-minute Loom of you walking through the corrected CRM entry has 10x more context than a VA who reads "the CRM entries need more detail." And they can rewatch it. And you can link the Loom in the SOP so future VAs or backup coverage can learn from the same feedback.
This is the single most effective feedback tool for remote VA management. Clients who implement the Loom method consistently report that repeat errors on the same task drop by 80% within two weeks. See the full management framework for where Loom fits into the broader system.
The SOP Update Loop: Converting Feedback Into Permanent Fixes
Feedback that isn't captured in the SOP is temporary. You'll give the same correction three months from now, to a backup VA, or when your primary VA forgets. Feedback that gets added to the SOP is permanent — it becomes a standard that applies every time, to every person who does that task.
The loop: give feedback → show corrected version → add the correction to the relevant SOP as a specific rule → add the check to the quality checklist. Takes 5 extra minutes. Eliminates the same problem indefinitely.
The result after three months of consistent SOP updates: your SOPs become a comprehensive quality system built from every real error your VA ever made. It's the most practical quality management framework that exists for small teams. See how to structure SOPs so they're easy to update and follow.
Free: The VA Feedback Template
Three feedback formats — quick correction, Loom template, and performance review — so your VA gets clear direction every time. Get it on your consultation call.
Get the Feedback Templates
Timing: When to Give Feedback and When to Wait
Immediate (same day): Errors that will compound if repeated — wrong template, wrong pricing, wrong recipient. Any mistake that affects clients or pipeline.
Weekly summary: Patterns you've noticed across multiple tasks that week. Tone issues, formatting inconsistencies, prioritization habits. These deserve a bit more context before raising.
Monthly review: Overall performance direction — where they've grown, where the gaps are, what skills to develop next. This is the conversation, not the correction.
The rule: immediate feedback for errors, pattern feedback for trends, monthly feedback for growth. Most owners get this backwards — they hold individual errors for the weekly review (letting them compound) and mention growth direction in the same breath as a specific correction (burying both).
Positive Feedback: The Half of Feedback Most Owners Skip
Here's the contrarian take on VA management: most owners are better at correcting than acknowledging. They message quickly when something's wrong and silently accept when it's right. That ratio shapes the VA's experience of working with you — and eventually their level of initiative, quality, and longevity.
When your VA nails something — a client email that's exactly right, a CRM entry that's flawless, a report that answers a question you hadn't even asked — say so. Specifically. "That follow-up to Sarah was perfect — exactly the tone and the detail I wanted. That's the standard." Two sentences. Thirty seconds. It costs nothing and it reinforces the behavior you want more of.
A VA who only hears from you when something's wrong will eventually minimize their footprint — doing less, checking more, avoiding initiative. A VA who gets specific positive feedback builds confidence that accelerates their performance curve. See how this compounds over time when building a VA-powered growth system.
When Feedback Isn't Working: Escalating Appropriately
If you've given specific, timely, Loom-backed feedback on the same issue three times and nothing has changed — that's a performance conversation, not a feedback conversation. Address it directly: "I've given this same correction three times with examples. What's blocking you from making this change?" Listen to the answer. If it's a system problem you can fix, fix it. If it's a capability or motivation problem, escalate to a performance plan.
Jarvis clients can flag persistent performance issues directly to the Jarvis team. We review the feedback history, assess whether it's a VA fit issue or a system issue, and recommend the right path — often a different role assignment before a replacement. See what to do when the relationship isn't working for the full escalation framework.