SOP Template: How to Write Standard Operating Procedures That Actually Get Followed (Free Examples)

The problem isn’t your VA. The problem is you don’t have a proper SOP template in place.

A good standard operating procedure template turns your tribal knowledge into a repeatable system. It means your VA can complete tasks correctly without pulling you into every small decision. And according to internal research at Armasourcing, 69% of managers say lack of documented processes is the #1 reason their remote teams underperform.

This guide gives you a copy-and-use SOP template, a 6-step process for writing your own SOPs, and three real virtual assistant SOP examples you can adapt today. No fluff — just the framework you need.

What Is an SOP? (And Why Most Teams Ignore Them)

An SOP — standard operating procedure — is a written set of instructions that describes how to complete a specific task. It tells the person doing the work: what to do, in what order, how to handle exceptions, and what success looks like.

Simple enough. So why do so many business owners skip them?

Because writing SOPs feels like overhead. You’re busy. The task is faster to just do yourself. And besides, your VA seems to get it — until they don’t, and a client gets the wrong invoice or a social post goes out without approval.

The real cost of not having SOPs isn’t the hour you saved by not writing them. It’s the hours you spend fixing mistakes, re-explaining processes, and rebuilding trust with clients after avoidable errors.

According to Atlassian’s research on team documentation, teams with documented processes onboard new hires 60% faster and see significantly fewer repeat errors.

SOPs aren’t bureaucracy. They’re respect for your team’s time and yours.

What a good SOP is NOT:

• A 20-page manual nobody reads
• A vague checklist with no context
• A one-size-fits-all document copied from Google
• Something you write once and forget

A useful SOP is specific, short enough to actually read, and written for the person doing the task — not for you.

The 5-Part SOP Template (Copy and Use Today)

Here’s a standard operating procedure template you can copy directly into Google Docs, Notion, or whatever your team uses. Fill in the brackets with your actual content.

That’s the full SOP template. You can adjust the number of steps and quality checks based on the complexity of the task. The key is: it should be specific enough that someone new can do the task correctly without asking you a single question.

If you’re in the process of building out your VA’s role, read our guide on how to train your VA without creating a 200-page manual — it covers how to prioritize which SOPs to write first.

How to Write an SOP Step by Step (6-Step Process)

Writing an SOP isn’t hard. The mistake most people make is trying to write it from memory, in one sitting, before they’ve actually observed how the task is done. Here’s the process that works.

Step 1: Choose One Task at a Time

Don’t try to document everything at once. Start with the tasks your VA does most frequently or the ones where mistakes cause the most pain. Pick one task and commit to finishing that SOP before moving on.

Step 2: Do (or Watch) the Task Once

Before you write a word, complete the task yourself — or screen-record your VA doing it. You want to capture every micro-decision: which tab do you open first, what do you type in, what do you check before moving on. These are the details that get missed when writing from memory.

Loom is great for this. Record the screen, narrate as you go, then use the recording as a reference while you write. The Nielsen Norman Group recommends combining video walkthroughs with written steps for maximum comprehension.

Step 3: Write the First Draft in Plain English

Write your SOP as if you’re explaining the task to a smart person who has never done it before. Use plain language. Active verbs. Short sentences. Avoid jargon and internal acronyms unless they’re defined.

A good test: read each step out loud. If it sounds confusing, rewrite it. Your VA shouldn’t have to re-read a step three times to understand what to do.

Step 4: Have Your VA Complete the Task Using Only the SOP

This is the most important step. Give your VA the SOP and ask them to follow it — without asking you any questions. If they get stuck, that’s not a failure on their part. It means the SOP has a gap. Note every question, every hesitation, every wrong turn. Those become the edits to your next version.

Step 5: Revise Based on Real Feedback

Update the SOP with everything you discovered in Step 4. Add screenshots or short video clips for complex steps. Call out the common mistakes explicitly: “Do NOT do X — it causes Y.” Make the quality checklist at the end reflect what actually gets missed in practice.

Step 6: Store It Where Your VA Will Find It

An SOP that lives in your downloads folder or a Slack message thread is useless. Every SOP needs a home — a shared Notion workspace, a Google Drive folder called “Team SOPs,” a ClickUp doc. It should be searchable, organized by task type, and accessible to your VA from day one.

