How To Write Task Instructions That Actually Work

Delegation And Productivity

How To Write Task Instructions That Actually Work

Clear instructions save hours of back and forth. Use this simple structure for every handoff.

By

Hire A Virtual Assistant Team

Updated

4 Minute Read

How To Write Task Instructions That Actually Work

How To Write Task Instructions That Actually Work

How To Write Task Instructions That Actually Work

How To Write Task Instructions That Actually Work

Table Of Contents

Key Takeaways

  1. Every handoff needs four things: the goal, the steps, the deadline, and what done looks like.

  2. An example of a finished result is worth more than a page of description.

  3. Ask your assistant to repeat the task back in their own words before they start.

Why Instructions Fail

Most bad instructions are not lazy. They are written from inside your head, where all the context lives. You know why the report matters, which client is sensitive, and what “good” looks like. Your assistant knows none of it. The result is work that is technically correct and practically wrong.

Good instructions close that gap without taking hours. They give just enough context for the assistant to make sensible choices on their own.

The Four-Part Brief

  1. Goal: What result do you want, and why does it matter?

  2. Steps: What are the main actions, in order?

  3. Deadline: When is it due, and in which time zone?

  4. Done means: How will you check the result?

A Before And After

Before: “Can you follow up with the leads from last week?”

After: “Goal: get replies from last week’s leads so we can book calls. Steps: open the ‘Leads’ sheet, filter Status = New, send the ‘Follow-up 1’ template from our shared folder, then change Status to Contacted. Deadline: Thursday 3 pm Eastern. Done means: every lead in the list has a status of Contacted, and any lead who replied is flagged in yellow for me.”

The second version takes two minutes longer to write and saves hours of guessing.

Add An Example Whenever You Can

Attach a finished sample: a well-written email, a correctly formatted spreadsheet, a report you liked. People copy patterns faster than they follow descriptions. Save your best examples in a shared folder so you can reuse them.

Use Short Sentences And Clear Formatting

Bullets, numbers, and bold labels make instructions scannable. Avoid jargon unless you define it. If English is your assistant’s second language, plain words are a kindness to both of you. Link directly to the files and tools involved so nobody has to hunt.

Confirm Understanding

Ask one simple question: “Can you tell me how you will approach this?” It takes a minute and catches misunderstandings before they become mistakes. Your assistant’s answer also tells you whether they need more context.

Turn Repeated Briefs Into SOPs

When you write the same instructions twice, save them as a standard procedure. Our guide to creating SOPs for your virtual assistant shows how to do that quickly. Over time you build a library that makes every new assistant productive faster.

Common Mistakes

  • Leaving out the deadline or the time zone

  • Assuming the assistant knows your customers

  • Giving feedback only on what was wrong, not what to do instead

  • Writing a novel when a checklist would do

Where Instructions Fit In The Bigger Picture

Instructions are the first step of the loop: brief, work, review, improve. Pair them with a weekly rhythm and regular check-ins. If your team handles customer conversations, Globaltize’s overview of customer support specialist responsibilities shows how detailed playbooks support consistent quality.

What This Looks Like In Practice

A marketing manager asked for “a quick competitor report.” What came back was ten pages she did not need. She rewrote the brief: three competitors, five bullet points each, pricing and main message only, due Thursday. The next version was one page and exactly right.

The assistant did not change. The brief did.

She now keeps her best briefs as templates.

A Quick Checklist Before You Start

Before you send a brief, check it has:

  • The outcome in one sentence

  • The format you want

  • A due date and time

  • Where to find inputs and access

  • What to do if stuck

See how to create SOPs for your virtual assistant or 7 delegation mistakes to avoid.

Questions Owners Ask

How long should a brief be?

Four to eight lines for most tasks. Longer briefs usually mean the task should be split.

Should I include an example?

Always, when you have one. An example prevents more mistakes than any paragraph.

Next Steps

Write a brief for the next task you plan to delegate, using the four parts above. When you are ready for someone to receive it, tell us who you need. For inspiration on clear writing, the Plain Language guidelines from the U.S. government are free and practical.

Written by

Hire A Virtual Assistant Team

Editorial Team

Practical guides on hiring, managing, and working with remote virtual assistants.

Table Of Contents

Ready To Hire A Virtual Assistant?

Tell us the role and the hours. We find and vet the candidates, and you choose who joins.

FAQ

Common Questions

Short, simple answers.

How Does The Hiring Process Work?

Who Makes The Final Hiring Decision?

How Do You Vet Candidates?

Ready To Hire A Virtual Assistant?

Tell us the role and the hours. We find and vet the candidates, and you choose who joins.