How to ACTUALLY Outsource Tasks to Virtual Assistants…So They Actually Get Done

Ever built IKEA furniture?

Of course you have. Everyone has.

And here’s the thing about IKEA: The instructions are wordless. Just pictures. Little arrows. Step 1, Step 2, Step 3. Bolt A into Hole B. Tighten. Flip. Repeat.

It takes you 45 minutes and you feel like a genius.

Now imagine IKEA handed you the same box of parts with no instructions. Just a photo of the finished bookshelf on the box and a note: “You’ll figure it out. It should be intuitive.”

You’d be furious. You’d return it. You’d leave a one-star review. You rage at a sofa or bed frame that just mocks and laughs at you with an evil smirk.

And here’s the part that should sting a little:

This is what most business owners do to a new hire.

They hand someone a login, say “you’ll figure it out,” and then act shocked three weeks later when it didn’t work.

Then they say things along the lines of:

“I tried a VA. Waste of money. Took longer to explain than to just do it myself.”

I’ve read that exact sentence a thousand times. This whole article is the answer to it and will walk you through every step to outsource tasks to Virtual Assistants without banging your head against the wall.

You’re welcome 🙂

---

---

What Tasks Can You Outsource to a VA?

Quick note before we dig in.

If you want the giant list of everything you could possibly hand off — admin, sales, marketing, e-commerce, the works — I already wrote that one. Go grab the tasks here:

What Does a Virtual Assistant Do? 130+ Real Tasks.

This article is the other half. The half nobody writes.

Not what to delegate. How to delegate so it actually sticks.

And stick with me, because the back half of this gets specific: I’m going to show you the exact task board to build for a Virtual Assistant and the exact software to run it on. That’s the part everyone skips and it’s the part that decides whether this works.

We’ve made over 1,100 placements across 35 countries, and I’ve personally run more than 10,000 interviews. So I’ve watched thousands of these relationships up close — the ones that hand someone their life back, and the ones that flame out in 60 days.

The thing that separates them is almost never the Virtual Assistant’s talent.

It’s the system they were handed. And the good news is that’s the one part you fully control.

---

You Have To Train Virtual Assistants

Let me put the core objection to bed.

Can a fry cook at Burger King walk into a McDonald’s and run the fryer with zero handoff?

No.

Could a 3-star Michelin chef walk into a kitchen they’ve never seen and execute a full dinner service on night one, no prep, no walkthrough?

No.

Someone with relevant experience ramps faster — the Burger King cook is probably running the McDonald’s fryer within an hour. But “faster” is not “magically, with no instruction.” No level of talent skips onboarding.

What’s funny is how often I hear, “Every hire I’ve ever made failed for X, Y, and Z reasons.” And the person saying it never stops to look at the one thing all those hires had in common.

It’s not a fun thing to hear. But it’s the most useful idea in this entire article, so sit with it for a second: If the setup is the same every time, the setup is the variable worth fixing.

Nail the onboarding and the system, and you get a team member who owns the work and stays for years.

Skip it, and you’ll churn through people faster than you can scarf down a bag of fries — and you’ll blame every one of them on the way out.

---

You Pay Upfront

Here’s the mental model that fixes everything:

The work doesn’t vanish when you delegate. It moves to the front.

A bad delegator pays the tax forever — explaining the same task on Slack every single day, re-explaining it, fixing it, re-fixing it, for the life of the relationship. That’s the “it takes longer than doing it myself” trap. And for them, it’s true. Forever.

A good delegator pays once, up front. One serious, focused afternoon preparing before the person ever logs in. Real time alongside them that first week. And then they basically stop paying.

That’s the entire trade: One good prep block and an engaged first week, versus a slow drip of frustration with no end.

You’re not signing up for a week of writing documentation. You’re signing up for one focused afternoon and a hands-on first week. Pay it now.

---

How to Write SOPs/Documentation In 2026

The objection I hear constantly: “Kyle, I don’t have time to sit down and write a 30-page operations manual.”

You’re right. Don’t.

Nobody writes SOPs from a blank page anymore. There’s no reason to.

Here’s the entire process:

Record yourself doing the task. Just talk through it on a Loom while you work.

And let me be clear about something:

It does not have to be polished.

It should be raw. Messy.

Word-vomit the whole thing — every click, every “I do it this way because,” every weird edge case, every “oh, and sometimes this happens instead.” Over-explain it. Give detail you think is irrelevant. The more you ramble, the more context you’re handing the machine.

Do it two or three times — just hit record the next few times the task naturally comes up. Different instances catch different situations, and that gives the AI even more to work with.

