How To Set Expectations With A Virtual Assistant

Why Expectations Cause Most Problems

When an assistant disappoints you, the cause is often a gap between what you expected and what they understood. You assumed a reply within an hour. They assumed within a day. You wanted a formatted report. They sent a list. Neither of you was wrong, because nobody said it out loud.

Setting expectations is the cheapest way to prevent friction.

What To Cover

Quality

What does good work look like? Share examples of finished work you like, and a checklist for common tasks. Explain the difference between “done” and “done well.”

Speed

State deadlines and typical turnaround times. “Routine tasks within one business day, urgent within four hours during overlap.”

Communication

Which channels, how often, and how quickly to respond. See communication norms.

Decision Authority

What can your assistant decide alone? Where must they ask? For example: “You can reschedule any internal meeting. Ask me before changing a client meeting.”

Escalation

How and when to raise blockers, mistakes, or questions. Encourage early flags: “Tell me about a problem when you see it, not when you have solved it.”

Availability

Working hours, time zone, holidays, and how to handle urgent requests outside hours. See time zones and scheduling.

A One-Page Expectations Document

Make it a shared document that both of you can edit. Ownership builds commitment.

Two-Way Expectations

Ask what your assistant expects from you: clear instructions, timely feedback, on-time pay, respect for time off. Write those down too. This turns expectations into an agreement rather than a list of demands.

Discuss Expectations Out Loud

On your first call, walk through the document and ask, “Is anything unclear or unrealistic?” Encourage honest answers. If your assistant is used to a more hierarchical culture, invite challenge explicitly. See cultural differences on global teams.

Revisit Regularly

In your monthly review, ask: “Are these expectations still right?” Update them as tasks and responsibilities change. See how to review performance.

When Expectations Are Not Met

Refer back to the document. Ask what got in the way. Adjust instructions or training before assuming a performance problem. See what to do when it is not working out.

Customer-Facing Expectations

For roles that talk to customers, add tone of voice, response-time targets, approved phrases, and escalation rules. Globaltize’s page on the live chat support agent role shows what structured expectations look like in support work.

What This Looks Like In Practice

A consultant wrote a one-page expectations document before her assistant started. It covered reply times, how to ask questions, what she could decide alone, and when to escalate. They read it together on day one. Six months later there had not been a single “I did not know I was supposed to” moment.

One page, read out loud, prevented most problems.

They update the page whenever a new situation comes up.

Before You Start

Before you write your expectations page, decide:

• Reply times for each channel

• What the assistant can decide without asking

• When to escalate to you

• Your quality standard, with an example

• Working hours and availability

See how to write task instructions that work or communication norms for remote teams.

Questions Owners Ask

Is a written document really necessary?

Yes. Spoken expectations get forgotten. A short page is enough.

What if my expectations change?

Update the page and say so. Changes are fine. Silent changes are not.

Next Steps

Write your one-page document today, and tell us who you need. For a helpful template on working agreements, the Atlassian Team Playbook has a team agreement play.