Virtual Assistant Performance Issues: How to Fix Mistakes and Missed Deadlines Fairly

Most virtual assistant performance issues start with a moment like this: the client pack should have gone out yesterday.

Your VA says it's nearly ready. Then a missing attachment turns into another round of checking. You finish it yourself and send a short message: "Please be more careful next time."

That message expresses frustration. It doesn't tell anyone what needs to change.

The same late delivery could have been caused by:

• unclear instructions,
• a missing permission,
• too much work,
• a skill gap, or
• ignoring an instruction they understood perfectly well.

Each of those needs a completely different fix. "Be more careful" fixes none of them.

Handling virtual assistant performance issues well means separating what happened from your theory about why. This guide walks you through it: protect the work, find the real cause, agree a fix, and test it. You can be fair without accepting endless mistakes, and firm without judging someone's character from one bad day.

Here, a virtual assistant (VA) is an independent freelancer or agency providing a service, not an employee.

Fix the damaged work first, judge later

Open the affected task and work out where things stand:

• Has wrong information reached a customer?
• Can the deadline still be saved?
• Is money, personal data or account access involved?

Then decide what needs containing right now, and who'll do it.

Match the response to the consequence, not your annoyance level:

• A typo in an unpublished draft can wait for correction.
• A wrong promise to a customer might need a quick clarification.
• A suspected data leak needs your incident process and possibly specialist advice, not a coaching chat.

Give a narrow instruction while you look into it:

"Pause sending these packs. Keep preparing drafts."

That stops the problem spreading without throwing away useful work. Don't lock every account by reflex if that destroys evidence or stops unrelated work for no benefit.

Save the original records: the task, the version, the message and the time. Don't rewrite the instructions and then use the improved version as proof the original was clear.

And if you must take over today, say so:

"I'm finishing this one to meet the deadline. We'll look at what happened tomorrow."

Otherwise your VA just learns that hard work vanishes back to you, and nothing improves.

Turn "unreliable" into something you can both check

Write three separate sentences:

1. The expectation. "The approved pack was due in the client folder by the agreed deadline."
2. What happened. "It was uploaded without the signed order form."
3. The effect. "The client couldn't confirm the work from that pack."

Each one can be checked. "You never pay attention" can't. "Everyone's disappointed" can't. If several cases are involved, list them individually rather than turning one mistake into a general pattern.

Include what went right too. Maybe the pack was well organised and every number matched, but the attachment check failed. That focuses the fix. It's not a compliment sandwich. It just stops the whole task being labelled broken.

Then check the finish line. Did "prepare the pack" mean a draft for you, a ready-to-send file, or a message delivered to the customer? If that was never clear, you've found a gap in the instructions. You can still explain the impact while admitting the requirement was incomplete.

And if the deadline only existed in your head? Don't call it missed. Set it clearly for next time, with a time zone and what must be delivered.

Ask them to walk you through it, not defend themselves

Share the specific examples before you talk, and say what you want to understand. Surprising someone with a list of accusations gets you rushed explanations, not useful evidence.

Then ask:

"Can you show me what you understood the finished result to be, which source you used, and where you became unsure?"

Follow the actual steps. Which file did they open? What did they check? What did they do when the required information was missing?

Use a safe example if the live record has sensitive information. You don't need their whole screen or unrelated client files.

Listen for a reasonable decision based on incomplete information. If two files both looked current, picking the wrong one is a version-control problem. If they knew which was current but skipped the check to finish faster, that's a different issue.

Don't judge on confidence, accent or how quickly they reply. Someone can explain a weak process fluently. Someone else can need a moment to explain a valid concern.

End by repeating your understanding and inviting correction:

"You found the missing form, asked in chat, and continued without it because there was no rule saying stop. Is that right?"

Agreeing on what happened is the foundation for fixing it.

Missing information or missing skill? Test it in this order

Work through the possible causes in this order. Each step rules something out before you move to the next.

1. Operating conditions. - Was the required information available? - Could they access it? - Was the trusted source clear? - Did someone else need to approve something first?

These aren't personal failings. Training someone to check a folder doesn't help if they can't open the folder.

2. Knowledge. Ask them to explain the rule and apply it to a similar example. If they can't tell a signed order form from an unsigned draft even with clear examples and access, that's a knowledge or skill gap.

