Scheduling Across Time Zones — A Practical Guide

If you work with people in other time zones, you’ve almost certainly missed a meeting or sent a message at 3 AM someone else’s time. Timezone math is deceptively tricky — here’s how to get it right.

Think in UTC

UTC (Coordinated Universal Time) is the global reference point. It doesn’t observe daylight saving time and never shifts. When you store, communicate, or log times, UTC eliminates ambiguity.

• Store timestamps in UTC in your database. Convert to local time only for display.
• Include the timezone offset when sharing times: “2 PM EST (UTC-5)” is unambiguous; “2 PM” is not.
• Use ISO 8601 format in code and APIs: 2026-03-28T14:00:00Z (the Z means UTC).

The Daylight Saving Time Trap

DST is the single biggest source of timezone bugs. Key things to know:

• Not all countries observe DST. Arizona, Hawaii, Saskatchewan, Iceland, Japan, and most of Asia and Africa do not.
• DST transitions happen on different dates worldwide. The US and Europe switch on different weekends, creating a period where the offset between them changes.
• When clocks “fall back,” the same local time occurs twice. When they “spring forward,” one hour of local time doesn’t exist at all.
• The abbreviation “EST” means UTC-5 (winter), while “EDT” means UTC-4 (summer). Using “EST” year-round is a common error.

A recurring meeting at “10 AM New York time” will shift by one hour relative to UTC twice a year. If your counterpart is in a location without DST, the meeting time changes for them.

Common Timezone Abbreviations

Abbreviations are ambiguous — “CST” could mean US Central, China Standard, or Cuba Standard Time. Prefer IANA identifiers like America/New_York or Asia/Tokyo in code. For human communication, include the UTC offset.

• PT (Pacific Time) — UTC-8 / UTC-7
• ET (Eastern Time) — UTC-5 / UTC-4
• GMT/UTC — UTC+0
• CET (Central European) — UTC+1 / UTC+2
• IST (India Standard) — UTC+5:30 (no DST)
• JST (Japan Standard) — UTC+9 (no DST)
• AEST (Australian Eastern) — UTC+10 / UTC+11

Best Practices for Distributed Teams

• Establish overlap hours — find 2–4 hours where everyone is awake and protect that window for synchronous work.
• Rotate meeting times — don’t make the same timezone always take the inconvenient slot.
• Put timezone info in your calendar invite — most calendar apps handle conversion automatically, but stating the timezone explicitly prevents errors when forwarding.
• Default to async — if something can be a written message instead of a meeting, the timezone problem disappears.
• Use a world clock — keep your teammates’ local times visible so you develop intuition for their working hours.

In Code: Use Libraries

// JavaScript — use Intl or a library, never manual offset math
new Date().toLocaleString("en-US", { timeZone: "America/Vancouver" });

// Store in UTC
const utc = new Date().toISOString(); // "2026-03-28T21:00:00.000Z"

Never do manual offset arithmetic (adding or subtracting hours). DST rules change — governments update them with as little as a few weeks’ notice. Let a maintained timezone database handle it.

Related Tools

• Time Zone Converter — convert times between any time zones instantly
• Meeting Cost Calculator — calculate the true cost of cross-timezone meetings