How to Manage a Virtual Assistant Without Accidentally Teaching Them to Ask Permission for Everything

Learning how to manage a virtual assistant often starts with a moment like this. Your assistant has finished the work you asked for.

You change the order of a few sections. Rewrite a perfectly fine sentence. Ask why they didn't check with you first.

The next day, they check with you before making the same kind of decision. And the day after.

Within a month, you're frustrated that they never take initiative.

Here's the uncomfortable bit: you taught them that. If reasonable choices keep getting reversed without a clear reason, asking permission becomes the safest way to work. Telling them to "take more initiative" won't undo that lesson.

Learning how to manage a virtual assistant well isn't about more meetings or more monitoring. It's about building habits on your side that let routine work flow, while the important exceptions still reach you.

Here, a virtual assistant (VA) is an independent freelancer or agency providing a service. Managing that relationship means managing priorities, capacity, quality and decisions, not supervising every minute of someone's day.

Your latest message shouldn't automatically jump the queue

Keep a visible list of committed work in priority order.

A new idea from you shouldn't automatically become top priority just because it's the most recent thing you thought of. Ask: does this change what we agreed?

If it's important, say what moves:

"Please do this first, and push the report to Thursday."

That's a decision. Compare it with:

"Can you quickly do this too?"

That hides the trade-off and leaves your VA juggling impossible promises.

Write a short priority note for the current week:

• the main result,
• fixed deadlines,
• work that can wait if things get tight.

A long list labelled "high priority" doesn't help anyone choose. And the hardest habit: stick to it, even when your own shiny new idea is the thing that has to wait.

Buy capacity honestly, don't rely on goodwill

An independent VA might work for other clients, or reserve a set amount of time for you. Plan within what you've agreed.

A friendly reply outside their normal hours doesn't mean you've bought permanent evening cover.

Talk about volume, not just hours. A service that comfortably handled a small queue last month might be facing a much bigger, messier one now. Same task title. Very different workload.

Ask your VA to flag capacity problems early, with the affected work and a suggested order. Then respond by:

• cutting scope,
• moving deadlines, or
• agreeing extra service.

Don't make "yes to everything" the only answer that feels safe.

And watch your own review capacity. Your VA can prepare work faster than you approve it. That leaves a pile of almost-finished items. That's your bottleneck, not a sign they should start even more.

Count unfinished work, not just busy work

Look at what's been started but not finished. Some might be waiting for your approval. Some for a supplier. Some got interrupted by a newer request.

Those differences matter far more than "my VA is busy."

The Kanban Guide (a well-known approach to managing work) calls this work in progress: things started but not yet finished. It recommends deliberately limiting it. You don't need the full method to use the idea.

Agree roughly how many things should be on the go at once. There's no universal number. Research waiting on outside replies behaves differently from drafting work that can be finished in one sitting.

Before adding a new task, ask:

• Can something existing be finished?
• Can something stuck be unblocked?
• Should something be deliberately paused?

Write the choice down. An invisible pause looks like forgetfulness later, when it was actually a priority decision.

And watch the oldest unfinished items, not just the newest urgent ones. A task can quietly hide behind daily updates while blocking a customer.

Make questions easy to ask and quick to answer

Agree a regular time and place for questions that need your decision.

When your VA asks, they should bring:

• the case,
• the evidence,
• the options,
• what happens if it waits.

And when you answer, give a decision or a clear next step. Not another vague "use your judgement."

Treat good escalation as part of good service. If you criticise someone for asking about a case outside their authority, they'll stop raising exactly the issues you want to hear about. If you criticise every independent choice, they'll ask about everything.

Look at repeated questions as clues:

• Is a policy unclear?
• Is a source missing?
• Haven't they demonstrated the judgement yet?

Fix the cause, rather than counting questions as a measure of dependence.

Keep genuine emergencies separate: a possible data leak, an unauthorised payment, an imminent customer deadline. Define those triggers in advance and give them a backup contact, so they're not choosing between silence and bombarding you.

Stop "correcting" choices that weren't wrong

