Home  →  Guides

What to Delegate to a Virtual Assistant First: The Delegation Playbook

Most founders do not fail at delegation because they hand over too little. They fail because they hand over the wrong things first. They give a brand new VA the one task that needs their judgement, watch it come back wrong, conclude that delegation does not work, and go back to doing everything themselves at 10pm. The VA was not the problem. The order was.

This playbook fixes the order. It covers what to hand over in the first two weeks, what to hold back until trust is earned, and how to hand work over so it comes back right the first time. If you have never delegated before, start at the top and work down. If you have tried before and it went badly, the section on what not to hand over first is probably where your last attempt went wrong.

The test before you hand anything over

Before a task goes to your VA, run it through three questions.

First, does it repeat? A task you do every day or every week is worth teaching once, because the teaching pays for itself. A task you do once a year is not. Teach the repeatable work first.

Second, does it have a right answer you can show? If you can point at a finished example and say "like this", a VA can learn it fast. If the right answer lives only in your head and depends on a feeling about a client, it is not ready to delegate yet. Write the example first, then delegate.

Third, what breaks if it goes wrong? A misfiled document is fixable. A wrong reply to your biggest client is not. Start with work where a mistake is cheap and visible, so your VA can learn and you can check without anxiety. Move up the stakes as the track record grows.

Tasks that pass all three tests go first. Tasks that fail the third test wait, no matter how much time they eat.

The first five things to hand over

These five categories are the standard first handover for a reason. They are repeatable, they have clear examples, mistakes are cheap, and together they can return ten or more hours a week to a founder.

1. Inbox triage and calendar

Start here, because this is where most founders bleed time without noticing. Inbox triage does not mean your VA answers everything. It means they sort it: urgent client mail flagged, newsletters and notifications filed, routine questions drafted for your approval, and anything needing your judgement left at the top with a one line summary.

Calendar work follows the same pattern. Your VA books meetings, sends confirmations, reschedules politely, and guards your focus time. Give them the rules up front: which meetings you accept, how much buffer you want between calls, and what never gets booked over. A VA with clear calendar rules will protect your week better than you do, because they are not the one tempted to say yes to everything.

2. Admin, data entry and filing

Expense receipts, CRM updates, contact lists, document filing, order tracking. This work is the definition of repeatable, and it is where a founder's hour is most wasted. It also teaches your VA your tools and your standards while nothing risky is at stake.

The trick is to hand over the system, not just the task. Show them where things live, how you name files, and what "done" looks like. A VA who files one invoice perfectly and one invoice sloppily has not been taught a standard. They have been given a chore. Spend twenty minutes on the standard and you will never file an invoice again.

3. Research and booking

Competitor research, supplier comparisons, travel options, venue shortlists, lead list building. Research is a perfect early delegation because the output is a document you can review in minutes, and a bad draft costs you nothing but a correction.

Give a research brief with four parts: the question, the sources you trust, the format you want, and the deadline. "Find me three options" is a bad brief. "Find three venues within twenty minutes of the office, under this budget, with parking, in a table with price, capacity and a link, by Thursday" is a brief a VA can nail. The quality of what comes back is almost always a mirror of the quality of the brief that went out.

4. Follow-ups and routine client operations

Chasing unpaid invoices politely, confirming appointments, sending onboarding documents, following up a quote that went quiet. This is the work founders mean to do and then forget, and forgotten follow-ups are lost revenue sitting in plain sight.

This category needs one guardrail: templates. Your VA should work from your approved wording for routine follow-ups, and escalate anything unusual to you instead of improvising. A template plus an escalation rule lets a VA chase money and appointments on your behalf without ever freelancing on your tone. If you are still deciding whether you need a VA at all, our guide to the signs you need a virtual assistant describes exactly this pattern: the work that slips is usually the work nobody owns.

5. Content and social support

Drafting posts from your notes, scheduling approved content, formatting a newsletter, clipping a long video into short posts. Content support is ideal second week work, once your VA has learned your voice from your inbox and your documents.

