By the Templateez Team · Licensed Attorney · June 2026

Virtual Assistant Intake Forms: What to Capture at Client Onboarding

A virtual assistant who starts work on day one without knowing the client's timezone, preferred communication channel, or which tools they already use is going to spend the first two weeks asking questions that should have been answered before the engagement began. Every clarification email is a delay. Every wrong assumption about scope is a scope dispute waiting to happen. Every tool access request that comes three days late is a task that sits unfinished while the client wonders what they are paying for.

Most VA businesses collect a name, an email, and a vague description of what the client needs help with. That is not intake — that is a lead form. A real virtual assistant intake form captures everything needed to start work immediately, set accurate expectations, and protect both parties when the engagement inevitably encounters its first ambiguity. Here is what that form should include.

Client information: more than a name and email

Virtual assistant work is deeply embedded in a client's daily operations. You are not showing up, performing a service, and leaving. You are inside their inbox, their calendar, their CRM — sometimes for months or years. That level of access requires a thorough client profile from the start:

• Client name and company — full legal name of the individual you report to, plus the company name if applicable. Solo entrepreneurs and small business owners are the core VA market, but you will also work with teams at mid-size companies where the point of contact is not the owner.
• Industry — a VA supporting a real estate agent has different daily rhythms than one supporting a SaaS founder or a healthcare consultant. Industry context shapes everything from the vocabulary in their emails to the compliance requirements you may need to follow.
• Company size — solo operator, small team (2-10), or medium business (11-50). This affects how many stakeholders you will interact with, how many calendars you may need to manage, and how formal the communication style needs to be.
• Website and social media profiles — capture all active URLs. You will need these whether you are managing social accounts, drafting content, or simply understanding the client's brand voice and public presence.
• Timezone — this is not optional information for a VA. It is foundational. If you are in EST and your client is in PST, every deadline, every meeting time, and every "end of day" means something different. Capture the client's primary timezone and note any seasonal adjustments (some clients travel frequently or split time between locations).
• Preferred communication channel — email, Slack, Microsoft Teams, Zoom, phone, or some combination. Many clients want quick questions handled over Slack but formal updates delivered by email. Some want a daily standup on Zoom. Others never want a call unless something is urgent. Get this right on day one.
• Response time expectations — same day, within a few hours, next business day. This is one of the most common sources of friction in VA relationships. A client who expects replies within an hour and a VA who checks messages three times a day are going to have a conflict by the end of the first week.
• Existing tools and platforms — what is the client already using? Google Workspace or Microsoft 365? Notion or Asana? HubSpot or Salesforce? Knowing this before onboarding means you can prepare, request access, and avoid the "I've never used that platform" conversation after work has already been assigned.

Service scope: defining what the VA will actually do

This is where most VA engagements go wrong. The client says "I need help with admin stuff." The VA interprets that as email and calendar. The client meant email, calendar, travel booking, expense reports, and managing their CRM pipeline. Three weeks in, someone is disappointed — either the client because the VA is not doing enough, or the VA because the client keeps adding tasks that were never discussed.

Your intake form should present clear service categories and let the client select everything that applies:

• Email management — inbox triage, drafting replies, unsubscribing from lists, flagging priority messages, maintaining inbox zero
• Calendar management — scheduling meetings, blocking focus time, managing conflicts, sending confirmations and reminders
• Travel booking — flights, hotels, rental cars, itinerary creation, loyalty program management
• Social media management — content scheduling, engagement monitoring, DM management, analytics reporting
• Data entry and database management — CRM updates, spreadsheet maintenance, contact list management
• Bookkeeping support — invoice creation, expense categorization, receipt tracking, bank reconciliation prep
• Customer service — responding to inquiries, processing returns, managing support tickets
• Research — market research, competitor analysis, vendor comparison, fact-checking
• Content writing — blog posts, newsletters, email sequences, social media captions
• Project management — task tracking, deadline monitoring, team coordination, status updates
• Personal tasks — gift ordering, appointment scheduling, event planning, household coordination

Beyond the category checklist, your intake should also capture three critical scope dimensions:

Primary focus. Of everything selected above, what is the single most important thing to get off the client's plate? This is what you prioritize on day one, not the full list. A client who selected eight categories but really just needs someone to stop their inbox from controlling their day should see inbox management handled first.

