The VA Role Nobody Defined Before Hiring

Why most VA roles are undefined when hiring starts

The most common way to hire a virtual assistant is to hire when overwhelmed. When an owner is overwhelmed, they do not have time to plan the role. So they post a vague description, hire quickly, and expect the hire to bring clarity to a situation the owner themselves cannot yet describe.

This is the structural cause of most failed VA relationships. The VA cannot define their own role. That is the owner’s job, and it has to happen before the hire, not after.

What role definition actually requires

Defining a VA role starts with a task audit. The owner lists everything they do in a given week, categorises each task by whether it requires their specific judgment, and identifies the set of tasks that could be owned by a trained person following a documented process.

That second category is the VA’s role. The tasks that remain, decisions requiring the owner’s direct knowledge, relationships, or authority, are not delegation candidates.

A role is not a list of things the owner would like to offload. It is a coherent set of responsibilities a single person can own, execute, and improve over time.

What happens when the role is not defined

Without a defined scope, the VA defaults to doing what they are told on a task-by-task basis. They are not building expertise, not improving systems, and not operating with any autonomy. They are waiting.

The owner interprets waiting as low initiative or low quality. The VA interprets vague direction as poor management. Both conclusions are partially right. Neither diagnosis fixes the problem.

How to define the role before posting the job

Start with a week of tracking. Write down every task you complete, every decision you make, every communication you send. At the end of the week, sort the list into: tasks requiring your specific judgment, and tasks anyone could complete if they had the right process.

The second list is your VA’s starting scope. Take the ten tasks with the highest weekly time cost and document each one. That documentation becomes the job description, the onboarding guide, and the performance benchmark simultaneously.

When this does not apply

If the VA is being hired for a specific, well-defined function, such as managing a single platform, handling one type of client communication, or running a documented workflow, role definition may already be implicit. The problem described here applies primarily to generalist hires expected to cover broad administrative or operational support.