How to communicate with your virtual assistant so they actually get it right

Most delegation problems that look like a skills gap are actually a communication gap. The task didn't get done wrong because your VA wasn't capable; it got done wrong because the instructions left room to guess. Here's how to close that gap, on your end, so the results actually match what was in your head.

The vague request that costs you a redo

Picture this message: "Can you make me a few Instagram posts for my sale next month?" It looks like a complete request. It isn't. How many is "a few"? What kind of post, reels, carousels, static images? What's the sale actually about, and when does it run?

A specialist working from that message has two options: guess, or ask. If they guess, you'll likely get work that's technically responsive but not what you pictured, and now you're both redoing it. The fix isn't complicated: the same level of detail you'd want back from your VA is the level of detail your request needs going in. "Can you create 5 Instagram carousel posts for our March sale (20% off, March 1-7), similar style to last month's launch posts?" takes thirty extra seconds to write and saves an entire redo cycle.

Tell your team how and when to reach you, once

A lot of communication friction isn't about tone or clarity, it's about mismatched assumptions nobody stated out loud. If your specialist doesn't know you're unreachable on Fridays, a message that goes unanswered for two days can read as being ignored instead of what it actually is. If you only check a specific channel weekly, anything urgent sent elsewhere will sit.

Setting this up once at the start, which channel for what, when you're generally reachable, what counts as urgent, removes almost all of this friction going forward. This is exactly why onboarding covers your communication preferences up front rather than leaving your team to guess at them over the first few weeks.

Recurring updates beat "any updates?"

Chasing status by asking "how's everything going?" puts the burden on you to remember to ask and on your specialist to reconstruct what's happened since the last time you checked. A standing weekly update, what's done, what's in progress, any open questions, flips that: you get the information without having to go looking for it, and nothing sits unspoken for two weeks because nobody thought to mention it.

Choose the right channel for the message

Not every update deserves the same format. A quick status check fits in a two-line message. Something with more nuance, a strategic question, a piece of feedback with a lot of context behind it, usually lands better as a quick video walkthrough or a real conversation than a wall of text. Fast Company's guide to delegating well makes a similar point: a written guide works for repeatable tasks, but talking someone through something once, even briefly, often prevents more confusion than a long written explanation would.

What this looks like once it's documented

The good news is none of this stays manual forever. Once your preferences, your brand voice, and your recurring request patterns are documented, which happens during onboarding, most of this friction disappears. Future requests get faster because the context is already there instead of being rebuilt from scratch every time.

If you're setting this up for the first time, our retainer packages walk through how onboarding and documentation work from day one, and our post on what makes a great client relationship with your virtual assistant team covers the relationship side of this if you want the fuller picture. Not sure what to hand off first? The 15-minute delegation audit is a free place to start.