Home  →  Guides

How to Manage a Virtual Assistant: The Weekly System After Onboarding

Most advice about virtual assistants stops at the hire, or at the first week. That makes sense, because those are the moments that feel risky. But most of the value of a good VA shows up later, in months two through twelve, and most of the slow failures happen there too. Nobody quits dramatically. The work just plateaus. The VA keeps doing the same five tasks, you keep doing the same twenty, and a year later you are paying for help that never grew past where it was in week three.

I run Virtual Assistant Capital, and the placements that work long term have something in common. It is rarely that the founder found a unicorn. It is that the founder settled into a simple, repeatable way of managing the person, and stuck to it once things felt fine.

This guide is that system. It assumes the VA is already hired and through their first week. If you are not there yet, start with how to onboard a virtual assistant and the delegation playbook, which cover the first handovers. Everything below is about what comes after: the weekly rhythm, how to measure the work, how to give feedback across a screen, how to grow the role, and how to tell when it is not working.

Managing a VA is not supervising a VA

The most common mistake I see after onboarding goes in one of two directions.

Some founders over-manage. They check every email the VA sends, ask for status updates three times a day, and keep every decision for themselves. The VA becomes a slower version of the founder's own hands.

Other founders under-manage. Once the VA is "up and running," they stop looking. No reviews, no feedback, no new responsibilities. Quality drifts without anyone noticing, small misunderstandings harden into habits, and six months later the founder concludes that VAs "just don't take initiative."

Management sits between those two. You are not watching the work as it happens. You are setting clear outcomes, checking them on a fixed rhythm, and moving decisions to the VA as fast as their track record allows. That is the whole job, and it takes far less time than either extreme once the rhythm exists.

The weekly rhythm

A remote VA cannot read your mood from across the room, so the rhythm does the work that proximity does in an office. Three touchpoints are enough for most roles.

The daily end-of-day note

This habit should already exist from week one. Keep it. A short written message at the end of the VA's day:

• What got done.
• What is waiting on you, with a clear ask.
• Anything unusual they noticed.
• What is planned for tomorrow.

Five minutes for them to write, two minutes for you to read. The "waiting on you" line is the important one. It turns the note from a report into a queue of decisions, and it stops the VA sitting idle because they did not want to bother you.

If the notes start getting longer and longer, that usually means the VA is unsure what matters. Ask them to keep it to the four lines above and to flag only exceptions.

The weekly 30-minute call

Once a week, on the same day and time, a short call. This call has a fixed agenda:

1. What went well this week. Name one specific thing. It costs nothing and it tells the VA what good looks like.
2. What went wrong or got stuck. Problems, near misses, anything that bounced back. No blame, just cause and fix.
3. One process change. One SOP to update, one step to remove, one tool setting to change. One, not five.
4. What moves next week. Any task or decision that moves from "draft for approval" to "handle alone," or any new task that gets handed over.

Thirty minutes is enough. If the call keeps running long, the daily notes are not doing their job, or too much is being saved up for the call.

Put the call in the overlap of your working hours. Protect that slot. The weekly call is the first thing founders cancel when they get busy, and it is the last thing they should cancel.

The monthly review

Once a month, take the weekly call a little further, or book 45 minutes instead. Look back over the month, not just the week:

• Which tasks are now fully handled without your input?
• Which ones still come back to you, and why?
• What did the VA do this month that you would have done yourself last month?
• What is the next block of work to hand over?
• Is there anything the VA wants to learn or take on?

That last question matters more than it looks. VAs who see a path tend to stay. VAs doing the same thing in month nine as in month one tend to drift, or leave, or both.

What to measure, and what not to

A lot of VA management advice is really about time tracking: screenshots, activity monitors, hours logged per task. I understand the instinct. You cannot see the person, so you want proof they are working. But hours are the wrong thing to manage.

If you pay for a set number of hours a week, hours are what the arrangement guarantees. What you actually care about is whether the work is getting done, at the quality you need, without you. So measure that.

