What Should a Virtual Assistant Contract Include? The Disagreements to Prevent Before They Happen

Here's why a virtual assistant contract matters more than most people think. Your new assistant has finished the customer guide.

You assumed you'd get the editable file. They assumed you wanted a PDF.

You planned to reuse the template for other products. They built that template in their own business before they ever met you.

Nobody is being difficult. You just agreed a task without agreeing what gets handed over, who can reuse it, or what counts as finished.

A good virtual assistant contract is mostly about stopping these predictable disagreements before they turn personal. A downloaded template can be full of impressive legal language and still leave every one of these questions unanswered.

This guide helps you prepare the practical decisions first, so whoever drafts or reviews your agreement knows exactly what deal you actually want. It's a discussion aid, not a legal template and not legal advice.

A virtual assistant (VA) here means an independent freelancer or agency you buy services from.

Start with the argument you want to avoid

Open a blank document. Describe one normal piece of work from start to finish:

• Who provides the input?
• Who makes decisions along the way?
• Where does the output live?
• Who accepts it as finished?

Then write down the awkward variations:

• The input arrives late.
• They come across private customer information.
• You ask for changes after approving it.
• A payment is late.
• The relationship ends with work half-done.

Each of those is a decision your contract needs to answer.

"Reasonable assistance" won't tell you if a new sales campaign is included in your inbox management fee. "All intellectual property belongs to the client" won't tell you who owns a licensed stock photo inside a design.

You don't need to predict everything. Focus on the things likely to happen, or expensive if they do: money, authority, personal information, ownership and endings.

Name the right parties, and don't let a label decide the relationship

Write down the correct legal names and contact details.

If you're buying through an agency, find out whether your agreement is with the agency, the individual assistant, or another company that employs or contracts them.

Ask who can sign and who can approve changes. The person who arranged the interview might not be able to change the agency's terms. And your VA should know whether a request from one of your colleagues can change the agreed scope.

Here's an important warning. Choosing a "contractor agreement" template doesn't settle whether someone is legally a contractor. If the way you work together looks like employment, the label won't protect you.

Give your adviser the real facts: where people work, how much control you'll have over hours and methods, how long the arrangement will last, and whether you'll restrict other clients. Our guide on contractor vs employee status explains what to prepare.

Also gather any existing agreements: platform terms, agency agreements, confidentiality promises you've made to your own clients. Your new contract shouldn't promise something those already forbid.

"Help with customers" isn't a scope. Here's what is

A useful scope describes an outcome and its boundaries.

Weak: "Help with customers."

Strong: "Prepare weekly customer-support drafts using our approved policy library."

Then add:

• Which queue or system they work in.
• What they can do on their own: send messages, change records, approve refunds, or only prepare proposals?
• What's excluded.
• What "finished" looks like, so either of you can check it.

Separate quality standards from personal preferences. "Accurate against our source information" can be checked. "Make it more professional" needs an example.

And write down your own responsibilities. If your VA needs an up-to-date price list, someone has to supply it. If something needs your approval, someone has to respond. Say what happens to deadlines when you're the one holding things up.

Finally, add a change process. A request for extra work should spell out the new work, how it affects existing deadlines, and any change in fee. Name who can approve it, and where approvals are recorded. That stops a casual "yes, sure" in a chat from turning into a whole new job at the old price.

Make the money and the availability describe the same thing

Be clear about what the fee buys.

Paying for a block of time doesn't automatically mean unlimited output. Paying per deliverable doesn't automatically mean instant replies all day.

Write down:

• the fee basis (hourly, monthly retainer, per project),
• invoice frequency and payment deadline,
• currency and who pays transfer fees,
• for retainers: what happens to unused hours, extra work and partial months.

Don't rely on the word "retainer" to answer those questions. It means different things to different people.

Expenses need rules too. Agree how purchases are approved before money is spent, which subscriptions your business owns, and what happens to any equipment you provide.

And talk about payment problems before they happen. What evidence comes with an invoice dispute? Does undisputed work still get paid? Get any proposed late-payment interest, suspension or withholding terms checked locally. Making up your own penalties isn't the same as having a legal right to them.

Our guide on paying an overseas VA covers the practical side.

Owning the file isn't the same as owning the work

Here's something that surprises a lot of business owners.

Having a file in your folder doesn't mean you own the copyright in it.

