What to Put in Your VA Contract (and What Happens Without One)

It happens more than it should, and almost all of it is preventable.

A contract is not about distrust. It is about clarity, and it is one of the fastest ways to look like a professional instead of a hobbyist. It sets the terms before anyone is annoyed, before money is on the line, and before something ambiguous becomes a real problem. Sending a written agreement with every client is the baseline of running a real VA business.

Here is what belongs in your VA contract, and a quick look at what tends to go wrong when you skip each part.

Scope of Work

This defines exactly what you are doing, how often, and at what level of detail. Name specific tasks, not vague categories. "Social media support" is not a scope of work. "Scheduling and publishing three Instagram posts per week from approved captions" is. The tighter your scope, the easier it is to say no to the extras later.

Without it: Your client expected daily inbox management. You understood it as clearing flagged emails twice a week. Neither of you is wrong based on a verbal agreement, and both of you are frustrated by week three. Vague scope is where scope creep starts.

Payment Terms and Late Fees

Spell out your rate, your billing cycle, how you get paid, and what happens when an invoice is overdue. Say when invoices go out, when they are due, and what your late fee is. Some VAs charge a percentage after a set number of days; others pause work. What matters is that it is written down, so you are not chasing money with no leverage.

Without it: A client pays 45 days late and treats it as normal. You have no documented terms to point to and nothing to fall back on but an awkward message. You either absorb the delay or risk the client by pushing back.

Revision Limits

If you produce deliverables such as content, graphics, templates, or reports, cap the number of revision rounds included. Two is common. Unlimited is not sustainable and invites scope creep dressed up as feedback.

Without it: You send ten email drafts. The client revises them, revises the revisions, then asks for a whole new tone and starts over. You have spent triple the hours you quoted with no way to bill for it, because nothing defined where the work ended.

Ownership of Work

This is your intellectual property clause, and it matters more than most VAs realize. Who owns the content, systems, and templates you build? Usually the client is paying for the deliverables and will want to own them, but if you reuse frameworks across clients or want the right to show work in your portfolio, that has to be spelled out. Decide what you keep and what transfers, and put it in writing.

Without it: You hand over a full content system, then have no clear right to show it in your portfolio or reuse your own templates. Or the reverse: a client assumes they own everything you have ever built and objects when you use a similar process elsewhere. A clear clause protects your ability to keep working.

Termination Notice

Either side should be able to end things, but not overnight. A standard notice period, often two weeks, gives you time to wrap up, hand off files, and send a final invoice. Say what happens to work in progress and whether a final payment is owed at the end.

Without it: A client ghosts you on a Friday with work half-finished and an invoice outstanding, and you have no notice period to hold them to. A clause here means you get paid for what you have done and part on clean terms.

Confidentiality

You will often have access to inboxes, financial data, customer lists, passwords, and strategy. A confidentiality clause commits you to keeping that private during and after the relationship. It reassures the client and it signals that you take their business seriously.

Without it: Clients hesitate to hand over real access because nothing on paper says their information stays private. Offering confidentiality up front removes that friction and makes you easier to hire.

Communication and Availability

Set expectations for how and when you work: which platform you use, your response time, and your working hours. This is where you protect your evenings and weekends before a client assumes you are on call.

Without it: A client sends an urgent task on Sunday expecting a Monday-morning turnaround and is surprised you do not check messages on weekends. Neither of you is wrong, but without written expectations it reads like you dropped the ball. Setting availability is part of a strong onboarding process.

Dispute Resolution

If something goes sideways and you disagree, how is it handled? Name a simple process. Many freelance agreements route disputes through mediation before anything legal, and name the governing jurisdiction so there is no argument over whose rules apply.

Without it: A disagreement over unpaid work turns into a standoff where neither of you knows what the other can actually do. A short clause keeps it from getting personal.

Send It With Every Client

None of this is about assuming the worst. It is about having one document you can both return to when memory gets fuzzy or expectations drift. A contract does not prevent every problem, it prevents the ones that come from ambiguity.

Put it in your onboarding sequence, sent alongside or right after your proposal. A one-page agreement covering scope, payment, revisions, IP, confidentiality, termination, and communication is not overkill. It is what separates a professional VA from a hobbyist, and clients notice the difference.