This one habit changes everything.

When reviewing work, ask first: does this meet the agreed standard?

If yes, leave it alone, even if you'd have done it differently.

Separate three kinds of feedback:

• Factual errors: a wrong customer amount. Must fix.
• Missed requirements: a required section left out. Must fix.
• Style preferences: a sentence you'd phrase differently. Probably leave it.

If you treat all three as equally serious, your VA can't tell where careful checking really matters.

If a preference genuinely matters, document it with an example. Don't expect them to guess a hidden style rule from a handful of rewrites.

And if you've simply changed your mind, say so:

"The brief was clear, but the event plan changed."

That's very different from "you should have known." One updates the work. The other destroys confidence in your instructions.

Finally, notice good decisions out loud, especially sensible pauses and good judgement within their scope. Specific praise ("good call holding that slide until the figure was confirmed") tells them which behaviour to repeat. Generic "great job!" doesn't.

Use the weekly review to decide things, not to read the task list aloud

Before the review, both of you should already be able to see:

• completed work,
• open decisions,
• upcoming deadlines.

Use the review for what the records can't answer. A simple running order:

1. Accepted results and meaningful corrections.
2. Delayed or ageing work, and why.
3. Next week's priorities, plus any changes to scope, availability or reviews.

Then ask your VA:

"What's making this harder than it needs to be?"

A source that always arrives late, or two people giving conflicting instructions, might matter far more than any single mistake. Name someone responsible for fixing each issue.

Record decisions straight away in the task or operating notes. Google's version history can help track changes to shared documents, but it doesn't prove anyone noticed the change. Tell your VA clearly what changed and when it applies.

A good review changes something: a priority, an exception, an unrealistic promise, a recurring rule. If it only produces a longer list of things to discuss later, check whether the right decision-maker was in the room.

A week in the life: presentation support done right

Here's a hypothetical example.

A consultancy buys presentation preparation from an independent VA. The VA builds client decks from approved notes and source material. The owner stays responsible for factual claims and final delivery.

Monday. They agree the client presentation is the main priority. An internal template refresh is lower priority. The owner supplies approved notes and confirms when they'll review the draft, so the VA can plan around a real approval window.

Tuesday. The owner sends an excited message about redesigning another deck. The VA asks: does this replace the template refresh, or should it be quoted separately? The owner records it as a proposed request. It doesn't silently interrupt the client deck.

Wednesday. The VA spots a revenue claim in the notes with no supporting evidence. They build the rest of the deck and flag that one slide with a specific question. The owner supplies the approved figure and source. The VA kept working safely without inventing the missing claim.

Thursday. The owner reviews the draft. One layout choice isn't what they'd usually do, but it's clear and within the style guide. They leave it. They correct one factual label and explain the source rule. The VA learns that reasonable choices won't be reversed just because the owner has a different taste.

Friday. The review spots a pattern: approved notes keep arriving close to the deadline. They agree an earlier cut-off for inputs. The fix is about the handover between them, not asking the VA to work faster.

Write the review down so anyone could pick it up

For that week, the review note might say:

"Client deck accepted after one factual-label correction. Unverified claim correctly held. Template refresh still pending by agreement. New redesign request not yet accepted. Owner to supply notes before the next preparation window."

That separates performance, scope and client-side delays. It doesn't turn every unfinished item into a failure, or every busy day into success.

A reusable review sheet:

WEEKLY VA REVIEW

Results accepted:

Meaningful corrections (and cause):

Open decisions, owner and deadline:

Capacity changes:

Next week's commitments:

My actions (inputs, approvals, decisions):

Rule or instruction to update:

Evidence to check next week:

Link to the actual work instead of copying long descriptions. And don't force a judgement just to finish the meeting tidily. If a correction is disputed, it might reveal two different files both labelled "current."

There's no right meeting length. A stable routine service might need a short written review. A changing customer-facing service might need a proper conversation.

When something goes wrong, don't take the whole job back

When there's a problem, first protect the affected work. If a draft contains a serious error, stop it reaching the customer and check similar work.