Then drop the transcripts into an AI and let it do the heavy lifting: Turning your blabber into clean bullets, ordered steps, and tidy sections.

You just “wrote” an SOP by talking for a few minutes.

A Loom beats a written doc anyway. They see your screen. They hear your reasoning. They catch the little asides no written step ever captures.

Then comes the move most people miss:

Make them write the final version.

After they’ve watched the Loom and done the task a few times, they write the SOP — in their own words, in a shared doc. You review it, fix what they misunderstood, approve it. Now that doc is the source of truth, and the next person you hire opens it and onboards themselves.

You just turned a task-doer into someone who owns the process. (I broke this method down further in my Buy Back Your Time review — worth a read.)

A word on the “time audit.” Every productivity book says to track every minute of your week before you delegate so you know what to hand off. Good advice. It works. And almost nobody short on time actually does it — because it’s admin, it’s paperwork, and it’s exactly the kind of thing busy founders avoid. So here’s my take: If you’ll do a real time-and-energy audit, do it. If you won’t, don’t let it stop you. Start with the obvious stuff eating you alive — the inbox, the scheduling, the follow-ups, the data entry — and hand that off first. You don’t need a spreadsheet to know what you hate doing.

Buy Back Your Time by Dan Martell (Review) — 4 Things It Gets Right, and 4 It Gets Wrong

---

How to Actually Manage Outsourcing Tasks to a Virtual Assistant (With a Task Board)

People love to overcomplicate it.

They go tool shopping instead of building a system. So let’s keep it dead simple: One board, the right software, clear cards.

Here’s exactly how I’d set it up.

Project Management: Use What You Already Have

Asana, Trello, Monday, ClickUp, Notion — they all do the same thing. The tool is not your bottleneck. I promise.

My two picks for a Virtual Assistant are Trello or Notion. I personally like Trello — clean, simple, and the card system maps perfectly to how a VA should work.

Notion has its own edge: One workspace can hold the task board, every SOP, your scratchpad, all of it in one place.

But here’s the real rule: If you’re already running your business somewhere, build the damn board there. Already living in Monday? Do it in Monday. ClickUp? ClickUp. The best tool is the one you’re already in.

I hold this belief hard:

A great assistant — VA or EA — molds to your world.

They fit into the tools and rhythms you already have, not the other way around. The entire point is to make your life easier, so don’t reorganize your stack around a new hire. Drop them into where you already live.

What a Good VA Task Board Looks Like

Here are the lists I’d build:

• The Idea Dump. A running list of everything you might one day hand off. You’re on a walk, you think “they should handle X,” you capture it — even if you never assign it. One caveat: This doesn’t have to live on the board. It gets messy fast, and it’s often cleaner to keep it somewhere else — a note, a separate doc, wherever. Up to you. The only rule is that you have a place to catch the idea the second it hits, so it’s out of your head.
• Assigned. What they’re actively working on right now.
• Review. Where finished work waits for your check — especially early, while you’re still calibrating quality.
• Done This Month. Completed and approved.
• All Complete (Archive). At the end of each month, sweep “Done This Month” into here. Now you’ve got a permanent record of everything this person has ever shipped. That archive is gold at review time, at raise time, and on the days you need to remind yourself the hire was worth it.

Then, separately, the part that actually buys back your time:

• Daily, Weekly & Monthly Recurring Tasks. The stuff that has to happen on a schedule, no exceptions. Some things are daily. Some weekly. Some only monthly — the report you pull, the reconciliation, the recurring audit. Each one with its SOP attached.

I’ve preached this in every article I’ve written, so here it is again:

Fill at least half their day with repeatable work.

If you wake up every morning wondering “what should I have this person do today,” you didn’t hire help — you gave yourself a second job as their activity director. Recurring tasks are the foundation. Ad-hoc work fills the gaps.

Inside every card, three labels:

• Urgency / Priority (1, 2, 3 is plenty)
• Due date
• Hours it took (they log it — this is your speed check, not spyware)

And the most important line on any card is the Definition of Done, which gets its own section below.

One more tool, brain-dead simple:

A basic Google Sheet where they log their recurring output each week. “Outreached 10 people on LinkedIn today.” “Published 5 articles this week.” A color-coded spreadsheet beats any fancy dashboard platform you’ll ever pay for.

The Rest of Your Stack

The board is the core. Here’s everything around it.

Communication: Email or Slack. Not WhatsApp.

Pick one channel.

