Hiring a virtual assistant creates a working relationship that should be documented before work begins. A contract is not a sign of distrust. It is the clearest way to align expectations and prevent the kinds of disputes that derail good working relationships.
Many operators learn this lesson the hard way. They bring on a VA without a written agreement, assume both sides understand the arrangement the same way, and eventually run into a disagreement about scope, payment timing, or who owns the work produced. A contract prevents those conversations from becoming conflicts.
This guide walks through the core components a virtual assistant contract should include, common mistakes to avoid, and how to choose the right level of formality for your engagement. Before you finalize any agreement, review the full VA hiring checklist to make sure the contract aligns with the role scope you have already defined.
Why a VA contract matters more than you think
Many small operators skip a formal contract because the VA relationship feels informal. The VA works remotely, often on a flexible schedule, and the engagement starts small. But even a part-time, project-scoped relationship benefits from clear written terms.
A contract does three things. It defines scope so both sides agree on what is and is not included in the engagement. It sets expectations around payment, timelines, and deliverables so there is a clear standard to evaluate performance against. And it addresses what happens when the relationship ends, so that transition is as smooth as the start.
Without these elements in writing, every ambiguous situation becomes a negotiation rather than a reference check.
Core components of a virtual assistant contract
Scope of work
The scope of work section should describe what the VA will do in enough detail that a third party reading it could understand the role. Generic language like "provide administrative support" does not help either side in a dispute. Specific language like "manage email inbox and respond to routine client inquiries, prepare weekly meeting agendas, and coordinate calendar scheduling for the operations team" is clear.
Include what is explicitly out of scope. If you need the VA to stay focused on operations and not take on marketing tasks, note that boundary. If certain confidential systems are off-limits, name them.
Payment terms
Specify the rate, the billing cycle, the payment method, and the due date for invoices. A clear structure prevents confusion:
- Rate: hourly, per deliverable, or monthly retainer
- Billing cycle: monthly in arrears or bi-weekly
- Invoice due date: within 14 days of receipt
- Payment method: bank transfer or your agreed platform
Include what happens if a payment is late. A simple clause, for example that work pauses if an invoice remains unpaid beyond 30 days, protects the VA's time and motivates prompt payment on your end.
Confidentiality and data protection
A VA often works inside your systems: email, CRM, project management tools, financial software. A confidentiality clause establishes that the VA agrees not to share, copy, or disclose any information accessed in the course of the engagement.
Include a data handling clause if the VA will access personally identifiable information about your clients or employees. Specify how data should be stored, which platforms are approved, and what the VA should do if they suspect a data breach.
Intellectual property ownership
Any work a VA produces in the course of the engagement should be assigned to the client by default. This includes documents, templates, spreadsheets, SOPs, and any other deliverables. A simple IP assignment clause covers this: all work product created by the VA under the agreement is the property of the client upon payment.
If the VA uses their own pre-existing templates or tools as a starting point, the contract should note that those assets remain theirs and the client receives a license to use the adapted output.
Termination terms
Include a notice period for ending the engagement, typically two to four weeks. Also specify conditions under which either party can terminate immediately (cause, non-payment, or material breach) and what happens to outstanding work and invoices at termination.
Clarity here prevents awkward situations where a VA stops working before a critical deliverable is complete, or where a client terminates without paying for hours already logged.
Contract model comparison
| Detailed service agreement | Simple one-page agreement | No written agreement | |
|---|---|---|---|
| Scope clarity | High: detailed SOW and exclusions | Medium: broad scope defined | None |
| IP protection | Full: explicit assignment clause | Partial: depends on language | None |
| Dispute resolution | Strong: written reference point | Moderate | None |
| Effort to set up | Moderate (template plus one hour) | Low (one to two hours) | Zero |
| Best for | Ongoing retainer, system access | Short-term or low-scope project | Not recommended |
| Recommended | Yes: for most ongoing VA relationships | Yes: minimum for any engagement | No |
Common contract mistakes to avoid
The most common mistake is setting the scope too broadly. "General admin support" can mean anything. When the VA and the client have different mental models of what that phrase covers, both sides feel the other is not holding up their end.
A second mistake is skipping the IP clause because the work feels low-stakes. Even if you are only using a VA to manage your calendar, the templates and systems they build in your tools are yours. Get that in writing.
A third mistake is using a generic freelance contract not adapted for a VA relationship. Generic contracts often miss the nuances of ongoing access to proprietary systems, real-time communication expectations, and the distributed nature of VA work. A VA-specific template addresses these from the start.
SCORE, the nonprofit small business mentoring network, offers free contract templates and legal guidance for small business owners hiring contractors. Their resources are a useful starting point before adapting a template to a VA-specific engagement.
How to use a template effectively
A good template gives you 80 percent of a solid contract in about an hour. The remaining 20 percent is adapting the scope, rate, and any role-specific clauses (such as social media access, client-facing communication authority, or financial system permissions).
Before you send the contract for signature, review the scope section out loud as if you were explaining the role to someone new. If anything is unclear or ambiguous, rewrite it. A contract that requires interpretation at signing will require interpretation again when a disagreement arises.
Once signed, both parties should keep a copy. File it in your document management system under the VA's name so it is easy to reference if questions come up later in the engagement.
For a complete guide to the hiring process that precedes the contract, see how to hire an operations virtual assistant.