The UK Intellectual Property Office's guidance on ownership explains that the creator of a commissioned work is generally its first copyright owner, unless you agree otherwise in writing. It also distinguishes between an implied licence to use something and actually transferring ownership.

In the US, the phrase "work made for hire" often gets thrown around. But the US Copyright Office's Circular 30 explains that for commissioned (non-employee) work, it only applies to specific categories, with written agreement requirements. It's not a magic phrase that transfers everything.

If people work in different countries, don't mix up rules from different places and assume payment transfers everything.

So, practically:

1. List the likely outputs: documents, spreadsheets, designs, recordings, procedures, editable source files.
2. Write down what you need to do with them: edit, publish, give to clients, sell, translate, or let a future assistant maintain them.
3. Ask your adviser to cover the rights you need, where, for how long, and from when.

Treat pre-existing materials separately. Your VA might reasonably keep their own general template while giving you the right to use it in your deliverable. That's fine, as long as it's written down clearly.

And if you're buying through an agency that promises ownership, ask how they get those rights from the people actually creating the work. A promise only means something if there's a valid chain behind it.

Stock photos, fonts and AI tools need their own paper trail

Your VA can't give you full ownership of something they only licensed from someone else.

So agree how third-party assets get approved and recorded. For each relevant deliverable, ask for a short asset note:

• where each image, font, music track or template came from,
• the licence and permitted use,
• which account bought it,
• any restrictions.

"It's royalty-free" isn't a complete answer.

Decide about AI tools too. Using AI to help draft public marketing copy is very different from uploading a customer list or contract into one. Permission for one doesn't mean permission for everything.

Don't demand a promise that all AI-assisted work has exclusive copyright protection everywhere. That's not something anyone can guarantee. Instead, ask for disclosure of meaningful AI use, and get advice where ownership really matters.

And settle portfolio use. Can your VA say they work with you? Show a redacted example? Paying for confidential work and permitting a public case study are two separate decisions.

Confidentiality needs a "permitted use" rule, not just a warning

A non-disclosure agreement (NDA) is about confidential information. A good one explains:

• what's confidential (unpublished prices, customer messages, login details, financial information, product plans),
• what they can use it for (for example, preparing replies to customers),
• what they can't do with it (reuse it in their own marketing, share with other clients, upload to unapproved tools).

Ask your adviser to include sensible exceptions, like information that's already public. Labelling everything in someone's life as confidential isn't realistic or helpful.

Agree what happens if something goes wrong: an email sent to the wrong person, a lost laptop. Give them an incident contact and ask them to report quickly with whatever facts they have, rather than waiting to write a polished explanation.

But know the limits. Confidentiality alone doesn't decide data protection roles, cover international data transfers, or secure your accounts. It's one piece. Our secure access guide covers the practical controls.

Map the personal data before adding a data schedule

Personal information sneaks into routine work through emails, bookings, order histories and staff records.

Write down:

• whose information is involved,
• what details the VA needs,
• where it's stored,
• what they'll do with it.

Then work out the legal roles. Don't assume every VA is automatically a "processor." Under UK GDPR, a controller decides why and how personal data is used, and a processor handles it on the controller's behalf. Which applies depends on what actually happens.

Where a controller-processor relationship exists, the ICO lists what the contract must include: details of the processing, documented instructions, confidentiality, security, use of sub-processors, help with people's rights, what happens at the end, and audits.

A single line saying "comply with GDPR" doesn't cover all that.

The ICO notes that some of its guidance is under review following recent legislative changes, so use the current version and proper advice when you finalise terms. If another country's rules might apply, get those checked too.

Overseas access and helpers are separate decisions

Keeping data on a UK server doesn't automatically settle international transfer questions.

The ICO's guidance on restricted transfers explains that letting a separate organisation overseas access personal information can count, even if the file never physically moves.

So map the real path: your business, the provider, the individual doing the work, and any other tools or organisations involved. Ask what transfer requirements apply before switching on access.

Subcontracting needs the same care. A VA might use:

• a colleague for holiday cover,
• a specialist for a design,
• a software tool that processes data.

Those are three different permissions. Don't lump them together, and don't let a substitute quietly use the original person's login.

Under UK GDPR processor arrangements, the ICO's guidance covers getting written authorisation for sub-processors and passing on equivalent data protection obligations.

