Stop losing money on
Virtual Assistant projects.
Vague task lists lead to 'quick favors' that quietly kill your profit margins and turn your business into a 24/7 on-call nightmare. Without a defined Scope of Work, you aren't a business owner—you're an unpaid intern for your own clients.
Pro Tip
Always include an 'Integration Clause' stating that the SOW represents the entire agreement, which prevents clients from enforcing 'promises' they claim you made during a casual discovery call or via a DM.
Uncompensated Availability
Clients assuming 24/7 access to you because 'virtual' is misinterpreted as 'always online' without defined service hours.
Skillset Overreach
Being held liable for specialized tasks (like legal drafting or tax prep) that were never part of your administrative hiring agreement.
Tool and Software Liability
Assuming the cost or security risk of third-party platforms without explicitly stating the client provides the licenses and access.
Built from real freelance projects
This template is based on real-world scenarios across freelance projects where unclear scope, missing payment terms, and revision creep led to lost revenue. It is designed to protect your time, define expectations, and ensure you get paid.
What is a Virtual Assistant Scope of Work?
A Virtual Assistant Scope of Work is a formal document that defines the specific administrative, creative, or technical tasks a VA will perform. It establishes clear boundaries regarding deliverables, timelines, and payment, while explicitly listing 'Out of Scope' activities to prevent unpaid work and ensure professional alignment between parties.
Quick Summary
This Virtual Assistant Scope of Work guide provides a comprehensive framework for defining professional boundaries and project deliverables. It covers essential sections including project overview, granular task lists, and explicit exclusions to prevent scope creep. By utilizing this template, VAs can mitigate risks related to uncompensated labor and mismanaged expectations. The guide also offers strategic advice on pricing and legal enforcement, making it an indispensable tool for VAs looking to scale their business professionally and profitably.
Why Virtual Assistants need a clear scope of work
For a Virtual Assistant, the Scope of Work (SOW) is the ultimate boundary-setting tool. Unlike traditional employees, VAs operate as independent contractors where every minute has a literal price tag. Without this document, the phenomenon of 'task creep' is inevitable; a client who hired you for inbox management will slowly start asking for graphic design, web updates, and cold calling. A professional SOW transforms you from a 'helper' into a strategic partner. it defines exactly what the client is paying for, how success is measured, and most importantly, where your responsibilities end. This clarity prevents burnout, ensures you are compensated for extra work through change orders, and provides a legal shield if a client claims a project wasn't completed to their vague, unwritten expectations. It is the difference between a scalable agency and a stressful freelance hobby.
Do you need an invoice or a contract?
Invoices help you get paid, but they do not define scope, revisions, or ownership. For most projects, professionals use both a contract and an invoice to protect their work and cash flow. MicroFreelanceHub bundles both into a single link.
Real-world scenario
Sarah, a VA, was hired for 'General Admin.' Within three months, her client asked her to launch a full Shopify store—a task she hadn't agreed to. Because Sarah had a detailed Scope of Work template in place, she didn't have to have an awkward emotional confrontation. She simply sent a polite email stating: 'I’d love to help with the Shopify launch! As per our current SOW, my focus is on inbox and calendar management. This new project falls under my "Out of Scope" section. I’ve attached a Change Order with the adjusted project fee for the store build.' The client, realizing the scale of the request, immediately signed the Change Order and paid an additional $2,000. Without that SOW, Sarah would have likely spent 40 hours of unpaid labor trying to 'be helpful' while her actual business suffered.
🛡️ What this scope of work covers:
- ✓Weekly Email Management & Filtering Report
- ✓Social Media Content Calendar (12 Posts/Month)
- ✓Documented Standard Operating Procedures (SOPs) for assigned tasks
- ✓Monthly Expense Reconciliation and Receipt Categorization
- ✓Travel Itineraries and Booking Confirmations
- ✓Customer Support Ticket Resolution (Max 20/Day)
Pricing & Payment Strategy
Virtual Assistant SOWs are typically priced in three ways: Hourly (billed monthly in arrears), Retainer (pre-paid blocks of hours), or Package-based (fixed price for specific deliverables like 'The Social Media Package'). For high-level executive VAs, a value-based retainer starting at $1,500/month is standard, whereas general admin often ranges from $30-$60 per hour depending on the complexity of the specialized software involved.
Best practices for Virtual Assistants
Quantify Everything
Avoid words like 'handle' or 'manage.' Use 'Process 10 invoices weekly' or 'Monitor inbox for 2 hours daily.'
Define 'Business Days'
Explicitly state that weekends and holidays are excluded from your turnaround times to protect your personal time.
1. Project Overview
This Scope of Work (SOW) defines the partnership between [VA Name/Agency] ('Service Provider') and [Client Name] ('Client'). The objective is to provide professional administrative and operational support to streamline Client’s business workflows beginning on [Start Date].
2. Scope of Work
The Service Provider will perform the following recurring duties:
- Inbox Management: Sorting, archiving, and responding to general inquiries using established templates.
- Calendar Coordination: Scheduling appointments and managing time-zone conversions for the Client.
- Data Management: Updating the CRM with new lead information on a weekly basis.
3. Deliverables
The following specific assets will be delivered according to the schedule below:
- Weekly Activity Report: Delivered every Friday by 5:00 PM EST.
- Social Media Queue: 5 posts scheduled in [Software Name] by the 25th of each month for the following month.
- SOP Manual: A digital folder containing step-by-step guides for all performed tasks, updated quarterly.
4. Timeline & Milestones
Work will be performed during standard business hours (Monday-Friday, 9:00 AM - 5:00 PM [Timezone]). Key milestones include:
- Onboarding Phase: Completion of access sharing and tool setup (Week 1).
- Review Meeting: Monthly 30-minute sync call to review performance and upcoming needs.
5. Revisions Policy
For creative deliverables (e.g., newsletters or graphics), the Client is entitled to two (2) rounds of revisions per asset. Revision requests must be submitted within 48 hours of receipt. Subsequent revisions will be billed at the standard hourly rate of $[Rate].
6. Out of Scope
The following items are explicitly excluded from this agreement and require a separate Change Order:
- Website development, coding, or advanced technical troubleshooting.
- Management of personal/private finances or family scheduling.
- Cold calling or outbound sales outreach.
- Work requested outside of defined business hours or on public holidays.
7. Approval Process
Deliverables will be deemed accepted unless the Client provides written feedback within three (3) business days of delivery. Final approval of all external-facing content is the responsibility of the Client. Work will be submitted for approval via [Project Management Tool/Email].
Legal Disclaimer: MicroFreelanceHub is a software workflow tool, not a law firm. The templates and information provided on this website are for general informational purposes only and do not constitute legal advice.
Frequently Asked Questions
What happens if the client asks for something not in the SOW?
You should issue a Change Order or a new SOW. Do not start the work until the new terms and fees are agreed upon in writing.
Should I include my communication tools in the SOW?
Yes. Specify that all work requests must come through Slack or Email, for example, to prevent 'instruction scatter' across multiple platforms.