Virtual Assistant Contract Template

In plain language: Identifies the client and the VA as legal persons or entities, confirms the VA is engaged as an independent contractor (not an employee), and states the effective date.

Common mistake: Using a trade name instead of the VA's legal name or registered business name. If the VA operates through an LLC, the contract must name the LLC — otherwise enforcing payment or IP clauses against the right legal entity becomes difficult.

In plain language: Specifies exactly which tasks the VA is responsible for, the expected output or deliverables, working hours or availability windows, and any tasks that are explicitly out of scope.

Common mistake: Describing scope as 'general administrative support' with no further detail. Vague scope leads to disputes about what the VA is obligated to do, makes performance evaluation impossible, and gives neither party a clear basis for termination.

In plain language: States the rate (hourly, per-project, or monthly retainer), the invoicing schedule, the payment due date, and any late-payment fee that applies to overdue invoices.

Common mistake: Agreeing on a rate verbally and not including a late-payment fee clause. Without a written fee, collecting overdue payments typically requires a demand letter and small-claims filing — both avoidable with two sentences in the contract.

In plain language: Confirms the VA controls how, when, and with what tools they perform the services, and that the client does not direct the method of work — the key distinction between contractor and employee status.

Common mistake: Including language that gives the client control over the VA's daily schedule, mandatory login times, or required equipment — behavior that courts and tax authorities use to reclassify the relationship as employment, triggering back payroll taxes and benefits liability.

In plain language: Prohibits the VA from disclosing or misusing the client's confidential information — including login credentials, customer data, financial records, and business strategies — during and after the engagement.

Common mistake: Omitting a definition of 'Confidential Information' and relying on a catch-all. Courts apply a reasonableness test — an undefined or overbroad confidentiality clause can be unenforceable, leaving the client's data legally unprotected.

In plain language: Assigns to the client full ownership of all work product, content, designs, code, and materials created by the VA in connection with the engagement.

Common mistake: No IP assignment clause at all, or a clause that only covers materials created on the client's premises or equipment. VAs work remotely on personal devices — without explicit assignment language, the VA may retain copyright in content, graphics, or code they create.

In plain language: Prevents the VA from directly soliciting the client's customers, vendors, or other contractors for competing work for a defined period after the engagement ends.

Common mistake: Including a broad non-compete alongside a non-solicitation clause. Non-compete clauses restricting a VA from doing any similar work are routinely struck down as unreasonable — a targeted non-solicitation is far more enforceable and achieves the core business protection needed.

In plain language: States the notice period for voluntary termination by either party, the conditions that allow immediate termination for cause, and what happens to outstanding payments and deliverables upon termination.

Common mistake: No termination clause at all, or one that omits what happens to work in progress. Without clear language, a dispute over a partially completed project can hold up final payment and the return of access credentials for weeks.

In plain language: Allocates responsibility between the parties if the VA's work causes harm or loss — typically limiting the client's liability for the VA's independent actions and requiring the VA to indemnify the client for damages caused by their own negligence or misconduct.

Common mistake: Omitting a liability cap entirely. Without one, a client could theoretically face unlimited claims from a VA for alleged breach — a liability cap proportional to fees paid is standard and routinely upheld.

In plain language: Specifies which jurisdiction's law governs the contract and how disputes will be handled — negotiation first, then mediation or arbitration, before any court proceeding.

Common mistake: Choosing governing law based solely on the client's preference without considering where the VA is located. Several jurisdictions — particularly in the EU and Canada — apply local labor and contractor protections regardless of the governing law clause, rendering a mismatched choice ineffective.

A virtual assistant contract is a legally binding agreement between a client and a self-employed VA that sets out the terms of their working relationship — scope of services, compensation, confidentiality, IP ownership, and termination conditions. It establishes the VA as an independent contractor rather than an employee and creates enforceable obligations on both sides before any work or system access begins.

In most cases, a VA is engaged as an independent contractor — they set their own schedule, use their own equipment, and typically work for multiple clients. However, misclassification risk arises when a client controls the method and hours of work, requires exclusivity, or provides the VA's tools. The IRS, CRA, and HMRC all apply multi-factor tests to determine true status, and misclassification can trigger significant back taxes and penalties for the client.

At minimum: parties and effective date, scope of services with specific tasks, compensation rate and invoicing terms, independent contractor classification, confidentiality obligations, IP assignment, non-solicitation restrictions, termination notice and for-cause conditions, indemnification, a liability cap, and governing law. Missing any of these creates gaps that are filled by jurisdiction-specific defaults — usually less favorable to the client.

For most straightforward VA engagements, a well-structured template is sufficient — especially if the VA handles low-risk administrative tasks. Consider engaging a lawyer when the VA will access sensitive customer data, financial systems, or proprietary IP; when the contract involves cross-border parties; or when the monthly contract value is significant enough that a dispute would be costly. A one-hour template review typically costs $150–$400 and is worthwhile for senior or ongoing engagements.

Yes — under copyright law in the US, UK, Canada, and the EU, the default rule is that the creator owns their work. Without an explicit IP assignment clause, a VA retains copyright in content, graphics, and code they produce. The client may have a license to use the work, but they do not own it. A properly drafted assignment clause transfers all intellectual property rights to the client at the moment of creation.

Fourteen days is the standard mutual notice period for VA contracts — long enough to allow an orderly transition and knowledge handoff, short enough that neither party is locked in longer than necessary. Higher-value or more operationally critical engagements sometimes use 30 days. Always pair the notice period with a for-cause termination clause that allows immediate exit for serious breaches like a confidentiality violation.

Without a specific clause, there is no automatic legal obligation for the VA to delete or return client data and credentials after termination. Best practice is to include a clause requiring the VA to return, delete, or destroy all confidential materials within 48 hours of termination and to confirm compliance in writing. Revoke system access on the same day notice is given, regardless of whether the notice period has run.

Broad non-compete clauses — restricting a VA from doing any similar work for any client in any geography — are routinely struck down as unreasonable for independent contractors. California bans them almost entirely; courts in the UK and Canada apply a strict reasonableness test. A targeted non-solicitation clause (preventing the VA from directly approaching the client's specific customers or contractors) is far more consistently enforceable and provides the core protection most clients need.

Yes — a well-drafted template is designed to be reused. You should customize the scope of services, rate, and availability terms for each VA while keeping the legal clauses (IP, confidentiality, termination, governing law) consistent. If you engage VAs in multiple jurisdictions, review the governing law and contractor classification clause for each location, as legal requirements vary significantly between US states, Canadian provinces, the UK, and EU member states.