Most VA relationships that drift into underperformance do so quietly. Output quality declines in small increments; delivery timing slips by a few hours and then by a day; communication becomes less proactive. Without a structured review process, that drift is only noticed when it has accumulated into a significant problem, at which point correcting it is harder than it needed to be.
A structured VA performance review creates a regular checkpoint: an explicit assessment of how the engagement is performing against defined standards, a conversation about what is working and what is not, and a clear record of the agreed adjustments. Done consistently, it prevents drift and creates the feedback loop that enables a VA to improve.
Why a structured review matters for VA engagements
The absence of a structured review does not mean the relationship is unmanaged; it means it is managed implicitly. The manager forms an impression of how the VA is performing based on daily interactions, and the VA calibrates their work based on the feedback they receive and the feedback they do not receive. That implicit management often works reasonably well in the early months of an engagement when expectations are fresh and standards are recently defined. Over time, the standard drifts as small adjustments accumulate without explicit correction.
A structured review externalizes the standard. It converts the implicit impression ("things seem fine" or "something feels off") into an explicit assessment against defined criteria. That explicit assessment is more useful for the VA because it tells them specifically what to change rather than conveying a general impression of dissatisfaction. It is more useful for the manager because it surfaces issues early and creates accountability for addressing them.
The how to manage a virtual assistant article covers the daily and weekly management practices that surround the review. The review is not a substitute for those practices; it is a periodic structured checkpoint that complements them.
What to measure in a VA performance review
Output quality against defined standards
Output quality is the most important dimension and the hardest to assess without a defined standard. Before a review can meaningfully evaluate output quality, there must be a documented description of what good output looks like for each task in the VA's scope: what format, what level of completeness, what accuracy standards, and what constitutes a deliverable that is ready to use versus one that needs correction.
Assessing output quality against a defined standard produces specific, actionable findings. The VA's CRM update entries are missing deal stage and close date fields, which the standard specifies as required. The pipeline summary report is delivered with current data but the formatting differs from the template in two ways. The customer follow-up emails are sent on time but the tone is more formal than the template examples specify. Each of those findings has a clear correction; a general impression that "output could be better" does not.
If documented standards do not yet exist for some tasks, building them is the first action item from the review, not a follow-on task. A VA cannot be assessed against a standard that has not been defined, and a review that produces the finding "we need to define this standard" is a useful output, not a failed review.
Delivery consistency and schedule adherence
Delivery consistency measures whether the VA's outputs arrive when they are expected to arrive. This is a separate dimension from output quality: a VA who produces high-quality work but delivers it late creates a different problem than one who delivers on time but with quality gaps, and each requires a different response.
Assess delivery consistency by task type over the review period. Which recurring tasks were delivered on schedule consistently? Which were occasionally late? Which were chronically late? For tasks that were late, what was the pattern: was notification provided ahead of the deadline, or was the delay only discovered when the expected output did not appear?
Consistent on-time delivery is a significant operational contribution even when output quality is still developing. A VA who reliably delivers on a defined schedule without reminders allows the manager to build workflows that depend on that delivery. Late delivery without advance notice is a more disruptive problem than late delivery with proactive communication, because it creates unexpected gaps at the point of dependency.
Communication and escalation patterns
Communication quality in a VA engagement covers two related behaviors: the proactive communication the VA initiates (status updates, flagged issues, advance notice of potential delays) and the escalation behavior when the VA encounters a situation outside the documented scope (when to ask versus proceed independently).
A VA who communicates proactively reduces the management overhead on the manager's side: you know the status of ongoing tasks without having to ask, you learn about potential issues before they become actual ones, and you receive advance notice of anything that might affect a deliverable deadline. A VA who communicates reactively or only when asked creates a monitoring task: the manager must actively check on status rather than receiving it.
Escalation calibration is the behavior most commonly miscalibrated in the first several months: VAs early in an engagement often either escalate too much (asking about things the process documentation covers) or too little (proceeding on assumptions where they should have asked). By the time of the first review, escalation patterns should have stabilized; continued miscalibration after explicit feedback indicates a gap in the process documentation or in the VA's understanding of the scope boundary.
Initiative and process improvement
Initiative is not a required behavior in the early months of a VA engagement; the primary requirement in the first ninety days is consistent execution of the defined scope. In a mature, well-functioning engagement, initiative signals that the VA has enough operational context to see beyond their task list and enough confidence in the relationship to offer observations.
Initiative in a VA engagement looks like: flagging a process that generates recurring questions and suggesting a documentation improvement; noticing a pattern in data that seems worth the manager's attention; identifying a tool configuration that could reduce the manual work in a current task. It does not look like making unilateral changes to processes without discussion.
In a performance review, note the specific instances where the VA demonstrated initiative over the review period. For a VA who has been in the role for more than six months and has not demonstrated any initiative, it is worth asking whether the environment invites it: some managers implicitly signal that the VA's job is to execute the assigned tasks and nothing more, and the VA adapts accordingly.
How to run the review conversation
A performance review conversation for a VA engagement is most effective when it is structured and time-bounded: thirty to forty-five minutes with a defined agenda shared in advance. Sharing the agenda and any written assessment with the VA before the conversation gives them time to prepare their own perspective and prevents the conversation from being one-sided.
A useful review agenda:
What is working well and why (ten minutes): start with specific examples of strong performance before addressing gaps. This is not politeness padding; it calibrates the VA on which behaviors to maintain and builds the psychological safety needed for the gap discussion to be productive.
What needs improvement and how (fifteen minutes): for each gap identified, describe what was observed specifically, what the standard is, and what the expected change looks like. Ask the VA for their perspective on the root cause before proposing a correction. A gap that stems from unclear process documentation has a different fix than one that stems from a skill limitation or a tool access problem.
Action items and timeline (ten minutes): every finding that requires a change should produce a specific action item with a clear owner and a timeline. "We will improve communication" is not an action item. "By next Friday, the VA will send an end-of-day status update for each open project at the start of each day" is an action item.
The VA should have the opportunity to raise issues in the other direction as well: are there tasks where the process documentation is unclear? Are there tool access issues that are affecting their ability to do the work? Are there scope items that are taking longer than expected for reasons the manager should know about? A one-directional review misses information that matters.
Acting on the review results
A review without follow-through is worse than no review: it tells the VA that the standards discussed do not actually matter. The action items from the review need a defined follow-up mechanism, whether that is a check-in at thirty days or a brief written confirmation that the agreed changes are in place.
For significant output quality issues or repeated missed deadlines, the review should produce a documented improvement plan: specific behaviors expected, measurable standards, and a defined timeline for demonstrating improvement. A VA who knows exactly what success looks like over the next thirty days and receives confirmation of progress at thirty days has a much better chance of reaching it than one who received general feedback and was left to interpret it.
For VAs who are performing well, the review is an opportunity to discuss scope expansion, acknowledge the quality of the work specifically, and reinforce what is working. High-performing VAs who receive no positive acknowledgment in reviews receive an implicit signal that their performance is unremarkable; specific acknowledgment of strong work is worth including.
When the review reveals a genuine mismatch between the VA's capabilities and the role requirements, the right response is direct: name the mismatch clearly, confirm whether it is correctable within a defined timeline, and if not, address the transition with the same professionalism you would bring to any role that is not working out. Extending a non-functioning engagement because the conversation is uncomfortable costs more time and output quality than addressing it directly.
How often to run reviews
A new VA engagement should have a structured review at thirty days and at ninety days. The thirty-day review catches onboarding calibration issues before they compound; the ninety-day review is the first assessment of whether the engagement has settled into a productive working pattern. The operations VA onboarding guide covers the onboarding structure that precedes these reviews.
After the ninety-day review, a quarterly cadence is appropriate for most VA engagements: frequent enough to catch drift before it accumulates, infrequent enough that each review covers a meaningful period of work. Engagements with high task volume or frequent scope changes may benefit from a more frequent cadence; stable engagements with consistent task scope and strong output quality can run at quarterly without risk.
Between reviews, the weekly check-in and ongoing feedback practices described in the how to manage a virtual assistant article handle the day-to-day calibration. The structured review is a supplement to that ongoing feedback, not a replacement for it.
For SOP creation virtual assistant and workflow management virtual assistant roles where the scope evolves as new processes are documented or workflows are built, the review should also assess the quality of the process assets produced, not just the execution of standing tasks.
Get a free consultation to build a VA management structure that includes a review cadence from the start of the engagement.