Published: September 24, 2026

“We need a virtual assistant” sounds like a hiring request, but it is usually a signal that work has become difficult to manage. The right first move is not writing a job post. It is identifying which work should leave the manager’s desk, what result the business needs, and who will manage the person after hiring.

A useful virtual assistant role intake converts a broad request into decisions a recruiter and candidate can act on. It separates essential duties from a manager’s wish list, exposes incompatible expectations, and gives the future assistant a fair picture of the job. That clarity improves sourcing, makes screening consistent, and lets onboarding begin with real assignments instead of a vague promise to “help with everything.”

Start with the bottleneck, not a title

Ask what is failing today. A founder may request an executive assistant because the calendar is crowded, then describe unpaid invoices, customer follow-ups, social drafts, and personal travel. Those activities do not automatically belong in one role. They use different systems, carry different risks, and may require different experience.

Turn the complaint into an observable outcome. “I am overwhelmed” is real, but it cannot guide a candidate. “Every qualified sales inquiry receives an approved response within one business day” is clearer. So is “the leadership calendar has protected focus time and every external meeting has a confirmed owner.” Outcomes reveal recurring work without pretending the assistant owns decisions that belong to a manager.

Document the bottleneck without inventing a return-on-investment claim. Useful evidence includes untriaged messages, meetings rescheduled, reports waiting for source data, and hours of coordination. The purpose is to size and prioritize the work, not promise a financial result.

Build workload from real examples

Collect two or three weeks of representative tasks when possible. For each task, record the trigger, normal volume, busy-period volume, required source, expected output, and person who accepts the result. Work that occurs “often” could mean twice a week or forty times a day. That difference changes staffing level, schedule, tools, and the work sample that would be fair.

Sort activities into four groups:

  1. Ready to delegate: the source, steps, authority, quality check, and receiver are known.
  2. Delegable after repair: the work is suitable, but instructions, access, or approval rules need attention.
  3. Reserved decisions: an assistant may prepare information, while an authorized manager retains approval.
  4. Out of scope: the activity conflicts with the role, requires credentials the company cannot appropriately share, or needs specialized judgment.

This classification prevents a common failure: advertising a tidy administrative role and then assigning bookkeeping judgment, human-resources decisions, or unsupervised customer commitments after the person starts.

Define authority one action at a time

Access to a system does not say what someone may do inside it. Use action verbs for every workflow. An assistant might view a shared inbox, label routine messages, draft from an approved template, and route exceptions. That does not necessarily permit sending every reply, changing account settings, accepting terms, or deleting records.

Write both the permitted action and stopping condition. For calendar work, a boundary might allow proposing times inside published availability while requiring approval before moving a customer commitment or travel meeting. In sales support, an assistant may update verified facts but stop before changing price, stage, ownership, or a promised delivery date.

Apply least privilege when planning access. NIST SP 800-53 Rev. 5 describes access-control and accountability principles that can inform local design. It does not prescribe a virtual assistant job description; responsible security, privacy, employment, and legal owners should decide the controls that apply.

Resolve schedule and manager capacity

“Flexible hours” is incomplete if the role depends on live approvals. Identify work that can happen asynchronously, decisions that need overlap, and the response time the manager can support. State the relevant time zone. A four-hour overlap requirement should have a work-related reason, such as a daily customer handoff, rather than being added by habit.

Then test manager capacity. Who holds the weekly one-to-one? Who reviews the first examples? Who answers questions when the primary manager is unavailable? A role with no manager is not made autonomous by hiring a more experienced candidate. It is simply missing an operating owner.

Name a primary manager and a backup for defined situations. AHRQ TeamSTEPPS 3.0 offers communication concepts such as handoffs and check-backs that are useful when designing transfers of responsibility. Adapt those concepts to the organization rather than presenting them as a staffing compliance standard.

Choose screening evidence

Every criterion should connect to an essential duty. If the role prepares customer follow-ups, review a short fictional writing exercise using a supplied source. If it maintains a tracker, use a small invented data set and score accuracy, exception handling, and questions asked. Do not use live commercial work as an unpaid test.

Separate what must be present on day one from what can be learned during onboarding. Familiarity with one software brand may be less important than following a documented process, reconciling conflicting inputs, and leaving a reviewable handoff. Inflating every preference into a requirement shrinks the pool without necessarily improving fit.

Use the same evidence rules for candidates at the same stage. The U.S. Equal Employment Opportunity Commission explains that employment practices can create legal risk when they discriminate or disproportionately exclude people without job-related justification. Employers should obtain advice for their location and arrangement; a general article cannot determine their obligations.

Run a ten-minute stress test

Before recruiting, walk through one ordinary day and one difficult day. On the ordinary day, ask who opens the source, what they produce, who reviews it, and what marks it complete. On the difficult day, introduce a realistic exception: the manager is offline, two requests conflict, a record contains sensitive data, or a customer asks for a promise outside the approved template. The role is ready only if the intake shows where the assistant stops and who receives the exception.

Test workload arithmetic too. Estimate recurring volume and handling time, then add meetings, training, administration, and reasonable variation. If the list consumes more hours than the proposed schedule, reduce scope or change capacity. Do not label impossible throughput as a performance expectation.

The final intake record

Keep one approved record with the business outcome, recurring duties, approximate volume, schedule and overlap, systems, minimum access, allowed actions, prohibited actions, primary manager, backup, screening evidence, first-week assignments, and unresolved risks. Add an owner and review date. Link to controlled procedures rather than copying instructions that will drift.

Recruiting can begin when the manager accepts the scope, confirms management capacity, and can explain how evidence will be judged. If the role still combines unrelated duties or depends on unapproved access, pause the search and repair the design. A clear intake may narrow the job, but that is an advantage: candidates can decide whether the real work fits them.

OnboardingEmployees supports teams that need a disciplined path from assistant-role definition through screening and first-week readiness. Review virtual assistant staffing services or request a staffing support plan.

Frequently asked questions

How detailed should a virtual assistant role intake be?

It should let a recruiter identify relevant evidence and a candidate understand recurring work, schedule, manager, and authority limits. It need not reproduce every procedure.

Can one assistant support several functions?

Yes, when workload is realistic, duties are compatible, and every workflow has clear ownership and access boundaries. A mixed role becomes risky when unrelated responsibilities are added without changing capacity, training, or supervision.

What if the manager cannot estimate volume?

Use a short observation period. Count representative requests and note seasonal variation. Treat the first estimate as a planning assumption with a review date, not a guaranteed forecast.

When should the intake be revised?

Review it when duties, volume, schedule, systems, manager ownership, access, or risk changes. Repeated exceptions during screening or onboarding also indicate that the role definition needs repair.

Continue building the workflow

Connect this process to the virtual assistant role brief, then use the virtual assistant onboarding checklist for the next handoff. The U.S. Equal Employment Opportunity Commission explains that employment selection procedures should be job related and consistent with business necessity.