Version control matters too. When you update an SOP, bump the version number and note what changed. That way your VA always knows they’re looking at the current version.

Building a proper onboarding process to go with your SOPs? See our guide on how to onboard a VA in 7 days without losing momentum.

SOP Examples for Virtual Assistants (3 Real Scenarios)

The SOP template above is the structure. Here’s what it looks like applied to three real VA tasks. These are simplified for brevity — your actual SOPs will have more steps.

VA SOP Example 1: Social Media Posting (Instagram + Facebook)

Purpose: Ensure all social media posts go out on time, on-brand, and approved before publishing.

Trigger: Use this SOP every Monday, Wednesday, and Friday before 9:00 AM PHT.

Steps:

1. Open the Content Calendar in Google Sheets (link in shared drive).
2. Locate today’s scheduled posts (column B = date, column C = platform).
3. Copy the approved caption from column D. Do not edit the caption — if you see a typo, flag it in Slack before posting.
4. Download the attached image from column E (Google Drive link).
5. Log into Buffer. Select the correct profile for each platform.
6. Paste caption + upload image. Set the scheduled time per the calendar (column F).
7. Click “Schedule” — NOT “Post Now.” All posts must be scheduled, not published manually.
8. In column G of the Content Calendar, mark status as “Scheduled” and add your name.

Quality Checks: Caption matches approved version. Image dimensions are correct (1080×1080 for feed). No misspelled client or brand names. Scheduled time is correct timezone (PHT).

VA SOP Example 2: New Client Onboarding

Purpose: Ensure every new client receives a consistent, professional onboarding experience within 24 hours of signing.

Trigger: Activated when a new client contract is signed and payment confirmed.

Steps:

1. Check the CRM (HubSpot) for the new client record. Verify contact name, email, and package type.
2. Duplicate the Client Onboarding folder template in Google Drive. Rename it “[Client Name] — [Month Year]”.
3. Send the welcome email using Template #3 in Gmail drafts. Fill in [Client Name], [Package], and [Kickoff Call Date] before sending. CC eli@armasourcing.com.
4. Share the client portal access link. The client’s login is their email + default password (in the password manager under “Client Portal Defaults”).
5. Create the kickoff call event in Google Calendar using the template event “Client Kickoff – [Name]”. Invite the client email and eli@armasourcing.com.
6. Update the CRM status from “Signed” to “Onboarding in Progress.”
7. Post in the #client-updates Slack channel: “[Client Name] onboarded. Kickoff: [Date/Time].”

If client email bounces: Do not guess an alternate email. Immediately message Eli on Slack with the bounced email and the client name.

VA SOP Example 3: Weekly Reporting

Purpose: Deliver an accurate weekly performance report to the team every Friday by 4:00 PM PHT.

Trigger: Every Friday morning. Allow 2 hours minimum.

Steps:

1. Open the Weekly Report Google Sheet (link in shared drive under /Reports/Weekly).
2. Pull the data for each metric listed in column A from their respective sources (sources listed in column B).
3. Enter this week’s data in column C. Do not overwrite last week’s data — it auto-moves to column D.
4. The summary chart on Tab 2 updates automatically. Screenshot this chart.
5. Open the Weekly Report email template (Gmail drafts — “Weekly Report Template”). Replace [Week Dates], paste the screenshot, and fill in the “Highlights” section (3-5 bullet points of notable changes).
6. Send to the distribution list (already saved in the To field). Do not BCC. Send time: between 3:30 PM – 4:00 PM PHT.
7. Mark the week as “Sent” in the Reports Log tab.

If a data source is unavailable: Note “Data unavailable — [reason]” in the cell rather than leaving it blank. Flag in the email highlights section.

Common SOP Mistakes That Kill Team Productivity

Having an SOP and having a good SOP are very different things. Here are the most common mistakes business owners make — and what to do instead.

Mistake 1: Writing SOPs that are too long.
If your SOP is longer than one page for a single task, it will get skimmed or ignored. Break it up. Create a separate SOP for each distinct task instead of one massive document for an entire role.

Mistake 2: Using vague language.
“Update the client” is not an instruction. “Send the client a status email using Template #2 in Gmail drafts by Thursday 5 PM” is. Every step should have a clear action and a clear outcome.