3. Capacity. Lay out everything that was actually assigned, including requests you sent outside the task system. Which did they think came first? Did you add an urgent job without moving another deadline?

4. Behaviour. If they understood the check, could do it, had time and access, and repeatedly chose not to, more training probably won't help.

Don't jump to number four before checking one to three.

Remember, this is an outsourced service, not an employee appraisal. You're checking whether the agreed output is achievable and being delivered, then agreeing any change. Don't assume you can control their whole working day.

A worked example: the missing signature

Here's a hypothetical example.

A small commercial photography business has a VA who prepares shoot packs: the approved brief, location details, customer contact and signed order form. The owner wants them ready before each booking. But nobody ever defined what happens when the customer hasn't returned the form.

One pack arrives late and without the signature.

In the walkthrough, the VA shows a message they sent the owner about the missing form. The owner was on a shoot and didn't answer. The VA then spent time searching old email threads before putting together an incomplete pack.

There are two failures here:

1. A process gap. There was no defined path for missing customer input.
2. A communication gap. The VA didn't update the task when the deadline became at risk.

Fixing only an attachment checklist would leave the second problem untouched.

So:

• The owner creates a "waiting for customer" status with a named person to chase it.
• New rule: an unsigned form must never be presented as signed. A pack can be prepared with a visible "outstanding" note, but only the owner decides if the shoot goes ahead without the agreement.
• The VA agrees to update the task as soon as missing input threatens the deadline, stating what's missing, who's been contacted and when a decision is needed.
• The owner agrees to name a backup decision-maker when they're unavailable, and to keep the current form in one agreed place.

The fix covers both sides. Diligence alone could never have produced a customer signature.

Feedback that names the fix, not just the fault

Keep it plain and close to the facts. For the photography example:

"The pack for the next shoot didn't have the signed form, and the task stayed 'in progress' after the deadline was at risk. I had to rebuild the missing item before contacting the customer."

Then the future rule:

"For the next packs, check the form against the checklist. If it's missing, mark the task 'waiting for customer' and write the decision needed. Don't mark a pack complete until every required item, or an approved exception, is there."

Then your part:

"I'll add the missing-input rule and a backup approver before you start the next pack."

Ask if anything still makes it hard to follow.

A few things to avoid:

• Burying the fix inside an emotional message about trust. Trust grows from repeated behaviour, but it's hard to act on as an instruction.
• Demanding an apology as the measure of success. Someone can apologise sincerely and repeat the mistake because nothing changed.
• Treating a calm explanation of a missing input as excuse-making. They might be helping you solve the real problem.

Send a short written summary afterwards, including any facts you disagree on.

Test the new rule before handing back full authority

A corrected document isn't proof the problem's fixed.

Run a practice case. For the shoot pack, give a safe sample folder containing:

• an approved brief,
• an unsigned form,
• an older signed form for a different booking.

Ask them to build the pack and explain its status.

The right result isn't a complete-looking folder. It's spotting that the current booking lacks a valid form, using the right waiting status, and escalating. You're testing judgement at exactly the point where it went wrong last time.

Discuss it straight away:

• If they grabbed the old signed form because it looked complete, show how the booking ID proves which form belongs.
• If they spotted the gap but forgot to tell the decision-maker, practise that step, not the whole training again.

Return lower-risk work first if the stakes justify it. Keep approval on outgoing sends while they prepare packs independently. And say what evidence will remove that restriction, so temporary checking doesn't become permanent micromanagement.

If the practice works but live work fails, look at what's different. Interruptions, volume or missing information might exist in real life but not in the test.

Pick a review period with real chances to improve

A useful review period needs enough relevant work to actually test the fix.

• If the task happens rarely, a short deadline might produce no evidence at all.
• If it happens constantly with serious consequences, waiting for a monthly meeting might be too slow.

Specify which cases you'll check, the standard and the check-in date. Use a practice case to test rare exceptions, rather than waiting for a real customer to experience one.

Don't create fake certainty from a percentage based on three cases. List them: which met the standard, which didn't, and whether the same failure came back.

Agree the support alongside the expectation: a worked example, fixed permissions, protected time or a narrower task list. If the promised support doesn't happen, write that down before judging whether they met the plan.

