Yes, VAs need written terms before hour one. A free checklist covering scope, payment, IP, confidentiality, and exit clauses, plus links to Salag's agreement builder and template library.
11 min read"We'll keep it casual" is how VAs lose money
Filipino VAs working with international clients hear it constantly:
- "We're a small team, we don't do contracts."
- "Let's try a week and see."
- "I trust you, we don't need paperwork."
Trust is good. Documentation is how trust survives a missed invoice, a scope explosion, or a founder who forgets what they asked for.
A contract is not hostility. It is alignment in writing so neither side performs archaeology in Slack six months later.
Contract vs SOW vs confirmation email
| Format | Best for | Strength |
|---|---|---|
| Full freelance agreement | Retainers, data access, IP-heavy work | Highest protection |
| Statement of work (SOW) | Defined projects or onboarding | Clear scope boundaries |
| Structured confirmation email | Fast starts, smaller budgets | Good if client replies "confirmed" |
For many VA engagements, a one-page SOW attached to a short services agreement is enough. What matters is written confirmation, not font choice.
Free VA contract checklist
Copy this list. Every item should be answered before you touch a client inbox.
1. Parties and engagement type
- Legal or business names of both parties
- Engagement type: hourly, monthly retainer, or fixed project
- Start date and initial term (month-to-month is fine if written)
2. Scope and deliverables
- Primary responsibilities listed (inbox, calendar, research, etc.)
- Explicit out-of-scope list (social media, bookkeeping, design, etc.)
- Weekly or monthly hour cap
- Single point of contact named
- Response-time expectations (business hours, not 24/7 unless priced for it)
3. Payment terms
- Rate and currency (USD for most global clients)
- Billing rhythm (weekly, biweekly, monthly)
- Due date (Net 15 or Net 30)
- Accepted methods (Wise, PayPal, etc.)
- Who pays platform or conversion fees
- Deposit for new clients
- Late fee policy
- Work-pause clause if invoices go overdue
See payment terms for virtual assistants for copy-paste clauses.
4. Revisions, changes, and scope creep
- How extra requests are handled (change order, written approval)
- What happens when scope expands mid-week
- ALIGN-style rule: compare new asks to written terms before executing
5. Confidentiality and data access
- NDA or confidentiality clause if handling sensitive data
- List of systems you may access (email, CRM, bank view-only, etc.)
- Rule for credential sharing (password manager, no plain-text passwords in chat)
- Data return or deletion on exit
6. Intellectual property
- Who owns work product (usually client upon full payment)
- Whether you may show work in portfolio (often anonymized)
- License for any templates or tools you bring in
7. Termination and handoff
- Notice period (e.g., 14 days either side)
- Final invoice and hour reconciliation process
- Handoff checklist (inbox labels, SOPs, credential revocation)
- What happens to prepaid retainer balances
8. Signatures or written confirmation
- Both parties sign, or
- Client replies "confirmed" to a structured terms email you archive
Sample one-paragraph summary (paste and edit)
I, [Your name], will provide [inbox + calendar support] for [Client] at USD $[12]/hr, up to [20] hrs/week, billed biweekly Net 15 via Wise. Out of scope: [social media, bookkeeping]. First two weeks due before access. Either party may end with 14 days notice. Work product belongs to Client upon payment.
Build a fuller version in the Agreement Builder.
Red flags when clients push back
- "Contracts kill the vibe" = flexibility on your side only
- "Just start, we'll formalize later" = scope grows before terms do
- Refusal to confirm in writing = pause before you accept passwords
Email-only contracts that hold up
When clients will not sign PDFs, send this pattern:
Subject: Scope and payment confirmation before [start date]
Include rate, hour cap, scope, out-of-scope, billing, deposit, and pause clause. Ask for a one-line reply: "Confirmed."
Archive the thread. That is your contract.
For deeper template structure, see freelance agreement templates and documenting verbal agreements.
How Salag helps
- Agreement Builder: generate VA-ready terms without starting from a blank page
- Freelance Agreement Templates: when to use SOWs, retainers, and NDAs
- Scope Creep Detector: catch drift against what you signed
- Freelance Readiness Checker: confirm you are protected before hour one
Bottom line
Virtual assistants need a contract because ambiguity always bills the VA first. Use the checklist, confirm terms in writing, and keep scope and payment where both sides can reference them. Structure protects good client relationships; it does not kill them.
Move safer. Not faster.
In short
Yes, virtual assistants need a contract (or equivalent written terms) before billable work starts. You do not need a 20-page legal document. You need scope, rate, payment rhythm, confidentiality, IP, and exit rules in writing. Use the checklist below, then build faster with Salag's Agreement Builder or freelance agreement templates.