Hiring a virtual assistant does not automatically remove you from the work.

If the VA still has to message you every time a familiar task comes up, ask where the latest file lives, confirm what “finished” means, or check what to do when something unusual happens, the task has been delegated but the process has not.

That is where a standard operating procedure, or SOP, becomes useful.

If you want to learn how to write SOPs for virtual assistant tasks, the goal is not to produce a long manual. It is to turn what you already know about a process into instructions that another capable person can follow without having to reconstruct your reasoning every time.

I regularly work inside structured workflows and SOPs as a virtual assistant. The procedures that are easiest to execute are rarely the longest. They make the outcome, source material, steps, quality standard, and escalation point obvious.

Here is how to build that kind of SOP.

A Good VA SOP Should Answer More Than “What Are the Steps?”

A list of instructions can tell your VA what to click or type.

A useful SOP also gives them enough context to know when the procedure applies, what good work looks like, and when they should stop rather than make an unsupported decision.

A practical SOP should normally answer questions such as:

• What result is this process supposed to produce?

• What starts the process?

• What information or files are required?

• What should happen, and in what order?

• What needs to be checked before the work is considered complete?

• What happens when the normal process does not fit the situation?

• Where does the completed work go, and who needs to know?

That distinction matters because real work rarely follows the happy path every single time.

1. Define the Outcome Before You Document the Actions

Start with the destination.

Before writing Step 1, write one or two sentences explaining what the process is supposed to accomplish.

For example, this is too vague:

Prepare the weekly social media posts.

A more useful outcome is:

Prepare the five approved posts listed in the weekly content calendar, schedule them for their assigned dates, and update the calendar so each item shows its final status.

The second version gives the VA something they can verify.

Add the scope at the same time. State when the SOP applies and, where necessary, what it does not cover.

For example:

• Applies to: approved organic social posts listed in the content calendar.

• Does not apply to: paid advertising, unapproved promotional offers, crisis communications, or posts requiring a new business decision.

This prevents an SOP from quietly expanding beyond the authority you intended to delegate.

UCLA’s SOP guidance for writers similarly treats purpose, scope, responsibility, and procedure as distinct parts of useful process documentation.

If the task is being handed to a new assistant, this step also connects directly to defining the first responsibility during VA onboarding. A task name alone is not enough. The person needs to know the expected result.

2. Perform the Task Once and Capture the Real Sequence

One of the easiest ways to write a weak SOP is to document the process from memory.

Familiar tasks contain small actions you may no longer notice.

You open a particular folder first. You check one column before another. You rename a file using a certain convention. You compare the final output with an approved example. You know not to continue when one field is missing.

Those details can disappear when you try to summarize the process later.

Instead, perform the task once while documenting what you actually do.

You can:

1. write notes as you work;

2. record your screen for reference;

3. capture screenshots at points where the interface matters;

4. note decisions you make automatically;

5. record the files, templates, or source material you use.

Then turn that raw capture into the SOP.

The recording is not necessarily the SOP itself. A video may be useful for demonstrating a visual process, but written instructions are usually easier to scan when the VA is completing the task for the fifth or fiftieth time.

3. Turn the Process Into Specific, Numbered Actions

Write the procedure in the order the work actually happens.

Each step should describe an observable action.

Prefer:

1. Open the current week’s content calendar.

2. Filter the Status column to “Approved.”

3. Open the matching approved asset folder.

4. Draft the scheduled post using the approved copy and asset.

5. Check the preview before scheduling.

Avoid instructions such as:

• Handle the content properly.

• Make the post look professional.

• Check everything.

• Use your judgment.

• Update it as needed.

Those phrases require the VA to guess what standard you have in mind.

Where possible, start steps with a clear verb:

• Open

• Check

• Compare

• Enter

• Rename

• Upload

• Review

• Schedule

• Record

• Notify

Do not split a simple process into dozens of microscopic steps just to make the SOP look thorough. Include enough detail for a qualified person to act correctly.

4. Link the Inputs, Templates, and Examples the VA Actually Needs

An instruction such as “use the correct template” is only helpful when the correct template is easy to identify.

For each process, list the resources required before the work starts.

That may include:

• the current brief;

• an approved content calendar;

• a spreadsheet;

• a brand or formatting guide;

• a folder of source assets;

• an approved example;

• a reporting template;

• access to the relevant platform.

