The 13-hour gap between Manila and New York doesn’t have to be a problem. With the right async time blocking structure, it becomes an advantage — your Filipino team works while you sleep, and you wake up to completed deliverables.
The issue isn’t the time gap. It’s that most employers haven’t designed their workflow around it deliberately.
This guide gives you the exact schedule blueprint, core overlap windows, and handoff templates to make async work predictably.
The Tiered Time Block System
The best async schedules use tiered priority blocks rather than fixed hourly slots. Here’s the structure that works for a Filipino VA supporting a US-based employer:
Premium blocks (protected): 9 AM–12 PM Manila time. Deep focus project work. No interruptions for non-urgent requests. This is where the highest-value work happens.
Flexible blocks: 1 PM–3 PM. Routine tasks — email management, data entry, scheduling, research. Can be rearranged if urgent project work carries over.
Buffer blocks: 3 PM–4 PM. Overflow work, unexpected requests from the US team, or admin tasks like invoicing.
Handoff block: 4 PM–5 PM. Dedicated to creating detailed EOD updates for the US team so they have full context when their workday begins.
This structure gives your remote worker autonomy over their premium hours while maintaining flexibility for the unpredictable nature of async workflows.
The “3-Hour Core Overlap”: Designing Your Sync-Async Window
Every US-Philippine async setup needs a core overlap window — the hours where both sides are awake and available for real-time decisions, urgent questions, and relationship-building.
The primary overlap window:
| Manila (PHT) | New York (EST) | Chicago (CST) | Los Angeles (PST) |
|---|---|---|---|
| 9:00 PM | 8:00 AM | 7:00 AM | 5:00 AM |
| 10:00 PM | 9:00 AM | 8:00 AM | 6:00 AM |
| 11:00 PM | 10:00 AM | 9:00 AM | 7:00 AM |
| 12:00 AM | 11:00 AM | 10:00 AM | 8:00 AM |
| 1:00 AM | 12:00 PM | 11:00 AM | 9:00 AM |
The 9 PM–12 AM Manila window (8–11 AM EST) is the 2026 standard overlap for PH-US teams. Schedule all recurring check-ins, standup calls, and decision-making conversations inside this window. Let everything else happen asynchronously.
For West Coast employers (PST), the overlap window is narrower and often requires fully async-first workflows with a single weekly sync.
For guidance on structuring around this, see our guide on PH-US time zone management.
2026 Deep Work Schedule Blueprint:
| Time Block (PHT) | Activity | US Team Role |
|---|---|---|
| 9:00 AM – 12:00 PM | Deep work / premium tasks | Async — review deliverables from previous day |
| 12:00 PM – 1:00 PM | Break | — |
| 1:00 PM – 3:00 PM | Flexible tasks / routine work | Morning US time — review overnight handoffs |
| 3:00 PM – 4:00 PM | Buffer / overflow | Afternoon US time — send new task assignments |
| 4:00 PM – 5:00 PM | EOD recap + handoff prep | — |
| 9:00 PM – 12:00 AM | Core overlap window | Both sides available |
2026 remote work trends favor deep work blocks from 1 PM–5 PM PHT, followed by sync windows starting at 9 PM PHT. This rhythm protects focus time while keeping the overlap window available for collaboration.
Outcome-Based Blocks Tied to Deliverables
Clock time becomes less meaningful in async setups. What matters is whether the work got done and whether the next person in the workflow has what they need.
Instead of “spend 3 hours on content research,” the block becomes “complete research doc with 10 sources and key insights summarized for US team review.” The VA might finish in 2 hours or need 4. What matters is the deliverable quality and the handoff.
This approach also protects against the most common async failure: a task that looks like it’s “in progress” for three days because nobody defined what “done” looks like.
For how to structure deliverables with clear handoff criteria, see our guide on structuring async handoffs.
Daily Standup Blocks for Async Updates
Real-time standups don’t work across a 12-hour gap. Async standup blocks do.
Schedule a dedicated daily slot — typically the last 15–20 minutes of the handoff block — for your remote worker to document: what was completed, what’s currently in progress, and any blockers with response deadlines.
A good async standup gives the US team everything they need to act when they start their day.
It also creates a running record of progress that serves as documentation if questions arise later. For how to structure this alongside your time tracking, see our guide on timeboxing for VAs.
Common Challenges in Async Schedules
Time zone handoff gaps. Without structured handoffs, a single task can span three days: US manager assigns at 5 PM PST, VA sees it the next morning Manila time, asks a clarifying question, US manager responds the following afternoon. Structured EOD recaps and task briefs with all context included eliminate this.
Internet reliability. Connection quality varies significantly across the Philippines. Metro Manila, Cebu, and Davao have stable infrastructure, but provincial and smaller city connections can drop unpredictably. Build in a 2-hour offline work buffer for deep work blocks — tasks that can continue without connectivity — so outages don’t derail the entire day’s schedule.
Micromanagement by proxy. Frequent check-ins and progress reports every few hours create the same stress as surveillance, even in async environments. The fix is defining deliverables clearly upfront and trusting the EOD recap to surface issues — not adding more touchpoints.
Holiday misalignment. The Philippines observes different holidays than the US. Expecting remote workers to push through their cultural observances while you take yours creates resentment. Build the Philippine holiday calendar into your schedule planning from the start.
Infrastructure Support for Async Teams
Monthly internet allowances of $20–$50 are now standard practice for employers serious about async work. This makes reliable connectivity a shared responsibility rather than a personal expense your remote worker might deprioritize.
Some employers also provide mobile hotspot subsidies as backup connectivity. A single point of failure shouldn’t derail an entire day’s schedule.
Time blocks are only as effective as the tools available during them. Laptop stipends, software subscriptions, and access to company accounts for shared tools are modest fixed investments compared to the ongoing productivity loss from workers operating with inadequate equipment.
2026 Tool Stack: Using Loom and Asana for Async Time Blocks
The right tool stack makes async scheduling visible and traceable without adding overhead.
Loom — For handoff communication where text isn’t enough. A 2–3 minute Loom walking through a completed deliverable or explaining a blocker is often clearer than a written description, especially for design or technical work. Include a brief text summary beneath the video so the US team can scan without watching every time.
Asana / ClickUp — Task-based platforms where time blocks map to specific deliverables. Each block has a task, a due date, and clear acceptance criteria. No ambiguity about what “done” looks like.
Google Calendar — Dual time zone display (Manila + your US time zone) on every event. Share your VA’s time block schedule as a calendar so you can see their availability without asking.
ManagePH — Handles clock-in/out tracking, daily standup collection, and invoice processing in one place. Time block entries connect directly to payroll records, which eliminates the end-of-month scramble to reconcile hours with deliverables.
The combination of Loom for async communication, Asana for task-deliverable mapping, and ManagePH for time tracking and standups covers the full async workflow without tool sprawl.
FAQ
What is a “Core Overlap” window for PH-US teams?
The core overlap window is the hours when both the US employer and the Manila-based remote worker are awake and available simultaneously. For US Eastern Time employers, this is 9 PM–12 AM Manila / 8–11 AM EST during standard time. This is the window to schedule check-ins, decision-making calls, and anything requiring real-time input. Everything else should happen asynchronously within each party’s deep work hours.
How many hours should be blocked for async work vs. coordination?
The 2026 standard for high-performing PH-US teams is 5–6 hours of protected deep work (typically 9 AM–3 PM PHT) followed by 2–3 hours of coordination and handoff preparation (3–5 PM PHT), with the core overlap window (9 PM–12 AM PHT) reserved for synchronous collaboration. More than 3 hours of synchronous overlap per day usually indicates a workflow that hasn’t been fully designed for async.
What are the best tools for async time blocking?
Google Calendar with dual time zone display for schedule visibility. Asana or ClickUp for mapping time blocks to specific deliverables with clear acceptance criteria. ManagePH for time tracking, daily standup collection, and payroll documentation — it keeps the async workflow connected to payment records without additional tooling. Loom for video handoffs when written description isn’t enough.
How do I handle emergency handoffs in an async environment?
Define a “response within X hours” rule before emergencies arise. A common standard: routine requests receive a response within the next working session (typically 12–16 hours); urgent requests flagged with a specific label or channel receive a response within 4 hours; true emergencies (system down, client escalation) have a designated contact method (WhatsApp or SMS) with a 1-hour response expectation. Post these standards in your team documentation so everyone knows the protocol before they need it.