Async by default: working across a 12-hour time gap

Manila is UTC+8. If you run a US Central business, your 9 a.m. Monday is your hire's 10 p.m. Sunday. That is a real constraint. It is also, for most roles, a solvable one — and for some it is quietly an advantage. The mistake is treating the gap as an exception to manage around rather than a condition to design for from day one.

Most friction in a cross-timezone setup comes from one thing: decisions and context that live only in the founder's head. A hire who wakes up to an ambiguous task and no one to ask is blocked for eight hours. A hire who wakes up to a clear handoff doc, a decision log, and explicit authority to proceed is working while you sleep. The difference is process, not time zone.

Map the gap honestly before you hire

The Philippines sits at UTC+8, so most of the US gets a gap of 11 to 14 hours depending on your time zone and the season. IBPAP, the Philippine IT-BPM industry association, reports that the sector employs roughly 1.9 million people — nearly all of them on US-facing shifts. Candidates from the Philippines expect the offset; most have worked it before.

What you need to map before the hire starts: which tasks genuinely require real-time back-and-forth (a live customer call, a Zoom with a vendor), and which only feel that way because you have never written them down. In most EA, bookkeeping, ops, and content roles, the real-time list is shorter than founders expect. Do that audit first — it determines how much overlap you actually need.

The handoff doc: your core async tool

A handoff doc is a short note you write at the end of your day — before you close the laptop, covering three things: what got decided today and why, what you want your hire to work on during their shift, and what they should do if they hit a blocker. It does not need to be long. Two hundred words done every day beats a beautifully formatted template that goes stale in week two.

The 'blocker' instruction is the part most founders skip. If your hire cannot reach you for eight hours and the guidance is 'ping me on Slack,' you have created a pause, not a process. Instead, specify a decision tree: try X first, if that does not resolve it try Y, and if neither works flag it in the log and move to the next task. Write this once per recurring task type and you almost never need to write it again.

Keep the handoff doc in a shared document, not a chat thread. Chat is lossy, things scroll off, context disappears, and a new hire cannot search back through six weeks of Slack to understand why a decision was made. A doc is searchable, appendable, and visible to both parties at any hour.

The decision log: making your reasoning legible

Async work breaks down when a hire makes a reasonable-sounding guess and it turns out to be wrong, because you never told them the actual reasoning. A decision log fixes this. It is a running record, one shared doc, newest entries at the top, of the choices you make that affect the hire's work: how to handle refund requests, which template to use for which client type, what 'urgent' means in your context.

A log like this also shortens onboarding for any future hire. Because the reasoning is written down, not just in your head, a second person can get to competence faster. That payoff compounds over time.

Overlap: use it for blocked work, not status updates

Most US-based founders with Philippines hires settle on one to two hours of overlap per day, usually achieved by the hire starting their shift in the late evening Manila time. That overlap is expensive in terms of your hire's lifestyle, do not fill it with status updates that could be async. Use it for work that genuinely cannot proceed without a real-time conversation: reviewing a draft together, walking through a new process for the first time, or unblocking a decision that is genuinely ambiguous.

If you find your overlap sessions are mostly 'so how did yesterday go,' you have an async problem, not a time-zone problem. Move those questions to the handoff doc and free up the overlap for real work.

For roles where overlap matters more, say, a customer support specialist handling live chat, consider Colombia or Mexico instead. Bogotá runs on US Central time year-round, and Mexico City sits at the same offset as most of the US, so a full US workday overlaps with normal working hours for your hire. The trade-off is cost: Colombian rates run roughly 1.25 times the equivalent Philippines band, and Mexican rates roughly 1.3 times, so if you are weighing a Philippines customer support specialist at $800–1,300 a month against a Colombian equivalent, expect something closer to $1,000–1,625.

Communication norms to set in week one

Set response-time expectations explicitly, in writing, before the first shift. Something like: routine messages get a reply within two hours during the hire's shift; anything marked urgent gets a reply within 30 minutes; anything outside shift hours is acknowledged the next morning. This is not micromanagement, it is the kind of clarity that prevents a hire from feeling obligated to be always-on, which is the burnout path.

Also define what 'done' looks like for recurring tasks. A social media manager who posts three times a week needs to know whether 'done' means scheduled in the tool, published and confirmed, or published and reported in the log. Vague definitions produce vague output. Write the definition once, store it in the same shared doc as the decision log, and update it when the definition changes.

When the system breaks: what to check

If you are regularly waking up to a hire who is blocked, the cause is almost always one of three things: the handoff doc is missing or too vague, the decision tree for blockers was never written, or the role scope is genuinely too wide for async management. The first two are fixable in a day. The third means you may have designed a role that needs more real-time presence than the time zone allows, and the right move is to adjust the scope or the country, not to ask the hire to work at 3 a.m.

A $900-a-month bookkeeper who quits in month two because the async setup was chaotic did not save you anything. The handoff doc you wrote in five minutes is usually why the setup held, or why it didn't.

Where Rolemote fits

If you are still in the hiring phase, Rolemote runs flat-fee overseas talent searches across the Philippines, Colombia, Mexico, South Africa, and Argentina. Candidates are screened on graded work samples and scenario answers, not resumes, the rubric is published: work sample 35%, scenario judgment 25%, experience specificity 20%, written English 15%, salary-band fit 5%. The whole search runs free; you pay a flat fee only when you ask to meet finalists. If nobody clears your bar, a re-run is free.

The reason this matters for async hiring specifically: a work-sample screen tells you something about how a candidate operates without supervision. Someone who can complete a structured task with a clear brief and return something usable is more likely to function well in a handoff-doc-driven setup than someone who interviewed well and then waited to be told what to do.