Schedule an International Meeting
The problem
Scheduling across time zones means someone always ends up at an inconvenient hour — usually the person who didn't check carefully. A meeting that's 9pm IST on Monday is 11:30am EST on Monday, but 3:30am AEST on Tuesday. This workflow ensures you find the right window, convert it precisely, and share it in a format that cannot be misread.
What you'll accomplish
Tools in this workflow
Follow this workflow in sequence to move from question to decision without losing context.
Step-by-step
Why this workflow works
The three steps are ordered to prevent the most common failure modes. Starting with the World Clock gives you a real-time overlap picture before you propose anything — you don't waste time suggesting a slot that's clearly unsuitable. The Time Zone Converter then validates your proposed slot precisely, including the calendar date for each participant. The Unix timestamp at the end acts as a single source of truth that eliminates human misreading of AM/PM and timezone abbreviations. Most scheduling failures happen not because people don't know timezones exist, but because they forget to check the calendar date change or the DST offset difference.
Frequently asked questions
What is the best time window for India and US East Coast meetings?
The overlap between IST (UTC+5:30) and EST (UTC-5) or EDT (UTC-4) is narrow. For IST business hours (9am–6pm) vs EST business hours (9am–6pm): 7:30–11:30pm IST maps to 9am–1pm EST. The practical sweet spot is 8:00–9:30pm IST, which is 9:30–11am EST — early enough for the US East Coast morning and late but manageable for India. For PST (UTC-8), the gap is three hours wider — there's essentially no good overlap for daily meetings.
What is a Unix timestamp and why is it better than writing '3pm IST'?
A Unix timestamp is a single integer representing the number of seconds since midnight January 1, 1970 UTC. For example, 1748000000 maps to one specific moment in time universally — it can never be misread as 3pm vs 15:00 or mistaken for a different timezone. '3pm IST' can be misread, mistyped, or misunderstood if the recipient doesn't know IST is UTC+5:30. '1748000000' is unambiguous. Most modern calendar apps, Slack, and developer tools understand Unix timestamps natively.
How does daylight saving time affect international meeting scheduling?
Daylight saving time (DST) shifts clocks by +1 hour in countries that observe it (US, UK, most of Europe, Australia). India does NOT observe DST — IST is always UTC+5:30. This means the offset between India and the US changes twice per year: India–US East is UTC+10:30 during US Eastern Standard Time (Nov–Mar) and UTC+9:30 during US Eastern Daylight Time (Mar–Nov). If you set a recurring meeting in January at 8pm IST, it will appear one hour different on the US side after March DST kicks in.
Which time zones should I know for common India–global meeting pairs?
India (IST) is UTC+5:30. Key offsets from IST: Singapore (SGT, UTC+8) is IST+2:30. Dubai (GST, UTC+4) is IST-1:30. London (GMT, UTC+0 winter / UTC+1 summer) is IST-5:30 or -4:30. New York (EST, UTC-5 winter / -4 summer) is IST-10:30 or -9:30. San Francisco (PST, UTC-8 / -7 summer) is IST-13:30 or -12:30. Sydney (AEST, UTC+10 / +11 summer) is IST+4:30 or +5:30.
How do I share a meeting time so no one misreads it?
Include the time in at least three formats: (1) your local time with full timezone name e.g. '3:00 PM IST (India Standard Time)', (2) UTC equivalent e.g. '09:30 UTC', and (3) the Unix timestamp e.g. '1748001000'. Also explicitly state the calendar date for every participant's timezone — a meeting on Monday evening IST is Tuesday morning for Sydney. If you're sending a calendar invite, let Google Calendar or Outlook handle the timezone conversion — don't type local times in the event description, use the timezone field.