Articles · Productivity
Find a meeting hour that survives daylight saving
Karachi at 7 PM is not always London at 3 PM in your head, and New York is not UTC−5 in July. Teams that hardcode offsets ship the wrong slide twice a year. A planner that stores Asia/Karachi, Europe/London, and America/New_York, then converts with the selected calendar date, is how you stop guessing. Search by city, country, or IANA id from a static list; internally the zone id is what matters.
Why this is worth doing in the browser
DevNestro’s Time Zone Meeting Planner never assigns New York = UTC−5. It uses the host time-zone database through TimeZoneInfo / equivalent instant conversion so DST and historical rules apply to the date you picked. Each participant has work start and end (default 09:00–17:00). Duration is 15 to 90 minutes. The grid lists local times and marks windows that sit inside every working-hour range. If none overlap, you still see the closest slots labelled Outside some working hours. Copy Schedule emits a plain-text agenda. Download .ics builds a standard calendar file in the browser; Google Calendar API is not required.
How to use the tool
Pick a date, add zones, set hours, choose duration, find times. Copy the text into chat or download .ics. Use Notepad if you want to keep talking points on the device, or Date Difference when the question is duration rather than clock time.
- Add IANA zones, not a handwritten UTC offset.
- Change the date before you trust a summer versus winter row.
- Read the Outside some working hours label instead of forcing a 7 AM on someone.
- Download .ics only after the group agreed on the instant.
Privacy
Participant labels and working hours stay in the page session. They are not uploaded and are not sent to analytics.
Stop arguing about offsets. Open the Meeting Time Planner, pick a date, and copy a schedule that uses real IANA zones.