← all posts

What to Delegate to a Virtual Assistant (and What I Never Would)

Hiring help is the easy part. You post a job, read a few replies, pick a person, and suddenly you have an extra pair of hands. The hard part, the part nobody really teaches you, is knowing what to delegate to a virtual assistant in the first place. I got this badly wrong at the start, and it cost me months.

In my first month I managed both classic mistakes at once. Some days I dumped a huge, half-explained pile of work on my assistant and wondered why it came back rough. Other days I clung to tiny jobs I should have let go of long before, because it felt faster to just do them myself. The video above walks through the same lessons if you would rather watch than read.

The mindset shift that made it click

What finally made delegation work for me was a simple change in how I thought about the work. You do not hand over whole roles. You hand over repeatable tasks and clear outcomes, and keep the judgment for yourself.

So I run one test on every task that crosses my desk. Could I write down, in plain steps, how to do this well? If yes, it can probably be handed to someone else, because the knowledge lives in the steps, not in my head. If no, if doing it well depends on taste, context, or a call that shifts every time, it stays with me for now.

Notice this is not about whether a task is important, since plenty of important work is completely repeatable. It is only about whether the how can be written down and followed by someone else, not whether you happen to enjoy it.

Start with a delegation audit

Before you delegate anything, you need to actually 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. All of it, into one running list, without filtering.

At the end of the week, mark each task on two simple scales:

• Is it repetitive, or does it genuinely need your judgment?
• Is it low value or high value to the business?

Now you have four corners. The tasks that are both repetitive and low value are your first delegation list, full stop. The repetitive but high-value tasks come next, once you trust the person. The judgment-heavy work stays with you longer, high value or low.

When I finally did this, I was a little embarrassed. Hours of my week were sitting in that bottom corner, repetitive low-value work I had never questioned because I had always done it. It did not have to be me. It only had to be written down clearly for once.

The first things I handed over

Here are the first tasks I let go of, roughly in the order I released them:

• Inbox triage. Not the important replies, just the sorting. My assistant files the newsletters, flags the handful of things that truly need me, and drafts nothing without an approved template. I went from a wall of two hundred messages to a short shelf of things that matter.
• Research and gathering. When I need ten options compared or a list of contacts pulled together, I write down what good looks like, and it comes back in a format I can scan in two minutes.
• Data entry and cleaning. Moving numbers into a spreadsheet, fixing formatting, turning a messy export into something a human can read. Pure repetitive work, perfect to hand off.
• Scheduling and calendar wrangling. All that back-and-forth of finding a time that works for everyone, which used to eat a shocking amount of my day.
• Formatting and repurposing content I had already made, turning one thing I wrote into three smaller pieces, following a pattern I set down once.
• First-pass replies to the routine questions we get over and over, using templates I wrote myself, so the words are still mine even when I am not the one hitting send.

Notice the pattern. Every one is a task where good already had a clear shape in my head, so I could describe it without inventing an answer from nothing. That is why they were safe to hand over first, and why they lifted weight off my week.

How I actually hand a task over

Here is the part almost everyone skips, and it decides whether delegation works or just creates a brand-new headache. This is the exact process I use every time:

1. Do the task once while recording my screen. I talk through what I am doing and why, and end up with a short recording of the real, messy thing, not a tidy fantasy version.
2. Turn it into a simple standard operating procedure, which is really just a plain written checklist. It does not need to be pretty, only followable by someone who is not me.
3. Hand over a small slice first, never the whole thing. One batch, one day, one small pile to start.
4. Check the first few results closely and give specific feedback. This part was great, this part missed, and here is exactly why.

And then, the hard part for a control freak like me: I let go. After a few solid rounds, I stop checking every single one. And the best thing happens. A good assistant starts improving the procedure themselves, spotting steps I left out, and the guide quietly gets better with daily use.

What I never delegate

Knowing your hard limits matters just as much as knowing what to release. A few things never leave my hands.

The first is final judgment and strategy. What we make, who we serve, where the business goes next. An assistant can gather everything I need, but the decision stays mine, because it is my name and my risk on the line.

The second is anything that needs my own voice or a real relationship. A message to a long-time customer, a sensitive reply, a thank-you meant to actually mean something. The moment that gets outsourced, people quietly feel it.

The third is high-trust decisions, the ones where a wrong call is expensive or hard to undo.

The fourth, and I am strict here, is sensitive access. My primary passwords, the core financial accounts, anything that could sink the whole business. When an assistant genuinely needs access, it is scoped and limited: their own login, only the permissions that task needs, nothing near the master keys.

Tight access is not suspicion. It is a clean boundary that protects both sides: if something goes wrong with an account, nobody wants a good teammate caught in 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 explain it clearly once, and after that it just exists, ready to hand off, improve, or automate later.

A library of these procedures is worth more than any single hire, because people move on but a documented way of working stays behind. The first task you delegate is slow and a little painful, because you are explaining your own work for the first time. The tenth is easy. Somewhere along that road you have quietly gone from doing the work, to describing the work, to reviewing a small system that mostly runs itself.

The mistakes I see people make

Let me save you the three I made.

The first is delegating a mess. If a task is chaotic and undefined inside your own head, handing it over just moves the chaos across the room. Define it first, then delegate.

The second is going silent. People hand a task over, give no feedback for weeks, then get frustrated it is not how they would have done it. That one is on you. Honest feedback in the first two weeks shapes everything after.

The third is the opposite failure, micromanaging so hard you save no time at all. If you check every keystroke and rewrite every result by hand, you have not delegated anything, only added a slow middle step and paid for the privilege.

Where to start

If you take one thing from all of this, let it be this. Do not try to hand over your whole life this weekend in a panic. Pick one task this week, the single most repetitive low-value thing you do, and give just that away properly. Document it once, check the first few rounds, then actually let it go.

That single small move will teach you more about delegation than any video could. If you are wondering where I find people, I hire through OnlineJobs.ph, and that is what the button below is for. Treat the person on the other end like the capable teammate they are, and this becomes one of the best decisions you can make, for you and for them both.