Scheduling Across The Pacific: California To Philippines
The California-Philippines time gap is usually 15 or 16 hours, depending on the season. Manila is ahead. When it's 9 AM in San Francisco, it's midnight or 1 AM the next day in Manila during standard time, and 10 PM or 11 PM during daylight saving shifts. This isn't a fun window for live meetings. I learned that the hard way in 2019 when I was coordinating a product launch between our San Mateo office and a dev team in Taguig. We scheduled a "quick sync" at 2 PM Pacific. I showed up refreshed. The Manila crew had been up since 4 AM their time. Two of them fell off the Zoom call mid-sentence from exhaustion. That was the day I stopped trying to find overlap and started building around the asymmetry. Pacific Standard Time (PST) is UTC-8. Philippine Time (PHT) is UTC+8. That's a 16-hour span. But California observes daylight saving time from roughly mid-March to early November, switching to PDT (UTC-7). During that window the gap shrinks to 15 hours. The Philippines does not observe DST at all. This means the offset flips every spring and fall, which throws off anyone who has their calendar hard-coded to a single number. There is almost no useful overlap between California and Manila business hours. If you force it, you get maybe 1-2 hours where both sides are working. During PST (November to March), 7 PM to 9 PM in Manila coincides with 3 PM to 5 PM in California. That's the most common window people use. It's late evening for Filipinos but reasonable for Californians. During PDT (spring/summer), the window shifts to 8 PM to 10 PM Manila time, which is worse for the Philippine side. I've seen teams burn out calling it "a small inconvenience." It's not. It's 8 PM on a Tuesday night. People have dinners. They have lives.
The first method is the rotating window approach. Pick a slot that rotates between the two zones every week or two. One week the Californians suffer a late slot. The next week the Filipinos do. Track it. After four rotations, each side has taken equal pain. Without rotation, one team always loses. This is not hypothetical. I managed a project where the Manila team absorbed the bad hours for eight straight months. Morale dropped. Two senior engineers left. That's a real cost. The second method is async-first scheduling. You reduce live meetings to the absolute minimum and push everything else into documented handoffs. Write things down. Record Loom videos. Use shared docs instead of status calls. In my experience, this cuts meeting load by about 60-70 percent and actually improves output quality because people aren't performing in real time. They have time to think. The third method is the staggered sprint. Instead of trying to sync daily, you run in 36-hour handoff waves. California finishes their day and hands off work. Manila picks it up, works through their day, and hands back before California starts again. It creates a near-continuous flow without requiring anyone to be online outside their normal hours. This works best for engineering teams where code commits and PR reviews are the primary coordination mechanism. It does not work for sales calls or client-facing work that requires real-time presence.
The Daylight Saving Trap
Here's something most people miss. When California springs forward or falls back, the gap changes mid-week. If you have a recurring meeting every Wednesday at 4 PM Pacific, during DST transition weeks your Manila counterpart will suddenly find themselves in a different time slot without any calendar update. I once had a weekly standup jump from 4 AM Manila time to 5 AM for two weeks straight because nobody updated the invite template. The team leader complained he couldn't sleep and was making stupid mistakes. A six-second calendar update would have prevented that. Set your recurring invites in UTC, not in local time. UTC doesn't change. It stays stable while both sides shift around it. The biggest mistake is assuming the time difference is static. It changes twice a year. Every time. If you send invites based on PST and don't account for the PDT switch, your meetings drift. The second mistake is assuming overnight work is sustainable. It's not. I've seen teams run the 8 PM-10 PM Manila window for six weeks straight and then collectively crash. Burnout isn't dramatic. It's quiet attrition. People stop volunteering. They do bare minimum. Then they quit. A third pitfall is timezone notation laziness. Writing "3 PM" on an invite without specifying the zone. Outlook does this by default sometimes. I've had multiple incidents where a Filipino developer showed up at 3 PM Manila time thinking it meant 3 PM their time, when the invite actually said 3 PM Pacific. The Californians were already 12 minutes into the presentation. Always write the timezone abbreviation in the invite body. PST, PDT, PHT. Not just the time.
Get the Full Details
Tools I Actually Use
Calendly with timezone detection works if you set it up correctly. It auto-detects the invitee's timezone and shows available slots in their local time. The catch is it only works if both sides use the scheduling link. It breaks down for ad-hoc meetings. For those I use World Time Buddy or the Apple Clock app's world clock feature. World Time Buddy shows both zones simultaneously on a visual slider. It's faster than mental math and prevents the kind of errors that come from calculating offsets in your head during a busy afternoon. For recurring cross-Pacific standups, I set the master calendar event in UTC. Then I have a small Zapier automation that translates it to both PST and PHT in the individual team members' calendars. It took me about 20 minutes to set up the first time. It saves maybe 5 minutes per month in corrections. The ROI is thin on time alone but the ROI on not annoying your team is substantial.
When This Breaks Completely
Async scheduling across this time zone doesn't work for everything. Client calls with decision-makers who expect immediate responses. Crises that need real-time triage. Sales demos where the prospect wants to talk now. For these, you either pay for a person to work graveyard shifts in one zone, or you accept that someone is going to be miserable for a few hours. I recommend being explicit about it. Don't dress it up as "flexibility." Say "this meeting is at 9 PM Manila time and you will need to adjust your evening." People respect honesty more than euphemism. If you're doing this full-time across the Pacific, consider a hybrid model. Have one person based in a middle timezone like Hawaii or even Singapore who serves as the bridge. It adds headcount cost but eliminates the constant late-night/early-morning pain for both core teams. In my experience, one middle-ground coordinator pays for themselves within three months in reduced burnout and fewer missed handoffs.
Bottom Line
The gap is 15-16 hours. There's no trick to make it smaller. The best approach is minimizing live overlap, rotating pain fairly, using UTC for recurring events, and being honest about what requires real-time coordination versus what can wait. I've run Pacific teams for over seven years now. The ones that last are the ones that stop pretending the overlap is easier than it actually is.