Recurring vs. project-based. Is this an ongoing monthly retainer or a one-time project? A VA hired to set up a CRM and migrate 5,000 contacts has a fundamentally different engagement than one hired to manage that CRM indefinitely. Capture whether the work is ongoing, project-based, or a trial period that may convert to ongoing.

Tasks specifically excluded. What should the VA never do? Some clients do not want their VA making phone calls. Others do not want them posting on social media without approval. Some will never want the VA to interact with certain clients or accounts. Documenting exclusions at intake prevents the "I didn't want you to do that" conversation later. This is similar to how marketing and PR firms define scope boundaries at onboarding — knowing what is off-limits is as important as knowing what is expected.

Access and tools: the operational backbone

A virtual assistant without access to the client's tools is a virtual assistant who cannot work. This section of your intake form is not a formality — it is the operational prerequisite for everything else. Every day of delayed access is a day of lost productivity that the client is paying for.

Capture the access level needed for each platform category:

• Email — delegated access (VA sends as the client), shared inbox, or forwarding setup. Each has different implications for how the client's contacts perceive the communication.
• Calendar — view-only, edit (can create and modify events), or full control (can accept/decline on the client's behalf). Most VA engagements need at least edit access.
• Social media accounts — which platforms (LinkedIn, Instagram, X, Facebook, TikTok, Pinterest), and what role: admin, editor, or analyst? A VA managing social media content needs editor access at minimum. A VA just pulling analytics can work with analyst-level access.
• File storage — Google Drive, Dropbox, OneDrive, or SharePoint. Which folders should be shared? Are there folders the VA should not have access to?
• Project management — Asana, Trello, Monday, ClickUp, Notion. Does the client already have boards and workflows set up, or will the VA be building them from scratch?
• CRM — HubSpot, Salesforce, Zoho, Pipedrive. What permission level? Can the VA create and modify deals, or only update existing records?
• Accounting software — QuickBooks, Xero, FreshBooks. View access for reporting, or edit access for invoicing and categorization? This distinction matters enormously for liability.
• Communication platforms — Slack workspace, Teams tenant, Discord server. Will the VA interact with the client's team, or only with the client directly?
• Password management — LastPass, 1Password, Dashlane. Will the client create a shared vault for the VA, or share credentials individually? Shared vaults are the professional standard — they allow access without exposing the actual password and can be revoked instantly when the engagement ends.
• Phone system — will the VA answer calls, check voicemail, or manage call forwarding? If the VA is answering the phone as the client's business, they need a script and clear guidelines on what they can commit to.
• Website CMS — WordPress, Squarespace, Wix. Admin access or editor access? A VA making blog post updates needs editor. A VA managing plugins, themes, or site settings needs admin.

Workflows and procedures: how the work actually gets done

Access to tools is only half the equation. The VA also needs to know how the client wants those tools used. Two clients can both use the same CRM, but one wants every lead logged within an hour and the other only wants qualified leads entered after a phone screen. Your intake form should capture the operational layer on top of the technical access:

• Existing SOPs — does the client have documented processes? Most small business owners do not, which means the VA will need to build them during the first few weeks. Knowing this upfront sets realistic expectations about ramp-up time.
• Decision authority — what can the VA decide independently versus what needs client approval? Can the VA reschedule a meeting, or does every change need a green light? Can they reply to a customer inquiry, or must they draft and wait for approval? The more authority the VA has, the more productive the engagement — but that authority needs to be explicitly defined, not assumed.
• Approval thresholds — if the VA has purchasing authority, what is the spending limit? Can they buy a $15 stock photo without asking? A $200 software subscription? Most engagements work best with a clear dollar threshold below which the VA can act independently.
• Escalation procedures — when something goes wrong or falls outside the VA's authority, how should they escalate? Text message for urgent issues? Email for non-urgent? Is there a backup contact if the client is unreachable?
• Scheduling rules — booking guidelines (minimum meeting length, buffer time between calls, blackout periods, no meetings before 9 AM or after 4 PM), client preferences for in-person vs. virtual, and any standing meetings that should never be moved.
• Email handling protocols — which emails should the VA reply to directly, which should be forwarded to the client, which should be archived, and which should be flagged for follow-up? Without these rules, the VA is guessing — and guessing with someone else's inbox creates real problems.
• Social media guidelines — does every post need approval before publishing, or can the VA post within brand voice guidelines? Are there topics to avoid? Hashtag conventions? Engagement rules (who to reply to, who to ignore)?
• Customer inquiry handling — what can the VA promise a customer? What should they never commit to? What is the standard response time the client wants maintained? What gets escalated immediately?
• Reporting cadence — daily summary of completed tasks, weekly recap, or as-needed updates? What format — a Slack message, a shared Google Doc, an email with bullet points? Some clients want to know everything the VA did today. Others only want to hear about blockers and decisions.

Confidentiality and compliance: protecting both parties

A virtual assistant has access to some of the most sensitive aspects of a client's business — their email, their financials, their customer data, their strategic plans. The intake form is where the boundaries of that access are documented:

• Non-disclosure agreement — is an NDA required before access is granted? Most professional VA engagements should have one. Your intake form should note whether an NDA is in place, pending, or not required.
• Data handling protocols — what information is considered sensitive? PII (personally identifiable information), financial records, health information, trade secrets. The VA needs to know what they are touching and what the handling requirements are.
• Industry-specific compliance — a VA supporting a healthcare practice may encounter HIPAA-protected information. A VA supporting a financial advisor may need to be aware of FINRA recordkeeping requirements. A VA working with an educational institution may handle FERPA-covered student records. These are not edge cases — they are common VA client industries, and compliance obligations transfer to anyone handling the data.
• Social media posting authority — can the VA post as the client without per-post approval? This is a reputational risk question that belongs in the confidentiality section, not just the workflow section. A wrong post from the client's account is a different category of problem than a late email reply.
• Financial boundaries — can the VA make purchases on behalf of the client? If so, what are the limits? Is there a company credit card, or does the VA use their own card and expense it? Financial access needs explicit documentation.
• Recording and transcription — does the client want meetings recorded or transcribed? Are there legal requirements in the client's jurisdiction about consent for recording (one-party vs. two-party consent states)?

Pricing and engagement terms: the business side of the relationship

The intake form is where the financial structure of the engagement is documented. Ambiguity about pricing is the fastest way to lose a client — not because the rate is wrong, but because the client did not understand what they were paying for:

• Rate structure — hourly, monthly retainer, or package-based. Each has trade-offs. Hourly gives the client flexibility but makes revenue unpredictable for the VA. Retainers provide stability for both parties but require clear definitions of what the retainer includes.
• Retainer details — how many hours are included per month? Do unused hours roll over? If the client needs more hours in a given month, what is the overage rate?
• Package scope — if the VA offers packages (e.g., "Social Media Management Package" or "Executive Assistant Package"), what is included and what is extra? Packages work well for marketing but create disputes when the client's needs do not fit neatly into the predefined box.
• Billing cycle — weekly, biweekly, or monthly. Monthly is most common for retainer clients. Weekly or biweekly may be appropriate for project-based work or new engagements where trust is still being established.
• Payment method — invoice (Net 15, Net 30), auto-pay through a platform, or direct transfer. Late payment terms should be specified here as well.
• Minimum commitment — one month, three months, or none. Many VA businesses require a minimum commitment to justify the onboarding investment. A client who churns after two weeks has consumed significant setup time that a single payment may not cover.
• Trial period — does the engagement start with a paid trial (typically one to two weeks) before converting to a full retainer? Trial periods reduce risk for both parties and are increasingly standard in the VA industry.
• Termination terms — notice period (typically two weeks or thirty days), and what happens when the engagement ends. The handoff plan is critical: returning all access credentials, transferring files and documents back to the client, documenting processes the VA built during the engagement, and deactivating shared vault access. A clean offboarding protects the VA's professional reputation and the client's operational continuity.

Building a professional engagement from the first interaction

A thorough intake form does more than collect information. It demonstrates to the client that you run a professional operation. When a prospective client fills out a form that asks about their timezone, their escalation preferences, their compliance requirements, and their tool access needs, they understand that this VA has onboarded enough clients to know what questions matter. That first impression of competence is what separates a $25-per-hour generalist from a $55-per-hour specialist.

The intake form is also your protection. When a client says "I thought you were going to handle my bookkeeping" and your intake form shows that bookkeeping was not selected in the service scope, you have documentation. When a client disputes a charge and your intake form shows the agreed rate structure and overage terms, you have a reference point. When an engagement ends and the client claims you still have access to their systems, your documented offboarding checklist shows every credential that was returned.

If you are building documentation across a multi-service professional practice, the Professional Services Bundle includes virtual assistant alongside 34 other professional service categories, each with profession-specific intake fields.