Link to the maintained location rather than attaching random duplicates wherever possible.

Examples are especially useful when quality is partly visual or stylistic. If you want a blog upload formatted in a particular way, an approved completed page may communicate the standard faster than another paragraph of abstract instructions.

The same applies to screenshots. Use them where the interface, field, location, or visual result would otherwise be ambiguous.

Do not put passwords directly inside an ordinary SOP. Keep access in the appropriate account or credential system and tell the VA where the approved access process lives.

5. Write the Decision Rules Before the Exceptions Happen

The normal sequence is only part of the procedure.

A VA also needs to know what to do when reality does not match it.

Consider a research task.

The normal instruction might say:

Enter the company’s contact email in Column F.

But what happens when there is no email?

A better SOP includes the exception:

If no suitable public email can be verified, leave Column F blank, add “No verified email found” to the Notes column, and continue to the next company. Do not guess an address.

That is an operational decision rule.

A social-content SOP might say:

If the assigned asset has not been approved, do not schedule the post. Change its status to “Waiting for Approval” and notify the reviewer.

An outreach SOP might say:

If the prospect appears on the exclusion list, stop and mark the record “Do Not Contact.”

You do not need to predict every possible edge case before the SOP can be used.

Document the recurring exceptions that are already known, then improve the procedure when new ones appear.

A simple format works well:

If [condition], then [action]. If [higher-risk condition], stop and escalate to [role].

This lets the VA make routine operational decisions without extending their authority into decisions you still want to retain.

6. Define the Quality Check and the Meaning of “Done”

“Complete” needs a definition.

Without one, the person writing the SOP may be thinking, “The result has been checked and recorded,” while the VA is thinking, “I finished the main action.”

Add a short quality checklist to the end of the procedure.

For a content-upload task, that might include:

• correct page or post selected;

• final approved copy used;

• links tested;

• formatting checked;

• featured image confirmed;

• SEO fields completed when included in scope;

• preview reviewed before publishing or submitting for approval.

Quality checks should be specific enough to pass or fail.

“Looks good” is hard to verify.

“Preview the post on desktop and mobile and confirm there are no broken headings, missing images, or obviously incorrect links” is much clearer.

The SOP should then say what evidence marks the task as done.

For example:

Done = the post is scheduled, the scheduled date is visible in the publishing tool, and the content calendar status has been updated to “Scheduled.”

That closes the loop.

When several assistants share related work, this becomes even more important. My guide to managing multiple virtual assistants explains why shared procedures, quality checks, completion criteria, handoffs, and escalation rules help prevent different people from gradually creating different versions of the same process.

7. Use a Repeatable SOP Template

You do not need to invent the document structure again every time you delegate a new recurring task.

Use one simple template and adjust the depth to match the work.

Fill-in-the-blank SOP template

A simple recurring task may not need every field.

A process involving approvals, multiple systems, sensitive access, or several people may need more detail.

The template is there to prevent important information from disappearing, not to create paperwork for its own sake.

Virtual Assistant SOP Example: Creating and Scheduling a Social Post

Here is what the template can look like when applied to a practical delegated task.

SOP name

Create and Schedule an Approved Social Media Post

Purpose

Prepare and schedule approved organic social content according to the current content calendar, then update the calendar so the publishing status is visible.

Trigger

A content-calendar item reaches Approved status and has an assigned publishing date.

Scope

This SOP covers normal approved organic posts.

It does not cover paid advertising, new campaign strategy, unapproved offers, crisis responses, or material changes to approved copy.

Required inputs

• approved content calendar;

• approved copy or brief;

• approved image or media asset;

• current formatting or brand guidance;

• access to the agreed scheduling platform.

Procedure

1. Open the current content calendar.

2. Find the next item with Approved status and confirm its scheduled date.

3. Open the linked approved copy and media asset.

4. Create the post in the agreed scheduling platform.

5. Copy the approved text without changing the core message or offer.

6. Upload the correct approved media.

7. Check that line breaks, links, tags, and other required formatting display correctly.

8. Set the publishing date and time shown in the content calendar.

9. Review the complete preview.

10. Schedule the post.

11. Confirm that it appears in the scheduled queue.

12. Change the calendar status from Approved to Scheduled and record any required scheduling reference.

Quality checks

Before marking the task complete:

• the correct platform/account is selected;

