How to Write SOPs for Your Filipino Virtual Assistant (Free One-Page Template)

Most founders skip SOPs because they feel like corporate paperwork. But a one-page checklist is the difference between a VA who guesses and a VA who executes exactly the way you would. Here is how to document your first five processes and hand them to a Filipino VA in one afternoon. When you write your first SOPs for virtual assistant roles, you are not building a bureaucracy; you are removing the guesswork from your operations.

Why SOPs Matter More With a Remote Filipino VA

The moment you hire someone in UTC+8, you lose the hallway conversation. Your VA works while you sleep. They cannot lean over your shoulder and ask "how do you want this one done?" in real time, because by the time they reach you, the question has already sat for hours.

A documented process becomes your shared team memory. It gives you consistent output, a faster onboarding curve, and the chance to delegate a task once instead of re-explaining it every single week. The good news is that simple checklists are enough for a small team. You do not need a thick binder; you need clarity. Around half of small businesses fail within five years, and unstructured operations plus an over-reliant founder are part of that picture, so building documentation early is cheap insurance.

Filipino VAs tend to respond well to structure and clear expectations. A written playbook signals that you run a serious operation and that you have thought about how you want work done. That clarity earns trust on both sides.

What an SOP Is (and Isn't)

An SOP, or standard operating procedure, is a step-by-step guide for HOW to complete a task. A policy document sets the rules or principles behind those tasks. It is a small distinction with big consequences for how you write.

SOP vs Policy

For a VA, you want task-level, operational SOPs. Think "process a new order," "publish this week's social posts," or "triage the inbox." These are the repeatable actions your VA will actually run.

Policies belong in a short separate document. Vacation rules, spending limits, and approval thresholds are policies. They tell your VA what is allowed, not how to do a task. Keeping the two apart means your VA can open the right file and find exactly what they need, rather than digging through a stack of rules.

The 5 Processes to Document First

Start with tasks that are recurring and rule-based, the things you do more than once a week. Five strong candidates cover most small operations:

• Inbox triage: labels, draft replies, and what to flag for your attention.
• Calendar and scheduling rules: who gets time, how buffers work, and where bookings land.
• Social media publishing workflow: approvals, scheduling windows, and posting cadence.
• CRM and data entry updates: how records stay clean and what fields matter.
• Client onboarding or follow-up emails: the sequence and the tone to use.

If a task repeats weekly and follows a pattern, it is a candidate for an SOP. Document these five before you hire, or during the VA's first week, so they start on solid ground instead of improvising.

SOPs for Virtual Assistant Teams: The 6-Step Writing Method

You do not need a consultant to write these. You only need to capture how you already work.

1. Pick a task and write the steps while you do it. Recording a Loom video as a first draft is faster and more accurate than typing from memory.
2. Turn it into numbered steps in plain English, with no jargon or shorthand only you understand.
3. Attach the tools, links, and login references. Never paste raw passwords; point to a password manager instead.
4. Define what "done well" looks like. Set a quality bar covering response time, tone, and format.
5. Add edge cases. What should happen when a particular situation comes up?
6. Test it. Have someone else, ideally your VA, follow the SOP and fix anything that confuses them.

The One-Page SOP Template

A one-page template keeps every SOP scannable and consistent. Use these fields for each process:

• Task name: a short, descriptive title.
• Goal: the outcome you want.
• Tools: the apps and links involved.
• Steps: numbered 1 through N.
• Quality bar: what "done well" means.
• Escalation rule: what to do when something falls outside the steps.

Writing your first SOPs for a virtual assistant becomes far easier once this template is in place, because each new process just fills in the same structure.

Where to Store SOPs (Tools)

Keep everything in one place so your VA never has to hunt for instructions. A single "VA Playbook" document in Google Docs or Notion with a table of contents works well for small teams. For walkthroughs, Loom or tools like Scribe and Tango capture video steps cleanly.

Version the document. Date each update so you and your VA always know the current version is the one you are reading. One source of truth beats a scattered folder of stale instructions every time.

How to Train Your VA on an SOP (and Improve It Over Time)

Writing the document is only half the job. In week one, walk through the SOP together on a video call, then have your VA execute it live while you watch. That first pass catches the gaps that only appear in practice.

Invite your VA to propose improvements. They see the process from the operator's side, so they will spot friction you have long since stopped noticing. Update the document and re-version it quarterly, or whenever you change a tool. Philippine agencies that publish SOP guidance make the same point: effective SOPs speed up tasks and lift productivity when they are short, visual, and actually tested.

Document your first five processes this afternoon, hand them to your Filipino VA, and watch the guessing disappear.