Contracts turn VA work into clear, professional habits clients can trust.
10 min readIntroduction
Contracts turn VA work into clear, professional habits clients can trust.
A contract is not hostility. It is shared memory for busy people in different time zones.
Minimum VA agreement block
Copy and adjust brackets:
SCOPE
Tasks: [inbox triage, calendar, travel booking]
Tools: [Google Workspace, Slack]
Hours: [Up to 20 hrs/week]
Out of scope: [bookkeeping, social design, phone sales]
COMPENSATION
Rate: [USD $12/hr] OR Retainer: [USD $1,800/mo up to 120 hrs]
Currency: USD
Billing: Biweekly invoice
Due: Net 15 (pay within 15 days)
Methods: Wise or PayPal
CHANGES
New tasks outside scope require written approval before work.
CONFIDENTIALITY
Both parties protect credentials and client data.
TERMINATION
Either party may end with [14] days written notice.
Scope section (most important)
List:
- Weekly tasks (bullets)
- Tools you need access to
- Hours cap or deliverable count
- Explicit exclusions ("does not include bookkeeping")
Vague "general admin" invites scope creep.
Detector: scope creep detector.
Retainer vs project
| Retainer | Project |
|---|---|
| Recurring hours per month | Fixed deliverables |
| Rolling task list | Milestone dates |
| Weekly change log | Phase approvals |
Sample retainer: retainer agreement for VAs.
Payment and pause clauses
Include:
- When invoices go out
- Net 15 or Net 30 (pay within 15 or 30 days)
- Late fee if stated upfront
- Pause work if invoice X days overdue
More copy-paste clauses in payment terms guide.
Approvals tie to contracts
Define "done" per deliverable. Client approves in writing before you treat work as final.
Workflow: client approval workflows.
Common mistakes
Starting on verbal "we will formalize later."
No hours cap on retainers.
Missing out-of-scope list.
No change process.
Sharing passwords before agreement signed.
Final thoughts
Virtual assistant contracts and scope protect good relationships from bad assumptions.
Write it once. Reference it often.
See The Salag Method.
In short
Virtual assistant contracts and scope put tasks, hours, rate, and payment in writing before work starts. You do not need lawyer language. You need clear bullets clients can confirm. Scope lists what is in and out. Change requests go in writing. Email can work for small jobs; retainers need fuller terms.
Payment examples: VA payment terms with examples.
Common questions
Virtual assistant contracts and scope put tasks, hours, rate, and payment in writing before work starts. You do not need lawyer language. You need clear bullets clients can confirm. Scope lists what is in and out. Change requests go in writing. Email can work for small jobs; retainers need fuller terms. Payment examples: VA payment terms with examples.
Yes for paid client work. A contract or signed SOW (scope of work document) should cover tasks, hours, rate, pay terms, confidentiality, and changes.
The list of tasks, tools, hours or deliverables, and what is explicitly out of scope. Vague scope causes unpaid extras.
A detailed onboarding email plus client agreement can work for small engagements. Bigger or long-term work needs fuller terms.
Rate, currency, billing rhythm, due dates, methods, late fees, and pause rules for overdue invoices.
State included rounds for document or creative work. Extra rounds need approval and may be billed separately.
Written change requests. New tasks outside scope need client approval before work starts.
Yes. Publish timezone, core hours, and expected response window.
Both sides should agree not to share client data or credentials. Use plain language both can follow.
Agreement builders and scope tools on Salag. Not a law firm; get local advice for complex situations.
Retainers cap hours per period and list recurring tasks. Projects list milestones and deliverables with dates.