Virtual assistant task brief template: how to hand over a job in five lines

Light graphic reading "Hand over a task in a few clear lines" beside a brief on a laptop

A good task brief tells your virtual assistant what you want, by when, why it matters and what they can decide on their own. Most rework comes from briefs that describe the task but skip the outcome. Use the template below the first time you hand over any task. If the task repeats, move it into your VA’s SOP so you never brief it again.

Briefing is where many early frustrations between clients and VAs start. The fix is simple, and it gets quicker every time you do it.

The template

Copy this into a document, email or task tool and fill in each line.

Task: One sentence describing the job.

Outcome: What does “done” look like? Describe the finished result.

Deadline: When you need it, and whether that’s firm or flexible.

Why it matters: One or two lines of context, such as who it’s for and what it feeds into.

Steps or example: The steps if there’s a set way, or an example of a past version you liked.

Resources: Where to find files, logins and information.

Decisions: What your VA can decide alone, and what needs you.

Check-in: When to update you, and how to tell you it’s finished.

That’s it. Eight lines.

What each section is for

Task and outcome

The task is what to do. The outcome is what you want at the end. “Research five venues” is a task. “A shortlist of five venues in Austin for 40 people on 12 March, under our budget, with photos and contact details, so I can pick two to visit” is an outcome. The second version means your VA knows when they’re done and what to leave out.

Deadline

Say whether the date is firm. “Friday, firm, because it goes to the board” is very different from “Friday if possible.”

Why it matters

Context helps your VA make good choices you didn’t think to specify. If they know a report is for a nervous investor, they’ll pay more attention to the numbers.

Steps or example

If there’s a right way to do it, list the steps. If you care more about the result than the method, share an example of what good looks like. Examples save more time than any description.

Resources

List where things live. A shared folder, a CRM view or a password manager entry. Share passwords through a password manager such as LastPass, so your VA never sees raw passwords.

Decisions

This is the line most people leave out, and it causes the most back-and-forth. Be explicit. “You can book anything under our usual limit without asking” or “Draft replies, but don’t send without my OK.”

Check-in

Say how you’d like to hear about progress. A note when it’s done? A halfway update for bigger jobs? Agree on the channel too, whether that’s email, Slack or a comment in your task tool.

A worked example

Here’s a brief a founder might send for a recurring sales task.

Task: Prepare the weekly pipeline summary.

Outcome: A one-page summary showing new leads, meetings booked and deals that moved stage this week, with three deals that need my attention flagged at the top.

Deadline: Every Friday by noon, firm, because I review it before the Monday sales meeting.

Why it matters: It’s how I decide where to spend my time next week.

Steps or example: Use last week’s summary in the shared folder as the template. Pull figures from the CRM’s weekly view.

Resources: CRM login in the password manager. Template in Sales > Reports.

Decisions: You choose which three deals to flag. Tell me why in one line each.

Check-in: Send it in our usual chat thread when it’s ready.

Once this runs smoothly for a few weeks, it goes into the SOP, and the brief isn’t needed anymore.

Common briefing mistakes

A few habits cause most of the rework I see:

  • Skipping the outcome. Your VA finishes the task but not the job you had in mind.
  • Hiding the deadline. “When you get a chance” means different things to different people.
  • No decision rules. Your VA waits for you on small things, or decides big things without you.
  • Briefing by voice note only. Fine for urgency, but write it down too, so it can be checked later.
  • Changing the brief without saying so. If priorities shift, tell your VA directly.

From brief to SOP

Every VA we place builds an SOP for your account from day one. It documents how your work flows, from recurring tasks to the tools you use. A task brief is the first draft of an SOP entry. When a task repeats, ask your VA to add it to the SOP using your brief as the starting point.

That’s how delegation scales. You brief once, your VA documents it, and the task runs without you. It also means holiday cover and handovers are much easier, because the knowledge isn’t only in two people’s heads.

Training comes first

A brief works best once your VA understands your business. In the first weeks, spend time training them on your processes, products and language. Daily contact is ideal, and weekly is the minimum. The better your VA knows your world, the shorter your briefs can become.

For more on handing over work, read our guide on how to delegate to a virtual assistant effectively, or see our VA services.

Frequently asked questions

What should a virtual assistant task brief include?

The outcome you want, the deadline, the context, the steps or examples, what your VA can decide alone, where to find what they need and how to tell you it’s done.

How long should a task brief be?

As short as it can be while still answering your VA’s likely questions. For routine tasks, a few lines. For a first-time project, a page.

Do I need to write a brief for every task?

No. Write one the first time. If the task repeats, it belongs in your VA’s SOP instead.

Find a VA worth briefing

If you’re ready to hand work over, let’s find the right person to hand it to. Book a discovery call with me and Nikki.