How to Write Simple SOPs Your Virtual Assistant Can Actually Follow

Most small business owners do not have written processes. They have habits, and those habits live in their heads. That works until you hand a task to a virtual assistant and the result comes back slightly wrong in four different ways.

The fix is not a 20 page operations manual. It is a short, plain document that tells someone exactly how you want one task done. That is an SOP, a standard operating procedure, and a good one fits on a single page.

Why Most SOPs Get Ignored

The usual failure is length. Founders sit down on a Sunday, try to document everything they do, and end up with a wall of text nobody opens. Or they write the opposite: "Handle the inbox." That is a wish, not a procedure.

A VA working in a different time zone cannot walk over to your desk and ask what you meant. Whatever you leave in writing is the whole instruction. So the document has to be short enough to read in a minute and specific enough to follow without guessing.

Start With One Task, Not Your Whole Business

Pick one task you repeat at least weekly. Sorting the inbox, sending invoice reminders, updating a listing, booking appointments. Write the SOP for that and nothing else.

If you are unsure where to begin, look at what you handed off first. Our post on what to delegate to your first VA has a starter list, and each item on it is a good candidate for a first SOP.

The Simplest Format That Works

Use the same five parts every time:

• Goal: one sentence on what done looks like.
• Where it happens: the tool, the account, the folder.
• Steps: a numbered list, five to ten items, each starting with a verb.
• Watch outs: the two or three mistakes you see most often, and the fix for each.
• When to ask: what should make your VA stop and message you instead of guessing.

That last part matters more than people expect. A VA who knows exactly when to escalate will save you from the quiet errors, the ones nobody notices until a client does.

Write Steps Like Instructions to a Smart Stranger

Assume your VA is capable but has never seen your business. Skip what any professional already knows. Spell out what is specific to you.

Compare these two steps. "Follow up with the lead" tells them nothing. "Open the leads sheet, filter by status New, send template B from the shared inbox, then change the status to Contacted" tells them everything. The second one takes ten seconds longer to write and removes a dozen questions.

Name the exact tools and files. Say which template, which folder, which column. If a step involves a judgment call, write down the rule you use. For example, "If the customer mentions a refund, do not reply. Forward it to me."

Show, Do Not Only Tell

A short screen recording of you doing the task once beats three paragraphs. Record it while you narrate, five minutes at most, and paste the link at the top of the SOP. Screenshots help too, especially for anything with a button that is hard to find.

Do not worry about polish. A rough recording of the real process is more useful than a clean mock-up of an imaginary one.

Put Time Expectations in Writing

Your VA cannot guess what fast means to you. State it in your own time zone. "Reply to new inquiries the same business day." "Invoices go out by 10 AM Eastern on the first of the month." If something is not urgent, say that too, so it does not get dropped in a hurry.

Test the SOP on Someone Who Is Not You

Give the draft to your VA and watch the first run, or read their questions afterward. Every pause is a bug in the document. If they ask "which folder?" the step was missing the folder. Fix it right then, while the confusion is fresh.

Do this once or twice and the SOP stabilizes. After that, most questions disappear and you get the time back that you were hoping delegation would give you.

Keep Them in One Place

Pick one home for every SOP, a shared folder, a Notion page, whatever your team already opens daily. Name each file after the task, such as Invoice reminders or New lead follow up, so your VA can find it by searching the obvious words. Putting a date on each one tells everyone which version is current.

If you are working with a staffing partner, ask whether they can share their onboarding checklist as a starting point. It is easier to edit a template than to write from a blank page.

Review Them Monthly, Briefly

Tools change and so do your preferences. Once a month, spend fifteen minutes with your VA and ask which steps felt wrong or out of date. Your VA is the one actually using the document, so they will spot problems before you do. Update the SOP, change the date, move on.

If the same mistake keeps showing up, do not just correct it again. Add it to the watch outs section. A repeated error is almost always a missing line in the document.

Common Mistakes

• Writing SOPs for tasks you do once a year. Start with the frequent ones.
• Mixing three processes into one document. One task, one page.
• Leaving out the why. A single sentence of context helps your VA make better calls on edge cases.
• Never updating them. An outdated SOP is worse than none, because people trust it.
• Writing it all yourself. Ask your VA to draft the second one from the recording, then edit it. They will often do it better than you.

A Realistic Plan

Write one SOP this week, for the task that costs you the most time. Test it, fix it, and then do the next one. A handful of short SOPs covering your most repeated work will do more for your delegation than any complicated system.

If you want help finding a vetted virtual assistant to hand your first SOP to, Talentgrama can help. Tell us what you need at talentgrama.com/contact.