Keep the fix within the service you're actually buying. If you bought a weekly deliverable, suddenly demanding instant replies all day changes the agreement, not just clarifies it.

For an agency arrangement, involve the agency's named manager where your agreement says so.

Make blocked deadlines visible early

A deadline needs an early warning rule, not just a finish time.

Tell your VA what to do when required input, approval or a system becomes unavailable. The update should say:

• what outcome is at risk,
• what's blocking it,
• the last useful moment for a decision.

"Still working on it" gives you nothing to act on. "The signed form is missing, the customer's been chased, and I need approval before marking it ready" tells you exactly what to do.

And here's the important bit: don't punish a correctly flagged blocker the same way as an unexplained miss. If early warnings always trigger anger, your VA learns to hide bad news until it's too late to fix.

At the same time, "blocked" can't become an indefinite hiding place. Assign an owner and a review point for every blocked item.

Our VA KPI guide explains how to track waiting work separately from late work, so your measures help solve problems rather than just produce judgements.

Know when coaching is no longer the answer

Not every mismatch can be fixed within the role, budget or time available.

• You might need a specialist where you hired a generalist.
• The VA might understand the standard but be unable to meet it, despite fair training and support.

Look for evidence that the fix changed behaviour. A brand-new exception that they escalated correctly isn't the same failure repeating. Repeatedly skipping the same understood check is more worrying.

You can also decide a task should stay with you or someone more qualified. Taking back one high-risk job while keeping their good routine work might make more sense than treating the whole relationship as all good or all bad.

Serious allegations like dishonesty, harassment or misuse of access need proper investigation and protective action, not a coaching script. Keep evidence, limit exposure sensibly and get advice. An allegation is still an allegation until it's assessed.

If ending the service, read the agreement's notice, dispute and handover terms. GOV.UK's guidance on contractors explains that tax and employment status can differ in the UK. If your actual setup raises status questions, get advice rather than borrowing a dismissal process.

Don't withhold earned payment or invent fines because you're unhappy. GOV.UK's guidance on payment obligations gives UK context, but resolve disputed fees under your actual contract, with advice if needed.

If ending is the right call, use a planned handover. Our offboarding checklist covers it.

Your repair worksheet

Keep this private, and follow any separate agency dispute process you agreed.

VA PERFORMANCE REPAIR WORKSHEET

Affected task and original instruction (link):
Expected result and agreed deadline:
What happened, evidence and business effect:
Immediate containment and who did it:
VA's account, and any facts we disagree on:

Cause to test:
  input / access / instruction / skill / capacity / behaviour

My fix or promised support:
VA's future action:
Practice case and expected result:
Live cases to review and the standard:
Early-warning rule for blocked work:
Review date:

Evidence at review:
Decision and reason:
Restrictions removed or continuing:

At the review, compare real work against the agreed standard.

If it worked, say so specifically and remove checks that are no longer needed. Keeping someone permanently under a cloud after they've improved makes the whole process feel like punishment with no way out.

If it didn't work, look at what the new evidence shows. You might need a different fix, a narrower role or a planned ending.

Either way, you're no longer deciding from frustration. The work is protected, the cause has been tested, and your next decision has a record behind it.

For everyday habits that prevent issues in the first place, see how to manage a virtual assistant and how to train a virtual assistant.

Frequently asked questions

What should I do when my virtual assistant makes a mistake?

First, contain any damage to the affected work. Then work out what happened with your VA, find the real cause, agree a specific fix, and test it on similar work before restoring full authority.

How do I give feedback to a virtual assistant without upsetting them?

Describe the expectation, what happened and its effect in checkable terms. Then state the future rule and your own part in fixing it. Specific, factual feedback is far easier to hear than criticism of character.

How many chances should I give a virtual assistant?

There's no fixed number. What matters is whether they had clear instructions, access and support, and whether the same understood mistake keeps happening after a fair chance to improve.

When should I end a virtual assistant arrangement?

When a clear, achievable standard keeps being missed despite fair support, or when serious misconduct is established. Follow your contract's notice and handover terms and get advice where needed.

Can I deduct money from my VA's invoice for mistakes?

Don't invent fines or hold back earned payment. Resolve disputes under your actual contract and applicable law, with advice if needed.