I’d use email or Slack, and I’d avoid WhatsApp unless that’s genuinely where you live all day — because the moment someone’s in your WhatsApp, they’re in your pocket forever. And a subtle point most people miss: The channel shapes the behavior. Slack invites a thousand little “quick question?” pings that pull you out of your day and train your VA to outsource their thinking back to you. Email makes someone pause, batch their questions, and think before they hit send. If you want fewer interruptions and a VA who solves more on their own, lean email and async.

Documentation: Loom plus one home for the SOPs.

Loom for recording. A single, obvious home for the written versions — a Notion section, a Drive folder, a Coda doc. One place. Not seven.

Access and Security: 1Password.

This is the one that scares people — handing a stranger the keys to your email, your CRM, your accounts. You solve it with a shared vault. You share the access, not the actual passwords. They log into the tools and never see your credentials. You scope what they can reach, and you revoke it in one click if it ends. Stop emailing passwords. Stop saying “I can’t delegate because I can’t share logins.” You can. This is solved.

Time Tracking: No. Do this instead.

I don’t believe in screen-recording or total-time-tracking software for a good Virtual Assistant. It’s surveillance that tells the person you just hired you don’t trust them.

Here’s the standard I use instead, and I set it in the interview so there are no surprises: Over time, I expect you to do a task at roughly 80% of my speed.

If something takes me an hour, once you’re up to speed you can have an hour and 15 — and that ramp should happen within a couple weeks, depending on complexity.

But if a task takes me 30 minutes and it’s eating your whole afternoon, the math is broken, because I’m not getting that time back. You don’t need spyware to catch that. You need a clear expectation, consistent work, and the discipline to notice when an hour’s task is taking four.

---

The Definition of Done

If you take one thing from this entire article, take this.

The number one mistake business owners make with a Virtual Assistant is assigning a task and saying:

“I’ll know it’s done when I see it.”

That. Never. Works.

For every recurring task, write down what “done” actually means. Not the task. The actual Definition of Done.

Bad: “Update the CRM.”

Good: “All new leads from today’s calls are entered with full contact info, the deal stage is set to ‘Contacted,’ and the call notes are pasted into the activity log. Done = every field complete, no blanks.”

See the difference?

The second version lets them check their own work. They never come to you asking “is this right?” because the standard is already written down. This forces you to think clearly about what you want, which is the actual hard part…and the reason most people skip it.

Here’s what real Definitions of Done look like, pulled from how I run my own assistant:

• Booking travel: “Three flight options in a doc, ranked, with layover times flagged, plus a cancellable hotel held for the right nights.” Not “book my trip.”
• Renting a car: “Decline all coverage, use the company card, midsize SUV, add the child seat. Done = confirmation forwarded with the total.” Not “rent a car.”
• A week-one learning task: “Watch five of my sales calls. Done = a one-page bullet list of what you noticed about how I communicate.” Not “learn how I talk.”

Write the finish line. Every time. This one habit saves more Virtual Assistant relationships than anything else I can tell you.

---

Onboarding: Map the First 90 Days Before They Start

Don’t wing the first month. Map it — on a calendar, before day one.

Write down:

• Week 1: Which two or three tasks they start with. Which SOPs and Looms they watch first.
• Month 1: What gets added in weeks two and three.
• Month 3: What they should fully own by then.
• Your side: This is the part people forget. Onboarding is your job too. Block the time. Give them 1Password access. Walk them through the CRM. Record the Looms. Show up to the calls.

Cadence: Meet daily for the first two weeks. It doesn’t have to be long — an hour, three days a week minimum, more if you can swing it. Then taper to weekly as they take the reins.

Start with 3 to 5 tasks, not 30. Do not dump everything on them in week one. Pick the few most obviously delegatable things, run each through the transfer method below, build trust on both sides, then add more.

And here’s the sign you nailed it:

By the end of onboarding, your Virtual Assistant should be able to run your weekly check-in themselves — board already updated, walking you through it, flagging what’s stuck. When the person you onboarded starts running the meeting, you’ve won.

---

How to Transfer a Task: Show, Supervise, Shut Up

Three phases for every task you hand off. I call it the Triple S.

Phase 1 — Show. You do the task while they watch. Screen share, narrate everything — every click, every decision, every “I do it this way because.” Record it so they can rewatch.

Phase 2 — Supervise. Now they do it, you watch. Could be the next day or the next week, depending on complexity. They have the reins. You answer every question and correct in real time. You let them struggle a little. You don’t let them drown. This is where most of the learning happens.

Phase 3 — Shut Up. The hard one for control freaks. You sit on the call, camera off, and let them work. They operate alone. You’re a safety net for serious issues only. If they get through a full session without needing you, they own the task. If they can’t, back to Phase 2.

At the end of Phase 3, they should be able to write the SOP for that task themselves.

