Skip to content

Global Meeting Planner

Use editable work schedules, future DST checks, supported holiday warnings, and burden scoring to choose a recurring live window your team can actually use.

Direct Answer

A good recurring meeting slot is inside each participant's selected working pattern, avoids sleep and off-days, flags supported holidays and DST offset drift, and does not make the same person absorb every bad hour. TimeNowHub uses transparent scheduling heuristics rather than claiming a universal optimum.

Server-rendered worked result

20:24 Tokyo / Fri, Jul 17 at 11:24 UTC

Score 2/10. Weak recurring live window; consider the rotation or async fallback. Highest burden: Tokyo (12).

TimeNowHub heuristic, not a universal optimum. Scores use editable schedules, sleep/off-day penalties, supported holiday conflicts, DST drift, and repeated-burden fairness.

Tokyo
20:24

Fri, Jul 17 · UTC+09:00

New York City
07:24

Fri, Jul 17 · UTC-04:00

London
12:24

Fri, Jul 17 · UTC+01:00

Recurring meeting decision tool

Add real participant schedules, inspect recurring DST drift and supported holiday conflicts, then share one decision artifact. Names stay in your browser and are never sent in analytics events.

TimeNowHub heuristic, not a universal optimum. Scores use editable schedules, sleep/off-day penalties, supported holiday conflicts, DST drift, and repeated-burden fairness.

Call Score
2/10

Weak recurring live window; consider the rotation or async fallback. Highest burden: New York City (12).

Series scope
6 weekly meetings

No supported DST offset drift is flagged for the selected series.

-12h 0h +12h
Participant

New York City

America/New_York

Work days
Participant

London

Europe/London

Work days
Participant

Tokyo

Asia/Tokyo

Work days
Candidate schedules

Pick a decision artifact

Google Calendar
Async fallback

No strong live window is available for this setup. Use the async handoff workflow for routine updates and reserve live time for decisions.

Selected result
2/10

Weak recurring live window; consider the rotation or async fallback. Highest burden: New York City (12).

  • • outside acceptable hours
  • • preferred hours
Occurrence 1
Fri, Jul 17 at 11:24 UTC
New York City
Fri, Jul 17 · 07:24 · UTC-04:00
Outside acceptable hours

outside acceptable hours

London
Fri, Jul 17 · 12:24 · UTC+01:00
Preferred hours
Tokyo
Fri, Jul 17 · 20:24 · UTC+09:00
Outside acceptable hours

outside acceptable hours

Occurrence 2
Fri, Jul 24 at 11:24 UTC
New York City
Fri, Jul 24 · 07:24 · UTC-04:00
Outside acceptable hours

outside acceptable hours

London
Fri, Jul 24 · 12:24 · UTC+01:00
Preferred hours
Tokyo
Fri, Jul 24 · 20:24 · UTC+09:00
Outside acceptable hours

outside acceptable hours

Occurrence 3
Fri, Jul 31 at 11:24 UTC
New York City
Fri, Jul 31 · 07:24 · UTC-04:00
Outside acceptable hours

outside acceptable hours

London
Fri, Jul 31 · 12:24 · UTC+01:00
Preferred hours
Tokyo
Fri, Jul 31 · 20:24 · UTC+09:00
Outside acceptable hours

outside acceptable hours

Occurrence 4
Fri, Aug 7 at 11:24 UTC
New York City
Fri, Aug 7 · 07:24 · UTC-04:00
Outside acceptable hours

outside acceptable hours

London
Fri, Aug 7 · 12:24 · UTC+01:00
Preferred hours
Tokyo
Fri, Aug 7 · 20:24 · UTC+09:00
Outside acceptable hours

outside acceptable hours

Occurrence 5
Fri, Aug 14 at 11:24 UTC
New York City
Fri, Aug 14 · 07:24 · UTC-04:00
Outside acceptable hours

outside acceptable hours

London
Fri, Aug 14 · 12:24 · UTC+01:00
Preferred hours
Tokyo
Fri, Aug 14 · 20:24 · UTC+09:00
Outside acceptable hours

outside acceptable hours

Occurrence 6
Fri, Aug 21 at 11:24 UTC
New York City
Fri, Aug 21 · 07:24 · UTC-04:00
Outside acceptable hours

outside acceptable hours

London
Fri, Aug 21 · 12:24 · UTC+01:00
Preferred hours
Tokyo
Fri, Aug 21 · 20:24 · UTC+09:00
Outside acceptable hours

outside acceptable hours

Holiday and data coverage

  • New York City: rule-based partial holiday coverage is enabled for US.
  • London: rule-based partial holiday coverage is enabled for GB.
  • Tokyo: rule-based partial holiday coverage is enabled for JP.

Holiday coverage is a rule-based planning hint, not a legal calendar. Unsupported countries and local/regional holidays require a manual unavailable-date check.

New York City

Fri, Jul 17 · 02:54 · UTC-04:00

Sleeping
Off hours
Focus heuristic

This city is outside the strongest concentration bands for live collaboration.

Business runway

0 hours left before 17:00.

London

Fri, Jul 17 · 07:54 · UTC+01:00

Awake
Off hours
Focus heuristic

This city is outside the strongest concentration bands for live collaboration.

Business runway

8 hours left before 17:00.

Tokyo

Fri, Jul 17 · 15:54 · UTC+09:00

Working
Peak focus
Focus heuristic

This city is inside a strong concentration band for decision-heavy work.

Business runway

1.1 hours left before 17:00.

Whose EOD?

Check which teammate is closest to the end of the workday before you lock the meeting.

Async Handoff

Estimate whether the next step should stay async instead of forcing a weak-overlap call.

Work-Hours Heatmap

Use the standalone legacy view, or open the integrated planner overlap tab.

Natural Language Query

Start with a direct scheduling question, then jump back into the planner once the intent is clear.