Philippines staffing guide
Design the Manila Cutoff Handoff Around One 4 p.m. Rule
A single cutoff time, a written acceptance test, and a next-morning review keep work from falling between two time zones.
Published · 7 minute read
On this page
Time-zone handoffs fail in the gap between "sent" and "accepted." The Manila assistant finishes at 4 p.m. local, the U.S. owner starts six hours later, and a task that was half-complete sits in a shared folder with no note. One cutoff rule, applied every day, removes most of that ambiguity without requiring anyone to work longer hours.
Pick a cutoff and protect it
Choose the time after which new work will be prepared but not started until the next shift. The cutoff should leave enough room for the assistant to write a handoff note and for the owner to triage before their own day fills. Publish it in both time zones and put it on the calendar as a recurring event. A cutoff that moves whenever someone is busy is not a cutoff.
Define what "handed off" means
A task is handed off when the next owner can see the goal, the work completed, the exact stopping point, the evidence, and the next action. A folder of half-edited files is not a handoff. Add a short acceptance test: can the receiver continue for fifteen minutes without asking a question? If not, the note is incomplete. This test is blunt, but it surfaces missing context faster than a long template.
Use a single handoff record
Keep one running document per client or work lane with a row per open item. Columns should include the task, owner, state, last verified action, next action, and the date the next action is due. The assistant updates it before leaving; the owner updates it before starting. Avoid parallel notes in email, chat, and a spreadsheet, because the newest version becomes impossible to identify.
Handle the urgent exception narrowly
Some work cannot wait for the next shift: a security report, a payroll cutoff, a customer commitment that expires overnight. Name those categories and the escalation channel. For everything else, the cutoff holds. If urgent exceptions become routine, the queue is mis-scoped or the owner is using the exception path to avoid planning. Review the exception log monthly.
Review the overnight result first
The owner's first fifteen minutes should be spent accepting, returning, or reprioritizing the handoff, not discovering it. Returned items need a reason code so the assistant can improve the brief. Accepted items move to the next state. This short ritual creates a feedback loop that is impossible when handoffs are scattered across chat threads.
Measure the gap, not the effort
Track items that waited more than one shift for acceptance, items returned for missing context, and urgent exceptions used. Pair those counts with the number of handoffs made. A low return rate with a high wait time suggests the owner is the bottleneck; a high return rate suggests the brief or the evidence standard needs work.