Start with the task, not a time-zone abbreviation
Convert one date when you already know the anchor time. Use working-hours overlap when you need a window. Check 12 weekly occurrences before repeating a meeting. Finish with a time summary or ICS download.
Choose an IANA zone such as America/New_York, not “EST” or a city name alone. City labels are shorthand for the final part of that identifier, not an address lookup. America/Indiana/Indianapolis and America/Indiana/Knox are distinct. If your exact city is not listed, select an IANA zone that represents its time rules.
Missing and repeated local times
New York’s 2026-03-08 02:30 does not exist because the clock jumps forward. Team Time Kit stops and asks for another time; it never quietly moves the meeting. On 2026-11-01, 01:30 occurs twice: first at UTC−04:00 (05:30 UTC), then at UTC−05:00 (06:30 UTC). You must select one.
For a 12-week series, each problematic occurrence is shown. All twelve must be valid before download. A missing time requires a different anchor time or start date. A repeated time needs an offset choice for that date.
Overlap is local working time
Workdays identify the local day a shift begins. A Monday shift of 23:00–07:00 continues into Tuesday. The closing endpoint is excluded. During a fall-back transition, both occurrences of local working minutes are included; during spring-forward, missing minutes do not exist. A window must fit the full meeting duration.
The search covers one calendar date in the first location, which may be 23, 24 or 25 hours. It examines one-minute UTC steps against every location’s shift. Dates with an ambiguous or nonexistent anchor midnight are rejected with a message. Equal shift endpoints are rejected; 24-hour shifts, multiple daily shifts, breaks, holidays and booked calendars are outside this version.
Original worked examples
- New York 2026-03-02 09:00 → London 14:00. March 9 → London 13:00. March 30 → London 14:00. The same New York clock time does not mean the same London clock time every week.
- 2026-06-01 12:00 UTC → Kolkata 17:30 and Kathmandu 17:45. Fractional-hour offsets are kept exactly.
- Los Angeles 2026-01-15 16:00 → Tokyo 2026-01-16 09:00, the next day.
- A Monday UTC shift 23:00–07:00 overlaps a second UTC shift 01:00–05:00 on Tuesday from 01:00 to 05:00.
What an ICS file contains
Each event has UTC DTSTART and DTEND values, a creation timestamp, a stable event identifier and a generic “Team time” title. A weekly export contains twelve independent VEVENTs, with no RRULE, names or attendees. Reimporting an identical event can still behave differently across calendar apps; review duplicates before importing. This tool does not connect to, read, or write a calendar account.
Time-zone data and supported range
Version 1.0.0 uses the browser’s native Intl.DateTimeFormat, backed by the browser or operating system’s maintained ICU/IANA time-zone data. There is no bundled third-party JavaScript time-zone library or external runtime request. Browsers do not expose a reliable tzdb version; this site does not invent one. The independent Node validation used Node 24.20.0, ICU 78.3 and tzdb 2026c. Your browser’s data can differ.
The core supports dates from 2000 through 2100; the date picker stops at October 15, 2100 to leave space for twelve weekly dates. Government rule changes can change future results. Update your browser, and regenerate a series when rules change. One-minute precision, 2–8 locations and 5–480-minute meetings are supported.
Sources
- IANA Time Zone Database — the source of regional civil-time rules.
- ECMA-402: Intl.DateTimeFormat — the native internationalization API used here.
- RFC 5545: iCalendar — UTC event fields and file format.
- World Time Buddy features and timeanddate meeting-planner help — product research references. Team Time Kit’s design, examples and code are original; no endorsement is implied.
Method and examples reviewed October 9, 2026. This suite plans meeting times; it does not track billable hours or create event run-of-show timelines.