Mistake 3: Writing the SOP once and never updating it.
Tools change. Processes evolve. An SOP that reflects how you worked 18 months ago will cause more confusion than no SOP at all. Schedule a quarterly review — 30 minutes to scan your top 10 SOPs and update anything that’s changed.

Mistake 4: Not including what to do when things go wrong.
Every SOP needs an “exceptions” section. What should your VA do if the tool is down? If the client responds angrily? If the file is missing? Covering these scenarios upfront means your VA can handle issues independently instead of freezing up and waiting for you.

Mistake 5: Never testing the SOP with a fresh pair of eyes.
The curse of knowledge is real. What’s obvious to you after doing a task 200 times is not obvious to someone doing it for the first time. Always have your VA run through the SOP before you call it final.

As Harvard Business Review notes, the biggest barrier to procedural compliance isn’t attitude — it’s clarity. People skip steps when the steps are ambiguous, not because they’re lazy.

How to Get Your VA to Actually Use Your SOPs

Writing the SOP is half the battle. Getting your team to use it consistently is the other half. Here’s what works.

Build the habit during onboarding. From day one, make it clear: every task has an SOP. Before your VA does anything for the first time, they read the SOP. This sets the expectation immediately and prevents the “I thought I could figure it out” problem later.

Link SOPs to the task, not just a folder. Don’t just have a Google Drive folder called “SOPs.” Put the SOP link in the task itself — in ClickUp, Asana, or Notion, there should be a direct link to the relevant SOP on every recurring task. Remove the friction of finding it.

Make updating SOPs part of the job. When your VA notices a step is outdated or finds a better way, they should feel empowered to flag it. Set up a simple process: “If the SOP doesn’t match reality, add a comment and message me.” You own the approval; they own the observation.

Use SOPs as your performance baseline. When reviewing your VA’s work, reference the SOP. “This step says X, but the output shows Y — what happened?” This makes feedback objective and removes personal tension from the conversation. It’s not about blame. It’s about the process.

Reward SOP compliance. If your VA follows the SOP and gets a clean result, say so. “The report came out exactly as specified — thank you.” Positive reinforcement makes people want to use the system, not avoid it.

Ready to build a VA relationship that’s built on trust and clear systems from day one? Start by reading how to hire a virtual assistant who’s already used to working within structured processes. Then check out our full guide on virtual assistants for agencies if you’re scaling a team.

The truth is, the best SOPs in the world won’t fix a bad hire. But with the right VA and the right processes in place, you can build a team that runs without you having to be in every conversation. That’s the goal.

FAQ

What should an SOP template include?

A good SOP template should include five core sections: (1) the title and metadata (version, owner, last updated), (2) the purpose — why this SOP exists, (3) the scope — when and to whom it applies, (4) step-by-step instructions written in plain English with specific actions, and (5) a quality checklist and exceptions section covering what to do when things go wrong. Screenshots or short video clips can be added for complex steps.

How long should an SOP be?

For most tasks, one page is ideal. Two pages maximum for complex, multi-stage processes. If your SOP is running longer than that, it’s likely covering multiple tasks that should each have their own separate SOP. The goal is for your team to read it before starting — not after they’ve already gotten halfway through the task.

What’s the difference between an SOP and a checklist?

A checklist tells you what to do. An SOP tells you what to do, why it matters, how to do each step specifically, and what to do when something doesn’t go according to plan. Checklists are useful for routine confirmation (did I do all the steps?). SOPs are for training, consistency, and error prevention. The best systems use both — an SOP for training and a checklist as the daily reference.

Do virtual assistants need SOPs for every task?

Not every task — but every recurring task should have one. Start with the tasks that happen most often or where a mistake would cause client-facing problems. Inbox management, reporting, posting content, onboarding clients — these are the high-value targets. One-off tasks usually don’t warrant a full SOP unless they’re likely to repeat.

How often should SOPs be updated?

Review your SOPs at minimum once per quarter. Any time a tool changes, a process evolves, or a team member flags that a step no longer matches reality, update the SOP immediately and bump the version number. An outdated SOP is often worse than no SOP — it creates false confidence and leads to errors that are hard to trace back to their source.