Virtual Assistant Contract: Template and Key Clauses (2026)

A virtual assistant contract sets the terms between a client and a virtual assistant, or VA, who provides administrative, scheduling, inbox, research or support work remotely. Because a VA often handles passwords, calendars, customer details and money tasks, the contract has to be clear about scope, confidentiality and access. This guide gives you a usable clause-by-clause skeleton, explains what each part does, and flags the common mistakes. This is general information, not legal advice. Contract and employment rules differ by country, for example the United States, the United Kingdom and India, so have an important agreement checked by a professional in your jurisdiction before you sign. ## When you need this contract Use a written contract for any ongoing VA arrangement, and even for a short trial if the assistant will touch sensitive accounts. It matters most when the VA works across time zones, handles client data, or is paid by the hour on a rolling basis. A clear contract prevents disputes about what was agreed, how many hours were worked, and what the assistant may and may not do with access to your systems. ## The clause-by-clause skeleton 1. Parties and effective date. Name the client and the virtual assistant in full, with addresses or registered details, and the date the arrangement starts. 2. Services and scope. List exactly what the VA will do: inbox management, calendar scheduling, travel booking, research, data entry, social media support, bookkeeping help, or customer replies. Be specific, because VA work drifts easily. Say what is not included, and that new task types need to be agreed. 3. Hours and availability. State whether the VA works a set number of hours per week or month, or purely on demand. Note the time zone, the usual working hours, expected response times, and how public holidays and leave are handled. 4. Fees and payment schedule. State the hourly rate or the monthly retainer, the currency, and what is included. Say how hours are tracked and reported, how often invoices are raised, the due date, the payment method, and a late payment charge. For retainers, say what happens to unused hours and to extra hours beyond the retainer. 5. Term and renewal. Say whether the contract runs month to month, for a fixed period, or until ended. Set out how it renews so no one is surprised by an automatic roll over. 6. Confidentiality. Central for a VA. Both sides keep each other's non public information private, and the VA agrees not to use or share client data except to do the work. Make this survive the end of the contract. 7. Access and account security. State how the VA is given access to systems, ideally through a password manager or delegated access rather than shared raw passwords, and that the VA must follow basic security practices. Require that all access is returned or revoked when the contract ends. 8. Data protection. Where the VA handles personal data of the client's customers, say that the VA will process it only on the client's instructions and keep it secure. Depending on the country, a fuller data processing clause may be needed, so check local data law. 9. Independent contractor status. State that the VA is an independent contractor, not an employee, and is responsible for their own taxes and benefits. Avoid terms that look like employment, such as fixed daily hours and heavy control, if independent status matters for tax and employment law in your country. 10. Ownership of work. Say that work the VA produces for the client, such as documents, spreadsheets and drafts, belongs to the client once paid for. The VA keeps their own tools and templates. 11. Tools and expenses. State who pays for any paid software, subscriptions or expenses the VA needs, and whether expenses must be approved in advance. 12. Non solicitation. Optionally, agree that neither side will poach the other's clients or staff for a reasonable period. Keep any such clause fair and limited, because overbroad restrictions are often unenforceable. 13. Standard of work and revisions. The VA agrees to work with reasonable care and to correct errors promptly. Set out how feedback and corrections are handled. 14. Limitation of liability. Cap the VA's total liability, often at the fees paid over a recent period, and exclude indirect losses as far as the law allows. Keep it balanced given that a VA is usually a small operator. 15. Cancellation and notice. State the notice each side must give to end the contract, and that the client pays for work done and approved up to that point. Address what happens to work in progress and to access on exit. 16. Governing law and disputes. Name the country or state whose law applies and how disputes are handled. This matters because client and VA are often in different countries. ## Common mistakes to avoid The biggest mistake is sharing raw passwords instead of using a password manager or delegated access, which creates a security risk and leaves no clean way to revoke access. The second is a vague scope that lets tasks pile on without more pay. Others include no clear hours tracking, forgetting a confidentiality clause when the VA sees sensitive data, treating the VA like an employee in a way that creates tax risk, and no exit clause covering return of access and data. Fix these and the relationship stays clean. ## From a signed contract to a running relationship A good contract is the start. The ongoing work is tracking the signed version, the hours and retainer, the renewal date and the confidentiality and access terms, especially when you work with several assistants or several clients. Adira is an AI legal operating system built on Claude that keeps the whole cycle, from drafting and reviewing a contract for risk, to signing it, to tracking renewal dates and obligations, in one workspace tuned to how you work, with public per-seat pricing and a short free trial. You can see how it works at adiralaw.com. A single pane showing the status of every contract is on its roadmap. For a single VA arrangement, a clear template and careful reading are enough; the workspace helps once you manage many at once.