Writing Down How Your Business Runs

Understanding Brain-Dumping and SOPs

Standard Operating Procedures, or SOPs, are the operating instructions for your virtual assistant or outsourcing agency. They explain how work should be completed so clients receive the same reliable service whether the task is handled by you, a team leader, or a new VA. A strong SOP helps a new team member become about 80% effective on a task during their first week instead of needing constant supervision.

For example, your agency may manage inboxes for several real estate clients. Without an SOP, each VA may label emails differently, miss urgent messages, or use a different reply style. With a clear process, every VA knows what to check, what to escalate, and how to record completed work.

The Importance of Brain-Dumping

Brain-dumping means moving the knowledge in your head into a format another person can use. Agency owners often carry hidden knowledge about client preferences, password procedures, quality standards, escalation rules, and special exceptions. If this knowledge stays in your head, your agency depends on you for every decision.

Start with the tasks you repeat most often or explain most frequently. Record how you onboard a client, assign work in ClickUp, check a VA's work, prepare a weekly report, or handle a missed deadline. Do not wait for the process to become perfect. Capture the real process first, then improve it after the team uses it.

Real-World Example: You personally review every client's social media post before publishing because you know each client's tone and approval rules. Record yourself reviewing a post, explain what you look for, and show where approval is logged. That recording can become a training resource for a team lead.

Creating Effective SOPs

Use three parts for every agency SOP:

1. Why: Explain why the task matters to the client and the agency. For example, accurate CRM updates help a client's sales team follow up with leads quickly.
2. What: List the exact steps, tools, decision points, and handoff rules. Include links to templates, sample files, and client-specific instructions.
3. Outcome: Define what finished work looks like. State the quality standard, deadline, proof of completion, and who checks the work.

Real-World Example: An SOP for processing a client's customer support tickets should explain why response time affects client retention, how to sort tickets by urgency in Zendesk, when to use saved replies, when to escalate, and how to mark the ticket complete. The outcome might be: every ticket is tagged correctly, answered within the agreed service window, and logged for the weekly report.

Organizing Your SOPs

Store SOPs in one searchable location, such as Notion, Google Drive, or a client-safe knowledge base. Use folders or databases for sales, client onboarding, service delivery, quality checks, finance, and team management. Give each SOP a clear name, owner, version date, and review date.

Keep client-specific instructions separate from your core agency process. A general "Inbox Management SOP" can link to each client's tone guide, escalation list, and working hours. Never place client passwords in an SOP. Store access details in a password manager such as 1Password or Bitwarden.

The Loom-First Approach

For tasks that are easier to watch than read, record a Loom video while completing the work. Show the actual tools, screens, naming rules, and decisions. Keep each recording focused on one task, such as creating a Trello card, sending a client update, or checking a blog upload.

After recording, add a short written checklist. Loom helps a VA see the process, while the checklist gives them a quick reference during delivery. Review recordings when a tool changes, a client changes requirements, or the same question appears twice.

Building a Culture of Self-Reliance

Teach team members to search the SOP library before asking a process question. This does not mean ignoring them; it means making questions more useful. Ask them to share the SOP they checked and explain which step was unclear. When a question reveals a missing rule, update the SOP instead of answering the same question privately every time.

A team lead should also run short spot checks to confirm that SOPs match real work. When processes are documented, searchable, and used consistently, you can add clients and VAs without becoming the agency's help desk for every small decision.