But don't automatically remove every permission and redo every unrelated task.

Explain the gap using the agreed standard and the evidence. Ask what caused it. Separate:

• missing instructions,
• information they couldn't access,
• capacity pressure,
• a genuine skill gap.

The same visible mistake can come from any of those.

Agree a specific fix and a review point. If the issue is in one type of task, tighten checks there, not across the whole service.

Our guide to handling VA performance issues goes deeper. The principle: respond in proportion, and avoid swinging between total trust and total control after every mistake.

If problems keep happening despite clear requirements, good inputs and a fair chance to improve, discuss changing or ending the arrangement under your agreement. Vague ongoing dissatisfaction helps nobody.

Good performance attracts extra work, so watch for scope creep

When someone's good, you naturally give them more. Over months, they might be doing a completely different job from the one you originally agreed and priced.

Once a month, compare the current workload with the original agreement:

• What's been added?
• What's become more demanding?
• What's been removed?

New customer contact, more systems or bigger reviews might need different skills, access and fees. They're not minor just because each one started as a small favour.

Invite your VA to propose how they'd deliver the bigger service, including method, availability and price. That's a normal business conversation, not a lack of commitment.

If several people in your business send requests, name one person who resolves conflicts. Otherwise your VA gets two "authorised" instructions that can't both be done. Give them a neutral line to use:

"These requests overlap with the agreed delivery. Please confirm which takes priority and whether the other date changes."

Our guide to keeping a good VA explains how unpriced growth quietly drives good people away.

Five micromanagement habits to drop this week

You might be doing some of these without realising. Each one makes your VA slower and more dependent on you.

1. Rewriting acceptable work. If it meets the standard, let it go. Save your edits for errors and missed requirements.

2. Asking "any update?" instead of looking. If you've agreed where status lives, check there first. Constant chasing interrupts the work you're waiting for.

3. Answering in fragments. Three half-answers across a chat thread are harder to act on than one clear decision. Reply once, completely.

4. Changing priorities by message. If something new jumps the queue, say what moves to make room. Otherwise your VA is left guessing.

5. Approving late. If your review slot keeps slipping, your VA can't plan. Either protect the slot or name a backup who can approve.

Try dropping just one of these for a fortnight and watch what happens to the number of questions you get.

Measure results, not online status lights

Pick a small number of measures tied to what you're actually buying:

• correct, accepted work,
• timely handling of eligible tasks,
• meaningful exceptions raised.

These tell you far more than messages sent or tasks started.

But read the cases behind the numbers. A week of complex exceptions isn't comparable to a week of routine work. A rise in waiting time might be your slow approvals, not their slow work.

Keep monitoring proportionate. Constant screenshots or watching someone's online status look like oversight, but they don't tell you anything about quality or unfinished decisions.

Our VA KPI guide shows how to set useful measures without rewarding busywork.

Good management leaves ordinary choices with your VA, makes your own decisions quick, and updates the agreement when reality changes. You'll know exactly what's being delivered and where to step in, without teaching anyone that every reasonable choice needs your permission first.

Frequently asked questions

How often should I check in with my virtual assistant?

Match it to the risk and maturity of the work. A new or customer-facing service may need frequent short reviews. A stable routine service may only need a short weekly written review, plus a route for urgent issues.

How do I stop micromanaging my VA?

Separate errors from preferences, stop rewriting acceptable work, give clear decision boundaries, and judge results rather than online status. Reversing reasonable choices teaches your VA to ask permission for everything.

Why does my virtual assistant keep asking me questions?

Often because a rule is missing, a source is unclear, or past experience taught them that acting alone gets corrected. Look at what the questions are about and fix the cause, rather than counting them.

What should I do when my VA has too much work?

Ask them to flag capacity problems early with a suggested order. Then reduce scope, move deadlines or agree extra service. Don't make "yes to everything" the only safe answer.

Should I use time-tracking or screenshot software?

It usually adds little. Online status and screenshots show activity, not quality or unfinished decisions. Measure finished work, exceptions and delays instead.