A Virtual Assistant SOP Template With a Worked Example
By the Streamline Creative team · Published
A good SOP template saves a virtual assistant from reinventing the structure every time a new task needs documenting. This guide gives you a practical SOP template you can copy, a filled-in example, and the mistakes that make SOPs get ignored.
What should a virtual assistant SOP template include?
A VA SOP template should include the task name and purpose, when and how often it runs, the tools and access needed, numbered steps with enough detail for someone else to follow, a quality check or definition of done, and a note on who to ask when something is unclear. Keep it to one or two pages; a template that is easy to fill in gets used.
Key takeaways
- One SOP per recurring task, kept short enough to actually use.
- Numbered steps with screenshots beat long paragraphs of explanation.
- A definition of done tells the next person what finished looks like.
- Store SOPs where the work happens, not in a folder nobody opens.
- Review SOPs when the task changes, not on a fixed calendar.
If you have not read it yet, our guide on how to create an SOP as a virtual assistant covers when to write one and the writing process. This article is the practical companion: a template you can copy and a filled-in example.
The SOP template
Copy this structure into a document and fill in the brackets. It works for most recurring VA tasks.
| Section | What to write |
|---|---|
| Task name | What this SOP covers, in a few words. Example: “Scheduling weekly social posts.” |
| Purpose | Why this task matters to the client, in one or two sentences. |
| Frequency and trigger | When it runs: every Monday, when a form is submitted, at month end. |
| Tools and access | Every login, tool, and file needed, and where the access is stored. |
| Steps | Numbered steps, one action each, with a screenshot anywhere a screen could be misread. |
| Definition of done | How to check the task is complete and correct before marking it finished. |
| If something goes wrong | Who to ask, what to do with an urgent problem, what should never be guessed. |
| Last reviewed | The date this SOP was last checked against how the task is actually done. |
How an SOP gets written, step by step
Spot the repeat
A client task has happened two or three times.
Copy the template
Duplicate your blank SOP and name it clearly.
Fill it in while working
Write each step as you do the task, with screenshots.
Define done
Add how to check the result before marking it finished.
Confirm with the client
Ask them to check it matches their expectations.
Review when things change
Update the steps and the last-reviewed date.
A filled-in example
Here is the same template completed for a common task, scheduling social media posts.
Completed SOP example
SOP - Scheduling the client’s weekly Instagram posts
- Purpose
- Keeps the client’s account active and consistent without anyone posting manually each day.
- Frequency
- Every Friday, for the following week.
- Tools and access
- Meta Business Suite (login in the shared password manager), caption drafts in the “This Week” folder, graphics in the shared drive.
- Steps
- Open the content calendar and confirm which posts are approved.
- Open Meta Business Suite and create each scheduled post.
- Paste the approved caption and attach the matching graphic.
- Set the date and time from the calendar.
- Double-check the preview on mobile view.
- Mark each post as scheduled in the calendar.
- Definition of done
- All approved posts for the week are scheduled, previews checked, and the calendar shows them as scheduled.
- If something goes wrong
- If a post fails to schedule, message the client the same day. Never rewrite an approved caption without asking.
Notice how short it is. The value is in the specifics: where things live, what approved means, and what to never guess.
Formatting tips that make SOPs get used
- One action per step. “Open the calendar, confirm approvals, and start scheduling” is three steps, not one.
- Screenshots for anything visual. A cropped screenshot with an arrow replaces a paragraph of description.
- Name files and folders exactly. Write “the This Week folder in the shared drive,” not “the content folder.”
- Keep it findable. Store SOPs in the same place the client’s other work lives, with consistent names like “SOP - Scheduling Instagram posts.”
Common SOP mistakes
- Writing it for yourself. The test is whether someone else could do the task from the document alone.
- Too much background. The purpose section is two sentences, not the history of the client’s business.
- No definition of done. Without it, “finished” means something different to everyone.
- Writing it once and never touching it again. Tools and preferences change; an outdated SOP is worse than none because it looks trustworthy.
Where a template fits in your workflow
Keep one blank copy of the template as your starting point. When a client task becomes recurring, duplicate it, fill it in while you do the task, and ask the client to confirm it matches their expectations. If you want a ready-made starting point with a completed example, the free SOP Starter Kit includes an editable template and a worked example you can adapt.
Frequently asked questions
What is an SOP for a virtual assistant?
An SOP (standard operating procedure) for a virtual assistant is a short document that explains how to complete a recurring client task the same way every time: what the task is, what tools it needs, the steps in order, and what a finished result looks like.
How long should a VA SOP be?
Usually one to two pages. If an SOP is getting long, the task may actually be several tasks that each need their own SOP, or the steps may need screenshots instead of more words.
Should VAs create SOPs for their clients?
Yes, and clients usually appreciate it. Documenting the recurring tasks you handle protects the client if you are ever unavailable, makes handovers easier, and shows a level of professionalism that supports raising your rates over time.
Where should SOPs be stored?
Wherever the client’s work already lives: a shared folder, a ClickUp doc, or a Notion page the whole team can find. An SOP that is hard to find will not be used, no matter how well it is written.
How often should SOPs be updated?
Whenever the task itself changes: a new tool, a new step, a new client preference. Add a line at the top of each SOP with the date it was last checked so outdated ones are easy to spot.
Download the SOP Starter Kit
A free toolkit with an editable SOP template and a completed example, ready to adapt to your client work.
Download the SOP Starter KitWant help putting this into practice?
You do not need to know exactly what solution you need. Tell us where the work gets stuck and we will take it from there.
Tell us what’s not working