Share
You hired a VA, sent them a list of tasks, and now you're spending more time managing them than you would have spent doing the work yourself. This is the most common failure mode — not the VA, not the tasks, but the management system. Or the lack of one.
Managing a virtual assistant is different from managing an in-house employee. You can't tap them on the shoulder. You can't read body language over Zoom. The feedback loop is slower, the communication is async, and the margin for ambiguity is zero. Here's the 5-rule framework Jarvis clients use to fix this.
How to Manage a Virtual Assistant: Why Most Owners Get It Wrong
The instinct when something goes wrong is to add more check-ins. More Slack messages. More oversight. That's the wrong direction. A VA who needs constant supervision isn't underperforming — they haven't been set up to perform.
One agency owner we work with was doing three daily check-ins with his VA and still felt like things were slipping. The problem wasn't the VA's work ethic — it was that tasks were being assigned without clear definitions of done. His VA was technically completing tasks but not hitting the outcome the owner had in his head. The fix wasn't more supervision. It was better task design.
See how Jarvis structures the first 30 days with every new VA to eliminate this problem before it starts.
Rule 1: Define Done Before You Assign
Every task you hand to your VA needs a clear definition of what "complete" looks like. Not "update the CRM" but "add all leads from last week's call log to GHL with status, notes, and next follow-up date by 5pm Friday." The more specific, the faster the output, and the less back-and-forth.
The one-sentence test: If you can't write the deliverable in one sentence with a due date, the task isn't ready to assign. Break it down first.
This sounds obvious but almost no owner does it naturally. They think out loud to their VA ("can you handle the email thing?") and expect the VA to translate vague intent into precise action. Some can. Most will do something reasonable that wasn't what you wanted.
Rule 2: Use Async-First Communication
Live calls and Slack pings feel like management. They're actually the opposite — they interrupt deep work, create dependency, and don't scale. The goal is a VA who works independently between defined touchpoints, not one who needs constant input.
The Jarvis communication stack: daily written update (5–7 bullet points: done, in progress, blocked), Loom videos for feedback or complex instructions, and a weekly 30-minute sync that covers the week's priorities. Everything else is async.
If your VA is messaging you more than once or twice a day with questions, that means your SOPs aren't complete. The fix is documentation, not availability. See how to write SOPs your VA can actually follow.
Rule 3: Track Outputs, Not Hours
Most owners who are new to remote management default to time tracking. They feel better seeing "8 hours logged" even if the output is mediocre. Hours are a proxy metric. What you actually want is results.
Instead of tracking hours, define 3–5 weekly KPIs for your VA. An email management VA: inbox at zero by 9am daily, response time under 4 hours, zero missed follow-ups. A GHL VA: pipeline updated daily, leads responded to within 2 hours, weekly report sent every Friday. When the KPIs are hit, you don't need to know what time they clocked in.
This also removes the guilt trip dynamic. "You only worked 6 hours yesterday" is a bad management conversation. "Three leads didn't get a follow-up" is a real one. See how Jarvis VAs report by output across different business types.
Rule 4: Give Feedback Within 24 Hours
The single most common management mistake with remote workers: waiting too long to address a problem. Something goes wrong on Monday. By Thursday you mention it. The VA has done the same thing six more times. Now it's a pattern instead of a correction.
Fast feedback loops aren't about being harsh — they're about being fair. A VA who hears "that follow-up email you sent yesterday — next time lead with X, not Y, because our clients respond better to that tone" learns and adjusts. A VA who hears "you've been writing these emails wrong for three months" feels ambushed.
Use Loom for detailed feedback — record your screen, show the specific output, explain what you wanted instead. It takes 2 minutes and removes all ambiguity. It also creates a library of examples your VA can reference.
Free: The VA Management Checklist
One-page system covering weekly KPIs, daily check-in structure, feedback cadence, and the 30-day performance review template. Already used by 40+ Jarvis clients.
Get It on Your Free Call
Rule 5: Review and Upgrade Every 90 Days
A VA who was perfect for month 1 might need different tasks by month 6. Your business grows. The ops evolve. The VA's skills should too. Every 90 days, sit down and ask: what's working, what's not, and what new systems should this VA own?
Jarvis VAs are trained on AI tools, so over time they can take on more complex workflows — automations, reporting, multi-tool processes. An owner who treats the 90-day review seriously ends up with a VA who replaces the equivalent of 2–3 people's work over 12 months. An owner who doesn't ends up replacing their VA every 6 months wondering why nothing sticks.
See how Jarvis VAs expand into automation work as they deepen their understanding of your business.
The First 30 Days: The Make-or-Break Window
More VA relationships fail in month one than at any other time. Not because the VA is bad — because the onboarding was rushed. The owner sends login credentials and a list of tasks. The VA does their best. The output is close but not right. The owner gets frustrated. The VA gets defensive. Within 8 weeks, someone quits.
The fix is a deliberate 30-day onboarding: week 1 is observation and setup, week 2 is supervised execution, week 3 is independent work with daily check-ins, week 4 is full handover with weekly reviews. See the full onboarding framework for the exact steps.
One coach we work with used to burn through VAs every 3–4 months. She implemented this onboarding and her current VA has been with her for 14 months. Same person, different system.
When the Framework Isn't Working
If you've implemented all five rules and still seeing consistent problems — missed deadlines, wrong outputs, communication gaps — it's one of three things: the VA is in the wrong role, the tasks don't match their skills, or there's a deeper issue that predates your management changes.
Jarvis replaces VAs at no extra cost if the fit isn't right after a genuine attempt at the framework. See how the guarantee works and what the replacement process looks like.
But before requesting a replacement, check the basics: Are the SOPs documented? Are KPIs defined? Has feedback been given consistently? In 80% of "bad VA" situations, the fix is in the system, not the person.