You wrote the SOPs. You shared them. The VA ignored them and did it their own way. Before concluding your VA is the problem, work through this diagnostic — because SOPs fail for predictable reasons that are usually fixable.
See also: what is a virtual assistant, how to hire a virtual assistant, virtual assistant pricing.
Why VAs Do Not Follow SOPs
1. The SOP Is Too Long or Hard to Use
An SOP that takes 10 minutes to read before starting a 5-minute task creates a strong incentive to skip it. Overly long, dense, or poorly organized SOPs get read once and ignored thereafter.
Fix: Trim SOPs to the minimum necessary detail. Use numbered steps, not paragraphs. Keep the most important steps in the first 5 lines.
2. The SOP Is Outdated
If the process changed after the SOP was written, the VA may have tried following it, found it did not work, and adapted on their own.
Fix: Date every SOP. Review and update SOPs quarterly. Ask VAs to flag when a step does not match current reality.
3. The VA Was Never Confirmed to Have Read It
Sharing an SOP does not mean it was read. Many VAs receive an SOP in onboarding, skim it once, and never return to it.
Fix: Require written confirmation ("I've read and understood the SOP for [task]") for each SOP during onboarding. For critical SOPs, walk through them together on a call.
4. The SOP Is Hard to Find in the Moment
A VA working on a task needs the SOP immediately accessible — not buried in a folder three levels deep. If finding the SOP requires more than two clicks, it will not be consulted.
Fix: Link the relevant SOP directly in the task brief or in the task management system beside the task type.
5. The VA Thinks Their Method Is Better
Sometimes VAs have genuinely found a better approach and adapted without communicating the change. This is not insubordination — it is initiative without communication.
Fix: Welcome this but formalize it. "If you have a better way, tell me and we will update the SOP together." This creates a culture where improvements are surfaced rather than silently adopted.
6. The SOP Was Never Properly Taught
Sharing an SOP is not the same as teaching it. Complex SOPs need a walkthrough — either a Loom video demonstrating the process or a live call where the VA executes it while you watch.
Fix: For any SOP covering a complex or high-stakes task, supplement the written document with a demonstration.
The SOP Audit Checklist
Before assuming the VA is the problem, check each SOP against these criteria:
- Is it 500 words or fewer for most tasks?
- Does it use numbered steps, not prose paragraphs?
- Was it updated in the last 6 months?
- Is it linked directly from the task management system?
- Did the VA confirm they read it?
- Was it demonstrated, not just shared?
- Does it include what to do when things go wrong?
If the SOP fails three or more of these criteria, the SOP is the problem — not the VA.
When the VA Is Genuinely the Problem
After fixing the SOP, if non-compliance continues:
- Have a direct conversation: "I need you to follow the SOP exactly unless you flag a problem with it first."
- Document the conversation and the specific instances of non-compliance
- Set a clear timeline: "If this continues after [date], I will need to reconsider this placement"
Most SOP compliance problems disappear when the SOP itself becomes genuinely usable. But some VAs have a consistent tendency toward independent action that does not respond to process. Identifying which situation you are in determines the right response.
Virtual Assistant VA places VAs with strong process discipline who actively use SOPs and flag outdated procedures. Find a candidate who respects operational standards.