• the approved copy and asset are being used;

• the publishing date matches the content calendar;

• links and required formatting have been checked;

• the post preview has been reviewed;

• the content calendar has been updated.

Exceptions and escalation

• If the media asset is missing or unapproved: do not schedule. Change the item to Waiting for Asset or Waiting for Approval and notify the reviewer.

• If the copy conflicts with the current approved offer: stop and ask for confirmation.

• If the scheduling platform shows an error: record the error and notify the appropriate contact rather than repeatedly attempting an action that may create duplicates.

• If the post requires a new business or campaign decision: escalate rather than inventing the decision.

Definition of done

The correct post is visible in the scheduled queue for the assigned date, the preview has passed the quality check, and the content calendar shows the post as Scheduled.

That is much more useful than an instruction such as “Please schedule this week’s social posts.”

The VA knows what starts the process, which material controls the work, what they are allowed to change, how they should check it, and when they should involve you.

Give Every SOP One Maintained Home

Writing an excellent procedure will not help much if nobody knows which copy is current.

Choose one maintained location for process documentation.

That might be a knowledge base, a shared document system, or another tool your business already uses.

The specific product matters less than the rule:

There should be one place where the current version wins.

My guide to tools for managing a virtual assistant goes deeper into separating the homes for tasks, communication, SOPs, files, walkthroughs, and credentials.

For the SOP itself, establish:

• where the current document lives;

• who owns it;

• who may edit it;

• where related templates live;

• when changes should be recorded;

• how the VA knows they are reading the current version.

A revision note does not need to become a complex compliance system for ordinary business tasks.

Something as simple as this can be enough:

Last reviewed: 9 September 2026
Owner: Marketing Manager
Latest change: Added approval rule for promotional posts.

Test the SOP With the Person Who Will Actually Use It

The writer understands the process too well to be the final judge of whether the documentation is clear.

Give the SOP to the VA and let them use it.

Watch for questions such as:

• Which file do you mean?

• Where is this field?

• What happens if this information is missing?

• Can I approve this myself?

• Where should I put the completed result?

• Should I continue when this error appears?

Those questions are useful.

They reveal where knowledge still exists in your head rather than in the procedure.

Penn State’s SOP writing guide recommends involving the people who perform a procedure in reviewing and improving its draft. That principle translates well to VA delegation: the person doing the work can identify ambiguities that the process owner no longer notices.

After the first real run:

1. fix unclear wording;

2. add missing links or examples;

3. record common exceptions;

4. remove instructions that proved unnecessary;

5. clarify quality checks;

6. update the SOP rather than leaving the correction inside a private message.

The goal is not to prove that your first draft was perfect.

The goal is to make the next execution easier.

Common SOP Mistakes That Create More Questions

Documenting only the happy path

If the SOP stops at the normal steps, every exception comes back to you.

Add the common decision and escalation rules.

Giving instructions without a definition of done

“Upload the page” and “research the companies” leave room for different interpretations.

State the acceptance criteria and completion evidence.

Referring to resources without linking them

“Use our template” is not an instruction unless the template is easy to find and clearly identified.

Explaining judgment with vague words

Instructions such as “choose a good prospect” or “make it professional” hide the actual decision criteria.

Write the criteria down where you can.

Making the SOP too long to use

More detail is not automatically better documentation.

If the VA has to search through several pages to find a five-step recurring procedure, split background reference material from the operational checklist.

Leaving corrections in chat

When a question changes the process, update the SOP.

Otherwise the written procedure and the real procedure slowly become two different things.

Never reviewing the document again

Processes change.

Tools change, templates move, approval rules change, and responsibilities shift.

An SOP should be maintained when the underlying workflow changes rather than treated as finished forever.

Turn Repeated Instructions Into a System

A useful SOP does not remove every question or every need for judgment.

It removes the questions that should already have an answer.

Start with one recurring task that repeatedly pulls you back into execution. Define the result, capture the real steps, add the required inputs, write the important decision rules, define the quality check, and let your VA test the document.

Then improve it from actual use.

You do not need a fifty-page operations manual before delegation can work. You need a dependable procedure for the next responsibility you want someone else to own.

At Boost VA, I support founders, agencies, and online businesses with recurring and project-based execution across growth, backend, and operations. If you have a defined workload that needs a reliable owner working within clear processes, tell me what you need help moving forward.