A good SOP for a virtual assistant fits on one page, starts with what done looks like, lists the steps in order with a screenshot or video for anything tricky and ends with a short section on what to do when something looks wrong. Record yourself doing the task once, have the assistant draft the written version and then correct it together. Review each SOP whenever the process changes.
Most owners know they should write things down. Few do, because writing procedures feels like a project. So the knowledge stays in their head, and every new hire learns by interruption.
The good news is that an SOP your assistant will actually use is short. Long manuals get skimmed and ignored. A clear page with the right details gets opened every time.
Why most SOPs fail
Before the template, it helps to know what goes wrong.
They describe the ideal process
Owners write down how things should work, not how they actually work. The assistant hits the first real exception and the document is useless.
They skip the why
Steps without context break as soon as anything changes. One sentence explaining the purpose lets a smart assistant adapt.
They live somewhere nobody looks
An SOP buried in a shared drive folder three levels deep does not exist in practice. Link it from the task itself.
They never get updated
The software changes a button and the process moves on while the SOP quietly goes stale. Then people stop trusting all of them.
A one page SOP template
Copy this structure for each process.
Title
Name it by the result. "Send weekly client invoices" is clearer than "Billing process."
Purpose
One or two sentences on why this matters and who relies on it.
When it happens
How often and when, such as every Monday by noon Eastern, or whenever a new lead form arrives.
What done looks like
Describe the finished state. For invoices, that could be every active client invoiced in QuickBooks and emailed, with the tracker updated with the date sent.
Before you start
Logins, files and information needed. Link directly to each one.
Steps
Numbered, one action per step. Add a screenshot or a short video link for any step where people tend to get lost.
Exceptions
The common things that go wrong and what to do about each. This is the most valuable section and the one most often skipped.
When to ask
The specific situations where the assistant should stop and check with you.
Last updated
A date and the name of who updated it.
An example
Here is a short SOP for handling a new website inquiry.
The purpose is to respond to every new inquiry within two business hours so leads do not go cold. It happens whenever a form submission lands in the leads inbox. Done means the lead is in the CRM with a tag, a reply has gone out using the right template and a follow up task exists for two days later.
- Open the new form email in the leads inbox
- Search the CRM for the email address to check for an existing contact
- If none exists, create the contact and add the source tag "website form"
- Choose a reply template based on the service they selected
- Personalize the first line using something from their message
- Send the reply from the shared sales address
- Create a follow up task for two business days later
- Label the email as handled
For exceptions, if the inquiry is from an existing client, forward it to the owner instead of replying. If the message is spam, delete it and do not add it to the CRM. If they ask for pricing outside the standard plans, reply with the general template and flag it in the update.
The assistant should ask before replying to anything that mentions a complaint, a refund or a legal issue.
That whole SOP takes a few minutes to read. It will save hours of questions. If you run a CRM, our CRM virtual assistant guide has more on the kinds of processes worth documenting there.
The fastest way to write them
Do not sit down to write twenty SOPs. Build them as you go.
- The next time you do a task, record your screen and talk through it
- Send the recording to your assistant
- Ask them to draft the SOP using the template
- Review the draft, fix what is wrong and add exceptions you know about
- Save it where the task lives and link it
This flips the work. The assistant does the writing and you do the checking. It also proves they understood the process, because gaps in the draft show you exactly what to explain again. It fits naturally into the onboarding checklist for the first two weeks.
Where to keep them
Pick one home. A shared folder in Google Drive or OneDrive works. So does a wiki tool like Notion or a page inside your project tool. What matters is that you can link each SOP from the task that needs it. Our guide to virtual assistant tools compares a few options.
Name files consistently. Start each with the area, such as "Finance" or "Sales," so they sort neatly.
Keeping SOPs current
Give the assistant ownership of updates. When they notice a step has changed, they edit the SOP and mention it in their daily update. You review the change at your weekly call.
Once a quarter, skim the list. Archive anything for a process you no longer run. Merge near duplicates. A smaller set of accurate documents beats a large set of stale ones.
Signs your SOPs are working
The assistant asks fewer repeat questions. New tasks get handed over faster. A second hire or a backup can step in without a week of training. And you can take a few days off without everything stopping.
A quick quality check for any SOP
Before you call an SOP finished, hand it to someone who has never done the task and ask them to follow it without help. If they get stuck, the document has a gap. If no one is available, read it aloud while pretending you have never seen your own software. You will spot the missing step quickly.
A few more checks are worth a minute each.
- Every link opens the right file or tool
- Each step starts with a verb such as open, copy, send or check
- Screenshots match the current version of the software
- The exceptions section covers the last three things that went wrong
SOPs for judgment calls
Some work cannot be reduced to steps. Replying to an upset customer or deciding which meeting to move are judgment calls. You can still document them. Instead of steps, write principles and examples.
For customer replies, that might be a short list of what you always do, such as apologize once and offer a clear next step, plus two or three past replies you liked. For calendar conflicts, it might be a ranked list of whose meetings come first. Examples teach judgment better than rules, and they give your assistant something to compare against when a new situation comes up.
When it makes sense to get help
If documenting processes keeps falling to the bottom of your list, an assistant with strong writing skills can take most of it off you. Learning how to delegate tasks when you are used to doing everything yourself is often the real first step. At delegateit, an Assistant starts at $1,500 a month full time or $900 part time. See our pricing page for detail.
SOP questions
How long should an SOP be?
One page for most tasks. If a process needs more, split it into smaller SOPs that link to each other.
Should I use video or written SOPs?
Use both. A short recording shows the process and a written page makes it easy to follow and update.
Who should write the SOPs?
Record the task yourself, then let your assistant draft the written version for you to review.
How often should SOPs be updated?
Whenever the process changes, plus a quick quarterly review to archive anything no longer used.