← All contract guides · 2026

Virtual assistant contract guide: retainer hours, scope, and credentials

A VA contract has to fence the retainer (what hours, what scope, what happens when the work overflows) and govern the account credentials a client hands over. Here's what it covers.

Virtual assistant work is a retainer that quietly expands: more hours, more tasks, more logins. The clauses that protect you are the monthly hours boundary with overflow billing, the scope definition, and the credential/confidentiality terms.

Here's what a defensible VA agreement covers in 2026, each mapped to a clause BookNox generates automatically.

The clause checklist

What must a virtual assistant contract cover?

  • Contracted monthly hours: a defined hours per month block billed monthly in advance, with unused hours not rolling over.
  • Response time SLA: acknowledgment of new requests within a stated number of business hours (24 unless you set one) during your stated business hours, and you're not on call outside them.
  • Overflow billing: hours beyond the block billed at your overflow rate, prorated in 15 minute increments, with the client's prior written approval before any overflow is logged.
  • Scope of work + amendments: covered task categories listed in the package; anything outside requires a written scope amendment before work begins.
  • Credentials handling: you use a password manager, never share credentials, and return or destroy all access within 7 days of termination.
  • Mutual confidentiality (survives termination): both sides keep business information shared during the engagement confidential, and the obligation continues after the contract ends.
  • Work product ownership: deliverables you create specifically for the client are assigned to the client on full payment; your materials, tools, templates, and expertise from before the engagement remain yours.
  • Independent contractor status: you perform as an independent contractor responsible for your own taxes, insurance, and equipment, so the engagement never reads as employment or agency.

Educational summary, not legal advice.

Every BookNox contract also carries the clauses that protect any service booking: a nonrefundable deposit tied to reserving the date, a cancellation policy written as a reasonable estimate of your losses rather than a penalty (with a rebooking credit), a force majeure clause, a liability cap that does not limit claims for death or personal injury caused by negligence, binding arbitration through a provider such as AAA or JAMS with a small claims carveout, general provisions (severability, entire agreement, no waiver), and an electronic signature block that cites the ESIGN Act and UETA, with a SHA-256 tamper evidence hash.

Timeline. A virtual assistant's monthly retainer under the default BookNox contract terms, from the first payment at signing to returning credentials after the engagement ends. At signing: First payment, hours billed ahead; Each new request: Acknowledged within 24 business hours; Before any overflow: Client approves extra hours in writing; End of each month: Unused hours do not roll over; 7 days after the end: Credentials returned or destroyed.
A virtual assistant's monthly retainer under the default BookNox contract terms, from the first payment at signing to returning credentials after the engagement ends.

Generic templates vs your craft

Why does a generic template get virtual assistants in trouble?

Generic freelance templates don't fence a retainer, so the agreed 20 hours becomes 30, scope creeps from inbox triage to full project management, and there's no written overflow rate to bill against. They also ignore the credential reality of VA work: you're handed logins to email, calendars, and payment processors, and a generic template says nothing about how those are secured or returned.

BookNox's VA contract pins monthly hours with prior approval overflow billing, requires a written scope amendment for new task types, and governs credentials explicitly, the clauses retainer work actually needs.

See all of BookNox’s contract clauses →

The modern clauses

What a VA contract needs in 2026 that older ones leave out

Hours, scope, overflow, credentials, confidentiality, and work product are the standing core, and BookNox generates all of them from your booking. Three further questions come up often now that contracts signed a few years ago rarely mention: what AI tools touch the work, what happens to client data beyond the passwords, and who actually does the work. For these, put the terms in writing as a scope amendment or a short addendum so nothing is left implied.

  • AI use disclosure: state which AI tools you use for drafting, research, transcription, or scheduling, and what never goes into them. A workable line: AI may assist with first drafts and summaries, but client confidential information stays out of any tool that trains on its inputs unless the client agrees in writing. A contract that answers the question before the client asks it avoids a harder conversation later.
  • Data handling beyond passwords: the credentials clause covers logins; data handling covers everything else you touch: customer lists, inboxes, invoices, and files. Name where client data lives (the client's own accounts, not your personal drive), how it moves, and what gets deleted at the end. A simple rule worth writing down: on termination you return or destroy client data within a stated window, then confirm it in writing.
  • Confidentiality with definitions: the generated contract already carries mutual confidentiality that survives termination. Strengthen it by naming what counts as confidential (business information that is not public, marked or not), the standard exceptions (already known, independently developed, or legally required disclosure), and how many years the obligation runs after the engagement ends.
  • Who does the work: if you ever hand tasks to an associate, the contract should say so: whether subcontracting is allowed, whether the client approves it in advance, and that the confidentiality and data terms bind anyone you bring in. Clients assume the person they hired does the work unless the contract says otherwise.

How BookNox generates this contract

From the booking, not a blank document.

You don’t fill in a template. Your client builds the booking on your quote page (package, date, options) and BookNox generates the finished virtual assistant contract with the right clauses already in it, freezes the wording at send time, and collects a signature compliant with ESIGN and UETA and the deposit through one link. The signed PDF carries a SHA-256 hash that shows any tampering and a full audit trail (IP, user agent, timestamps).

Sources, read on October 22, 2026: 15 U.S.C. 7001, the federal ESIGN Act, which says a signature or contract may not be denied legal effect solely because it is electronic, and Florida Statutes 668.50, one state’s enactment of the Uniform Electronic Transaction Act, which says the same under state law.

Educational summary, not legal advice. Have a licensed attorney in your state review any contract before you rely on it.

Common questions

virtual assistant contract FAQ

  • What happens when the work goes over the contracted hours? Overflow hours are billable at your stated overflow rate, prorated in 15 minute increments, but only with the client's prior written approval before any overflow is logged. Unused hours within a month don't roll over.
  • How is scope creep handled? The package lists covered task categories; any task outside that list requires a written scope amendment before work begins. That keeps "can you also..." from silently expanding the engagement.
  • What about the client's passwords and accounts? The credentials clause requires you to use a password manager, never share credentials with third parties, and return or destroy all access within 7 days of termination, with mutual confidentiality that survives the contract.
  • Who owns the work I produce as a VA? Under the generated contract, deliverables you create specifically for the client are assigned to the client once they have paid in full. Your materials, tools, templates, and expertise from before the engagement remain yours, so a client never ends up owning your systems.
  • Do I have to tell clients when I use AI tools? The generated BookNox contract does not require an AI disclosure, though a client's own paperwork may. Answering before being asked is the cheaper path: name the tools you use, what they are used for, and what client information never goes into them, and add it as a written addendum to the contract.
  • Is this a downloadable VA template? BookNox generates the finished VA contract from the booking and collects the electronic signature and first payment in one link, $29/month flat.

Keep reading: How to stop scope creep before it kills your profit · Service packages instead of hourly billing · Why handshake deals destroy service businesses

More guides and tools: Coaching contract guide · Tutoring contract guide · Hair and makeup contract guide

← Back to all contract guides

What it costs you

$29/month flat. No booking fee.

No tier gates. No fee on top of Stripe’s standard processing. The deposit lands in your bank directly via Stripe Connect Express. BookNox is never in the money path.

See the BookNox vs HoneyBook comparison →

GET PAID

One tap reserves the date.

No back and forth on invoices. No “send me a contract.” The deposit lands in your account and the calendar entry for every booking lands on your phone.

  • Payments through Stripe, transparent fees
  • A contract generated on every booking
  • Lead, price, and calendar entry sync

Send a real virtual assistant contract today.

Set up your packages, send a proposal, and take a signed contract plus a real deposit in one link. $29/month flat, no booking fee.