How to Keep a Good Virtual Assistant When the Job Has Quietly Grown

Wondering how to keep a good virtual assistant? Start with a story you might recognise. Your assistant used to prepare customer reports.

Now they also chase missing figures, answer questions about the reports, remind you to approve them, and explain late deliveries to customers.

Their invoice still describes the original reporting service.

Nothing dramatic happened. You added small requests because this person was good. They said yes because they wanted to help.

Then a deadline slipped. A message sounded a bit strained. A rate review arrived that felt surprisingly big.

If you want to know how to keep a good virtual assistant, start here: look at what you're actually buying now, compared with what you agreed. A reliable independent provider can enjoy the work, respect you, and still become unhappy with an arrangement that has quietly changed shape.

A thank-you gift doesn't fix that. A clear, workable service does.

Here, a virtual assistant (VA) means an independent freelancer or agency providing a service, not an employee.

The job can change while the task name stays the same

Open the original proposal, scope or first invoice. Next to it, write what your VA actually did last month. Use real work and messages, not your sense of how busy things feel.

Look beyond volume. Notice these shifts:

• From clean inputs to messy ones. A report built from tidy data is different from one that needs chasing and interpretation.
• From batches to interruptions. A weekly batch is different from requests arriving all day.
• From drafting to representing you. Preparing a draft for your review is different from replying directly to your customers.

Each uses a different kind of capacity:

• More volume needs more time.
• More interruptions need reserved availability.
• More responsibility might need more expertise or authority.

A bigger fee doesn't automatically solve all three.

That explains something that confuses many business owners: a VA might turn down extra work even when you offer to pay more. They might have room for another planned batch, but not for unpredictable calls. Their other clients may already fill the hours you now need.

Ask what's become difficult, not "are you happy?"

"Are you happy?" is easy to answer politely with "yes, all good!"

A more useful question:

"Which requests have become harder to fit around our agreed service, and what's taking unnecessary effort?"

Send the topic in advance. Say you're reviewing the scope because the business has changed, not raising a complaint. Give them time to gather examples.

Ask specifically about delays you cause:

• Do approvals arrive after the agreed window?
• Does a colleague send requests directly, skipping the priority list?
• Do source files change after work starts, creating unpaid rework?

Don't ask about their other clients. You need to know what availability they can offer you, not their private business.

Write down specific friction and its consequence. "Late source changes mean the same report gets built twice" is something you can fix. "We should communicate better" lets everyone nod and change nothing.

End by asking:

• Which work do they want to keep?
• Which would they like to stop?
• Is there a service they'd like to develop?

Treat answers as proposals, not obligations. Retention doesn't mean promising a future you can't provide.

Invisible coordination is the hidden reason good VAs burn out

Make a simple map for each deliverable:

• What needs to arrive?
• Who supplies it?
• Who prepares the result?
• Who approves it?
• Who answers questions afterwards?

Include waiting and chasing, even if it's not on the invoice.

You're looking for work that got an owner by accident. If every missing input automatically becomes your VA's problem, they may now be coordinating people, not preparing documents. That's valuable work, but it's a different service.

Here's a revealing test:

"What would stop happening if my VA followed the original agreement exactly?"

If reports would wait forever for your figures, your VA is now managing dependencies. Name it before discussing whether the fee is fair.

Watch for responsibility without authority too. If your VA is held responsible for customer deadlines but can't get your approval in time, good work becomes exhausting. Success depends on repeated nagging, not a workable agreement.

Give each dependency a response time or a fallback:

"If I miss the approval window, delivery moves to the next slot, or my named backup decides."

Don't expect your VA to absorb every delay by working extra hours.

A worked example: when more money wasn't the fix

Here's a hypothetical example.

A small property consultancy buys monthly report preparation from an independent VA. The original service: build reports from approved figures the owner supplies, check the layout, return drafts for sign-off.

As the business grows, several associates start sending figures directly. Different formats. Missed deadlines. The VA starts reconciling conflicting versions, chasing associates, and answering clients asking when their reports will arrive.

