Key Takeaways
Most virtual assistant performance problems are management problems. Not because the VA is off the hook — but because unclear expectations, missing feedback loops, and no documentation are almost always the root causes. Before assuming you hired the wrong person, it’s worth asking whether you gave them what they needed to succeed. This guide walks you through how to identify real performance issues, give effective feedback, build a simple improvement plan, and decide when to coach versus when to cut ties. Done right, addressing performance issues fairly keeps good hires and builds a stronger remote team.
The Most Common VA Performance Problems (and Their Real Causes)
Most VA performance issues aren’t random. They follow predictable patterns, and each one usually points back to a system failure, not a character flaw. Here’s what you’ll typically see — and what’s actually driving it:
- Missing deadlines — The VA doesn’t have a prioritization system. If you’re assigning tasks across Slack, email, and a project tool without clear due dates and priority levels, missed deadlines are inevitable.
- Poor quality output — Briefs are unclear. If you’re sending a one-line request and expecting polished work, the problem is the brief, not the VA’s capabilities. Document your standards with examples.
- Communication gaps — You’re using the wrong async tools, or there’s a timezone mismatch with no overlap window. A VA working 12 hours ahead needs a structured check-in system, not just an open Slack channel.
- Low initiative — There’s no feedback or recognition loop. VAs who never hear anything positive — only corrections — stop volunteering ideas. Engagement requires acknowledgment.
- Inconsistent output — There are no Standard Operating Procedures (SOPs). Without documented processes, quality varies based on the VA’s memory and interpretation each time.
Identifying the root cause before addressing performance issues is not optional — it’s the difference between a coaching conversation that works and one that doesn’t.
Before You Have “the Talk” — 4 Questions to Ask Yourself First
Before scheduling a performance conversation with your VA, run through these four questions honestly:
- Did I communicate expectations clearly? Not just verbally — in writing, with examples. If expectations lived in your head, they weren’t communicated.
- Do I have specific examples? “Your work has been inconsistent lately” is not actionable. “The last three blog posts were submitted without images and missed the keyword placement we discussed” is.
- Have I given feedback before now? If this is the first time you’re raising an issue that’s been going on for weeks, you’ve delayed too long. That context matters.
- Is this a performance issue or a fit issue? Sometimes a VA is doing fine at what they were hired to do, but the role has changed. That’s a different conversation.
If you can’t answer yes to questions 1 and 2, you’re not ready for the performance conversation yet. Fix the clarity problem first. For a structured approach to setting expectations from day one, review your VA onboarding checklist to identify gaps.
How to Give Performance Feedback to a Remote VA
Remote feedback requires more precision than in-person feedback. You can’t rely on tone of voice, body language, or a casual follow-up chat in the hallway. The best framework for remote performance feedback is SBI: Situation – Behavior – Impact.
Here’s how it works:
- Situation — Describe the specific context. “In the social media scheduling report submitted on February 14th…”
- Behavior — Describe the observable behavior, not your interpretation. “…the captions for the Tuesday and Thursday posts were missing, and the scheduling links were broken…”
- Impact — Describe the real-world consequence. “…which meant I had to manually reschedule those posts on the day they were due, which added 45 minutes to my workflow.”
Deliver feedback in writing first. Send a written summary before or after any call — it gives the VA time to process, and it creates a record. Avoid vague language like “attitude,” “effort,” or “enthusiasm.” Stick to observable behaviors and measurable outcomes.
After delivering the feedback, ask the VA to respond. You want to know if there was a system failure on their end, a misunderstanding, or a workload issue you didn’t see. Feedback is a two-way exchange, not a one-way verdict.
One reliable external framework: research from Harvard Business Review on effective performance feedback consistently shows that specific, behavior-based feedback outperforms general assessments for remote workers.
Building a Simple PIP (Performance Improvement Plan) for VAs
A Performance Improvement Plan is not a warning letter — it’s a structured agreement about what success looks like and how you’ll measure it. For remote workers, a good PIP has three parts:
Part 1: Specific Expectations
List the exact behaviors or outputs that need to change. Be concrete. “Improve communication” is not a specific expectation. “Respond to all Slack messages within 4 business hours and send an end-of-day summary every Friday by 5 PM PHT” is.
Part 2: Timeline
Give a defined window — typically 30 days for a VA. Set a mid-point check-in at 15 days. The timeline should be realistic: enough time to demonstrate change, short enough to maintain accountability.
Part 3: Measurable Outcomes
Define what success looks like at the end of the PIP period. “Zero missed deadlines over 30 days,” “all deliverables submitted with the required format checklist completed,” or “weekly reports submitted by end of day every Friday.” Outcomes need to be binary — either they happened or they didn’t.
Send the PIP as a document, have the VA acknowledge it in writing (email is fine), and schedule your check-in dates at the start. Do not surprise a VA with a PIP in a live call — send it in advance so they can review it before discussing.
Pair the PIP with a review of the probation period for a VA if this issue emerged early in the engagement — the frameworks overlap significantly.
When to Coach vs. When to Let Go
Not every performance issue is worth investing in. Use these signals to guide your decision:
Coaching is likely to work when:
- The VA has a strong track record in other areas and this is an isolated issue
- The root cause is a system failure (unclear SOPs, missing tools) that you can fix
- The VA acknowledges the problem and shows genuine willingness to change
- The skill gap is trainable within a reasonable timeframe
- The relationship has been positive overall
It’s time to end the engagement when:
- The same issue has recurred after multiple rounds of feedback and a completed PIP
- There are integrity concerns — missed transparency, inconsistencies in reported hours, or misrepresentation
- The VA is disengaged and unresponsive during the improvement process
- The role has fundamentally evolved beyond what the VA was hired or is willing to do
Ending a VA engagement is a business decision, not a moral judgment. If you’ve been fair — clear expectations, honest feedback, a structured PIP — you’ve done your part. Holding on too long out of guilt is costly for both sides.
How to Prevent VA Performance Issues Before They Start
Most performance conversations can be avoided with better systems upfront. Here’s what works:
- Build SOPs for every recurring task. A written process removes ambiguity. The first time a task is done well, document it. Use Loom videos, Google Docs, or Notion — the format matters less than the consistency.
- Run 30-day check-ins. At 30 days, have a structured conversation: What’s working? What’s unclear? What do you need more of? Don’t wait for issues to surface — surface them proactively.
- Implement weekly reviews. A short weekly async update (5 bullet points: what was completed, what’s in progress, any blockers) keeps both parties aligned and creates a natural record.
- Set a communication protocol. Response time expectations, preferred tools, escalation paths — document it in the first week. Ambiguity in communication is where performance problems breed.
If you’re starting a new VA engagement, use the hiring a VA who delivers framework to build these systems into the selection process rather than adding them after problems emerge.
Frequently Asked Questions
How do I address a VA performance issue without damaging the relationship?
Be specific, private, and solution-focused. Use the SBI framework, deliver feedback in writing, and give the VA space to respond. Frame the conversation around what success looks like going forward, not just what went wrong. VAs who feel respected during difficult conversations are far more likely to improve and stay engaged.
How long should a VA PIP last?
For most VA roles, 30 days is appropriate. It’s enough time to see consistent behavior change, short enough to maintain momentum. Include a 15-day check-in to identify whether progress is on track before the final evaluation.
Can I terminate a VA immediately for performance issues?
This depends on your contract terms and the nature of the issue. For serious violations — dishonesty, breach of confidentiality — immediate termination may be warranted. For performance gaps, most contracts require a notice period and/or a PIP process. Review your agreement before acting.
What if the VA performs well in some areas but not others?
Focus the PIP on the specific underperforming areas rather than the overall engagement. A VA who excels at content scheduling but struggles with client-facing communication may need training in one area, not a full exit. Be surgical with your feedback.
How do I document performance issues properly?
Keep a log of specific incidents with dates, the task or expectation involved, what was delivered, and the impact. Use email or a shared doc rather than just Slack messages — those are harder to retrieve. Documentation protects you and ensures the VA understands the pattern, not just a single incident.
Need Help Scaling Your Business?
Get matched with a pre-vetted Filipino virtual assistant in under 7 days. Book a free discovery call.






