Here's the catch with every list of tasks to outsource to a virtual assistant: the task you most want to hand over is often the one you understand least.
It's been on your list for weeks. It feels heavy. You'd happily pay someone to make it disappear.
Then you try to explain it to someone, and you realise you've never actually decided what "done" looks like.
That's why lists of tasks to outsource to a virtual assistant are only half useful. They're great for jogging your memory. But a task appearing on a list doesn't make it the right one to start with in your business.
This guide gives you both. First, the common list, so you can see what's possible. Then a simple one-week method for choosing which task should go first, so your first handover actually works and actually comes off your plate.
Here, a virtual assistant (VA) means an independent freelancer or agency you outsource work to, not an employee.
The usual list (useful, but only as a starting point)
Here are tasks small businesses commonly outsource to VAs. Use it to jog your memory, not as a shopping list.
Admin and inbox - Sorting and labelling incoming email - Replying to routine enquiries from templates - Filing documents and attachments - Keeping contact details up to date
Scheduling - Booking and rescheduling appointments - Sending reminders and joining details - Preparing agendas and meeting packs
Customer support - Answering common questions - Checking order status - Logging issues and following them up
Finance admin - Collecting receipts and invoices - Preparing draft invoices for approval - Chasing missing paperwork
Research and data - Supplier and competitor research - Lead lists and CRM updates - Data entry and spreadsheet clean-up
Marketing support - Scheduling approved social posts - Resizing images and formatting content - Uploading product listings
Pretty much any of these can work. The problem is that "pretty much any" doesn't tell you where to start.
Why "handle my inbox" is a terrible first task
"Handle my inbox" sounds like one job. It's actually dozens.
Inside your inbox are newsletters, supplier questions, customer complaints, invoices, meeting requests and decisions only you can make right now. Treating all of them the same makes the job look far simpler than it is.
The same goes for "admin," "marketing" or "social media." These are categories, not tasks.
A good first task is small enough that both of you can tell exactly when it's finished. That's what the rest of this guide helps you find.
Spend one week as a detective in your own business
Open a simple spreadsheet or notebook. For one normal working week, record the non-core work as you do it.
For each item, note:
- What triggered it. A customer order, a supplier email, a meeting.
- Active minutes spent. Just the doing, not the waiting.
- The result. What finished looked like.
- Anything that stopped you.
Be specific. Not "email, 45 minutes." Instead: "asked a client for a missing purchase order, 8 minutes."
That tiny difference matters. The first entry tells you nothing. The second tells you the trigger, the action and a likely repeatable need.
Keep waiting separate from working. If a supplier takes two days to reply, that's not two days of your labour. Note the wait separately, because it still affects deadlines.
At the end of the week, scan your calendar and sent folder for anything you forgot to log. Add monthly or seasonal jobs too, with how often they really happen.
Don't take an unusually busy week and multiply it into a permanent job. Use a normal week as your guide.
Ask why each task exists before paying someone to keep it alive
Here's a step almost everyone skips.
For every entry in your diary, finish this sentence:
"This needed doing because..."
"A customer placed an order" is a real reason. "I felt I should check" might just be a habit.
Then ask who actually uses the result. If you produce a weekly report that nobody reads, don't outsource it. Stop doing it, or do it less often.
Paying someone to maintain pointless work makes your diary lighter but your business no simpler.
Be careful with this, though. Don't silently stop anything that's a contractual, legal or customer commitment. If you're not sure why something exists, find out first.
Now give every entry one label:
- Keep (stays with you)
- Remove (stop doing it)
- Simplify (do it a cheaper way)
- Automate (a simple app connection could do it)
- Delegate (a VA could do it)
- Investigate (you're not sure yet)
"Investigate" is fine as a temporary label. Just give it a question and a deadline so it doesn't become a forever pile.
Turn every vague task into one with a visible finish line
For each task marked "delegate," write the finish line as a result, plus the proof.
- "Research suppliers" becomes: "a comparison of suppliers meeting these requirements, with source links and a list of unanswered questions."
- "Organise documents" becomes: "every current project has the required files in its named folder, with missing files listed."
Avoid making the finish line a number of actions when you actually need an outcome. Twenty follow-up emails don't tell you if the missing information arrived.
This step also shows you where a task needs specialist skills. A VA can collect supplier specs against your brief. Deciding which safety certificate is legally enough for your product might need someone qualified.
That's not a reason to avoid delegating. It's a reason to know exactly what you're delegating.
Throw out the dangerous candidates before comparing time saved
Some tasks eat hours but are still a bad first handover, because a mistake could hurt.
Changing payment details. Deleting customer records. Publishing claims you haven't approved.
For these, the safe first version is often preparation, not action. Your VA prepares the change, you approve it. That still takes a big chunk of work off your plate.
Check what access the task would need, too. Some permissions are broader than they sound:
- Google Drive's sharing settings separate view, comment and edit access, and access given to a folder usually flows down to everything inside it. A "private" document inside a widely shared folder may not be private.
- Google Calendar sharing can show just free or busy time, full event details, or allow changes. If the job is suggesting meeting times, it may not need permission to change your whole calendar.
Treat safety as a veto, not just one score among many. A risky task doesn't become acceptable because it's frequent, boring and quick to explain.
Score what's left on four simple questions
For the tasks that survive, ask four questions. No complicated formula needed.
1. Does it repeat soon? A task that comes up daily gives your VA lots of practice and you quick feedback. A once-a-year task gives you very little.
2. Is it clear enough? You don't need perfect documentation. But can you show a finished example and explain the main exceptions?
3. How hard is it to check? Checking a document has the right client name is quick. Checking a research recommendation might mean redoing the research. Pick tasks where checking is quicker than doing.
4. What changes when it's gone? Does a backlog shrink? Does a customer get an answer sooner? Do you get a solid block of free time? A small task can be worth handing over if it constantly interrupts important work.
If two tasks look equally good, pick the one you can set up properly this week. Your first task isn't a permanent statement of what matters most. It's a place to prove delegation works.
A worked example where the "obvious" choice was wrong
Here's a hypothetical example. The numbers are invented to illustrate the method, not typical workloads.
A small consultancy owner wants help with "marketing and admin." During one recorded week, the owner:
- prepares 4 client meeting packs at 18 minutes each (72 minutes),
- coordinates 2 appointments at 25 minutes each (50 minutes),
- updates 3 project records at 12 minutes each (36 minutes).
That's 158 minutes in total. The diary also shows a long, unfinished attempt to rewrite the company's service description.
The owner's instinct is to outsource the service description. It's the most frustrating thing on the list.
But the diary shows why it's stuck: the owner hasn't decided which type of client to target. A marketing specialist could help with that, but it's not a routine admin task. So it goes into "investigate," with a separate brief.
Appointments repeat, but they're tricky to hand over yet. The owner has never written down travel time or which empty-looking slots are really protected for client work. So that becomes a "prepare first" task: write the rules, then delegate.
Meeting packs are the winner. Each one is built from an approved agenda, the last action notes and the project status. The owner can check the right versions are there without rebuilding the whole thing. The VA prepares a draft in a set folder, and the owner still sends it at first.
Project records look good too, but some updates depend on notes the owner never writes down after client calls. That exposes a habit to fix: write the agreed change down straight after the call.
So the first assignment is meeting packs, not all 158 minutes of work. That's a smaller, smarter choice backed by evidence.
Your real saving is smaller than the original time, and that's fine
Here's the bit that keeps people honest.
The time a task takes you today is only the starting point. Once you hand it over, you'll still spend some time:
- preparing inputs,
- answering questions,
- reviewing the output,
- fixing mistakes.
Count all of it.
Sticking with the same example, imagine the owner eventually hands over all three workflows. The original 158 minutes remain the baseline. But the owner still spends 25 minutes on inputs and questions, and 20 minutes reviewing and correcting.
158 minus 45 = 113 minutes actually freed up.
That doesn't include the VA's fee, which is a separate cost. And it doesn't mean the business earned more money. What the owner does with that time is what creates value.
Also watch for work that just moves rather than disappears. If you stop building meeting packs but spend the same time digging through messages for missing instructions, nothing has really changed. Fix how information flows before blaming the VA.
For the bigger financial picture, see our guide to virtual assistant ROI.
Bundle the steps either side of the task
Once you've picked a task, look at the steps just before and just after it.
Handovers often fail because the VA owns the middle bit, but nobody owns getting the inputs or checking what happens afterwards.
For the meeting packs, a sensible bundle might be:
- check the meeting is confirmed,
- gather the approved documents,
- flag anything missing,
- prepare the pack.
That's one coherent job, because every step supports the same upcoming meeting.
What isn't coherent is tacking on social media design to "fill spare time." That needs different skills, and it slowly turns a clear admin role into a pile of whatever you dislike this week.
Also decide who chases missing information. If the VA can request an agenda from the project lead, say so. If you have to provide it, set yourself a deadline. "Waiting for agenda" isn't enough if nobody knows whose job it is.
Test the handover on a past case before going live
Before trusting a VA with live work, give them a representative past case with invented or cleaned-up information. Include the same inputs they'd get normally, plus one ordinary gap they should notice.
For meeting packs, that might be an agenda, last meeting's action notes, and a project update with two conflicting version dates. Ask for a draft pack plus a note on anything they couldn't resolve.
Pay for this time and agree it in advance. It's a test of the handover, not free work. Our paid trial guide explains how.
Then check:
- Is the right client named?
- Are the required documents there?
- Was the version conflict flagged rather than guessed?
- How long did your review take?
If something went wrong, find out why. Was it a missing input you never supplied? An instruction they ignored? A different but perfectly reasonable approach?
Your one-task decision worksheet
Use this for one candidate task at a time:
FIRST TASK DECISION WORKSHEET
Task:
Dates seen and actual frequency:
Trigger:
Who uses the result:
My active minutes per case:
Waiting time and why:
Inputs needed and who provides them:
What "finished" looks like, and where the proof lives:
Decisions needed to finish:
Worst realistic mistake, and how it's contained:
Access needed for a safe first version:
My estimated prep and review time:
Decision: remove / simplify / automate / delegate / investigate / keep
Why:
First trial case and fee:
What would make me expand, change or stop:
Keep measured numbers separate from guesses. If you haven't timed something, label it a guess.
Then pick one task, set a preparation date, and keep the rest in a queue with a note explaining why each one is waiting.
Your first task doesn't need to be your biggest problem. It needs to be useful work you can recognise when it's done, explain when it's wrong, and stop carrying once someone else can reliably own it.
Next steps: our main guide on how to hire a virtual assistant, and how to delegate to a virtual assistant once someone's on board.
Frequently asked questions
What tasks can I outsource to a virtual assistant?
Common examples include inbox triage, appointment scheduling, meeting preparation, document organisation, data entry, research, customer support replies, invoice and receipt admin, CRM updates, social media scheduling and product listings. The right choice depends on your business, not a generic list.
What should I delegate to a virtual assistant first?
Something that repeats often, has a clear finish you can check quickly, has mistakes you can contain, and usually doesn't need your decision to complete.
What should I never outsource to a virtual assistant?
It depends on the business, but high-risk actions like changing payment details, deleting customer records or publishing unapproved claims shouldn't be the first thing you hand over. Start with preparation and keep approval for the risky step.
How do I know how much time I'll save?
Record the time a task takes you today. Then record the time you still spend preparing, answering questions and checking after handing it over. The difference is your real saving.
Should I outsource the tasks I hate most?
Not necessarily first. The task you hate most is often the one you understand least. Pick something clear for the first handover and come back to the hard one once the relationship works.