Virtual assistant agency contracts: the six clause groups that prevent disputes

What to take away

Group clauses by the argument they prevent, not by legal category. It is the only way to tell which ones your agreement is missing.
Four clauses do most of the work in retainer agreements: the unit, overage, unused capacity, and access on exit.
The clause about who owns the accounts is the one people discover they needed on the worst possible day.
This is a checklist for a conversation with a lawyer, not a substitute for one. Have the agreement drafted or reviewed by somebody qualified in the places you and your client operate.

Nothing here is legal advice, and no term, notice period or figure is recommended. The specifics belong to your jurisdiction and your counsel.

Group	The argument it prevents	Where agreements are usually thin
What was bought	I thought that was included	Overage, rollover and intake, all three
How it will be done	You said you would be available	Absence and continuity
Access and data	Who had my password	Removal on the day somebody leaves
Money	We never agreed to that	The mechanism for a price change
People	We would like to hire your assistant	Who directs the work day to day
Ending it	You have all my logins	Account ownership

Group one: what was actually bought

These prevent the argument that starts "I thought that was included".

The unit. Reserved hours, task count, or coverage window. One of them, defined.
Scope, in list form. The tasks covered, in the client's language.
Exclusions. Named specifically, including at least one thing a reasonable buyer might assume was included.
Overage. What happens above the unit: queues, billed at a stated line, or an agreed increase. Silence means absorbed.
Unused capacity. Whether it lapses or carries, and for how long. Without this, custom becomes contract.
Intake. How work arrives, and what happens to work sent another way.

The last three are the ones retainer agreements most often lack, and they cause more disputes than everything in the remaining groups combined.

Group two: how it will be done

These prevent the argument that starts "you said you would be available".

Coverage. Days, hours and time zone, with a rule for holidays.
Response and turnaround, separately. Acknowledgment is not delivery.
Who performs the work. A named person, a pooled team, or either at your discretion. Say which.
Absence and continuity. What happens when the named person is away or leaves.
Quality and review. Whether anything is reviewed before it reaches a customer, and by whom.

Do not promise coverage that your roster cannot hold in the worst week of the year. Whether it can is a staffing question, answered in the hiring and training guide.

Group three: access, data and confidentiality

These prevent the argument that starts "who had my password".

What access is granted, and to which systems.
Who may hold credentials, and the rule against sharing them.
What happens on the day somebody leaves your business.
Confidentiality, in both directions.
Personal data, where the work touches customer information: what may be handled, where, and by whom.
Records. Where the work touches books or receipts, say what the client will still be able to produce. The IRS guidance on which business records to keep is the baseline the client has to be left able to meet.

Obligations here vary by where you are, where your people are and where the client's customers are. That spread is exactly why this group needs professional review rather than a template.

Group four: money

These prevent the argument that starts "we never agreed to that".

Amount, and what it buys, matching the unit above.
Invoicing and payment timing.
What happens when payment is late, including whether work pauses and how notice is given.
Price changes. How much notice, and in what form. A written mechanism turns an increase into an administrative event.
Expenses and third-party costs, and who approves them.

Group five: people

These prevent the argument that starts "we would like to hire your assistant".

Worker status. State how the people delivering the work are engaged. The Labor Department's page on misclassification myths is clear that the economic reality of the relationship decides this, not the wording of an agreement, so the clause describes the arrangement rather than creating it.
Direct hiring. Whether the client may employ someone from your team, and on what terms.
Client instruction. Who directs the work day to day, which is a question your worker-status position depends on.

Take advice on this group specifically. It is the one where a clause that sounds protective can misdescribe the arrangement.

Group six: ending it

These prevent the argument that starts "you have all my logins".

Term and renewal. How it continues, and whether it renews automatically.
Notice, on both sides, in writing.
What the client receives at the end: documented processes, exported files, transferred access, and by when.
Account ownership. Whose accounts are whose, stated for every system either party created. This is the clause people wish they had.
What happens to work in progress.

An agreement that makes leaving straightforward is easier to sign. The exit clause is a sales asset as much as a legal one, which is why it belongs in the proposal too, as the guide on writing a clear agency proposal sets out.

Where the terms come from

The agreement should say what the proposal said, and the proposal should say what you agreed out loud. Where those three diverge, the divergence is the dispute.

So draft the agreement from the shape you described in the discovery conversation. The question sequence that produces that shape is in the guide to running a useful agency discovery call, and how the shape is presented and defended in the sale is in the sales and proposal guide.

Any renewal, auto-renewal or cancellation term is also a claim you make publicly, and the FTC's advertising guidance for small businesses requires a reasonable basis for a claim before it is made, including an implied one. If your public material says a client can cancel at any time, the agreement has to say the same thing.

Before you sign anything

Have it reviewed by a lawyer familiar with the places you and your client operate.
Read it as the client. Which sentence would you argue about?
Check that every promise on your website appears in it, and nothing more.
Keep versions, dated, and file the version each client actually signed.

Common questions

Can I use a template?

As a starting list of headings, yes. As the agreement you sign, only after somebody qualified has read it against your actual arrangement.

How long should the term be?

That is a commercial decision, not a legal one. Shorter terms with a clean notice period close more deals and expose you to less onboarding loss than long lock-ins do.

Should the contract name the assistant?

Naming a person makes the promise concrete and makes absence a breach. Name the role and the backup arrangement instead, and introduce the person separately.

What if the client sends their own agreement?

Read it against these six groups and mark what is missing or reversed. Then get advice. Client agreements are usually written for suppliers of goods and fit this work poorly.