How to Manage a Virtual Assistant: A Practical Guide
Key Takeaways
- Track deliverables, not hours - a weekly output scorecard replaces most status meetings.
- A daily EOD update from your VA (3 lines: done, in-progress, blocked) eliminates 80% of status questions.
- The weekly priorities doc is the most effective management tool for remote VAs - update it every Monday.
- Specific, timely feedback retains good VAs longer than salary alone.
- Most management problems trace back to unclear expectations, not VA performance.
- Write an AI use policy before your VA starts - it prevents data leaks and unlocks faster output on research and drafting tasks.
Hiring a virtual assistant is the easy part. Managing one well is where most business owners lose time.
The common mistake is managing a VA the way you manage in-person employees - with ad hoc requests, verbal instructions, and assumed context. VAs work remotely, often across time zones, with limited visibility into your business priorities. Without deliberate structure, the output quality drops and both sides end up frustrated.
This guide covers the mechanics: how to set expectations, communicate effectively, track output, and run a management system that takes less than two hours per week of your time.
Before Your VA Starts: Foundation Documents
Most VA management problems are planted before day one. The fix is documentation.
Role Brief (write this once, update it quarterly)
A role brief is a one-page document that answers:
- What does this role cover? (Task categories, not individual tasks)
- What hours and time zone are required?
- What tools does the VA have access to?
- What does success look like in 30, 60, and 90 days?
- What is out of scope for this role?
Stealth Agents provides a role brief template during onboarding - or you can write one in a shared Google Doc in under 30 minutes.
Weekly Priorities Doc
Create a shared Google Doc or Notion page titled "Weekly Priorities." Every Monday, list the top 3 to 5 tasks or projects for the week. Your VA checks it first thing and uses it to prioritize when competing requests come in.
This single document eliminates 60 to 80% of the "what should I work on?" questions that consume manager time in the first 90 days.
SOP Library
For every recurring task, write a one-page standard operating procedure. The format: task name, frequency, step-by-step instructions, tools used, how to handle edge cases, and how to mark complete. Record a short Loom walkthrough for any multi-step workflow.
Your VA cannot guess your preferences. SOPs replace guessing with reliable execution.
Communication Rhythms
Remote management lives or dies on communication structure. Ad hoc messaging creates noise and misses blockers.
Daily EOD Update
Ask your VA to send a short daily update at the end of their shift. The format:
Completed today:
- [task 1]
- [task 2]
In progress:
- [task 3] - 60% done, will complete tomorrow
Blockers:
- Need your approval on [X] before I can proceed
This takes your VA 5 minutes to write. It replaces daily status calls and gives you full visibility without real-time availability.
Weekly Check-In
A 30-minute weekly call or async Loom exchange covers:
- What went well last week
- What got stuck and why
- Top 3 priorities for the coming week
- Any feedback in either direction
Skip reading out the status update - your VA already sent that in writing. Use the meeting for judgment calls, course corrections, and context your VA cannot get from documentation.
Response SLA Agreements
Set explicit expectations for response times:
- Your VA responds to messages within 4 business hours
- You respond to blocker questions within 24 hours
- Urgent items (use a tag or emoji flag) get a 2-hour turnaround
Write these in the role brief. The most common source of VA frustration is waiting on decisions with no clarity on how long to wait.
Tracking Output Without Micromanaging
The temptation when managing remotely is to track hours. Hours measure presence, not output.
Output-Based Tracking
Build a simple weekly scorecard with 4 to 6 KPIs tied to the VA's core responsibilities. Examples:
| Role Type | KPIs |
|---|---|
| Executive admin | Emails processed, meetings scheduled, inbox zero items |
| Customer service | Tickets resolved, first-response time, satisfaction score |
| Marketing ops | Posts scheduled, leads entered in CRM, reports delivered |
| Research | Briefs completed, sources cited per brief, deadlines met |
Review the scorecard monthly - not daily. If output is on target, the management loop is working.
When to Use Time Tracking
Time tracking is appropriate for:
- Project-based billing where you pay per deliverable plus hourly
- New VAs in their first 30 days while you calibrate workload
- Roles with highly variable output such as creative work or research
Tools like Toggl and Hubstaff allow voluntary time tracking without activity screenshots. Avoid screenshot-based monitoring - it signals distrust and increases VA turnover.
Giving Feedback That Actually Changes Behavior
The most common VA management mistake: vague feedback, delivered late.
"Be more careful" is not actionable. "The report had the wrong date range, which I caught just before it went to a client - in future, please double-check the date filter before sending" is actionable.
Use this three-part structure for corrective feedback:
- Situation: what specifically happened
- Impact: why it mattered (client saw it, deadline was missed, I had to redo it)
- Preferred behavior: exactly what to do differently
Deliver feedback within 24 hours. Feedback given three days after the event is half as effective because the VA cannot recall the specific context.
Positive feedback matters as much as corrective feedback. Name what the VA did and why it was effective: "The research brief was exactly the right depth - three sources per claim, no fluff. That is the standard for this client going forward." Specific praise creates repeatable behavior.
Performance Reviews
Run a formal 90-day review after your VA's first quarter. Cover:
- Output quality against the scorecard
- Communication reliability (did updates arrive consistently, were blockers flagged early)
- Initiative (did the VA proactively solve problems or wait for instructions on everything)
- Role fit (is the current scope still accurate, or should it expand or contract)
After the first 90 days, quarterly reviews are sufficient for a stable engagement. The 90-day review is the most important - it is when you decide whether to expand the role, add a second VA, or make a change.
Scaling from One VA to a Team
Once one VA is running smoothly, most business owners expand within 6 to 12 months. The jump from one to three VAs requires a different management structure.
For two VAs: Keep separate role briefs. Use a project management tool (ClickUp, Asana) to assign tasks instead of direct messages - this gives you a single view of all work in progress.
For three or more VAs: Designate a lead VA who handles cross-VA coordination and surfaces blockers to you. You manage the lead; the lead manages the team's day-to-day output. This is the architecture most businesses use to operate 5 to 10 VAs without adding a full-time manager.
Centralized SOPs: Move your SOP library into a shared team wiki (Notion or ClickUp Docs). All VAs reference the same procedures. When one VA improves a process, the improvement benefits the whole team.
Managing AI-Enhanced VAs
In 2026, most VAs use AI tools - ChatGPT, Claude, Perplexity, or similar - for research, drafting, and summarization. This is a productivity multiplier, not a problem. A VA with AI access completes research briefs and first-draft emails 2 to 3x faster than one without. Your job as the manager is to set the boundaries before they start, not after an incident.
Write an AI Use Policy (One Paragraph, Before Day One)
Your policy needs three things:
- Permitted tools: List which AI tools are approved. Most managers approve ChatGPT or Claude for writing and research tasks but block proprietary or uncertified tools.
- Data boundaries: Specify what cannot go into an AI prompt: client names and contact details, financial figures, proprietary processes, legal communications, or anything under NDA. If the VA is not sure, the rule is: do not input it.
- Review requirement: AI-assisted output that goes to clients, partners, or the public must have a human read-through before it leaves the VA's hands. Factual claims in research briefs need source verification.
Post this policy in your shared SOPs folder. Revisit it when you add new tools or the VA's scope changes.
Add AI Output Quality to the Scorecard
Track AI-assisted deliverables separately from manual ones until you have calibrated the VA's review quality. Example KPI addition for a research VA: "Research briefs: all factual claims include source URL." This catches AI hallucination before it reaches a client without requiring you to read every output.
Common AI Management Mistakes to Avoid
Banning AI entirely. A VA who cannot use AI tools is slower and less competitive. The risk is in misconfigured data access, not the tool itself.
No data boundary training. Most VAs understand AI tools but have not thought through which client data is confidential. A 10-minute walkthrough of your data boundaries prevents the most common incidents.
Expecting AI to replace VA judgment. AI assists with speed and drafting. It does not replace the VA's role in fact-checking, tone calibration for your specific clients, or catching context the model does not have. Frame AI as a first-draft tool, not a replacement for the review step.
Common Management Mistakes
Not writing SOPs before handing off tasks. Your VA will try to infer your preferences from your requests and make mistakes. SOPs eliminate inference.
Managing by Slack DM. Real-time chat is inefficient for task management. Use a project management tool so every task has a status, deadline, and owner.
Skipping the weekly check-in when things are going well. Silence is not feedback. A VA who never hears from you does not know they are meeting expectations and will eventually disengage.
Expanding scope too fast. Wait until current responsibilities are stable before adding new task categories. Overloading a VA before they have built context leads to quality drops across the board.
Mixing personal and business tasks without clear boundaries. If you want a VA to handle both business admin and personal scheduling, write it in the role brief. Assume the boundary is business-only unless you explicitly state otherwise.
Next Steps
For the mechanics of bringing a VA on before the management phase begins, read the onboarding checklist - it covers everything from access provisioning to week-4 performance gates.
If you are still evaluating the cost of adding a VA to your team, the virtual assistant cost guide breaks down hourly rates, monthly packages, and the true cost of ownership across hiring models.
Ready to match with a VA? Book a free consultation - Stealth Agents presents candidates within 24 hours of your role brief.
Frequently Asked Questions
How do you manage a virtual assistant effectively?
Effective VA management comes down to three things: clear written expectations (role brief and weekly priorities doc), a structured communication rhythm (daily EOD update and weekly check-in), and output-based tracking rather than hour surveillance. Most VA management problems trace back to unclear expectations set at the start, not the VA's competence.
How often should I check in with my virtual assistant?
A daily written EOD update and a weekly 30-minute video or async check-in works for most setups. Daily calls are too time-intensive and signal micromanagement. Less than weekly leads to misalignment and missed blockers. After 90 days with a reliable VA, many managers shift to biweekly calls and rely on the daily written update for continuity.
How do I know if my virtual assistant is actually working?
Track deliverables instead of monitoring activity. Set clear weekly targets - for example, 50 emails processed, 10 LinkedIn connections sent, 3 reports completed - and review them weekly. If output is consistently meeting targets, the question of whether they are working becomes irrelevant. For roles where time tracking matters, tools like Toggl or Hubstaff provide voluntary tracking without screenshots.
What should a virtual assistant daily update include?
A good daily update takes under 5 minutes to write and covers three things: what was completed today, what is in progress and where it stands, and any blockers or decisions needed from you. Keep it to bullet points, not paragraphs. If your VA is not sending daily updates, set the expectation in writing - most VAs will adopt the habit within a week.
How do I give feedback to a virtual assistant?
Give feedback within 24 hours of seeing an issue, in writing, using a three-part format: situation (what happened), impact (why it mattered), and preferred behavior (what to do differently). Avoid vague feedback like 'be more careful' - it does not help the VA change behavior. Positive feedback should be equally specific: name what they did and why it was effective.
How do you manage multiple virtual assistants?
Managing two or more VAs requires a project management tool (ClickUp, Asana, or Notion) to replace direct message-based task assignment. Each VA should have a documented role brief so responsibilities do not overlap. Hold a weekly team huddle of 15 to 20 minutes for shared context. Appoint a lead VA to coordinate between team members once you have three or more VAs - this scales your oversight without consuming more of your time.
What tools do you use to manage a virtual assistant?
The core toolkit for most setups: a project management tool (ClickUp, Asana, or Trello) for task assignment and tracking, a shared communication channel (Slack or Teams) for async messaging, a shared document system (Google Drive or Notion) for SOPs and the weekly priorities doc, and optionally a time tracker (Toggl) for project-based billing. Avoid using email as your primary management interface - it buries task status in threads and makes tracking nearly impossible.
How long does it take to onboard a virtual assistant?
Most VAs reach 70 to 80% productivity by the end of week 2 if you provide a clear role brief, written SOPs for each task, and daily check-ins in the first week. Full productivity typically takes 30 to 60 days depending on the complexity of your workflows. The biggest bottleneck is almost always the business owner's time to write SOPs and answer questions, not the VA's learning curve.
Should my virtual assistant use AI tools?
Yes - but with clear boundaries. A VA who uses AI tools (ChatGPT, Claude, Perplexity) for research, drafting, and summarization completes those tasks 2 to 3x faster than one who does not. The requirement is a written AI use policy that specifies: which tools are permitted, what data must not be input (client names, financials, proprietary processes), and what human review step is required before AI-assisted output leaves the building. Set this policy before the VA starts, not after an incident.
Ready to hire a virtual assistant?
Stealth Agents matches you with pre-vetted VAs in 24 to 48 hours.
Talk to a Staffing Expert