Note the word drafting. Your VA prepares, you approve, at least at first. The founders who hand a new VA their social accounts with no approval step are the ones who wake up to a post they would never have written. Approval in week two is training, not micromanagement. Drop it when drafts stop needing corrections.

What not to hand over first

Just as important as the list above is the list below. Hold these back until your VA has a track record, and in some cases keep them yourself permanently.

Do not hand over anything that moves money without a control: bank access, card details, payment approvals, refunds. A VA can prepare invoices and chase payments long before they should approve them. Access follows trust, and trust follows months, not days.

Do not hand over client negotiations, pricing decisions, or difficult conversations. A VA can brief you for a negotiation and draft your follow-up. They should not be the one deciding what to concede, because they do not carry the relationship or the context behind it.

Do not hand over hiring, firing, or performance conversations about other team members. Do not hand over passwords to your core accounts in week one. Share access through a password manager with individual logins where possible, and revoke what is not needed. And do not hand over strategy: which markets to enter, which clients to drop, what to build next. Your VA can research a strategy. They cannot set it for you, and asking them to is how founders end up executing someone else's guess.

If you are hiring your first VA, read how to hire a virtual assistant before you write the job post. The brief you write there decides whether the handover below works, because a VA hired for the wrong job will be handed the wrong work no matter how good the playbook is.

How to hand work over so it comes back right

Delegation fails most often in the handover, not in the person. A good handover has five parts and takes about fifteen minutes per task the first time.

First, the outcome. Say what done looks like in one sentence. "Every invoice filed in the finance folder by Friday" beats "sort out the invoices".

Second, an example. Show a finished version: a VA who has seen one will reproduce it.

Third, the constraints. Budget, deadline, tools, tone, and what they must not do. Constraints are what keep a capable VA from solving the wrong problem brilliantly.

Fourth, the check. Tell them when you will review it and how. "Send me the draft before you post it" is a check. Silence for a week followed by a frustrated correction is not a check. It is an ambush.

Fifth, the escalation rule. Tell them what to do when they are stuck: who to ask, what to try first, and when to stop and bring it to you. The best VAs are not the ones who never get stuck. They are the ones who escalate early instead of guessing quietly.

Record the handover once, in writing, even if you also explain it on a call. A short screen recording plus a written checklist becomes a standard operating procedure your next hire can use too. Founders who document as they delegate end up with a business that can grow.

The 30 day ramp

Week one is shadowing and small tasks. Your VA watches how you handle the inbox, learns the tools, and takes on admin and filing with daily checks. Expect questions: they are a good sign, while silence usually means guessing.

Week two is ownership with review. Your VA owns inbox triage, calendar, research and follow-ups, and sends you a short end of day summary: what was done, what is waiting on you, what needs a decision. Review the summary, correct the standard once, and move on. Do not re-do the work yourself. Correcting the standard is management. Re-doing the work is just doing the work twice.

Week three is ownership with lighter review. The end of day summary continues, but you stop checking every item and start checking by exception. This is also the week to add one category up the stakes ladder, such as drafting client replies or preparing a report, with approval still in place.

Week four is the review that matters. Sit down and ask three questions: what is off your plate, what still comes back wrong, and what should your VA own next? Most founders discover at this review that the VA is ready for more than they expected, because the first month was spent on cheap mistakes instead of expensive ones. That is the point of the ramp. It is also the moment to write down the next month's handover list, so delegation keeps compounding instead of stalling at admin.

If your last VA arrangement fell apart, there is a good chance it skipped this ramp entirely. Our post-mortem on why virtual assistants do not work out names the pattern: everything handed over on day one, no standard, no check, and a quiet conclusion that delegation does not work. The ramp exists to prevent exactly that story.

The three mistakes that undo a good handover

The first mistake is dumping everything on day one. A new VA handed twenty tasks learns none of them properly and the founder concludes they hired badly. Five tasks learned well beat twenty tasks learned badly, and the five grow into twenty within a month if the ramp holds.

