Async Communication Norms for  US-Philippine Remote Teams

Here’s what most employers think async communication means: “I’ll send messages whenever I want and they’ll respond when they’re online.”

That’s not async communication. That’s just bad communication.

Real async communication is structured. It has rules. It has expectations.

Here they are.

Set Clear Response Time Expectations 

Here’s where most async systems fall apart.

Someone sends a message. Hours pass. No response.

The person who sent the message starts wondering: “Did they see it? 

The person who received it is thinking: “I’ll get to that later.” Then later turns into tomorrow. 

Nobody knows when they’re supposed to respond to anything. You need clear rules.

Here’s a basic framework:

Urgent issues (something is broken, a client is waiting, a deadline is today): 2-4 hours during working hours.

Regular questions (project clarifications, task questions, normal work stuff): 24 hours.

General updates or information (something to know but not urgent): 48 hours.

Planning or ideas (things that can wait): up to a week.

Document this. Put it in writing. Make sure your VA knows these are the expectations.

Structure Daily Status Updates 

Let me tell you what happens without daily updates.

You have no idea what your VA is working on. They think they’re doing great. You think they’re not doing enough. Or maybe they’re stuck on something but they don’t want to bother you.

Nobody knows what’s actually happening until something goes wrong.

Daily recaps fix this.

Not long updates. Not essays about every little thing they did.

Short, structured updates.

Here’s the format that works:

What I finished yesterday What I’m working on today What’s blocking me

That’s it. Three sections.

Your VA should be able to write this in 5 minutes. You should be able to read it in 30 seconds.

Schedule Meetings vs Using Messages 

Here’s a simple rule: most things don’t need meetings.

If you can write it in a message, write it in a message.

Meetings should be for:

• Sensitive conversations (performance issues, major changes)
• Complex brainstorming (new projects, big decisions)
• Relationship building (getting to know each other, team bonding)

Everything else? Messages.

Create Documentation That Saves Time

Here’s what happens without good documentation:

Your VA asks a question. You answer it. Two weeks later, they ask the same question again. You answer it again.

A month later, you hire another VA. They ask the same question. You answer it a third time.

This is a waste of everyone’s time.

Document everything that might need to be referenced later.

I’m not talking about corporate documentation with fancy formatting and table of contents.

I’m talking about simple documents that answer common questions.

How to handle client refunds. How to process invoices. How to update the inventory spreadsheet. What to do when a client emails asking for changes.

Write it down once. Share it somewhere everyone can find it.

Google Docs works. Notion works. Even a simple shared folder works.

Tools That Make Async Communication Easier

You can’t rely on email threads and Slack history. Information gets lost. People can’t find things. Everyone wastes time searching.

Most employers cobble together 5-6 different tools. That works if you’re organized. But it also means information is scattered across multiple places.

Platforms like ManagePH consolidate this stuff. Time tracking, status updates, PTO requests, invoice approvals, all in one place. 

Everything your VA submits, you can review when you’re working.

The point is: async communication requires structure. You can’t just wing it with random Slack messages and hope everything works out.

Making Async Work for Different Time Zones

US to Philippines is one of the trickiest time zone gaps.

If you’re on the East Coast (New York, Miami, etc.), you’re 12-13 hours behind Manila.

If you’re on the West Coast (California, Seattle, etc.), you’re 15-16 hours behind Manila.

That’s basically opposite schedules.

Here’s what works:

East Coast employers: You have a few hours of overlap. If your VA works 9 AM to 6 PM Manila time, and you start your day at 7 AM, you overlap from 7 AM to 9 AM your time (that’s 7 PM to 9 PM Manila time).

West Coast employers: You have almost no overlap. When you wake up, your VA is wrapping up. When you’re in the middle of your workday, they’re asleep.

This actually forces you to do async correctly. You can’t rely on real-time back-and-forth at all.

UK employers: You’re 8 hours behind Manila. When you start your day at 9 AM, it’s 5 PM in Manila (end of their workday). Similar situation to East Coast US.

Australia employers: You’re very close to Manila time (1-3 hours depending on Australian city). This is the easiest time zone situation. You can actually have sync meetings during normal work hours for both of you.

For US employers, accept that real-time communication isn’t happening regularly.

That’s okay. 

The work still moves forward. Your VA gets through their tasks during their day. 

You review and assign new work during your day.

It works if you let it work.

The Real Goal of Async Communication

Let me tell you what async communication is actually about.

It’s not about avoiding meetings or being hands-off.

It’s about respecting that your VA is a real person with a real schedule who needs to actually sleep and have a life outside work.

And it’s about building systems that let work happen smoothly without requiring everyone to be online at the same moment.

When you do this right:

Your VA knows exactly what’s expected of them. They know when they need to respond to messages. They know when they can log off and be done for the day.

You know what your VA is working on. You can review their progress without interrupting them. You can plan work because you have visibility into what’s getting done.

Work moves forward consistently instead of in fits and starts.

Nobody’s burnt out from weird hours or constant interruptions.

That’s the goal.