DST-aware by date
Offsets are calculated for the date you choose using IANA time-zone data. That matters when regions change clocks on different weeks.
Compare local times, see working-hours overlap, and plan confidently across daylight saving changes.
Offsets are calculated for the date you choose using IANA time-zone data. That matters when regions change clocks on different weeks.
If a local time is skipped when clocks move forward, the planner asks you to choose another time instead of silently changing it.
The copied link stores the plan in its URL. SimpleTaskKit does not create a meeting record or store your schedule on a server.
Compare an October meeting while London still observes British Summer Time, then change the date to see the offset after the UK clock change.
Open this exampleInspect a December plan across India and the US East Coast, including the date boundary and the limited overlap between standard working hours.
Open this examplePlan a near-region call between India and Dubai, where neither selected zone changes clocks for daylight saving time during the year.
Open this exampleCompare India and Singapore for a practical Asia working-hours overlap without a seasonal daylight-saving offset change in either zone.
Open this exampleYes. It resolves offsets for the selected date using IANA time-zone data, so seasonal clock changes are reflected.
When clocks move forward, some local times do not exist. When clocks move back, an hour can occur twice; the planner identifies these cases.
No. The green overlap is only a planning guide using 09:00–17:00 in each selected zone. Team preferences and working patterns may differ.