How to Write an SOP Before Hiring a Virtual Assistant

Start with an outcome, not a vague task list

Choose work you can demonstrate and inspect: preparing an internal meeting pack, updating a task tracker or organizing approved documents. Replace requests such as 'keep everyone organized' with a visible result such as 'prepare the current agenda and open-action list for the weekly planning meeting.'

EPA's Guidance for Preparing Standard Operating Procedures recommends concise, step-by-step instructions with enough detail for someone with basic relevant knowledge to reproduce the process. It also distinguishes an SOP from its supporting checklist. This guide adapts those general writing principles to business administration; it is not a statement of EPA requirements for your business.

Write down the process as it currently works. If nobody can identify the approved input or decide what happens when information is missing, resolve that gap before asking a new assistant to run it. Keep business priorities and decisions with a named client owner.

• Outcome: what should exist when the work is complete?
• Scope: where does this workflow start and end?
• Readiness: are the source material, rules and decision owner available?
• Boundary: which decisions are outside the assistant's authority?

Example: assign a weekly internal planning pack

The following is an original, fictional example for a generic business team. It contains no customer records or personalized Support Blueprint information. The schedule, roles and checks are illustrative choices, not an existing VSI internal policy or promised service level.

Purpose: the operations lead can see the agreed agenda, open actions and decisions needed before the weekly planning meeting. The VA prepares the pack; the operations lead retains priority and commitment decisions. Use this assignment card as the beginning of the SOP, then add the procedure below.

• Roles: the VA compiles documents and maintains the tracker. The client operations lead owns priorities and approves release. A named client backup handles approval if the lead is unavailable; that authority does not automatically pass to the VA.
• Frequency and trigger: prepare the pack weekly after the lead confirms the meeting date. Check open actions at the start and end of each agreed working day. Set the draft and approval cutoffs relative to the meeting in the team's agreed timezone.
• Inputs: the current agenda template, previous approved meeting notes, action-owner updates, the shared action tracker and the lead's priority list.
• Steps: gather current inputs, reconcile action updates, prepare the draft, run the checklist, request approval and release only the approved version.
• Outputs: a draft agenda, an updated open-action list, a decision-needed list and a link to the approved final pack.
• Approval limits: the VA may correct formatting and copy confirmed updates. The lead must approve changed action owners, changed due dates, new commitments and distribution of the final pack.
• Quality checkpoints: check each action against its source update; confirm owner, due date and status; test document links; verify the approved recipient list and final version before release.
• Escalation and evidence: put missing or conflicting information in a decision-needed list with its source and needed-by time. Record the approver, approved version, release status and unresolved items in the shared tracker.

Turn the assignment into instructions someone can follow

Name the actual folder, document and tracker fields in your own SOP. 'Update the spreadsheet' is not enough if the team has several copies. Link the approved source inside your private working instructions and use fictional or redacted screenshots for training where practical. Do not put passwords or sensitive records in a public template.

For this illustrative workflow, the operating steps would read as follows. Each step has an action and an observable result, rather than a general instruction to be careful.

• Gather: open the current template, previous approved notes and owner updates. Confirm that the meeting date and timezone match the lead's instruction. If an expected input is missing, record the gap instead of substituting an old version.
• Reconcile: compare every open action with its latest confirmed update. Copy the reported status and source link into the tracker. Do not mark an action complete merely because its due date has passed.
• Draft: place the lead's confirmed topics in the agenda. Add open actions and a separate decision-needed list. Keep unconfirmed owner or deadline changes visibly pending.
• Check: compare the draft with the tracker, remove duplicate entries, test links and confirm that each open action has an owner and due date or a clearly recorded blocker.
• Request approval: send the draft link, version and specific unresolved decisions to the lead through the agreed channel. Ask for a decision by the agreed approval cutoff. If approval is late, contact the named backup and report the release risk; silence is not approval.
• Release and hand off: distribute only the approved version to approved recipients. Record its location and approval, then carry unresolved items into the next-action list. At the end of the working day, report completed work, pending approvals and the next action for each blocker.

