ZoneGrid

Best meeting time across multiple time zones (without burning people out)

• 7–9 min read • by ZoneGrid
remote work scheduling fairness

There is no single “best” meeting time when your team spans three continents. What you want is a repeatable rule that keeps meetings predictable and fair, while protecting focus time and sleep.

Try a real multi-timezone setup in ZoneGrid
Open a preconfigured view (adjust parameters to your real format):
Open example overlap Open blank tool

The principle: optimize for fairness, not convenience

If the same region always pays the cost (early mornings or late evenings), morale drops fast. Fair scheduling means you distribute inconvenience over time and prefer async when the meeting isn’t essential.

Start with the right inputs

1) Working hours per person (or per region)

Time zones alone are misleading. Ask each region for a default window (for example 09:00–17:00), and allow exceptions for parents, part-time schedules, or local constraints.

2) Meeting criticality

Treat recurring meetings like expenses. If a meeting is not clearly worth the cost across time zones, make it async. A useful question: “What decision will we make that we can’t make async?”

Three patterns that work

Pattern A: Core hours

Pick a 2–4 hour overlap that everyone agrees is “meeting-safe” and keep most recurring meetings inside that window. Core hours reduce chaos and make planning easier.

  • Best for: teams with consistent overlap.
  • Tradeoff: someone may still be slightly inconvenienced, but it’s predictable.

Pattern B: Rotation

If overlap exists but is painful for one region, rotate the meeting time every week or every month. Rotation is the simplest fairness mechanism.

  • Best for: teams with one large time gap (e.g. Americas ↔ Asia).
  • Rule: rotate on a schedule, not ad-hoc.

Pattern C: Async-first (default)

Many meetings are status updates in disguise. Replace them with a short async template: agenda → updates → risks → decisions needed. Then run a short sync only when a real decision is blocked.

  • Best for: low-criticality or high-frequency meetings.
  • Bonus: async creates a written record.

A simple decision rule

Use this rule for recurring meetings:

Rule of thumb
If the overlap window is ≥ 2 hours, use core hours or rotation. If it is < 2 hours, default to async (or rotate sparingly for critical decisions).

Example: LA + Warsaw + Tokyo

This trio often has limited overlap. The “best” time depends on whether you optimize for: (a) consistent core hours, (b) fairness via rotation, or (c) minimizing meetings.

Open the example in ZoneGrid
View overlap Read overlap workflow

Share your team setup

If your configuration lives in the URL, you can paste it into docs and everyone sees the same view. That saves time and prevents “which settings did you use?” confusion.

/app.html?tz=America/Los_Angeles,Europe/Warsaw,Asia/Tokyo&hours=9-17

A quick checklist for healthy scheduling

  • Define default working hours per region.
  • Decide which meetings must be synchronous.
  • Use core hours when overlap is decent.
  • Rotate when one region repeatedly pays the price.
  • Prefer async for status updates and low-impact calls.
  • Review recurring meetings monthly.
Want a faster way to decide?
Open your team time zones in ZoneGrid and share the URL in your team docs.
Open ZoneGrid Back to blog