How to Give Constructive Feedback to Your VA

Learn how to give constructive feedback to your VA after a mistake, understand what happened, agree on useful next steps, and follow up with clear expectations.

You open the replay email your virtual assistant (VA) sent after your workshop, and the link to the recording is missing. Now you need to get that link to the people who attended and address what happened with your VA.

When I notice a mistake like this, I take a few minutes to investigate before I bring it to the person. I want to understand what they were working from and whether the expectation was clear. Sometimes I find that the instructions haven’t caught up with a change I made.

Constructive feedback gives your VA a clear understanding of the issue and a chance to help resolve it. Describe what happened, explain its impact, and hear their perspective before agreeing on what needs to change. That conversation is more useful when you have the context to ask specific questions.

You might discover that they missed a documented step. You might also learn that something about the process made the task harder to complete carefully. Either way, you need enough information to address the right issue and help them deliver better work next time.

What does constructive feedback look like when you manage a VA?

Useful feedback makes the expected standard clear enough for your VA to apply it to their work. “Please be more careful” leaves them to guess what you want them to check. Naming the missing replay link gives you something specific to discuss.

The impact matters too. Addressing virtual assistant mistakes starts with identifying what happened and how it affected the work. If someone opens that email expecting to watch the workshop, they need a working link. Explaining that connection helps your VA understand why the step deserves attention, especially when it’s one small item in a task they complete often.

I want the person to leave our conversation knowing what I’m asking of them and feeling comfortable telling me if they need clarification or support. They also need room to explain something I haven’t seen from my side.

You can be warm and direct in the same conversation. When the work needs a correction, say so plainly. Keep the feedback focused on the task, and give the person a clear opportunity to respond.

What’s worth checking before you address a mistake?

Before I bring a concern to a team member, I spend about 10 to 15 minutes looking at the information they had when they completed the task. That often helps me understand why the result differed from what I expected.

For example, maybe I asked for a change in Slack, but the standard operating procedure (SOP) still describes the old process. If the person followed that document, I need to acknowledge the conflicting instructions when we talk. I also need to update the process so they have a reliable reference next time.

Sometimes the instructions are clear, but a tool failed. An email didn’t send, an automation stopped, or the person couldn’t access something they needed. Reviewing the relevant task conversation may reveal that they flagged the problem earlier.

Collect what you find before deciding what it means. You don’t need to solve the whole situation before speaking with your VA. You need enough context to ask useful questions and recognize where your own communication or systems contributed.

How do you describe the issue without making it personal?

Describe the part of the work that needs attention. If you’re frustrated, it’s easy to reach for a phrase like “You’re careless with these emails.” That turns one missed step into a judgment about the person, which makes it harder to discuss what happened.

The Agency for Healthcare Research and Quality’s 2023 TeamSTEPPS feedback guidance recommends describing the performance concern and letting the person explain, rather than assuming why it happened. Its guidance comes from healthcare teams, but that communication principle also fits how I approach feedback with a VA.

A specific observation gives both of you something to work with:

Vague criticism	Specific observation
“You’re careless with these emails.”	“The replay email went out without the recording link.”
“You never follow instructions.”	“The link check listed in the task wasn’t completed before this email was sent.”
“I can’t rely on you.”	“The upload arrived after the agreed deadline, and I didn’t receive an update.”

Keep your wording within what you know. You may know the link was missing without knowing whether your VA skipped the check, misunderstood it, or encountered a problem. Describe the result first, then ask about their experience.

That also makes accountability around delegated work clearer. You’re addressing an identifiable part of the work that needs to change, and the person has an opportunity to explain their side.

When does feedback need a live conversation?

A short written message works well when the issue is clear and the correction is straightforward. If your VA missed a step in a current checklist, a task comment or Slack message may be enough to explain what needs attention and give them room to reply.