Add an Eisenhower priority rule without expanding authority

The Eisenhower matrix separates tasks by urgency and importance. Columbia University's student-support guide describes four responses: do urgent and important work, schedule important work that is not urgent, delegate or avoid urgent work that is not important, and remove work that is neither. Here, importance means its effect on the team's agreed outcome, not whether a message sounds demanding.

Use the following fictional priorities alongside the planning-pack SOP. The client lead defines importance, deadlines and trade-offs. The VA applies those agreed rules and escalates uncertainty. A task can move categories when its deadline or impact changes.

• Important and urgent: an action owner disputes a deadline that must be discussed at the upcoming planning meeting. The VA flags the conflict immediately and prepares the source notes; the lead decides the deadline. Urgency does not authorize the VA to change a commitment.
• Important, not urgent: recurring missing action updates make the weekly pack hard to prepare. Schedule a review of the update template and responsibility rules with the lead. The VA proposes a clearer collection process; the lead approves the change.
• Urgent, lower importance: the lead asks for the approved agenda in the standard print layout before the meeting. Delegate this bounded formatting task to the VA using the approved template, but do not let it displace the unresolved deadline decision or required accuracy checks.
• Neither urgent nor important: someone suggests decorative icons for old meeting folders with no effect on finding current work. Leave that request out of the active queue unless the lead identifies a useful purpose. Do not invent extra work to fill a task list.

Separate doing the task from approving a decision

VSI's public administrative and executive role templates describe planning responsibilities, approved systems, client sign-off and escalation. They are proposed templates to adapt at kickoff, not automatic permission for every listed activity. Your SOP should be equally explicit about what the VA can do, what needs approval and what remains outside the role.

For the planning-pack example, document editing and tracker updates may be delegated while changes to commitments and final release stay with the lead. Give the assistant individual accounts with the permissions needed for that work, rather than broad system administration access. Use approved access methods and never share credentials in chat.

An SOP is not a substitute for suitable training, access safeguards or professional supervision. Clinical, legal, licensed and financial decisions require the appropriate authorized owner. If a proposed assignment involves those decisions or sensitive records, confirm its scope and controls separately rather than extending this generic example.

• May do: compile approved information, correct formatting and log confirmed updates within the agreed role.
• Approval required: change an owner or due date, accept a new commitment or distribute the final pack.
• Stop and escalate: conflicting instructions, missing access, an unexpected sensitive document or a request outside the agreed scope.
• Record the decision: keep the approver, permitted action and approved version with the task; an unclear chat reaction is not a release rule.

Define done and make quality checks visible

A draft, a checked draft and an approved release are different states. In this example, the pack is done when the required sections are present, action entries match confirmed sources, links work, required approval is recorded and the approved copy has reached the approved recipients. An item with an unanswered decision remains pending, not complete.

Use checkpoints before a mistake becomes an external action. Check source completeness before drafting, accuracy before requesting approval, and the version and recipients before release. If a check fails, name the correction owner and move the item back to the appropriate stage.

During review, inspect evidence rather than asking only whether the work felt busy. Look at missing inputs, corrections, late approvals and repeated blockers. These are proposed review categories, not claims about VSI performance or guaranteed improvements. Agree any response targets with the client instead of treating an example as a service promise.

• Task status: not started, in progress, waiting for input, waiting for approval or complete.
• Accuracy evidence: source links and the completed task checklist.
• Approval evidence: approver, version and release permission.
• Blocker evidence: what is missing, who can resolve it, the needed-by time and the next action.

Test the draft before live work and revise what is unclear

EPA's SOP guidance recommends testing draft instructions with someone other than the writer and keeping procedures current when the process changes. For a business handoff, ask a colleague or prospective task user to run through the instructions with fictional material. The person who knows the process should resolve the gaps and approve the usable version.

