Drag & Drop Meeting Planner

The Draggable Timeline

Quick-Drop Slots

Jump the block to a common UTC start, then fine-tune by dragging.

UTC Start → Local Time, Per Hour

Want an auto-ranked shortlist instead of dragging? Try the AI Meeting Planner.

The Local-Time & Comfort Formula

Standard Offsets (IANA tz database)

No saved slots yet. Drag the block and tap "Save This Slot" to remember up to six.

How to Use the Drag & Drop Planner

1. Add each participant as a chip with their IANA time zone using the panel on the right.
2. Grab the violet meeting block on the 24-hour track and drag it left or right (arrow keys work too).
3. Watch each participant's local start time and green/amber/red comfort dot update live as the block moves.
4. Set the meeting length (30, 60, 90, or 120 minutes); the block widens and the end time is factored into each comfort score.
5. Stop where the fewest dots are red, save the slot, and confirm against everyone's live calendar before booking.

Scheduling by Feel: A Short History

In 2026, a product manager building a launch calendar for collaborators in San Francisco, London, Bengaluru, and Tokyo does not want a ranked list or a spreadsheet of offsets — she wants to grab a meeting block, slide it along the day, and feel where it lands for everyone. The Drag and Drop Meeting Planner is built for exactly that tactile workflow: a 24-hour track, a draggable meeting block, participant chips you place by time zone, and a live green-amber-red comfort indicator under each name that updates the instant the block moves.

Underneath the direct manipulation is the same UTC arithmetic every scheduler relies on. Coordinated Universal Time (UTC) became the world's reference standard in 1972, replacing Greenwich Mean Time (GMT) when the International Telecommunication Union adopted atomic timekeeping with leap seconds. The position of the meeting block on the track is read as a UTC start hour; each participant's local clock is then that UTC hour plus their standard offset, modulo 24. London at UTC+0, New York at UTC-5, Bengaluru at UTC+5:30, and Tokyo at UTC+9 each receive the same block translated into their own wall time.

The time-zone identifiers come from the IANA Time Zone Database (the tz database, zoneinfo, or Olson database, after founder Arthur David Olson). It is the canonical dataset used by Linux, macOS, Java, Python, and the browser's own Intl.DateTimeFormat API, and it names regions with an Area/Location convention such as America/New_York, Europe/London, and Asia/Kolkata. Because the planner draws from the same database your calendar app reads, the local times under each chip match what your operating system would show for the chosen slot.

Comfort is scored the moment the block stops moving. A participant whose local meeting time falls fully inside 9 AM to 6 PM is shown green (good); 7 to 9 AM or 6 to 10 PM is amber (early or late but workable); anything before 7 AM or after 10 PM is red (asleep). This three-band model is deliberately coarse because the value of a drag interface is the feel, not the decimals — you slide until the reds turn amber and the ambers turn green, and you stop where the compromise looks fairest.

India Standard Time, at UTC+5:30, is the half-hour offset that trips up tools built on whole-hour assumptions. Standardised in 1906 around the 82.5 degrees east meridian near Mirzapur, IST means a meeting block whose left edge sits at 12:00 UTC reads 5:30 PM in Bengaluru, not 5:00. The track honours the half hour, so dragging the block one notch (one hour) still lands Bengaluru on the :30, and the comfort band flips precisely when the local time crosses 6:00 PM.

Direct-manipulation scheduling has a long pedigree. The drag-to-resize calendar block was popularised by Google Calendar and Apple iCal in the 2000s, and the multi-participant overlay traces back to Microsoft Outlook's Scheduling Assistant and tools like World Time Buddy and Every Time Zone. What this planner adds is a fairness lens: by surfacing each participant's comfort colour as you drag, it makes the human cost of a slot visible in real time, which the literature on distributed work — GitLab's Remote Work Report, Buffer's State of Remote Work — consistently flags as the difference between a sustainable cadence and quiet burnout.

Daylight Saving Time is the planner's honest footnote. The offsets are standard-time values, so during DST a city shifts an hour: the United States moves on the second Sunday of March and first Sunday of November under the Energy Policy Act of 2005, the European Union on the last Sundays of March and October under EU Directive 2000/84/EC, and India, Japan, and most equatorial regions never change. Because the roster lives in your browser via localStorage, the practical habit is to keep the team saved and re-drag the block after each transition, confirming the final slot against everyone's live calendar before sending the invite.