One instant. Every local schedule.
One instant. Every local schedule.
Organizer local time, in 24-hour notation.
Choose or type a runtime-supported IANA identifier, such as Asia/Dubai. Abbreviations such as CST are ambiguous and are not accepted.
Whole elapsed minutes from one through 1440. The end is exclusive.
Team meeting
2026-06-10T05:00:00.000Z
End: 2026-06-10T06:00:00.000Z
At least one location has occupied minutes outside its selected work window.
Organizer: Asia/Dubai; 2026-06-10 at 09:00.
Resolution: unique. Offset at start: UTC+04:00; at end: UTC+04:00.
Organizer end: 2026-06-10 at 10:00.
The end is exclusive. Date shifts below compare each local start date with the organizer’s entered date. Timezone rules come from the installed browser/runtime. Keep it updated and reconfirm future local times when rules change; the calendar download fixes the selected UTC instants.
Each card shows both real endpoints. A workday checkbox selects the local day on which a work window starts. Overnight windows continue into the next day. Holidays, leave and calendar bookings are not inferred.
America/New_York
Start: 2026-06-10 · 01:00 · UTC-04:00
End: 2026-06-10 · 02:00 · UTC-04:00
Start date shift: 0 day(s).
Local work window: 09:00 to 17:00; starting weekdays: Mon, Tue, Wed, Thu, Fri.
Outside selected hours for part or all of this meeting
Europe/London
Start: 2026-06-10 · 06:00 · UTC+01:00
End: 2026-06-10 · 07:00 · UTC+01:00
Start date shift: 0 day(s).
Local work window: 09:00 to 17:00; starting weekdays: Mon, Tue, Wed, Thu, Fri.
Outside selected hours for part or all of this meeting
Asia/Dubai
Start: 2026-06-10 · 09:00 · UTC+04:00
End: 2026-06-10 · 10:00 · UTC+04:00
Start date shift: 0 day(s).
Local work window: 09:00 to 17:00; starting weekdays: Mon, Tue, Wed, Thu, Fri.
Entire meeting fits
Asia/Kolkata
Start: 2026-06-10 · 10:30 · UTC+05:30
End: 2026-06-10 · 11:30 · UTC+05:30
Start date shift: 0 day(s).
Local work window: 09:00 to 17:00; starting weekdays: Mon, Tue, Wed, Thu, Fri.
Entire meeting fits
Use the source date and named zone. A skipped time is rejected; a repeated time requires the selected occurrence. Offsets come from installed runtime timezone data.
The end is the start plus an elapsed minute count, even if a local clock jumps forward or backward. The end endpoint is excluded from occupied minutes.
Each location uses its own offset at each instant. Every occupied minute must belong to its local work window and an enabled starting weekday; overnight windows continue from that weekday.
Check forty-eight starts, spaced by thirty elapsed minutes, over the next twenty-four elapsed hours from the selected instant. Each candidate must fit the entire meeting in every selected work window. Up to twelve matches are shown; this grid does not guarantee every possible start or check calendar bookings.
Resolve an organizer’s named timezone and compare the same real start and end in each configured location. Local dates and endpoint offsets remain visible, so a next-day or previous-day meeting is easy to identify.
Inspect skipped and repeated organizer times, choose a repeated occurrence deliberately and keep elapsed duration separate from wall-clock labels. Half-hour and quarter-hour offsets are supported through named timezone rules.
Model separate local work windows and starting weekdays for each location. Overnight windows continue from their selected starting day, and the entire elapsed interval must fit before a location receives a positive fit result.
A local date and clock label can be interpreted with a candidate source offset to obtain an instant . The candidate must convert back into exactly the entered local date and time under the named zone’s rules. A valid unique time has one matching instant, a skipped time has none, and a repeated time can have two. The planner does not assume that a current offset remains valid for the entered date.
The original organizer entry is the morning of June 10, 2026, at nine o’clock in Asia/Dubai. Under the applicable offset, this resolves to five o’clock UTC on that date. A sixty-minute meeting ends one elapsed hour later. London, New York and Mumbai each display that same pair of instants through their own named-zone projections. Their clock labels are different, but the event is shared. Work-window results then depend on each location’s configured schedule rather than on a single global office-hour label.
On the demonstrated autumn clock-change date, the organizer label at one thirty in America/New_York occurs twice. The earlier instant precedes the later instant by one elapsed hour. Selecting either occurrence gives a concrete starting point; the default unique-time setting rejects the unresolved choice. The report retains both UTC alternatives, so a recipient can verify which one was selected. This is a chronological distinction and does not rely on guessing an abbreviation from the local clock text.
For a location , its local projection is . The offset depends on the instant, so start and end can use different values. A meeting crossing a seasonal change can appear longer or shorter when subtracting local clock labels, while the elapsed interval stays fixed. A date-line projection may start on the previous or next local date. The displayed date-shift count compares local start dates with the organizer’s entered date and is separate from elapsed duration.
The work predicate indicates whether an occupied minute belongs to a configured local window and enabled starting weekday. A location fits only if this holds throughout the minute-aligned meeting. The optional slot search evaluates forty-eight starts on a thirty-minute elapsed grid; it does not search every possible minute. Overnight windows are anchored to the day they start, and the exclusive end avoids rejecting a meeting merely because its final endpoint equals closing time.
Compare several local schedules with the complete meeting duration in view. Labels and windows are editable, allowing different shifts and working weeks without assuming that every participant follows the same office hours.
Use explicit repeated-time examples and endpoint offsets before publishing a meeting time. The original fourteen-city comparison remains available for a broader overview, while the default group keeps the editable workflow manageable.
See why a location name, calendar date and wall time are needed together. Compare elapsed duration with local clock movement and understand why a fixed UTC instant can project onto different local calendar dates.
Enter a valid date from 2000 through 2099, a minute-aligned local time and a supported IANA timezone identifier. Keep the source zone explicit rather than inferring it from your device. If the time is repeated by a clock change, select the earlier or later occurrence. If the time is skipped, choose a different local time; the planner does not silently move it.
Choose a whole elapsed duration from one through 1440 minutes, then edit participant labels, named zones, work start/end and work starting weekdays. An end earlier than its start creates an overnight window anchored to the selected starting weekday. Inspect both real endpoints and whether the entire meeting fits each local work window. The original fourteen-city comparison remains available as a preset.
Optionally search the next twenty-four elapsed hours on a thirty-minute start grid. Each candidate must fit the whole meeting in every configured window; the search does not inspect personal calendars. Select a candidate, review its exact UTC instant and occurrence, then copy, share, download CSV or save a one-off UTC calendar event. Print or save PDF for the visible report and selected working.
Copy all location records or generate a link containing active planner settings. Review the meeting title and location labels before sharing a link, because these fields are included. Search suggestions are recomputed from the receiving browser’s timezone rules.
CSV retains complete numerical and literal meeting context. The calendar file contains a one-off UTC event with an exclusive end and a descriptive report. Downloading it does not contact participants, invite attendees or publish the meeting.
Use Print / Save PDF to capture the current report, location cards and selected working. The editor controls and slot-search interface are excluded from the printed record. Review browser print scale and destination before saving or printing.
The Toolarithm Timezone Meeting Planner translates a one-off organizer entry into a concrete UTC interval and readable local projections. It preserves the original Dubai morning example and makes the original fourteen-city catalog available as a preset. The default editable group starts with a smaller set of locations so individual labels, named zones and working windows are easy to inspect. Additional supported IANA identifiers can be typed, and the planner supports up to twenty location rows. The organizer date and timezone remain explicit throughout the report rather than being inferred from the computer running the page.
Local wall time and actual time are treated as different pieces of information. Candidate offsets are checked around the source date and each candidate is round-tripped through the named zone. A skipped label is rejected, while a repeated label requires an earlier or later occurrence. The meeting end is calculated by adding whole elapsed minutes to the selected instant. Each location’s start and end are then projected independently, retaining local dates, clock labels and endpoint offsets. A timezone rule change within the displayed interval is identified rather than hidden behind a single assumed offset.
Availability is an explicit schedule model. Each location defines its own work start, work end and starting weekdays. Overnight windows continue into the next local date from an enabled starting day, and every occupied minute must fit for a positive whole-meeting result. The optional search tests a finite elapsed-time grid over the next twenty-four hours and reports only grid matches. It does not inspect private calendars, infer holidays or guarantee every possible meeting start. A selected suggestion is loaded with the correct repeated-time occurrence so that its actual instant remains stable.
Complete copying, CSV and shared settings keep source interpretation and local schedules reviewable. A calendar download creates a one-off UTC event with a unique identity and exclusive end, without sending invitations or publishing anything. The installed browser or server timezone database supplies location rules; those rules can differ across versions and change following political decisions. Keep software updated and reconfirm future local times when necessary. A saved UTC event fixes the selected instants, while the local projections may change if regional timezone rules are updated later.
Written and maintained by the Toolarithm editorial team. No review date is shown without a maintained editorial record. No independent professional review is claimed.
Conversion factors are normalized to canonical units and checked in both directions. Exact definitions and offset formulas are preferred over rounded lookup values.
Read the editorial methodologyReview dates change only after a substantive method or content check.
Keep building