For each recurring responsibility, write one line that describes the outcome, and one or two simple checks. Some examples:

• Inbox: Every email that needs you is flagged by end of day. Nothing older than one working day sits unanswered without a reason.
• Calendar: No double bookings. Every external meeting has an agenda or a note on what it is about.
• Invoices and payments chasing: Every overdue invoice has had a follow-up within the agreed number of days, logged in the system.
• CRM: Every call or meeting has notes and a next step within 24 hours.
• Reports: The weekly report arrives on the agreed day, in the agreed format, with no figures you have to correct.

These are not formal KPIs and they do not need a dashboard. They need to be written down somewhere you both can see, and checked at the weekly call. When something slips, you are talking about the outcome ("three invoices were not chased this week, what happened?") rather than the person ("you seem slow lately").

The one time I would look at hours is when a task is taking far longer than you expected. That is usually a process problem, not an effort problem: a tool that is slow, a step that is not needed, or a decision the VA keeps waiting on. Ask about it as a process question.

Feedback across a screen

Feedback is harder remotely, because there is no hallway conversation to soften it and no tone of voice in a written message. A few habits make a large difference.

Make it specific. "This client reply is good, but for this account I always confirm the delivery date in the first line" is useful. "Can you be a bit more careful with client emails?" is not, because the VA has no idea what to change.

Make it fast. Feedback given the same day, on the actual piece of work, changes behaviour. Feedback saved up for a monthly review mostly creates anxiety.

Separate the fix from the judgment. Most mistakes in the first few months are missing context, not missing ability. Treat them that way. Fix the SOP or the escalation rule, and say so: "That one is on me, the rule did not cover it. I have added it."

Use a short video for anything complicated. A two-minute screen recording that shows what you wanted, with your reasoning spoken out loud, is clearer than a long written message and much easier to receive.

Say the good things out loud. Founders are often generous with corrections and silent about wins. A VA who only ever hears about mistakes learns to stop taking initiative. When they catch something, handle an exception well, or improve a process, tell them, specifically.

Ask for their feedback too. At the monthly review, ask what is slowing them down. The answers are often things like "I wait half a day for approvals" or "the shared drive is a mess." Those are management problems, and fixing them speeds up everything else.

Growing the role: how decisions move to the VA

During onboarding, you probably split decisions into three buckets: things the VA handles alone, things they draft for your approval, and things that always come to you first. Managing the VA well over time is mostly the steady movement of work from the second bucket into the first.

Here is a simple rule that works. When the VA has drafted a type of reply or decision several times in a row and you have approved it without changes, move it into "handle alone." Tell them explicitly, and update the written rules. Do not just stop reviewing and hope they notice.

Some things should stay with you much longer, sometimes permanently: anything that moves money, commits you to a price or a date, responds to a complaint or legal matter, or touches a relationship that is important to you. That is not about trust in the person. It is about where the decision belongs.

As work moves, access may need to move with it. Grow access with the responsibilities, not ahead of them, and keep a written list of what has been granted. Our VA security and NDA guide covers the practical side of this, including password managers and keeping payments behind your approval.

Keeping SOPs alive

In week one, the VA probably drafted SOPs from your recordings. That is the right start. The risk after that is that the SOPs freeze while the work changes around them, until nobody trusts the documents and everything lives in the VA's head.

Make the VA the owner of the SOPs, so the knowledge lives in your business rather than in one person's memory. When a process changes, they update the document the same week. When you correct something, part of the fix is the SOP change. At the monthly review, glance at the list and ask which ones are out of date.

Managing across time zones and holidays

Most VA relationships cross at least some distance, and a few practical rules prevent a lot of friction.

Agree a reply window, both ways. For example: urgent items get a reply within an hour during overlap hours, everything else by the start of the next working day. Write it down. A lot of tension comes from mismatched expectations about speed rather than actual slowness.

