When I say “hold,” I mean synchronous work.
Your VA is online at the same time you are. You can hop on a call. Send a message and get an immediate response. Work through something together in real-time.
When I say “async,” I mean asynchronous work.
Your VA works on their own schedule. They pull tasks from a queue, complete them, and hand them back. You communicate through recorded videos, detailed task descriptions, and tools that don’t require both of you to be online simultaneously.
Neither one is automatically better.
I’ve seen both work beautifully. I’ve seen both fail miserably.
The difference usually comes down to whether you’ve set it up properly.
When You Actually Need Real-Time Overlap
Some work just doesn’t work async.
Customer support is the obvious one.
If you’re running a help desk for US business hours, someone needs to be answering tickets during US business hours. That probably means night shifts for your Filipino VA.
It’s not ideal. But it’s reality if you need live coverage.
Executive assistant work often needs real-time too.
Calendars change. Priorities shift. Someone needs to grab you with a question right now. The back-and-forth delay of async communication breaks the whole thing.
Same with live sales support. Crisis management. Anything tied to events happening right now.
The pattern to look for: If the work involves immediate responses to unpredictable situations, you probably need synchronous time.
When Async Actually Makes Sense
Async works great for deliverable-based work.
Content creation. Design. Development. Data entry. Research. Marketing tasks.
If you can write a clear brief, provide examples, and define what “done” looks like, the actual execution doesn’t need to happen while you’re watching.
How to Actually Decide
Here’s how I think about it.
Go synchronous if your VA’s work involves live customers, executives, or operations where instant decisions matter.
If you’re in a regulated industry that requires real-time supervision. If you don’t have good documentation and task systems set up yet.
Without those systems, async just becomes confusion. People checking messages at all hours trying to figure out what’s expected.
Go async if the work is deliverable-based and you can batch it into clear tasks.
If you can define a narrow overlap window for alignment and use written briefs and recorded videos for everything else.
If you’re willing to set real boundaries around response times.
That last one matters.
If you say “we’re async” but you get annoyed when your VA doesn’t respond to messages within 30 minutes, you’re not really async.
You’re just creating unpaid on-call time.
Most successful setups I’ve seen are hybrid.
A small predictable overlap window. Maybe daily, maybe a few times a week. Plus heavy use of async tools for execution.
This respects time zones. Preserves everyone’s sanity.
Still gives you real-time touchpoints for complex stuff.
The Traps That Kill Async Arrangements
Async fails in predictable ways.
Trap one: Vague handoffs.
You tell your VA to “work on the website” or “improve social media” without specific tasks or examples.
They spend hours guessing. You spend hours explaining why it’s wrong.
You’ve created more back-and-forth than just getting on a call would have taken.
Trap two: No decision authority.
Your VA has to ask permission for every tiny choice.
So they either interrupt you constantly or sit idle waiting for responses.
Define what they can decide independently. Document the framework.
Trap three: Treating async as “work whenever.”
If you’re not tracking when work happens, you lose visibility into overload, off-hours creep, and whether you’re accidentally creating unpaid overtime.
Async doesn’t mean untracked. It means work happens outside meetings, but within agreed schedules with proper time recording.
Trap four: No feedback loops.
If you never tell your VA whether work met expectations or how to improve, quality drifts.
Async requires more explicit feedback because you’re not watching work happen.
Trap five: Assuming async means zero meetings ever.
Some things genuinely benefit from conversation.
Weekly check-ins for alignment. Monthly retrospectives. Onboarding for new projects.
Use sync time strategically for high-value discussions, not routine updates.
Avoiding these traps comes down to intentional design.
How to Actually Make the Transition
Once you’ve decided on your approach, implement it deliberately.
Start with a written proposal.
Outline the schedule, overlap hours if any, communication tools, response time expectations, how you’ll handle urgent situations.
Discuss it with your VA. Refine based on their input.
This is an agreement between two adults, not a top-down mandate.
Set up your tools before you need them.
If you’re going async-heavy, organize your task system, create initial documentation, record template videos.
If you’re going synchronous, lock in recurring meeting times and sync calendars.
Do a trial period with explicit check-ins.
Run your model for a month. Then have a real conversation about what’s working and what’s not.
Maybe your overlap window is at the wrong time. Maybe your task descriptions need more detail.
Adjust based on what actually happens.
Watch for signs the model isn’t working.
If your async VA is constantly messaging off-hours for clarification, your documentation isn’t detailed enough.
If your sync VA seems exhausted or misses meetings, the schedule isn’t sustainable.
If you’re frustrated by slow async progress, you might need more overlap for complex decisions.
Be willing to evolve.
Your optimal balance will shift as projects change, as your VA gets more autonomous, as you refine processes.
What works during onboarding might not be what works six months in.
The goal isn’t perfection on day one.
It’s picking a reasonable starting point, implementing thoughtfully, and improving based on real data.
What This Actually Comes Down To
There’s no universal right answer here.
Sync works when you need real-time responsiveness, when work is tied to unpredictable events, when you’re early in a relationship and building understanding.
It requires predictable overlap, sustainable scheduling, proper documentation.
Async works when roles are deliverable-based, when you have strong systems, when you’ll set and honor real boundaries.
It requires upfront investment in processes but creates healthier long-term patterns.
Most successful arrangements blend both.
A defined window for alignment and complex coordination. Async execution for focused work.
This gives you benefits of both while avoiding the worst of each.
Whatever you choose, make it explicit.
Write it down. Put systems in place. Track actual time. Stay compliant with labor rules.
Your VA will appreciate the clarity.
Your business will benefit from sustainable operations.
You’ll avoid the legal and relationship problems that come from vague expectations.
The question isn’t really hold versus async.
It’s how much of each, when, and with what systems supporting it.
Get that right and everyone wins.
Your VA has a sustainable job they can plan their life around.
You get great work without burning people out or breaking laws.
That’s the goal.