Before You Hire a VA - Document Your Processes First

The #1 predictor of VA hiring success is not how much you pay, which company you use, or how experienced the VA is. It is whether you documented your processes before handing them off.

Most founders skip this step. They hire a VA, give vague instructions like "manage my inbox" or "handle social media," and then wonder why the results are disappointing. The VA is not the problem. The handoff is.

This guide gives you the practical framework for documenting your processes so that your VA can hit the ground running and deliver results from week one.

Why Process Documentation Is the #1 Hiring Success Factor

There is a pattern across Hacker News, Indie Hackers, and every founder community that discusses VA hiring. The success stories share one thing: the founder documented their processes before delegating. The failure stories share one thing: they did not.

Here is why documentation makes the difference:

Removes ambiguity: "Sort my inbox" can mean 50 different things. "Label emails using these 5 categories, draft responses using these templates, and flag anything from clients A, B, and C for my personal response" means exactly one thing
Reduces training time: A VA with good documentation can be productive in days instead of weeks
Creates accountability: When the process is written down, both you and your VA know what "done correctly" looks like
Enables replacement: If your VA leaves, the next person can pick up immediately instead of starting from scratch
Improves the process itself: Writing down what you do forces you to notice inefficiencies you have been ignoring

Documentation is not extra work before hiring. It is the work that makes hiring work.

The Rote Test - How to Know When You Are Ready to Delegate

Not every task is ready for delegation. Here is the simple test from experienced founders:

Keep doing the task manually until it becomes rote enough that you can write down an exact process.

If you cannot describe the task in specific, repeatable steps, you are not ready to hand it off. You will end up explaining it poorly, your VA will do it wrong, and you will both be frustrated.

Signs a Task Is Ready to Delegate

You do it the same way every time with minimal variation
You could explain it to a stranger in under 10 minutes
The decisions involved are rule-based, not judgment-based (at least for the first version)
A mistake would be annoying but not catastrophic

Signs a Task Is NOT Ready Yet

You make different decisions each time based on gut feeling
You cannot articulate why you do it a certain way
The task changes significantly every time
The consequences of doing it wrong are severe

If a task is not ready, keep doing it manually while paying attention to the patterns. After 2 - 4 more cycles, you will usually notice the repeatable structure that makes it delegatable.

Creating Standard Operating Procedures for Your VA

An SOP does not need to be a corporate document. It needs to be clear enough that someone who has never done the task can complete it correctly. Here is the format:

SOP Template

Task Name: [Clear, specific name]

Purpose: [Why this task matters - one sentence]

Frequency: [Daily / Weekly / As needed]

Estimated Time: [How long it should take]

Tools Needed: [Software, logins, access required]

Steps:

[First action - be specific about what to click, where to go, what to look for]
[Second action]
[Continue until the task is complete]

Decision Points:

If [situation A], then [action A]
If [situation B], then [action B]
If [anything unexpected], then [escalate to me with a description of what happened]

Done Looks Like: [The specific output or state when the task is complete]

Common Mistakes: [Things that have gone wrong before or could go wrong]

Example SOP - Daily Email Triage

Task Name: Morning Email Triage

Purpose: Ensure my inbox is organized and actionable by 9 AM so I start the day focused on client work.

Frequency: Daily, Monday - Friday

Estimated Time: 30 - 45 minutes

Tools Needed: Gmail (login provided), Asana (for task creation)

Steps:

Open Gmail. Sort by unread emails received since last triage
Newsletters and notifications: Archive immediately. Do not delete
Client emails: Read and categorize:
- Routine questions: Draft a response using the templates in the "Email Templates" Google Drive folder. Leave as draft for my review
- Urgent requests: Forward to my personal phone via text with a one-line summary
- Invoices or documents: File in the appropriate client folder on Drive
Sales inquiries: Add to the "Leads" pipeline in our CRM with source, name, and request summary
Internal team messages: Respond directly if the answer is in our documentation. Otherwise, flag for my attention
Spam or irrelevant: Archive and unsubscribe where appropriate

Decision Points:

If an email mentions a deadline within 24 hours, flag as urgent regardless of sender
If you are unsure whether to respond or escalate, escalate. Better to ask than to send a wrong response
If a client sounds upset, do not draft a response. Forward to me immediately

Done Looks Like: Inbox has fewer than 10 emails, all requiring my personal decision. All drafted responses are ready for review. CRM is updated with new leads. No unread emails older than 24 hours.

Common Mistakes: Accidentally archiving client emails thinking they are newsletters. Always check the sender domain before archiving.

Tools for Documenting Processes

You do not need fancy software. Here are the practical options:

Notion

Best for teams that want a centralized knowledge base. Create a "VA Playbook" database with each SOP as a page. Add tags for category (email, social media, billing), frequency, and priority. Your VA can search, comment, and suggest updates.

Google Docs

Best for simplicity. Create one doc per process. Organize in a shared Google Drive folder. Use headings, numbered lists, and screenshots. Your VA can add comments with questions or suggestions.

