Virtual assistant SOP checklist: how to write instructions a VA can actually use
Use this virtual assistant SOP checklist to write clear steps, quality checks, escalation rules, access limits, and a 30-day improvement loop.
Operator sections with practical steps.
Decision points before handoff.
Visible citations and source notes.
Key takeaways
- A useful VA SOP defines the outcome, tools, inputs, rules, and quality checks.
- Start with 3 SOPs for the first work lane instead of documenting the whole company before the assistant starts.
- Every SOP should include 1 good example, 1 common mistake, and 1 ask-for-help rule.
- For the first 2 weeks, review risky work before it goes out and review a small sample of safe work so the SOP improves from real misses.
- The SOP is finished when a trained assistant can run the task, report blockers, and update it.
A virtual assistant SOP is not a polished binder. It is the operating note a remote person opens while doing the work. If the SOP only says "handle inbox" or "update CRM," the assistant still has to guess what good looks like and which exception needs the owner.
Use this checklist for the first 30 days with a VA, offshore admin, remote executive assistant, or operations helper. It fits recurring work like inbox sorting, scheduling, lead research, CRM cleanup, invoice follow-up, and weekly reporting.
SOP versus checklist
Copy-ready SOP header
Put this short block at the top of a new SOP before writing the steps.
- Purpose: [finished result]. Trigger: [what starts the work]. Due: [time and time zone].
- Allowed: [safe actions]. Stop and ask: [money, customer, legal, access, or missing-data exceptions].
- Proof before submit: [three to five checks]. Escalate in: [the named channel] with links or screenshots.
Start with the outcome, trigger, and risk level
Write the SOP title as a recurring result, not a vague activity. "Prepare Friday CRM follow-up list" is better than "CRM work." Add the trigger, due time, owner, tools, and risk level. A safe cleanup task can move faster than a customer-facing reply, refund note, or contract edit.
A simple opening block names purpose, timing, finished work, file location, exception reviewer, and what the assistant may not do alone. The U.S. Bureau of Labor Statistics describes administrative assistant work around scheduling, correspondence, records, and office support, all visible finished work for a first VA lane.
List inputs, tools, permissions, and security rules
Every SOP should tell the assistant where the work starts: inbox label, CRM view, folder, spreadsheet, template, saved search, or project board column. Then list the tools and permission level.
NIST's Digital Identity Guidelines treat authentication and account recovery as formal controls. For a small business, that means named accounts, MFA, a password manager, least-privilege access, and same-day removal when the role ends. Do not put passwords in an SOP.
Add an access check near the top: "If you cannot open the CRM view, calendar, template folder, or password manager item, stop and post a blocker before starting a workaround." That line prevents duplicate files, old templates, or credential requests in chat.
Write steps as observable actions, then add examples
Steps should be actions someone can see: open the saved view, filter by due date, check the source field, update the next step, save, and post the summary. Avoid "use judgment" unless the judgment rule is written.
For an inbox SOP, a useful rule sounds like this: "If the email mentions refund, cancellation, legal language, discount, payroll, bank details, public review, or an angry customer, draft only and tag the owner before sending." For a CRM SOP: "If source, owner, or next step is missing, do not mark the record complete; add the missing-field note and put it in Review Needed."
Add one clean example and one anti-example. A clean CRM record shows company name, contact owner, source URL, last touch, next step, and due date. An anti-example should show the missing field and the exact place where the assistant must stop for review.
Add a quality checklist the assistant uses before submitting
The QA section should be 5 to 8 checks, not a second SOP. For scheduling, check attendees, time zone, meeting link, agenda, buffer time, confirmation, and CRM note. For lead research, check company fit, title, source link, duplicates, email format, and confidence rating.
ISO's quality management principles emphasize process, evidence, and improvement. In a VA work process, that means the finished work has to meet written requirements before the manager reviews taste or preference.
"Looks good" is not a requirement. "All 12 rows have source links, company size, role title, and next action" is a requirement.
For the first 2 weeks, keep review heavier than you want it to be later. Review 100% of customer-facing, financial, or sensitive finished work before they leave the company.
For safe internal work, review a small sample and write down repeated misses. If 4 of 18 CRM records are missing source links, strengthen the checklist and example instead of asking someone to be more careful.
Give the assistant escalation language to copy
Ask-for-help rules tell the assistant when the SOP stops. Without them, careful assistants ask about everything and confident assistants guess on work they should not own. Put the red lines in one box: money, legal terms, angry customers, refunds, payroll, contracts, reviews, missing data, and tool access.
Give the assistant language they can paste into the daily update. Example: "I paused this because the invoice amount does not match the signed agreement."
"I checked QuickBooks, the contract folder, and last month's invoice. Please confirm whether to revise the invoice or update the contract note."
Another example: "I drafted the customer reply but held it because the message mentions a refund and a public review. Please approve or edit before I send."
A realistic scenario: a VA manages invoice follow-up for 12 clients and finds a $240 mismatch between the CRM note and invoice. The SOP should ask them to gather facts, hold the action, and escalate with links.
Use the first 30 days to improve the SOP
The first version only needs to be usable. Day 1 is the walkthrough and access test. Days 2 to 5 are practice on old examples or safe live work.
In week 2, review the work. Week 3 moves stable work to a small lane. Week 4 is the scorecard review and SOP cleanup.
End the month with a simple decision: keep, tighten, or expand. Tighten means the examples, access, QA checklist, or ask-for-help rules need repair. Expand means adding the nearest adjacent work process, not 10 random tasks.
How to use this playbook
Read this article like a work guide. Pick one task, one role, or one quality rule and turn it into a short checklist before you give it to an assistant. Small changes are easier to train and easier to check.
The next step is simple: connect the idea to a role scorecard, SOP, onboarding plan, or weekly scorecard. That turns the article into a tool you can use.
Where this fits
Virtual assistant SOP checklist: how to write instructions a VA can actually use fits the same basic path used across OutsourcedU: choose the work, write the rule, train the person, check the result, and add more only when the work is steady. Skipping steps usually creates cleanup work.
If this topic is active in your business, the next supporting page is SOP templates for outsourcing. Use that page to connect the article to a broader setup plan, including outcomes, rhythm, quality checks, and management expectations.
FAQ
What should a VA SOP include?
Include the outcome, trigger, frequency, inputs, tools, permissions, step-by-step actions, examples, quality checks, ask-for-help rules, owner, and last-updated date. For a first VA, 3 strong SOPs are more useful than 30 vague documents.
How detailed should a virtual assistant SOP be?
It should be detailed enough for a trained assistant to complete the task without repeated clarification. If a step could be read 2 ways, add a rule, screenshot, example, or escalation note.
Who should update SOPs?
The manager owns the standard, but the assistant should help update steps, examples, mistakes, and blocker notes as they perform the work. Review SOP changes weekly during the first 30 days.
Sources
- U.S. Bureau of Labor Statistics, Secretaries and Administrative Assistants — Administrative responsibilities.
- NIST SP 800-63B Digital Identity Guidelines — Supports authentication, account recovery, MFA, and access-control practices.
- Atlassian, code review best practices — Supports smaller review batches for catching errors.
- ISO, Quality management principles — Supports process, evidence, and improvement principles behind quality checks.