Working the Overlap Between PST and Philippine Time
Most people trying to coordinate meetings between California and Manila just add twelve hours and call it a day. That works until daylight saving time hits, and then suddenly everyone is showing up an hour early or an hour late because one side thinks they're on PDT and the other is still locked to the old offset. It happens more often than you'd think, and it costs real time fixing it after the fact. Pacific Standard Time is UTC-8. Philippine Time is UTC+8. That means the raw difference is exactly 16 hours when PST is active. When California shifts to PDT, the gap narrows to 15 hours. The Philippines does not observe daylight saving time, so the shifting always comes from the West Coast side. This creates a rotating window of overlap rather than a fixed one. The overlap window when PST is in effect runs from 8:00 AM in Manila to 4:00 PM in Manila, which corresponds to 4:00 PM the previous day through 12:00 AM midnight in Los Angeles. You get exactly eight hours of shared working time, and that's the only window that matters if you're scheduling live calls or real-time collaboration sessions. During PDT, the window slides forward by an hour, giving you nine overlapping hours from 9:00 AM to 5:00 PM Manila time.
I learned this the hard way when I was managing a project where the Manila team had to review deliverables before the Pacific team wrapped their day. We set up a recurring sync at 3:00 PM Manila time, which looked comfortable on paper at 11:00 AM Pacific. Then California flipped to daylight saving time and that same 3:00 PM Manila slot became 12:00 PM PDT, which felt fine for a couple weeks, and then the client in San Francisco started complaining that the call ran too long into their afternoon. We ended up moving it to 2:00 PM Manila time, which gave us a buffer on both sides during the overlap period and eliminated the back-and-forth about timing.
The Practical Scheduling Problem
The main difficulty isn't calculating the time difference. Any good calculator handles that instantly. The actual problem is remembering which offset is currently active and making sure both parties are referencing the same one. I've seen people schedule a meeting for 9:00 AM PST while the other party reads it as 9:00 AM PDT, and the resulting confusion takes longer to resolve than the original coordination would have taken. The best approach is to always anchor your schedules to UTC. Instead of saying "let's meet at 9:00 AM PST," say "the meeting is at 17:00 UTC." Both Manila and Los Angeles can convert that independently without anyone needing to check whether daylight saving time is in effect. It removes the entire class of errors that come from mixing offsets on the same calendar invite. When you're building a recurring schedule, pick a time that works comfortably during the PDT window, not the PST window, because that's the narrower overlap. A 1:00 PM to 3:00 PM Manila slot translates to 9:00 AM to 11:00 AM PDT, which leaves both teams room to breathe. During PST months, that same slot becomes 5:00 AM to 7:00 AM Pacific time, which is brutal, but it's better than having a meeting that works for Manila but pushes into late evening for California.
Get the Full Details
Tooling and Automation
Most calendar platforms let you assign a specific timezone to each event, and they handle the conversion automatically for everyone on the invite list. The catch is that some legacy systems and older email clients don't embed timezone data correctly in invites. I ran into this with a vendor who was using an outdated internal scheduling tool, and half the invites arrived with the wrong local time because the timezone metadata was stripped during transit. The workaround was to include the UTC time explicitly in the body of every invite, formatted as something like "14:00 UTC (06:00 PDT / 22:00 PHT)." It's verbose, but it eliminates the guesswork entirely. For teams that coordinate frequently across these two zones, setting up a shared Google Calendar view with both Pacific and Philippine time overlays is worth the fifteen minutes it takes. You can toggle each timezone on and off, which makes it immediately obvious when a proposed time falls outside the overlap window. If you're building something more custom, the Intl.DateTimeFormat API in JavaScript or the pytz library in Python handles timezone conversions reliably, but you should always validate the results against a known reference point rather than trusting the output blindly.
Common Pitfalls and What They Actually Cost
The single biggest mistake I see is assuming that "PST" in a calendar entry means Pacific Time year-round. It doesn't. PST is only valid from the first Sunday in November through the second Sunday in March. For the rest of the year, the correct abbreviation is PDT. When someone labels an event "PST" in July, there's a fifty-fifty chance they mean Pacific Daylight Time and just used the wrong label, or they actually mean standard time and have scheduled the meeting incorrectly. Either way, the recipient has to ask for clarification, and that friction adds up across dozens of meetings per quarter. Another pitfall is the first week after each daylight saving transition. Systems that cache timezone data or use manual offset calculations can temporarily show the wrong time for about a week until everything synchronizes. I had a deployment pipeline that pulled the current Pacific offset from a hardcoded config file, and it stayed on PST for eleven days after the spring flip. Every automated report generated during that window had timestamps that were an hour off, and the Manila team flagged it because their internal logs showed different times than our export files. The fix was switching to a dynamic timezone lookup instead of a static offset value.
When This Approach Falls Short
Even with perfect timezone handling, the fundamental constraint remains: the overlap window is small and shifting. If your teams need more than four hours of synchronized working time per day, this pairing is not efficient. You're better off either staggering work across a wider range of zones or finding a midpoint location with more compatible hours. Central European Time, for instance, overlaps with both Pacific and Philippine time for roughly six to seven hours depending on the season, which makes coordination significantly easier. Async communication also breaks down when the overlap is too narrow to support meaningful back-and-forth within a single business day. A question sent at 4:00 PM Pacific hits the Manila team at 8:00 AM their time, which is fine, but if they don't respond until 6:00 PM Manila time, that's 2:00 PM Pacific, and you've burned most of your remaining overlap window before getting an answer. In practice, this limits same-day resolution to urgent items and forces everything else into a next-business-day rhythm that slows down iteration. The most practical solution I've found for teams that need consistent daily coordination across these zones is to establish a core synchronous block during the PDT overlap, keep everything else async with clear documentation, and rotate the on-call or live support responsibility so neither side bears the burden of late or early hours exclusively. It's not elegant, but it keeps the collaboration moving without burning people out on one side or the other.