Include an ordinary case and an exception. In this example, provide a fictional action update that matches the tracker, then another that conflicts with a recorded deadline. Check whether the user can identify the correct source, prepare the pack and stop at the approval boundary without verbal rescue.

Keep the current approved SOP in one agreed location with an owner and version. During initial onboarding, discuss recurring questions in the agreed review rhythm. Revise the relevant step when the tool, approval owner or workflow changes, and confirm the change before it is used. Archive superseded instructions so they are not mistaken for the current process.

• Could the user locate all required inputs without asking where they were?
• Did the output match the written definition of done?
• Was missing or conflicting information escalated rather than guessed?
• Did the test expose a process problem, a training need or an unclear instruction?

Use public role SOPs and bring a focused brief to discovery

VSI's administrative and executive support pages provide public role SOPs you can read before hiring. Use the administrative template for records, reports and routine coordination; use the executive template when the work centers on leadership priorities, agendas and follow-up. Their named tools are examples, not included subscriptions or proof of an enabled integration.

For the next step, use the standalone Build Your Support discovery page linked below. Prepare a concise brief with your recurring outcome, task frequency, approved systems, decision owner, language needs and known approval limits. Keep customer records, passwords and personalized working documents out of public examples; discuss the appropriate sharing method for sensitive material with VSI.

A narrow first SOP does not mean a part-time VSI plan. Every new human VA provides 40 hours per week. VSI's current USD rates are $12 per hour* for the first English-only Team Lead VA and $9 per hour* for each additional English-only VA. Spanish-bilingual support is $17 per hour for the first Team Lead VA and $14 per hour for each additional VA. AI and marketing work are quote-only; these human VA rates do not price those services.

VSI requires an upfront four-week retainer as prepaid service credit, not an extra service fee. We have two weeks to find the right VA for your business. Your retainer remains unused service credit while matching is underway. If we cannot find the right person within the two-week matching period, we refund your retainer. Your retainer is used only once you have the right VA, paying for their agreed service at the agreed hourly rates. After the retainer is used, billing becomes weekly once the retainer is used. Four weeks means agreed service, not a calendar month. Confirm the full scope and retainer amount in your agreement and review the current pricing page before committing.

Common questions

Do I need every SOP finished before hiring a virtual assistant?

No. Start with a useful draft for one recurring workflow and a clear list of other work you want to discuss. Resolve missing inputs, approval owners and access limits before handing over live execution. Broader documentation can develop as the agreed role becomes clearer.

How long should a virtual assistant SOP be?

Long enough to reproduce the task without guessing, but short enough to use while working. A simple task may need only an assignment card and checklist. A more complex workflow needs steps, examples, exception handling and approval rules. Length is less useful than a successful test.

Can I use a video instead of a written SOP?

A walkthrough can demonstrate a tool, but pair it with written inputs, outputs, steps, approval limits and exception rules. The written version should identify the current process and be easy to update when a screen or rule changes. Use fictional or appropriately redacted material for demonstrations.

Does an urgent task let the VA bypass approval?

No. Priority controls when a task receives attention; permission controls which actions may be taken. Put an urgent escalation route and a named backup approver in the SOP. If approval is unavailable, record the blocker and follow the agreed fallback rather than assuming consent.

Are VSI's public SOP templates ready-made company policies?

No. They are proposed planning templates. The client and VSI must confirm the selected duties, training, systems, access, targets and escalation contacts at kickoff. The illustrative workflow in this guide is also a planning example, not customer evidence or a personalized support plan.

Can I hire a VSI VA for only the hours needed by this example?

VSI does not offer a part-time human VA plan; each new human VA provides 40 hours per week. The example shows how to document one workflow, not the full weekly workload. Use discovery to discuss the wider recurring responsibilities and whether that capacity fits your needs.