That’s how you know the transfer is complete. They don’t just do it — they could teach the next person to do it.

Show. Supervise. Shut up. Run it across every task and you’ll have someone operating independently inside a month.

---

How to Run a Good Check-In (The Meeting Operating System)

A bad check-in is you, on a call, doing the work for them while they watch. That’s not a meeting. That’s you doing their job with an audience.

A good check-in runs on rails. Same structure every time. I borrowed the bones of this from Traction by Gino Wickman and stripped it down for a single Virtual Assistant.

Here’s the agenda:

1. Wins. One business win, one personal win, from each of you. Thirty seconds. It sets the tone and reminds you there’s a human on the other end.
2. Calendar / Priorities Review. A quick scan of what’s coming, what’s due, what moved.
3. The Scorecard. The handful of numbers and top priorities that define whether the role is being done well this month — each with its Definition of Done, marked done or not done. Five to seven things. Red, yellow, green.
4. To-Do Review. Walk the board. What got finished, what’s stuck, what’s blocked.
5. IDS — Identify, Discuss, Solve. The heart of it. Surface the real issues, discuss them, and solve them — with an owner and a deadline attached, not a vague “let’s circle back.” Most “problems” with a VA are just issues nobody made the space to solve.
6. Rate + Reset. At the end, both of you rate the meeting 1 to 10 — it keeps everyone honest about whether these are useful. Then reset the board the same day so you walk into next week clean.

Run that. Async for the day-to-day, this synced check-in on a real cadence — daily for two weeks, then weekly.

And know this: A 1:1 is not the same as talking all day in Slack. Slack is task execution. The check-in is relationship, coaching, and the space where your VA tells you the thing they’d never put in a message.

The relationships that last for years all share one trait: A structured, predictable, un-skipped check-in. Every single one.

---

Give Feedback Immediately. And Kindly.

If they format an email wrong on day two, you fix it on day two. Not day 30.

Most people get this backwards. They’re too “nice” to give feedback early, so it festers — then too frustrated to give it kindly later, when it finally boils over.

Flip it. Be direct early. It’s the kinder thing in the long run. Early, specific, unemotional feedback kills a bad habit before it sets. Letting it slide for a month and then erupting helps nobody.

---

Don’t Skip the Interview (Where Most People Hire the Wrong Person)

Everything above assumes you hired someone with a brain. So let’s make sure you do — because the system only works if there’s a thinking human running it.

Here’s the problem: Your candidates have read the books. They’ve memorized the STAR method. They’ve rehearsed “my greatest weakness is I care too much.” They know how to answer the checklist.

So don’t run a checklist. Do you want to sound like every other interviewer they’ll talk to this week? No. You want the real person, not the rehearsed one.

After 10,000 interviews, here’s what I know:

The first 30 minutes show you competence.

The last 10 minutes show you character.

Competence gets someone considered. Character gets them hired.

So at the end, I throw out the script and run a lightning round — questions with nothing to do with the job:

• Is pineapple on pizza acceptable?
• What did you want to be as a kid?
• Ferrari or Lamborghini?
• Snow or surf?
• Do you wear sunscreen?
• Craziest thing you’ve ever done?

They relax. They think the interview’s over and we’re just chatting. They have no idea this is the most important part.

The answers don’t matter — the person does. If someone lights up describing a backpacking trip, they’re a human I’ll enjoy working with for the next year. If they say they don’t wear sunscreen and they love skydiving, I know they’ve got an appetite for risk. If they refuse to pick Ferrari or Lamborghini and mutter “BMW,” I know they’re a reliable executor who won’t shoot for the stars — useful to know. And if someone can’t even take a stance on pizza — “well, I don’t like it, but I don’t judge, we should respect all choices” — that’s a dud. If they can’t have an opinion about a pizza topping, they will never have one about anything in your business.

Now here’s the reverse, and it’s the real trick:

The skill that separates great candidates is threading — taking an answer and pulling it one level deeper, then bouncing somewhere new. Light, personal, light, deeper. A sharp candidate will even do it to you — drop a short, specific answer with one detail left dangling that begs a follow-up.

So you be the one threading. Ask the weird question, then pull the thread. “You ate crocodile in Thailand? What else did you try?” Go three levels deep on something they couldn’t possibly have rehearsed, then jump tracks. The person who can hold that conversation — relaxed, specific, real — is the one with a brain. The one who answers everything in calculated, safe, pre-packaged sentences is the one who’ll be exactly that robotic on the job.

I wrote the whole playbook on this, from both sides of the table, in my book 10,000 Interviews.