The second mistake is the vague brief. "Handle my emails" is not a brief. Neither is "do some research". Every vague brief produces a result the founder did not want, and the founder blames the VA for a failure that was written into the instruction. If the result disappoints you, read your own brief before you judge their work.

The third mistake is delegating and then re-doing. Founders who check a VA's work by redoing it themselves teach the VA that quality does not matter, because someone else will fix it. It also means the founder saved no time at all. Check, correct the standard, and let the next one come back right.

Hire for judgement, not just typing speed. Our guide to virtual assistant interview questions includes a trial task template, and the trial task is the fastest way to test the exact skill this playbook depends on: can this person take a brief, follow a standard, and escalate instead of guessing? Run the trial task on a real first week task from the list above, and you will know before you hire whether the handover will work.

What good delegation feels like

Good delegation does not feel like giving orders. It feels like your week getting quieter in a specific way. The inbox stops being the first thing you dread. Appointments confirm themselves. Follow-ups happen without you remembering them. Friday arrives and the admin is done, not waiting.

It also changes what your time is worth: an hour once spent filing becomes an hour for a client, a hire, or a decision only you can make. Our pricing is straightforward: Essentials at $899 a month for 20 hours a week, Executive at $1,599 a month full time, and AI Manager at $2,599 a month for a full time, AI fluent assistant. If you are unsure which hours fit your list, our guide to part-time vs full-time virtual assistants walks through the decision. The question is what your recovered hours are worth, and whether they are currently being spent on work someone else could do to your standard.

If you want one dedicated person who learns your business instead of a rotating pool, read our dedicated virtual assistant page. One person, your standards, your ramp. That continuity is what turns a first handover into a working delegation habit, and a habit into the extra hours that built the business in the first place.

Frequently asked questions

What is the very first task I should delegate to a virtual assistant?

Inbox triage, with approval on replies. It is repeatable, it has clear examples, mistakes are cheap, and it immediately shows you how your VA works: how they prioritise, how they write, and whether they escalate or guess. If inbox triage goes well in week one, the rest of the handover will go well too.

How much time should I spend training my VA in week one?

Plan on an hour or two a day in week one, mostly in short check-ins rather than one long session. Fifteen minutes per task for the handover, plus a short end of day review. That time falls fast. By week three you should be spending minutes, not hours, on review. If you are still spending hours in week four, the briefs or the standards need fixing, not the VA.

Should my VA reply to clients directly?

Not in week one. Start with drafts you approve, then move to approved templates for routine replies, then to direct replies for a defined set of routine situations, with an escalation rule for anything unusual. Direct client contact is earned by a track record of good drafts, not granted on day one.

What if my VA does a task differently from how I would do it?

Ask whether the outcome is right before you correct the method. Different is not wrong, and a VA who finds a faster way to the same result is an asset. Correct the method only when it affects quality, risk, or how a client experiences your business. Correcting everything to match your habits exactly is how founders end up doing the work twice.

How do I know if I am delegating too much or too little?

Too little looks like a VA with empty hours and a founder still doing admin at night. Too much looks like errors on work the VA was never trained for, or a VA who has stopped asking questions because they are overwhelmed. The fix for both is the same: go back to the ramp, one category at a time, with a written standard for each.

What should I never delegate to a virtual assistant?

Bank access and payment approvals without controls, pricing and negotiation decisions, hiring and firing, and strategy. A VA can prepare, research, draft and chase around all of these. The decision itself stays with you. That boundary protects both of you: you keep control of what matters, and your VA is never put in a position where a mistake could damage the business.

Start with one task this week

You do not need to delegate your whole business to get the benefit. Pick one task from the first five, write the outcome in one sentence, find one finished example, and hand it over with a check time. One task, done properly, teaches you more about delegation than a month of thinking about it.

Then add the next one, and the next. That is how founders end up with a week that looks nothing like the one they have now: not because they hired a miracle, but because they handed work over in the right order, with a standard, a check, and a ramp. The playbook is simple. The discipline of following it is the whole job.