The owner, wanting to keep this excellent VA, offers a higher monthly fee.

The VA appreciates it, but says the arrangement is becoming difficult. The owner hears this as reluctance to grow with the business.

Then they look at the task records together. The real issue:

• The VA can reserve a planned block for building reports.
• They can't promise constant availability for questions from every associate.
• They don't have authority to decide which conflicting figure is correct.

So they redesign the service:

• The consultancy supplies one approved input file by a set cut-off.
• The VA flags discrepancies in a shared register.
• The VA builds reports from approved data and returns a batch for review.
• The owner appoints one associate to resolve input conflicts.

The extra coordination work becomes a separate, optional service with its own hours and limits. The VA can choose whether to take it.

The new fee reflects the revised report work. But the bigger fix is removing the unlimited responsibility for other people's inputs.

Early warning signs a good VA is starting to struggle

People rarely announce they're unhappy. They show it in small ways first. Watch for:

• Replies getting shorter or more formal than usual.
• More "just checking" questions about things they used to handle on their own.
• Deadlines slipping on work that used to be routine.
• Work arriving at odd hours, suggesting they're squeezing you in around other commitments.
• A rate review out of nowhere, which is often a polite way of saying "the job has grown."

None of these proves anything on its own. But they're a good prompt to have the "what's become difficult?" conversation before resentment builds, rather than after a resignation email arrives.

And when you have that conversation, listen for the specific friction. It's usually something you can fix far more cheaply than replacing someone who already knows your business.

Negotiate the shape of the service, not just the price

Before talking money, decide what you genuinely need:

• More output?
• Faster turnaround?
• Specialist judgement?
• A predictable window when someone responds?

These are different purchases, even if one person could provide all of them.

Invite your VA to quote against that need. They might suggest a project fee, a recurring package or hourly with a cap. Compare what's included, what happens to unused time, and how extra work is approved.

Don't assume a monthly fee makes every urgent request included. Some providers write this down explicitly. Virtual Assist USA's published agreement, for example, makes services subject to acceptance and availability, with separate rush provisions. That's one provider's terms, not a standard to copy, but it shows the principle.

If you're proposing a higher fee, explain the basis plainly: the work has grown, or the deliverable is more demanding. You don't need to dress it up as a loyalty reward.

If their price is more than you can afford, say what budget you can sustain and ask what scope fits it. Dropping low-value reports or reducing frequency can keep the valuable part of the relationship without asking someone to subsidise your growth.

And don't just compare their fee with a cheaper advertised rate somewhere else. Include the context they already understand, the quality of their work, and how much of your time a replacement would need. Our VA ROI guide helps you compare fairly.

Paying on time beats any thank-you gift

A thank-you gift doesn't make up for invoices that need chasing.

Check your basic payment routine:

• Where do invoices arrive?
• Who checks them?
• What information is needed?
• When are they paid?

Give your VA a clear route if a payment's missing. If you question one line on an invoice, raise it promptly and pay the undisputed part. Don't leave the whole invoice sitting because of one query.

For UK transactions, GOV.UK's guidance on payment obligations explains payment terms in that context. It's not a universal rule for every cross-border arrangement, so check your actual terms.

Reliability also means decisions. If your VA needs your approval to finish work, keep a realistic review window, and name a backup for when you're away. Missing your part repeatedly forces them to carry unfinished work into time already promised to others.

Use one channel for new requests. A casual message from a colleague shouldn't silently become a new commitment. Ask your VA to route extra requests into an agreed queue so you can accept, decline or renegotiate visibly.

In the consultancy example, the owner reviews the discrepancy register before the cut-off. If figures are still disputed, that report waits rather than being rushed through on a guess. The VA can plan because the client now honours their side of the deal.

Offer growth, without disguising extra work as "development"

Some VAs want more responsibility. Others want to become excellent at one stable service. Neither is a lack of ambition. Ask rather than assume.

If your VA suggests a new service, try it as a defined project:

