July 2026
---title: "How to Give Feedback to Your Virtual Assistant"slug: "how-to-give-feedback-to-va"focusKeyword: "how to give feedback to your virtual assistant"tier: "info"cluster: "managing-va"wordCount: 1360---Most virtual assistant relationships underperform not because the wrong person was hired, but because feedback was handled poorly after the hire. An assistant who receives vague, delayed, or inconsistent feedback cannot improve. An assistant who receives specific, timely feedback builds toward a higher standard with each iteration.The challenge for most founders is not motivation. They want better output. The challenge is knowing how to translate dissatisfaction with a piece of work into actionable guidance that changes future work without damaging the working relationship.
## How to give feedback to your virtual assistantSpecific feedback names the gap between what was delivered and what was expected. It describes the output element that missed the mark and provides enough guidance that the assistant could correct it without asking follow-up questions.Vague feedback names a feeling. "This is not quite right" tells the assistant you are dissatisfied. It does not tell them what to change. "The email subject line does not match the tone of the body, which is formal. Subject lines should be direct and professional, like this example" gives them a gap, a standard, and a reference.The practical test is this: could the assistant improve the output using only the feedback you gave? If they would need to ask a clarifying question to understand what to change, the feedback was not yet specific enough.## The difference between task-level and pattern-level feedbackTask-level feedback addresses a specific output. Pattern-level feedback addresses a recurring behavior across multiple outputs. Both are necessary and should be handled differently.Task-level feedback is time-sensitive. Give it as close to delivery as possible. The assistant has the most context for the task when it is recent. A correction delivered the same day a piece of work arrives is far more actionable than a correction delivered a week later.Pattern-level feedback is better handled in a scheduled conversation. If your assistant has been formatting reports inconsistently across several weeks, that conversation belongs in a weekly check-in rather than a per-task note. The weekly context lets you address the underlying cause rather than just the most recent instance.| Feedback type | Timing | Format | Purpose ||---|---|---|---|| Task correction | Same day | Written note | Fix this output, update the standard || Escalation note | Immediately | Short message | Clarify before work continues || Pattern feedback | Weekly check-in | Conversation | Address recurring themes || Standard update | After pattern feedback | Reference document revision | Codify the correction || Positive reinforcement | As it occurs | Brief acknowledgment | Signal what to keep doing |## How to build a feedback rhythmSporadic feedback produces sporadic improvement. A feedback rhythm gives the assistant a predictable structure within which to develop.A practical rhythm for most VA relationships: task-level notes delivered as outputs arrive; a weekly check-in of ten to fifteen minutes to address pattern-level issues; a monthly review of the reference documents to incorporate accumulated corrections and remove outdated guidance.The weekly check-in does not require a call. An async voice message or a short written summary with a response window works well for most remote relationships. What matters is that there is a dedicated moment for pattern-level discussion separate from task-level corrections.The monthly reference document review is often skipped. Skipping it allows reference documents to drift from the actual standards you use. Outdated guidance confuses the assistant and creates the kind of subtle errors that are hard to diagnose.## Mistakes that prevent feedback from landingDelayed feedback is the most common problem. A note on output that arrived two weeks ago cannot connect to the specific decisions the assistant made. The context has faded.Mixing correction with capability criticism is a second mistake. Feedback tells the assistant what to change. Capability criticism assesses whether they can do the work at all. Correction is productive. Capability criticism, when the real issue is a documentation gap rather than a skill gap, is demoralizing and usually wrong.Giving feedback without confirming it was received is a third. A message sent does not constitute communication until it has been acknowledged. A short reply from the assistant confirms the correction was understood. Without that acknowledgment, the feedback may not have landed in the way you expected.For the broader management system this feedback rhythm lives inside, see our guide on how to manage a virtual assistant. For the delegation framework that sets up clear expectations from the start, how to delegate effectively covers the output definitions that reduce feedback volume over time.Research from Harvard Business Review on feedback and performance consistently shows that specific, timely corrections produce faster performance gains than general coaching, with direct application to remote working relationships.## What to do when feedback is not workingIf the same correction is being made repeatedly after the first month, the issue is almost certainly in the system rather than in the assistant. The most common causes are: the correction is not documented in the reference materials, the original brief did not define the output standard clearly enough, or there is a tool or access issue the assistant has not raised.Before concluding that an assistant cannot meet a standard, work through those three causes. In most cases, one of them explains the gap. The corrective action is to update the documentation, rewrite the brief, or resolve the access issue, not to replace the person.When performance is genuinely not improving after thorough calibration, have a direct conversation. Describe the expected standard, show examples of work that meets it, and ask the assistant to walk you through how they understood the correction. That conversation usually surfaces the gap faster than any amount of written feedback.## FAQ**How much feedback is appropriate in the first month?**Frequent, specific feedback is appropriate and expected during calibration. The assistant is learning your standards from scratch. Corrections at this stage are investments. After the relationship stabilizes, usually by week four to six, feedback volume drops naturally as the assistant works to an established standard.**What if my assistant does not seem to be incorporating feedback?**Check whether the correction is in the reference document. Verbal corrections that are not documented are easy to forget. Check whether the feedback was specific enough to act on. Then have a direct conversation. Ask the assistant to describe how they understood the correction and what they changed. That conversation surfaces the gap quickly.**Should I give positive feedback, or is that unnecessary?**Brief acknowledgment when the assistant gets something right is useful because it signals what to continue. "The format on this research brief was exactly right" tells the assistant that they interpreted the standard correctly. Without that signal, they cannot distinguish between work you noticed and approved and work you did not notice.**Is written feedback better than verbal?**Both have a place. Written feedback is better for specific corrections because it creates a record the assistant can return to. Verbal feedback is better for pattern-level discussion because it allows back-and-forth. The default for most remote VA relationships should be written, with verbal reserved for situations where context needs real-time exchange.**What if I realize a correction I gave was wrong?**Correct it promptly. Tell the assistant the previous guidance was inaccurate and provide the updated standard. Then update the reference document. There is no cost to correcting your own instructions. The cost is in leaving wrong guidance in place and having the assistant follow it until you notice.---
