Hiring a Virtual Assistant

How to Scope a VA Role So You Actually Get Leverage

A vague scope guarantees a slow ramp. Use this 4-part scoping framework to turn 'help me with stuff' into a real role.

7 min read Hiring a Virtual Assistant

Why most VA engagements stall in week 3

The number one cause of a slow VA ramp is a fuzzy scope. The founder says 'I just need general help' — and then spends week 3 frustrated that the VA hasn't 'taken initiative.' The VA is fine. The scope failed them.

The 4-part scoping framework

Use this structure to write the scope before you ever interview a candidate. It takes 30–45 minutes and saves weeks of churn.

  • Outcomes: 3–5 results the VA owns (e.g., 'inbox to zero by 6pm daily')
  • Recurring tasks: the weekly drumbeat (calendar review, CRM updates, weekly report)
  • Tools: the exact stack they'll use (Gmail, HubSpot, Notion, etc.)
  • Decision rights: what they can decide alone vs. what to escalate

Write the SOP before the hire

If you can't write a 1-page SOP for at least three of the recurring tasks before hiring, you're not ready to hire — you're ready to design the role. Spend a week capturing your own steps with Loom and a doc, then hire against that.

Ready to put this into practice?

Talk to us about staffing a VA matched to your industry, tools, and tone.

Explore related VA roles & industries

Put what you learned into practice — see the roles we staff and the industries we serve.