The first things to delegate to a virtual assistant
# The first things to delegate to a virtual assistant
Hiring help is the easy part. You post a job, read some replies, pick a person, and suddenly you have an assistant. The hard part, the part nobody really teaches, is knowing what to actually hand over.
I got this badly wrong at first. In my first month with an assistant I managed both classic failures at once. Some days I dumped a huge messy pile of half explained tasks on them and wondered why the results came back rough. Other days I clung to little jobs I should have released months earlier, because in the moment it felt faster to just do them myself.
Getting it wrong is expensive in a sneaky way. Hand over the wrong things and you spend more time fixing rough work than you ever saved, and you quietly conclude that delegation does not work for you. It works. The skill was never in the hiring, though. The skill is in choosing what to let go of, and being honest about what you are holding onto out of habit rather than need.
The mindset shift that made it click
What finally made delegation work for me was a change in how I thought about the work itself. You hand over repeatable tasks and clear outcomes, and you keep the judgment. My automations and my assistant are both excellent at the same thing: doing a defined job the same careful way every time. Neither should be asked to decide what the job ought to be in the first place.
So I run one test on every task that crosses my desk. Could I write down, in plain steps, how to do this well? A yes means the task can probably be handed off, because the knowledge lives in the steps rather than locked in my head. A no, meaning the quality depends on taste or context or a call that shifts every time, means it stays with me for now.
That single question does most of the sorting. Notice it says nothing about importance. Plenty of genuinely important work is completely repeatable. Notice it also says nothing about enjoyment. Some judgment work is tedious and some repeatable work is a pleasure. The only thing that matters is whether the outcome depends on a decision only you can make, or on steps anyone careful could follow.
Run a delegation audit first
Before you delegate anything, you need to know what you do all day, and almost nobody truly does. Here is the exercise that changed everything for me.
For one full week, write down every task you touch, no matter how tiny. Answering a message. Moving a file. Booking a call. Fixing a broken spreadsheet. Capture it all in one running list without filtering.
At the end of the week, mark each task on two scales. Is it repetitive, or does it genuinely need your judgment? And is it low value or high value to the business? That gives you four corners to look at. Tasks that are both repetitive and low value are your first delegation list, full stop. Repetitive but high value work comes next, once trust is established. The judgment heavy work stays with you for a good while longer, whatever its value.
When I finally did this properly, I was a little embarrassed. Hours of my week sat in that bottom corner, repetitive low value work I had never questioned because I had always done it, so I assumed it had to be me. It did not have to be me. It only had to be written down clearly, once.
The six things I handed over first
Here is the concrete list, roughly in the order I let each one go.
Inbox triage came first. The sorting only, never the important replies. My assistant reads the inbox, files the newsletters, flags the handful of things that genuinely need me, and drafts nothing beyond templates I have already approved. I went from facing a wall of two hundred messages every morning to a short shelf of things that matter.
Research and gathering came second. When I need ten options compared or a list of contacts pulled together, I write down exactly what good looks like, hand it over, and it comes back in a format I can scan in two minutes.
Third was data entry and cleaning. Moving numbers into a spreadsheet, fixing formatting, turning a messy export into something a human can read. Pure repetition, perfect to hand off.
Fourth was scheduling, all the back and forth of finding a time that works for everyone, which used to eat a shocking amount of my day.
Fifth was formatting and repurposing content I had already made. One thing I wrote becomes three smaller pieces, following a pattern I set down once.
Sixth was first pass replies to routine questions, using answer templates I wrote myself, so the words stay mine even when I am not the one hitting send.
There is a pattern running through all six. Every one was a task where good already had a clear shape in my head, so I could describe it. None needed anyone to invent an answer from nothing. That is exactly why they were safe to release first, and why they lifted weight off my week almost immediately without lowering the bar on anything a customer sees.
How I actually hand a task over
This is the step almost everyone skips, and it decides whether delegation works or just creates a new headache. Handing a task over well is a skill of its own. My process now, every time:
I do the task once while recording my screen, talking through what I am doing and why. The result is a short recording of the real messy version, rather than a tidy fantasy of it.
I turn that into a simple standard operating procedure, which is really just a plain written checklist. It does not need to be pretty. It needs to be followable by someone who is not me.
I hand over a small slice first. One batch, one day of the task, one small pile. Never the whole thing at once.
I check the first few results closely and give specific feedback. This part was great, this part missed, and here is exactly why.
Then, and this is the genuinely hard part for a control freak like me, I let go. After a few solid rounds I stop checking every single one. The best part comes after that. A good assistant starts improving the procedure themselves, spotting steps I left out and finding faster paths, and the written guide quietly gets better because someone other than me finally uses it every day.
What I will never delegate
Knowing your hard limits matters as much as knowing what to release, so let me be equally clear about what stays.
Final judgment and strategy stay with me. What we make, who we serve, where the business goes next. An assistant can gather everything I need to decide well. The decision itself is mine, because my name and my risk sit on the line.
Anything needing my own voice or a real personal relationship stays too. A message to a long time customer, a sensitive reply, a thank you that is supposed to mean something. Outsource that and people feel it, even if they could never say exactly why.
High trust decisions stay, meaning the ones where a wrong call is expensive or hard to undo.
And I am strict about sensitive access. My primary passwords, the core financial accounts, anything that could sink the business, none of it gets shared. When an assistant genuinely needs access for a job, it is scoped: their own login, only the permissions that one task needs, nothing near the master keys. That has nothing to do with distrusting a person. I would not hand a brand new hire the keys to everything on their first day, or their hundredth. Tight access protects the assistant as much as me. If an account ever goes wrong, nobody wants a good teammate caught in the middle of a mess they were never given the power to cause.
The part that compounds
Here is what nobody tells you about all this documenting. Every task you write down once becomes a permanent asset you own. You do the painful part, explaining it clearly, exactly one time. After that it simply exists. You can hand it to the next person, improve it, or automate the whole thing later.
A library of written procedures is worth more than any single hire, because people move on and a documented way of working stays behind. The first task you delegate is slow and a little painful, because you are learning to explain your own work for the first time. The tenth is easy. Somewhere along that road the assistant stops just following your procedures and starts improving them, and you have quietly gone from doing the work, to describing the work, to reviewing a small system that mostly runs itself.
Three mistakes to skip
Delegating a mess is the first. If a task is chaotic and undefined inside your own head, handing it over just moves the chaos across the room. Define it, then delegate it.
Going silent is the second. People hand a task over, give zero feedback for weeks, then get frustrated that the result differs from how they would have done it. That one is entirely on you. Honest feedback in the first two weeks shapes everything after.
Micromanaging is the third, the opposite failure. If you check every keystroke and rewrite every result by hand, you have added a slow middle step and paid money for the privilege. The point is buying back your own attention, and you only get it back if you genuinely release the work once it is good enough.
Where to start
Do not try to hand over your entire life this weekend in a panic. Pick one task this week, the single most repetitive low value thing you do, and give just that one away properly. Document it once, check the first few rounds, then actually let go. That one small move will teach you more about delegation than any article could.
If you are wondering where I find people, I hire through OnlineJobs.ph, and the audit above is what I run before every hire. For more on how I run this lean little operation, including where automation takes over from the assistant, it is all at [xavierfok.com](/).
Get new guides and videos first — join the Telegram channel.