Training

How to Train a Virtual Assistant With SOPs

4 min read

Illustration of an open book, representing training and procedures

The fastest way to train a virtual assistant (VA) is to stop explaining the same task twice. Write it down once as a short standard operating procedure (SOP), then let the VA follow it, improve it and own it.

You do not need a thick manual. A page or a three-minute recording per task is enough. This guide shows how to create SOPs, train in the first 30 days and keep quality steady.

What is an SOP?

An SOP is a short, repeatable set of instructions for one task. A good one answers:

  • Why does this task exist?
  • When is it done?
  • How exactly is it done, step by step?
  • What does “done well” look like?
  • What should the VA do if something goes wrong?

A simple SOP template

Copy this and fill it in for each recurring task.

TASK NAME: [e.g. Weekly invoice follow-up]

PURPOSE
[One sentence: what this achieves.]

WHEN
[Daily / weekly on Monday morning / when X happens]

TOOLS AND ACCESS
[Tools needed and where the login is.]

STEPS
1. [Open ...]
2. [Check ...]
3. [Send ...]

QUALITY CHECK
- [What to double-check before finishing]

EXAMPLES
- [Link to a good example]

IF SOMETHING GOES WRONG
- [Who to message, how, and what to include]

DECISIONS
- You may decide: [...]
- Ask me first: [...]

How to create SOPs quickly

  1. Record yourself doing the task. Narrate what you click and why. A five-minute recording captures more than a page of notes.
  2. Turn it into steps. Write numbered steps from the recording, or ask your VA to.
  3. Add examples. One good example and one common mistake.
  4. Let the VA test it. Ask them to follow the SOP exactly and flag unclear steps.
  5. Fix the gaps. Update the SOP. Date it so you know it is current.

A neat trick: once your VA is comfortable, ask them to write or improve SOPs. They know where the instructions were unclear.

A 30-day training plan

Week 1: learn the basics

  • Walk through tools and access. See safe account access.
  • Start with two or three small, low-risk tasks.
  • Review every result the same day.
  • Use a short daily check-in.

Week 2: widen the range

  • Add one new task type.
  • Switch from reviewing everything to reviewing a sample.
  • Ask what was unclear and fix the SOP.

Week 3: build independence

  • Give a task with a goal rather than detailed steps.
  • Let the VA make small decisions, with a clear rule for when to ask.
  • Move check-ins to two or three a week.

Week 4: review and plan

  • Hold a 30-day review: what worked, what did not, what to change.
  • Agree new goals and hours.
  • Add the next set of tasks.

The onboarding checklist fits alongside this plan.

Teach judgement, not just steps

Steps handle the usual case. Judgement handles the rest. Help your VA with:

  • Decision rules. “If the refund is under $50, approve it. If it is more, ask me.”
  • Priorities. What to do first when everything is urgent.
  • Examples of tone. Show three replies you consider good.
  • Context. Why customers or clients matter, not only what to type.

Give feedback that works

  • Be specific. “The subject line was unclear” beats “needs improvement”.
  • Be prompt. Feedback the same day lands better.
  • Praise what is right, so they repeat it.
  • Explain the reason, so the lesson carries to other tasks.
  • Fix the SOP, not only the mistake.

Keep quality consistent

  • Checklists. A short checklist at the end of each SOP.
  • Spot checks. Review a sample of work every week.
  • A shared knowledge base. One folder or wiki everyone uses.
  • Change log. Note when instructions change.
  • Regular reviews. A monthly look at what to improve.

Mistakes to avoid

  • Documenting everything on day one. Start with the top three recurring tasks.
  • Writing for yourself. Write so a stranger can follow it.
  • Never updating. An old SOP is worse than none.
  • Training only by chat. Instructions get lost in message threads.
  • Skipping the test. If the VA cannot follow it, it is not finished.

Why SOPs pay off

  • Faster onboarding for the next VA.
  • Less rework from unclear instructions.
  • Less dependence on one person.
  • Easier delegation as the business grows. See how to delegate.

Frequently asked questions

How long should an SOP be?

One page, or a recording under five minutes. If it needs more, split it.

Do I need special software?

No. A shared document or folder is enough to start. See tools for working with a VA.

Who should write the SOPs?

You, or your VA from your recordings. Review them together.

How often should I update them?

Whenever a process changes, and review them every few months.