To hire a Virtual Assistant, just flip it: The book teaches candidates how to turn an interview into a conversation. Your job is to run that conversation, so the polish has nowhere to hide.

---

When 1 Virtual Assistant Isn’t Enough Anymore

Here’s how you know the system is working:

You keep finding more to hand off.

That’s not scope creep. That’s the flywheel. Once you see what a good Virtual Assistant takes off your plate, your brain starts spotting delegatable work everywhere. Great problem to have.

When you hit the ceiling, you’ve got three moves:

• Go full-time. If you maxed out 20 part-time hours in the first month — and you will — make it 40. Same person, more capacity.
• Hire a second VA. When the recurring load genuinely exceeds one human, split it. One on admin and CRM, one on social and content.
• Level up the role. Sometimes the bottleneck isn’t volume — it’s judgment. You don’t need more task execution, you need someone who anticipates instead of waits, who builds the systems instead of just running them. That’s not a VA anymore. That’s an Operations Manager or a true Executive Assistant. When you’re spending your check-ins assigning every individual task instead of reviewing outcomes, you’ve outgrown a VA. Go read those guides.

---

Frequently Asked Questions

Do I need SOPs before I outsource tasks to a Virtual Assistant?

Yes — but they don’t need to be fancy. A Loom of you doing the task while you narrate is an SOP. A doc with bullets and screenshots is an SOP. You need enough that they can finish a task without guessing, not a 30-page manual. One focused afternoon of recording before they start saves you months of chaos after.

What project management tool should I use for a VA?

Whatever you’ll actually use. Trello or Notion are my picks — Trello for a clean board, Notion if you want SOPs and tasks in one workspace. They all do the same thing. If you already run your business in another tool, build the board there. The tool is never the bottleneck — the board structure and the Definition of Done are.

Should I use time-tracking software on my Virtual Assistant?

I don’t. Screen-recording spyware tells the person you just hired you don’t trust them. Set a speed expectation instead — over time they should work at about 80% of your pace on a task — and watch for anything that should take an hour and is taking four. Have them log hours on each card. That’s enough.

Email or Slack for working with a Virtual Assistant?

Either, not WhatsApp. Slack is instant and invites constant pings. Email forces them to batch and think before they ask. If you want fewer interruptions and more independent problem-solving, lean email and async.

How many hours a week do I need from a Virtual Assistant?

Most people start at 20 (part-time) — enough for inbox, calendar, CRM, and a few recurring tasks. You’ll likely max that out within the first month, which is your signal to go full-time. Start at 20 and scale up.

How long does it take to onboard a Virtual Assistant?

A strong one contributes in week one and owns most recurring tasks by month two — if you’ve done your part: Documentation ready, daily check-ins for the first two weeks, 3 to 5 tasks to start. If it’s month two and you’re still assigning every single task by hand, the issue is usually the system, not the person.

What if it’s just not working out?

Move fast. Don’t spend three months hoping. First, audit your own setup — is there a Definition of Done, are there SOPs, did you actually onboard them? If yes and it’s still not landing, it’s a fit problem, and a replacement beats a slow death. (If you hired through a placement service like HireUA, the replacement is on us. If you hired solo on a freelance platform, you start the search over.)

Can AI just do all of this instead of a Virtual Assistant?

AI handles the button-pushing — drafting, summarizing, formatting — beautifully. But it still needs a driver: Someone to own the outcome, catch what’s wrong, make the judgment calls, and run the parts that need a human. The best Virtual Assistants today use AI as a tool. It’s not AI instead of a VA. It’s a sharp VA with AI in their stack.

---

Or — Skip the Trial and Error

Everything in this article works. I’ve handed this exact system to clients hundreds of times and watched it turn a buried founder into someone who takes a real vacation.

But here’s the honest read on it:

It’s a lot. The prep, the board, the SOPs, the Definition of Done, the onboarding map, the meetings, the feedback discipline — that’s real work, and it’s the kind of admin a lot of founders won’t do, no matter how cleanly I lay it out.

That’s the gap we fill.

HireUA doesn’t hand you a resume and wish you luck. We find the person, vet them through the interview process above, and help you stand up the systems so it sticks. We’ve got a library of SOPs, scorecards, and board templates for dozens of roles — your CSM will share them or build a custom one for your exact situation once you’re onboard.

And one more thing. Everything above assumes you can hand someone an SOP and a couple of Looms and they’ll run with it. That depends on hiring someone sharp in the first place — which is the other half of what we do. We place people with a brain, so you’re not running this whole system and praying it survives a bad hire.

If you’d rather build the machine than do all of this yourself — book a call with HireUA and we’ll get the right person in the seat with the systems to match.

That’s the deal.