Batch your approvals. If the VA's day ends before yours begins, a decision you make at your lunchtime does not get acted on until tomorrow. Clear the "waiting on you" list from the daily note at a fixed point in your day, ideally before the VA's next shift starts.

Plan for public holidays early. Your VA's public holidays may not match yours. Ask for the list at the start of the year, and agree how cover works for anything time-sensitive. Surprises here are avoidable.

When it is not working

Sometimes, even with a good rhythm, a placement stalls. Before deciding it is the person, run through a short check on the system.

• Are the outcomes for each responsibility written down, or only in your head?
• Has the weekly call happened every week for the last month?
• Is feedback specific and same-day, or occasional and general?
• Are the escalation rules current, or do they still reflect week one?
• Is the VA waiting on you for things that could be decided without you?

If most of those answers are "no," fix the system first and give it a few weeks. In my experience, that resolves more problems than replacing the person. If you want a fuller list of the patterns that cause placements to fail, I wrote about them in why virtual assistants don't work out.

If the system is in place and the same problems keep coming back, it may genuinely be a fit problem. That is not a failure on either side. It is a mismatch, and it is better to say so early than to drag it out.

How we support this at Virtual Assistant Capital

When we place a VA, we work with you on the first three tasks, the escalation rules and the communication rhythm, because those are the foundation for everything in this guide. After that, the day-to-day management belongs to you, since you know your business and your clients. We stay in the background for the things that are harder to handle alone: if the fit is not right within 30 days, we replace your VA at no cost, and the documented processes carry over to the new person.

Our plans are month-to-month. Essentials is $899 a month for 20 hours a week, Executive is $1,599 a month for a full-time VA, and AI Manager is $2,599 a month for a full-time VA who is fluent with AI tools. There is a $0 recruitment fee, you get a free shortlist of 2-3 vetted VAs within 72 hours, and you pay only once your VA starts. The details are on our pricing page.

FAQ

How much time does it take to manage a virtual assistant? After the first few weeks, most of it is reading a short daily note, a 30-minute weekly call, and a slightly longer monthly review. Expect more time in the first month while processes settle, then less as decisions move to the VA. If it keeps taking more time, look at approvals that could be handed over.

Should I use time tracking or screenshot software for my VA? You can, but it measures the wrong thing. Write down the outcome you expect for each responsibility and check those outcomes at the weekly call. Look at hours only when a task takes far longer than it should, and treat that as a process question rather than an effort question.

How do I give a remote VA feedback without it feeling harsh? Make it specific, give it the same day, and attach it to a real piece of work. Fix the SOP or rule when the mistake came from missing context, and say so. A short screen recording is often clearer and kinder than a long written message. Mention the good work as specifically as the mistakes.

How often should I meet with my virtual assistant? A daily written end-of-day note, a 30-minute call once a week at a fixed time, and a longer monthly review is enough for most roles. The daily note handles status, so the weekly call can focus on problems, process changes and what moves to the VA next.

When should I give my VA more responsibility? When they have drafted the same type of decision several times and you have approved it without changes, move it to "handle alone," tell them explicitly and update the written rules. Keep anything that moves money, commits to prices or dates, or handles complaints with you for longer.

What if my VA still is not working out after a couple of months? Check the system first: written outcomes, a weekly call that actually happens, specific feedback and current escalation rules. If those are in place and the same problems repeat, it may be a fit problem. With Virtual Assistant Capital, we replace a VA at no cost if the fit is not right within 30 days.

The short version

Managing a virtual assistant after onboarding comes down to a simple rhythm and the discipline to keep it once things feel fine. Ask for a short daily note with a clear "waiting on you" line. Hold a 30-minute weekly call with a fixed agenda: one win, one problem, one process change, and what moves next. Do a monthly review that looks at what the VA now handles alone and what comes next. Measure outcomes, not hours. Give feedback that is specific, fast and fair. Move decisions to the VA as their track record earns it, and grow access with the work. Keep the SOPs owned by the VA and up to date. Do that, and the role keeps growing instead of stalling at week three.