Async management is the skill nobody teaches Australian small business owners until they need it.

Most of us learned to manage by managing in-person. You walk past someone’s desk, see they look stuck, ask what’s up. That informal feedback channel does not exist when your VA is 3,500 kilometres away in Manila. You have to replace it with something deliberate, or the relationship slowly degrades into wrong work delivered politely.

This is the playbook that works.

The two-hour offset is not the problem

Everyone worries about the timezone. Manila is GMT+8. AEST is GMT+10. AEDT is GMT+11. The overlap is 4-6 hours a day, more than enough for live conversation when you need it.

The actual problem is what happens during the 18 hours a day you do not overlap. Your VA finishes work at the end of their day. You start your day. Nine hours pass between when your VA stopped and when you start reading what they did. If your VA hit a blocker at 2pm Manila time, the block is 24 hours old before you see it.

The fix is not “work the same hours”. The fix is making sure the handoff between you carries enough information that the offset does not matter.

The daily handoff ritual

This is the single highest-leverage piece of async management. Every VA on every placement we run sends an end-of-day message. The format is fixed:

Today: three sentences on what got done.

Blocked: anything I could not finish, with a one-line reason and what I need from you.

Tomorrow: top 2-3 things I will work on, in order.

That is the entire ritual. It takes the VA 3 minutes to write. It takes you 30 seconds to read. It eliminates the most common failure mode in async management, which is “I assumed you knew”.

The discipline matters. If your VA misses the handoff three days in a row, that is the first sign of a problem. Address it directly: “I rely on the daily handoff. Walk me through what got in the way of writing it this week.”

Where to put the handoff

The daily handoff goes in a single channel. We use a private Slack channel named #<client>-daily for every placement. One message a day, threaded if there is detail to add. Searchable, scannable, dated.

Not email. Not WhatsApp. Email is for external comms; WhatsApp is for urgent only. The handoff lives in the team channel.

If you do not use Slack, the equivalent in your tooling is a dedicated Teams channel, a shared Notion page with a daily entry, or a private channel in whatever your team uses for everything else. The medium matters less than the singularity.

Comms tools that work

In order of importance:

A team chat with a dedicated channel for this VA. Slack, Teams, Discord, whatever you already use. One channel, one VA. Founders who try to put VAs into the existing team channel end up with the VA missing context because they are getting noise from your conversations with everyone else.
Loom or a similar screen recording tool. The single biggest accelerator of async trust. When you record yourself doing the task once, your VA learns 10x faster than from any written SOP. Loom for one-way; meeting recordings for two-way.
A shared Google Drive or Notion workspace. SOPs live here. Templates live here. The week-1 onboarding doc lives here. Searchable.
A shared password manager. 1Password Teams is the standard. Never share credentials in chat. Never. Every shared login is a security incident waiting to happen.
A scheduled weekly video call. 30 minutes, every week, same time. This is for the things that do not fit in chat: feedback, performance, scope changes, anything personal. Async fills the gaps; the weekly call sets the direction.

Six tools is the cap. More than that and your VA spends 30 minutes a day checking notifications instead of doing work.

The trust-debt trap

This is the failure mode I see most often, and it is almost always the founder’s fault, not the VA’s.

The pattern: you hire a VA, they do good work, you give them more. They do average work on the more. You do not say anything because you do not want to be the bad guy. You quietly stop giving them the harder work. They notice. They do not say anything because they do not want to lose the role. The relationship slides quietly to “they do basic admin and nothing more”.

Six months later, you are paying for 20 hours a week of work you could have hired anyone to do. You are about to replace them, and you blame the VA, and the VA could have grown into a senior team member if you had told them at week 6 that the harder work was below your bar.

The fix is a weekly feedback ritual. 15 minutes of your half-hour weekly video call goes to feedback. Two questions:

What did I get wrong this week that I could have done better?

What did you get stuck on that I could help unstick?

Both directions. The VA gives you feedback on you. You give the VA feedback on them. If the answer to either question is “nothing”, you ask again. There is always something.

Founders who skip this ritual end up replacing VAs every 18 months. Founders who run this ritual keep VAs for 4+ years.

SOPs are the substrate

You cannot manage async without writing. Specifically, you cannot delegate a task you have not written down.

A working SOP for an async task has five fields:

What: the outcome (not the task)
Why: the context that makes the outcome non-obvious
How: the steps, with the tools and links
Done looks like: an example output the VA can pattern-match
Escalate when: the explicit list of situations to flag to you

The bit founders skip is “escalate when”. They assume the VA will use judgement. Then they get frustrated when the VA either over-escalates (every email becomes a question) or under-escalates (problems land in your inbox as fait accomplis).

Write the escalation rule explicitly. Specifically:

Anything over [dollar threshold] that costs the business
Anything from [named client list] regardless of content
Anything where the customer uses the word “lawyer”, “ACCC”, “consumer affairs”, or “refund”
Anything where you would normally check with the founder if you were unsure

That last one is the catch-all. Everything else is in scope.

The four async failure modes

In order of how often they kill relationships:

1. The silent grind

Your VA works for 6 hours on a task that should have taken 2, does not surface that they are stuck, and ships an okay-but-not-great output 9 hours later than expected.

Why it happens: cultural deference. Manila VAs (and most VAs anywhere) are trained to be helpful and not bother the principal. Asking for help feels like admitting weakness.

Fix: an explicit rule. “If you spend more than 30 minutes stuck on something, message me. I would rather lose 2 minutes answering than have you lose 4 hours guessing.”

2. The over-confirmation loop

Your VA messages you to confirm every decision. You spend an hour a day answering questions you would rather have them answer themselves.

Why it happens: scope is too vague, or the VA has been burned previously for taking initiative.

Fix: write the SOP more specifically (most common cause), and explicitly grant them autonomy on bounded decisions. “For refunds under $100, just do it. Above $100, ask me.”

3. The drift

Three months in, the VA is doing the work but the quality has slowly degraded. Nobody mentioned it. Nobody fixed it.

Why it happens: no feedback ritual. See trust-debt trap above.

Fix: weekly 15-minute feedback conversation. Non-negotiable.

4. The wrong-priority spiral

You ask for X. Your VA spends 4 hours on X. You needed Y more urgently and forgot to mention it.

Why it happens: priority is implicit in your head and not explicit in the handoff.

Fix: a shared task tracker (Trello, Asana, ClickUp, Notion, whatever) where each task has an explicit priority tag. Your VA works the top of the list, not the most recent message.

What about timezone matching

Many AU founders ask for AEST-aligned VAs (8am-4pm AEST). It works for some roles. It is not the default best choice.

AEST-aligned (8am-4pm AEST = 6am-2pm Manila): best for customer-facing roles where live chat or phone calls matter. Adds a $1-2/hr premium.

Hybrid (10am-6pm PHT = 12pm-8pm AEST): standard Manila working day with strong afternoon overlap into AU. Best default for most placements.

Async overnight (Manila daytime, your sleep): best for ops, research, and content tasks with no real-time component. You hand off at end of your day, wake to a done list. Underrated for founders who want a clean morning.

Pick one and keep it for 90 days. Mid-week shifts confuse everyone.

Cultural notes that matter

Three small things that compound over months:

Directness gradient: AU founders are direct. Manila culture is more indirect. Your VA will sand off the edges of bad news to be polite. Train them, gently, to surface bad news as plainly as good news.
Public holidays: Philippine public holidays are not Australian public holidays. There are ~18 of them and they bunch in November-December. Plan around them.
Typhoon season: late June through November. Internet outages happen. A reliable VA has a backup plan (mobile hotspot, co-working space). Ask in the discovery interview.
Birthdays and life events: Manila workplace culture celebrates these. Acknowledge them. A $20 GrabFood voucher on a birthday returns months of loyalty.

The 90-day checkpoint

By day 90 of any async relationship you should be able to answer four questions clearly:

Do you read the daily handoff every day? (If no, the ritual is dead and the VA knows it.)
Have you had at least one feedback conversation each direction this month? (If no, you are accruing trust debt.)
Has your VA solved one problem you did not know existed? (If no, scope is too narrow or trust is too low.)
Would you take a 4-week holiday and trust the VA to keep things running? (If no, you have not actually delegated yet; you have just relocated the work.)

If you can answer yes to all four at day 90, you have a relationship that lasts years.

What’s next

For the wider hiring framework, see How to hire your first VA in Australia.

For the week-by-week onboarding playbook that sets up the async rhythm from day one, see Onboarding a VA week by week.

Ready to start? Book a discovery call. 30 minutes, no card, no obligation.