Read the version shown with results
This build uses IANA Time Zone Database 2026f. The source archive is pinned and its derived transition data is bundled with the application. The planner does not call a remote time service at runtime and does not rely on the device’s time-zone database to decide the named-zone transitions.
Plan within 2026–2035
The supported local planning dates run from 1 January 2026 through 31 December 2035. A seven-day search needs its whole range inside those limits. A twelve-week recurrence may extend past the final supported date even when its first date is valid. Out-of-range results are reported rather than presented as verified predictions.
Understand future rule changes
Civil-time policies can change after a data release. The bundled rules describe the best available instructions in that specific release; they cannot guarantee future political decisions. A newer build can therefore produce a different result for a future event. Recheck important schedules when a rule-data update becomes available.
Use the city mapping deliberately
The curated directory contains 32 cities, with aliases that resolve to stable city identities. Each maps to an IANA identifier. The full bundled identifier search supports additional named zones, while the editorial zone directory explains twelve selected rule sets. A city label, an abbreviation, and an offset are not interchangeable fields.
Read examples as dated examples
The reference meeting is 27 October 2026 at 13:00 UTC. City and zone tables contain selected seasonal dates. They illustrate real calculations under the bundled version and are not current-time indicators. Use an explicit meeting date for planning; a device-clock shortcut is only a convenience.
Know the product limits
- Availability comes from your entered hours; it does not check holidays, personal calendars, travel, or willingness to join.
- Projects remain in this browser unless you export or share a copy.
- Calendar downloads contain reviewed events and do not send invitations or keep earlier imports synchronized.
- The recurring preview covers twelve weekly occurrences, not an indefinite series.
Make a result reproducible
Keep the selected IANA identifiers, date, time, duration, ambiguity decisions, and data version. A JSON project backup preserves the settings. If you investigate a mismatch, compare those inputs before treating a different calendar display hour as a failed conversion.
Sources
Follow the original references for the rules and formats used in this guide.