And please don't add a fictional substitution right to a contract just to make it look independent. Agree what can genuinely happen, then design approvals and access around that.

Plan the ending while everyone's still happy

It feels odd to discuss endings at the start. It's much easier now than later.

Cover:

• How either side ends it, with how much notice.
• What gets handed over: current files, source materials, open tasks, pending approvals, account details.
• In what format, by when, and to whom.
• Whether handover help is paid, and at what rate. "Cooperate fully" can hide a lot of unpaid work.

Separate removing access from deleting records. Someone's access should be removed promptly, but your business may need to keep some records for tax or legal reasons. Don't promise immediate deletion of everything if you're legally required to keep some of it.

For UK GDPR processing contracts, the ICO describes returning or deleting data at the controller's choice, deleting copies subject to legal requirements, and practical arrangements for backups.

Get liability, insurance, governing law and dispute terms reviewed by someone qualified. An unlimited indemnity might be unrealistic. A liability cap might exclude the very loss you were worried about. And choosing a governing law doesn't make cross-border enforcement easy.

Test the deal against one real project

Here's a hypothetical example.

A consultancy hires a freelance VA to write a customer onboarding guide. The VA suggests using a layout they already own and writing new instructions from the consultancy's notes. Other staff will update the guide later.

Before drafting the agreement, the owner lists what's needed: the editable source file, the final PDF, approved illustrations and an asset note. The VA writes drafts. The owner confirms technical claims and approves publication.

The rights discussion separates:

• the VA's existing layout,
• the newly written text,
• any licensed illustrations.

The owner explains they need to edit and reuse the guide. An adviser turns that into proper ownership or licence terms, rather than just copying "all work made for hire."

The source notes contain real customer examples. So they agree to use invented examples in the working document, avoiding unnecessary exposure of real correspondence.

Later, the owner asks for a second guide for another product. The change process kicks in. The VA explains the extra time and cost. The owner approves it in writing.

Finally, the owner checks the folder: could someone else open the editable file, find the permissions and see what's still unfinished? If not, the contract discussion has exposed a gap before it causes a problem.

Take this sheet to whoever drafts the contract

Prepare one page with your decisions. For each issue, write the business decision, the supporting document, and who needs to confirm the legal wording.

VA CONTRACT DECISION SHEET

Legal parties (exact names):

Where each person works:

Intended relationship (and facts for status review):

Scope: outcomes, authority, exclusions:

Change process and who approves:

Fee basis, currency, invoicing and payment terms:

Unused hours, extra work, expenses:

Outputs and what I need to do with them:

Pre-existing materials and licences:

Third-party assets and AI tool rules:

Confidential information and permitted use:

Personal data: whose, what, where, roles:

Overseas access and subcontractors:

Ending: notice, handover, access removal, records kept:

Open questions for the adviser:

For example: "Need to adapt the onboarding guide for later products. Asset list attached. Adviser to confirm licence and ownership structure."

Then ask your VA to read the operating parts in plain English. They should be able to explain what they'll deliver, what needs extra approval and what information they can use. Sort out any differences before signing.

The real test of a good contract is simple: when an ordinary disagreement comes up, can you answer it from what you agreed, without guessing what the other person meant?

For the wider process, see our guide on how to hire a virtual assistant, and when the contract's signed, use our onboarding checklist.

Frequently asked questions

Do I need a contract for a virtual assistant?

Yes. Even a small arrangement benefits from written terms covering scope, payment, confidentiality, ownership of work, data handling and how it ends. It prevents disagreements neither of you intended.

Can I use a free virtual assistant contract template?

A template can be a starting point, but it often misses the practical decisions that cause real disputes. Prepare your operating decisions first and have the agreement reviewed for the countries involved.

Do I automatically own the work my virtual assistant creates?

Not necessarily. In the UK, the creator of commissioned work is generally the first copyright owner unless agreed otherwise in writing, and US "work made for hire" rules for contractors are limited. Agree ownership or licence terms explicitly.

Does my virtual assistant need to sign an NDA?

A confidentiality agreement is sensible when they handle business or customer information. It should explain what's confidential, how it can be used and what happens at the end. It doesn't replace proper data protection arrangements.

Does calling my VA a contractor in the contract make them one?

No. The label doesn't decide legal status. How the relationship works in practice matters, so get advice if your setup involves close control, fixed hours or exclusivity.