I’d make time for a live conversation when I need to understand more about what happened. Maybe the person needs a demonstration of the process, or we’ve already discussed the same issue and the agreed change hasn’t happened. Talking together gives us space to explore that.

Keep a few notes in front of you, then let the conversation unfold. You want to remember the concern without becoming so focused on your next point that you miss what the person is telling you.

Ask them to walk you through their experience. They may describe a timing problem or misunderstanding you hadn’t considered. What you learn will help you decide whether a reminder is enough or whether they need more support.

How do you help your VA meet the expected standard?

One question I ask my team is: “How can I make sure you’re well-resourced to get the best results?” Once we understand what happened, I want to know whether there’s a practical adjustment that would help them complete the work well.

Imagine your VA needs to publish a replay immediately after a call, but that timing falls right before school pickup. They rush to finish and miss a check. If your clients don’t need immediate access, a confirmed delivery window of 12 or 24 hours might give your VA enough space to complete the task carefully.

You’d need to review what you’ve promised clients before changing that deadline. Once everyone knows when to expect the replay, your VA has a workable window, and your clients have a clear expectation. That supports both the team experience and the client experience.

Sometimes the support is much smaller: a quick demonstration or a reminder to use the checklist every time, even when the task feels familiar. Choose the adjustment that addresses what you learned, then confirm how you’ll both put it into practice.

What happens after the feedback conversation?

Send a short follow-up while the conversation is still fresh. Capture what you agreed and when you’ll check in, including anything you’ve committed to provide. That gives both of you a reference when the task comes around again.

If your VA agreed to use the checklist before each replay goes out, include that. If you offered to demonstrate a step or clarify the instructions, record your part too. Your follow-up needs to reflect the conversation you had, including any details that remain unresolved.

Make the check-in specific enough that you both know when it will happen. “We’ll revisit this soon” is easy to lose track of. Reviewing the next replay together gives you a clear opportunity to see whether the adjustment helped.

A 2016 review by Benjamin Harkin and colleagues in Psychological Bulletin analyzed 138 studies involving 19,951 participants and found that encouraging progress monitoring improved attainment on average. The research covered behavior change broadly; it supports checking progress without establishing a specific review schedule for your VA.

The follow-up doesn’t need to be lengthy. A few clear sentences help you carry the agreement into the work and give your VA somewhere to refer back to if they’re unsure.

How do you tell whether a mistake is becoming a pattern?

Keep a private record of feedback conversations so you have something to review when another concern comes up. When you’re having a hard day, a new mistake can make it feel like you’re constantly addressing the same problem. Dates and notes help you assess that impression.

You might look back and find that the last documented issue happened four months ago, on a different task. Or you might find several conversations about the same missed step, with a clear agreement that still hasn’t been followed. Those situations need different consideration.

Review the context and follow-through alongside the number of incidents. Consider whether the expectations were clear, what support you provided, and whether the person made the agreed changes. Your record may be incomplete, so use it alongside what you know about their work.

Document positive feedback and improvements too. That gives you a fuller picture of their contribution when deciding what support to offer or whether the working relationship is still a good fit.

FAQs about constructive feedback for a VA

Prepare your next feedback conversation with support

When something goes wrong, you still need to decide how to bring it up and what to ask. Having support with that preparation gives you space to consider the context and choose wording you’re comfortable sharing.

Team Feedback Builder helps you prepare feedback for the situation in front of you. Bring it what happened and the relevant instructions or conversations. It helps you review the context, then drafts a short written message or brief talking points for a live discussion.

After you’ve spoken with your VA, bring your notes back for help writing the follow-up and capturing the agreement in your private Team Feedback Log. You can also use it when someone does good work and you want to share specific praise.

Start with one situation you want to address, and prepare the conversation before you send that message. Get Team Feedback Builder.

It’s also included in the ALL ACCESS PASS: AI-Powered Ops Team, alongside the other skills and Build Your AI-Powered Team, the workshop where I show you how to customize the instructions and use the skills together in your business.