huddl

Guides

How do we plan across time zones?

Propose instants carefully, check the displayed local date, and write travel or remote-meeting expectations clearly.

On this page

Follow the guide with these controlled fictional examples from the current application.

Huddl product screen showing time options in the When calendar
Current Huddl example: time options in the When calendar. Fictional people and planning details are shown.
Huddl product screen showing reviewing time options in Updates
Current Huddl example: reviewing time options in Updates. Fictional people and planning details are shown.

Read the date as the viewer sees it

Huddl availability schedule in the current app, using a fictional Saturday picnic example
Example: availability schedule for a fictional Saturday picnic in the current Huddl app.

Huddl stores time selections with their source-zone interpretation and displays applicable dates for the viewer. Around midnight, one shared instant can fall on different calendar days for different people.

Before responding, check the full date and local time shown on your device. A familiar label such as Friday evening may not mean the same local day elsewhere.

Write the shared expectation

  1. Add future options from a known source time zone.
  2. Ask remote participants to verify their displayed local time.
  3. Put the final call or arrival expectation in the plan context.
  4. Recheck the current plan after daylight-saving or travel changes.

Do not rely on abbreviations alone

  • Prefer a full date and location context.
  • Avoid ambiguous abbreviations such as CST without a city or offset.
  • Confirm fixed-event times with the authoritative organizer.
  • Use direct contact when a traveler is already in motion.

Put it into practice