How to Write a Virtual Assistant Brief That Gets Results

When delegation fails, founders tend to blame the virtual assistant. More often, the real cause is a brief that never gave the VA a real chance to succeed. Ambiguous instructions, missing context, and undefined quality standards produce predictable results: work that misses the mark, repeated back-and-forth, and a founder who concludes that delegation is not worth the effort. Writing a clear brief takes 30 minutes. The return on that 30 minutes is weeks of clean, independent execution.

Why Most VA Briefs Fail

The most common briefing mistake is describing what you want without explaining why you want it or what good looks like. A brief that says 'manage my inbox' leaves a VA with no guidance on prioritisation, tone, escalation thresholds, or what constitutes a resolved ticket versus one that needs your attention. The VA makes reasonable guesses, some of which are wrong, and you correct them one by one over several weeks. A brief that defines outcomes from the start eliminates most of those corrections before they happen.

Element One: Task Description

Write a precise description of what the task involves, including the starting point and the expected end state. 'Review inbound emails each morning, archive newsletters, flag anything requiring my response with a one-line summary, and draft replies to routine requests using the templates I provide' is a task description. 'Handle my email' is not. Specificity is not bureaucracy — it is the difference between a VA who can act independently and one who needs daily guidance.

Element Two: Expected Output

Define what a completed task looks like. If you are asking a VA to research five potential podcast guests, the output should be a specific document format: name, show URL, episode count, topic alignment to your business, and contact email. If you are asking for a competitor content summary, specify that it should be a single page, sorted by platform, covering the last 30 days. When a VA knows exactly what finished looks like, they can self-assess quality before sending work to you.

Element Three: Tools to Use

List every tool involved in the task: the platform where work is done, where it is stored, and how it is shared with you. If you want research saved in a Notion database, say so. If you want calendar events created in Google Calendar with a specific format, write that down. If the task requires Zapier, Airtable, or any login-protected system, confirm access is granted before the VA starts. Tool ambiguity creates delays; tool clarity creates momentum from day one.

Element Four: Frequency and Deadline

State how often the task should be completed and by when. Daily tasks should specify the time window. Weekly tasks should name the day and, where relevant, the delivery time. One-off tasks need a clear deadline. Without this, VAs default to 'as soon as possible,' which means different things to different people. A brief that says 'every Monday by 10am your time zone' eliminates that variable entirely and sets a clear performance standard from the first week.

Element Five: Quality Standard

Describe what a strong output looks like, and — equally useful — what a poor one looks like. If you want responses written in a formal tone without exclamation marks, say that. If a research document needs sources linked rather than just cited, say that. If a social post should never include the phrase 'exciting news,' say that too. These preferences are invisible until something arrives that violates them. The brief is the right place to surface them, not the feedback conversation after the fact.

Common Mistakes to Avoid

The four most common briefing errors are: writing a brief once and never updating it as your needs evolve, failing to share example outputs that demonstrate what good looks like, not specifying a decision hierarchy for situations the VA has not seen before, and omitting any mention of what should be escalated versus handled independently. A living brief — one that you refine over the first few weeks based on questions your VA asks — is significantly more effective than a static document written before the working relationship begins.

Frequently Asked Questions About Writing a VA Brief

How long should a VA brief be? A brief does not need to be long — it needs to be complete. For a recurring task like email management, a one-page document covering all five elements (task description, expected output, tools, frequency, and quality standard) is sufficient. For complex tasks involving multiple steps or platforms, a two-page SOP is appropriate. The test is not length but whether a competent person could complete the task correctly after reading it once, without asking any clarifying questions. Where should VA briefs be stored? A shared Notion document or Google Drive folder is the most widely used setup. Notion works well for teams that want the briefs to be searchable and linked to a project board. Google Drive suits teams already running on Google Workspace. The location matters less than consistency — both you and the VA should know where to find and update briefs without hunting through email threads. Should I write a new brief for every task? For recurring tasks — yes, always. For one-off tasks, a clear Slack or email message with output defined is sufficient. The ROI on writing a full brief is highest for tasks that recur weekly or daily, since the brief is written once but used hundreds of times. How do I brief a task I've never fully documented before? Record a Loom screen walkthrough while completing the task yourself. This takes 5–10 minutes and gives your VA a precise visual reference they can revisit without asking you to re-explain. The Loom replaces the need for a written SOP in the early stages — you can refine the written version later as questions arise.