Ready to get
    your time back?

    Back to Blog
    Delegation Guides

    How to Write SOPs for Your Virtual Assistant (With a Template)

    Ramzi ChahinRamzi ChahinOct 1, 2026 8 min read
    How to Write SOPs for Your Virtual Assistant (With a Template)

    The fastest way to make delegation stick is to write down how things are done. Standard operating procedures (SOPs) turn "ask me how I like it" into a document your assistant can follow, improve and use to train the next person.

    The good news: SOPs don't need to be long or formal. The best ones are short, specific and kept up to date.

    Why SOPs Matter

    • Consistency: the task gets done the same way every time.
    • Less dependence on you: your assistant doesn't need to ask every time.
    • Faster onboarding: a new assistant can get up to speed in days, not weeks.
    • Continuity: if someone leaves or is on holiday, the work doesn't stop.
    • Better delegation: once a task is documented, it's much easier to hand over.

    What to Document First

    Don't try to document everything at once. Start with tasks that are:

    1. Frequent: done daily or weekly
    2. Error-prone: where mistakes are costly or embarrassing
    3. Repeatable: done the same way each time

    Good first candidates: inbox triage rules, scheduling preferences, meeting preparation, expense submission, the weekly report, travel booking preferences and new-client onboarding.

    The Fastest Way to Create an SOP

    Writing SOPs from scratch takes time most founders don't have. A faster method:

    1. Record yourself doing the task once, with a screen recording, narrating as you go.
    2. Ask your assistant to write the SOP from the recording, using the template below.
    3. Review and correct it in five minutes.
    4. Let your assistant do the task from the SOP, and update the document wherever it was unclear.

    AI tools can also turn a recording transcript into a first draft, which your assistant then checks and edits.

    The SOP Template

    Copy this structure for each task.

    Task name

    A short, clear name, such as "Weekly investor update" or "Booking travel for the CEO."

    Purpose

    One or two sentences on why this task matters and what good looks like.

    Owner and frequency

    Who does it, how often, and by when (for example, "Every Friday by 3pm UK time").

    Tools and access

    The tools, accounts, templates and folders needed.

    Steps

    Numbered steps, each starting with a verb. Add screenshots or links where helpful.

    Rules and preferences

    The judgment calls: what to prioritise, what to avoid, when to escalate.

    Definition of done

    How the assistant knows the task is complete and correct.

    Last updated

    The date and who updated it.

    A Worked Example: Inbox Triage

    Purpose: Make sure the CEO only sees email that needs their decision, and nothing important is missed.

    Owner and frequency: Executive assistant, twice daily, at 9am and 3pm.

    Tools and access: Delegated Gmail access, labels set up, and the shared "Needs decision" document.

    Steps:

    1. Open the inbox and sort by unread.
    2. Archive newsletters and notifications, and unsubscribe from anything unread for 30 days.
    3. Reply to routine requests (scheduling, simple questions) using the saved templates.
    4. Draft replies to anything that needs the CEO's tone, and save them as drafts.
    5. Add every email that needs a decision to the "Needs decision" document, with a one-line summary and a recommended action.
    6. Label anything waiting on someone else as "Waiting" and set a follow-up reminder.

    Rules and preferences:

    • Investors, board members and key customers are always flagged the same day.
    • Never reply to legal or HR matters without approval.
    • If something looks urgent and the CEO is unavailable, message them directly.

    Definition of done: The inbox is empty or labelled, drafts are saved, and the decision list is up to date.

    Where to Keep SOPs

    Keep them in one place your whole team can find and search:

    • Notion or Confluence: good for structured wikis with search
    • Google Docs or Microsoft Word in a shared folder: simple and familiar
    • Your project management tool: good for linking SOPs directly to recurring tasks

    Use a consistent naming format, such as "SOP – Inbox triage", so documents are easy to find.

    Keeping SOPs Up to Date

    An outdated SOP is worse than none. To keep them current:

    • Make the assistant the owner of updating SOPs whenever a process changes.
    • Review them every quarter, or whenever something goes wrong.
    • Add a "last updated" date to every document.
    • Delete SOPs for tasks you no longer do.

    Common Mistakes

    • Too long: if an SOP is longer than a page or two, split it.
    • Too vague: "handle the inbox" isn't a step. "Archive newsletters" is.
    • Missing the judgment calls: the rules and preferences section is where most of the value is.
    • Written once and forgotten: schedule reviews.
    • Written by the wrong person: your assistant should usually write them, and you should review them.

    SOPs are also the backbone of a smooth first week. See our 7-day onboarding plan, and our list of tasks to delegate for ideas on what to document next.

    Frequently Asked Questions

    What is an SOP for a virtual assistant?

    A short written guide explaining how to complete a recurring task: its purpose, the tools needed, the steps, the rules for judgment calls and what "done" looks like.

    How long should an SOP be?

    Usually one page or less. If it's much longer, split it into separate SOPs for each part of the process.

    Who should write SOPs, me or my assistant?

    Usually your assistant, based on a recording or walkthrough from you. You then review and correct it. This is faster for you, and it confirms they've understood the task.

    What tools are best for SOPs?

    Any shared tool your team already uses: Notion, Confluence, Google Docs or your project management tool. What matters most is that SOPs are easy to find and kept up to date.

    How many SOPs does a small business need?

    Start with five to ten for your most frequent, error-prone tasks, and add more as you delegate new work.

    If you'd like an assistant who documents processes as they learn them, book a call.

    Ramzi Chahin
    Ramzi Chahin

    Founder, VentureCopilot

    Ramzi is the founder of VentureCopilot, which matches founders and growing companies with vetted, AI-fluent remote talent. He writes about hiring, delegation and building lean teams.

    Ready to hand off the work that's slowing you down?

    Book a free 30-minute call and we'll help you figure out the right hire for your stage.

    Book a call