Loom

Best for complex or visual processes. Record your screen while doing the task and narrate your thought process. A 5-minute Loom video often communicates more effectively than a 2-page document.

Tango

Best for step-by-step screenshots. Tango automatically captures screenshots as you work and creates a formatted guide. Ideal for tool-heavy processes like CRM data entry or scheduling workflows.

Trainual or SweetProcess

Best for businesses building extensive process libraries. These are dedicated SOP platforms with templates, progress tracking, and testing features. Worth the investment if you plan to hire multiple VAs or build a team.

Video Documentation - Show, Do Not Tell

For many tasks, a screen recording is worth more than any written document. Here is how to do it effectively:

Recording Tips

Narrate your thinking: Do not just show what you click. Explain why you make each decision. "I am checking this field because sometimes the data imports incorrectly and needs manual correction"
Go at teaching speed: Slow down from your normal pace. What feels slow to you feels right for someone learning
Show edge cases: If there is a common exception or unusual situation, include it. "Sometimes you will see this error. Here is what to do"
Keep it under 10 minutes: If a process takes longer to demonstrate, break it into multiple videos

When to Use Video vs. Written Documentation

Use Video When	Use Written When
The process involves multiple screens or tools	The process is purely text-based
Decision points depend on visual cues	Steps are linear and predictable
The tool interface is complex	The task is simple data entry
You want to show pace and flow	You need a quick reference checklist

The best approach is both: a video for initial training and a written checklist for daily reference. Your VA watches the video once, then uses the checklist going forward.

Testing Your Documentation - The Paid Trial Work Sample

Before your VA starts full-time, test your documentation with a paid trial. Here is the process:

Pick 2 - 3 documented tasks from your SOP library
Give your VA access to the documentation and tools
Do not explain the tasks verbally - let the documentation do the work
Set a 2 - 4 hour trial where they complete the tasks using only your documentation
Review the results and note where they struggled

If your VA completes the tasks correctly using only the documentation, your SOPs work. If they get stuck, the problem is the documentation, not the VA. Fix the gaps and test again.

This trial serves two purposes: it validates your documentation and evaluates whether the VA is a good fit. If they can follow clear instructions and produce quality output, they are ready.

Common Documentation Mistakes

Too Vague

Bad: "Update the spreadsheet with new data." Good: "Open the Q1 Sales Tracker in Google Sheets. Add new entries from the CRM export (File > Import > select the latest CSV). Match columns: Name to Column A, Email to Column B, Deal Value to Column C."

Missing Context

Bad: "Send follow-up emails to leads." Good: "Send follow-up emails to leads who submitted a contact form more than 48 hours ago but have not received a response. Use the 'First Follow-Up' template. If they already received a follow-up, use the 'Second Follow-Up' template."

No Decision Framework

Bad: "Handle customer complaints." Good: "For billing complaints under $50, issue a credit immediately and send the 'Billing Resolution' template. For complaints over $50, escalate to me with a summary of the issue and the customer's account details. For service complaints, log the issue in the 'Service Feedback' Notion database and respond with the 'We're Looking Into It' template."

Assuming Knowledge

Bad: "Run the weekly report." Good: "Open Google Analytics. Navigate to Acquisition > Overview. Set the date range to the last 7 days. Screenshot the traffic summary and paste it into the #weekly-metrics Slack channel with the caption 'Traffic Report: [date range].'"

Updating and Improving Processes as Your VA Works

Documentation is not a one-time activity. Processes change, tools update, and your VA will discover better ways to do things.

Build a Feedback Loop

Ask your VA to note any step that was unclear or missing when they first used an SOP
Schedule monthly SOP reviews to incorporate improvements
Give your VA permission to update documentation directly (with change notes)
Track which SOPs get the most questions - those need the most improvement

Version Control

Date every SOP update
Keep a simple changelog at the top of each document
Archive outdated versions instead of deleting them

Let Your VA Own Documentation

The best outcome is when your VA takes ownership of the SOP library. They maintain it, update it as processes change, and create new documentation for tasks they develop. This creates institutional knowledge that survives personnel changes.

The Compounding Returns of Good Documentation

Process documentation delivers returns far beyond VA delegation:

Faster onboarding for future hires: Whether it is a second VA, an employee, or a contractor, documented processes mean faster ramp-up every time
Business value: A business with documented, repeatable processes is worth more than one that runs on the owner's tribal knowledge
Personal freedom: When your processes are documented, you can step away without the business stopping. Vacations become possible. Sick days do not create emergencies
Continuous improvement: Written processes can be analyzed, optimized, and automated. You cannot improve what you have not defined
Reduced stress: Knowing that your operations are documented and delegated creates peace of mind that no amount of personal hustle can match

The founders who invest 10 - 20 hours in documentation before hiring a VA consistently report that it was the best business investment they made that year. The VA hire works better. The processes improve. And the foundation scales.

Ready to hire a VA? Document your processes first, then find your match.

Before You Hire a VA - Document Your Processes First (The Non-Negotiable Step)