• what they'll deliver,
• what context you'll provide,
• the fee,
• how you'll judge it.

Keep existing work visible so the experiment doesn't eat time already committed.

Teaching someone your company's way of doing things is normal. Expecting a general assistant to become your tax adviser because you bought them a course isn't.

A qualified VA might already have skills you're not using. Ask for evidence and run a trial, rather than assuming based on their title.

And agree who pays for any optional training or tools, and who keeps access afterwards. Don't surprise anyone with a repayment demand that was never discussed.

If the only real result of "development" is more work at the old fee, you've just renamed scope creep.

Build backup openly, as protection, not a threat

Even a great relationship can end. Your VA might change direction, become unavailable, or decide your new needs no longer fit their business.

So keeping someone and planning for continuity go together.

Start simple:

• Keep current files, procedures and open cases somewhere your business controls.
• Talk openly about backup: which work must continue during an absence, and which can wait.
• Ask whether they offer cover, whether an agency handles it, or whether you'll arrange it separately.
• Check any backup person is allowed under your contract and data rules before sharing customer information.

In the property example, a backup gets a cleaned-up sample report and the instructions first, and practises with made-up figures. Only after that would real work be considered.

Done well, this actually helps retention. Nobody enjoys feeling that the business falls apart whenever they take a day off. Our offboarding checklist covers continuity in detail.

Keep their independence visible in how you work together

You're buying a service from an independent provider. Agree outputs, fees, availability and communication. Don't treat the relationship as permission to control their whole working life.

You can still set quality standards, protect customer information and agree service hours. Those just belong in a workable agreement, not in assumed authority that keeps expanding.

Legal status depends on more than wording. GOV.UK's guidance on contractors explains that tax and employment status can differ. If your actual working practices raise questions, get advice. Our contractor or employee guide explains what to prepare.

For agency arrangements, discuss scope and fees with the agency. Don't make private promises to the individual that conflict with the agency agreement.

Clear boundaries can actually strengthen the relationship. When a request is outside the agreed service, a "no" isn't personal. It's just outside the service.

Turn the conversation into an updated agreement

Write a short service review note while the conversation's fresh:

VA SERVICE REVIEW

Original scope (link):

What's changed (with examples):

My VA's concerns:

What I need now (volume / speed / judgement / availability):

Revised scope:

What I must supply, and by when:

What's excluded:

How extra work is requested and approved:

Availability reserved:

Revised fee and start date:

Backup and continuity plan:

Next review date:

Confirm the revised scope and fee through whatever your contract requires before it starts.

At the next review, check whether the friction actually reduced. Were the files ready on time? Are conflicting requests still arriving? Does the fee match the work?

If your VA still decides to leave, respect it and use the agreed handover. You can offer a revised service they might prefer, but you can't guarantee anyone stays through the right mix of praise and money. Sometimes a business grows in a direction a provider doesn't want to follow.

Keeping a good VA is much easier when staying is a sensible business decision for them. That starts with a service they can deliver well, a client who keeps their own promises, and an easy way to renegotiate before small favours become the whole job.

For more, see how to manage a virtual assistant and how to build a VA team.

Frequently asked questions

Why do good virtual assistants leave?

Often because the arrangement has quietly changed: more responsibility without authority, unpaid coordination, constant interruptions or late payments. Many like the client but find the service no longer works for their business.

Should I give my virtual assistant a raise?

If the recurring work has grown or become more demanding, yes, discuss a revised fee. But fix the shape of the service too. A higher fee alone rarely fixes unlimited responsibility.

How do I stop scope creep with my VA?

Compare the original agreement with what they actually did last month, route new requests through one agreed queue, and quote genuinely new services separately.

Is it bad to have a backup for my VA?

No. Discussed openly, backup protects the service and the VA, who no longer has to feel the business collapses if they take a day off.

Do bonuses and gifts help keep a virtual assistant?

Recognition is nice, but it can't fix a service that's become unworkable. Reliable payment, clear scope and quick decisions usually matter far more.