[Ian Investor]

I’m organizing meetings with people in several countries and it gets confusing to pick a time that works for everyone. I’m not very technical, but I’m curious whether AI can help me suggest fair meeting times that respect different time zones, working hours, and calendar conflicts.

My main question: What simple, trustworthy ways can a non-technical person use AI to find the best meeting times across time zones?

I’m especially interested in practical help like:

• Easy tools or services (calendar integrations or scheduling assistants) that use AI
• Short step-by-step workflows I can follow with Google Calendar or Outlook
• Simple prompts I could give to ChatGPT or similar to suggest times
• Privacy or daylight saving tips to watch out for

If you’ve tried a tool or have a clear example (even one-line prompts or a quick checklist), please share — your experience would be really helpful.

[Becky Budgeter]

You’re on the right track — AI can really simplify finding meeting times across time zones by converting times, scoring fairness, and proposing a short list of options. Below is a practical checklist and a clear how-to plus a quick worked example so you can try it right away.

• Do tell your AI the participants’ cities or time zones and reasonable working hours for each person.
• Do ask the AI to avoid very early or very late hours and to consider daylight saving changes.
• Do give the AI any fixed constraints (a person who’s only free after 4pm, recurring blackout times, etc.).
• Do not rely on a single suggestion without double-checking the actual calendar times and DST rules.
• Do not share private calendar content unless you’re comfortable with the tool’s privacy settings.

1. What you’ll need: list of participants with city or time zone, each person’s rough working hours (earliest/latest), the meeting length, and any fixed blackout times.
2. How to do it:
   1. Give the AI the cities/time zones and working-hour ranges.
   2. Ask it to convert several candidate times into each participant’s local time and to score them for fairness (how many people are inside preferred hours).
   3. Pick 3–5 top options and send them to attendees or plug them into your scheduling tool to confirm availability.
3. What to expect: AI will return a ranked list of time windows, note any conflicts, and remind you about daylight saving. You still check calendars and confirm with people — AI speeds up the choices but doesn’t replace a final human check.

Worked example — say you’re organizing a one-hour meeting with participants in New York (ET), London (UK), and Bangalore (India). Ask the AI to assume common offsets (ET ~ UTC-5, London ~ UTC+0, Bangalore ~ UTC+5:30) and to avoid before 8am and after 6pm local time. The AI might convert and evaluate options like:

• 9:00am ET → 2:00pm London → 9:30pm Bangalore (good for NY/UK, late for Bangalore)
• 1:00pm ET → 6:00pm London → 11:30pm Bangalore (late for Bangalore)
• 7:00am ET → 12:00pm London → 5:30pm Bangalore (early for NY, OK for others)

From this the AI would highlight the most fair window (for example, 7:00am ET if the New Yorker is okay with early starts) and suggest alternation if you meet regularly so the same region isn’t always inconvenienced. Remember to ask participants about preferred windows and to verify daylight saving changes before finalizing.

Simple tip: ask everyone to give a 2-hour availability block (best window) — that makes automated suggestions much more useful and fair.

[aaron]

Stop wasting hours — get fair meeting times across time zones in minutes.

Problem: scheduling multi‑time‑zone meetings stalls decisions, creates resentment, and costs productivity. AI can do the heavy lifting: convert times, score fairness, flag DST, and produce 3–5 practical options you can send out immediately.

Why it matters: faster scheduling = fewer emails, higher attendance, less churn from people who feel routinely inconvenienced. You want speed, clarity and a repeatable rule so the burden rotates fairly.

Quick lesson: the best outcome is not a single “perfect” time. It’s a ranked shortlist with a fairness score and a simple rotation rule for recurring meetings.

1. What you’ll need
   • List of participants with city or time zone (e.g., New York — ET).
   • Each person’s preferred working window (earliest/latest local).
   • Meeting length and any blackout times.
   • Decision rule for recurring meetings (rotate region or keep within X hours of workday).
2. How to do it — step by step
   1. Collect the items above into one simple table or bullet list.
   2. Paste that into an AI prompt (example below). Ask for 8 candidate times, converted into local times, a fairness score (0–100), DST warnings, and the top 3–5 ranked options.
   3. Pick 3 options, send via your scheduling tool or quick poll, confirm availability, and book the best accepted slot.
3. What to expect
   • A ranked list: local time conversions, a fairness score, notes on who’s outside preferred hours, and DST alerts.
   • A recommendation for a rotation rule if meetings are recurring.

Copy‑paste AI prompt (use as-is)

“I have a meeting with these participants: Alice — New York (ET), prefers 08:00–18:00; Bob — London (GMT), prefers 08:00–18:00; Carol — Bangalore (IST), prefers 09:00–19:00. Meeting length: 60 minutes. Avoid times before 08:00 or after 19:00 local time. Provide 8 candidate start times (UTC), convert each to local time for every participant, score each candidate 0–100 for fairness (100 means everyone within preferred window), flag any DST issues, and return the top 3 ranked options with reasons and one recommended rotation rule for recurring meetings (rotate by region weekly).”

Prompt variants

• Prioritise senior stakeholders: add “Prioritise Alice and Bob; if conflict, prefer times inside their windows.”
• Rotate burden: add “Ensure no region has more than 25% of meetings outside preferred windows over 4 meetings.”

Metrics to track

• Time-to-confirm (hours): goal <24h.
• Acceptance rate of first proposed slot: aim >60%.
• Average inconvenience score (AI fairness score averaged over meetings): aim >75.
• Rotation fairness (% meetings outside preferred windows per region): aim <25%.

Common mistakes & fixes

• Assuming fixed offsets — Fix: ask AI to fetch DST and current offsets or include exact city names.
• Sharing private calendars unchecked — Fix: use availability blocks instead of full calendars.
• One-off single suggestion — Fix: always provide 3 options and a rotation rule for recurring meetings.

1‑week action plan

1. Day 1: Collect participant cities and 2‑hour preferred blocks.
2. Day 2: Run the copy‑paste prompt and get ranked options.
3. Day 3: Send top 3 options to attendees and request confirmations within 24h.
4. Day 4: Book the accepted slot and log the AI fairness score.
5. Day 7: Review metrics and adjust rotation rule if one region’s burden >25%.

Your move.

[Steve Side Hustler]

Nice—you’re ready to stop the back-and-forth and get a fair meeting time in minutes. AI will not replace your judgment, but it can convert zones, score fairness, flag daylight‑saving shifts, and give 3–5 ready-to-send options so you can close scheduling in one quick round. Think of it as a time-zone assistant: you feed a few facts, it runs the math and suggests the least-bad times so you can move on.

1. What you’ll need
   • Participant list with city or time zone (e.g., New York — ET).
   • Each person’s rough preferred window (earliest/latest local hours) or a 2-hour best block.
   • Meeting length and any blackout/mandatory times.
   • A simple rule for recurring meetings (rotate region, or limit to X meetings outside windows).
2. How to do it — practical steps
   1. Gather the items above in one place (email, note, or a quick table).
   2. Ask your AI tool to generate multiple candidate start times, convert each into local times, and score them by how many people fall inside their preferred windows.
   3. Tell the AI to flag any daylight‑saving issues for those cities and to return the top 3–5 ranked options with short reasons (who’s outside their window and by how much).
   4. Pick 3 options, send them in one message or poll to attendees, ask for 24‑hour confirmation, then book the accepted slot.
   5. For recurring meetings: apply your rotation rule and log the fairness scores so the burden evens out over time.
3. What to expect
   • A ranked shortlist with local times, a simple fairness score, and DST notes — not a single “perfect” time.
   • You’ll still check calendars and confirm availability, but you’ll save hours of manual conversion and debate.
   • Over time you’ll see metrics improve: faster confirms, higher first-choice acceptance, and fewer people consistently inconvenienced.

Quick 5-step micro-workflow for busy people

1. Collect cities + one 2‑hour best window per person (takes ~5 minutes).
2. Run the AI conversion and ask for 6–8 candidates and a top 3 ranked list (takes ~2 minutes).
3. Send the top 3 in a single message/poll and request answers within 24 hours (takes ~1 minute).
4. Book the accepted slot and note the AI fairness score in your log (takes ~2 minutes).
5. Rotate next meeting’s region if the same group meets regularly so no one’s always outside their window.

Simple habit: ask people for a 2‑hour “best block” instead of full calendar access. It’s fast, private, and makes AI suggestions much more useful and fair.

[Jeff Bullas]

Spot on: a ranked shortlist beats hunting for a single “perfect” time. Let’s turn that into a 5‑minute, no‑friction workflow you can use today, plus a couple of insider tricks to keep things fair over months, not just one meeting.

Try this now (copy‑paste prompt)

“Help me schedule a 60‑minute meeting across time zones. Participants and preferred windows (local time): Dana — New York, 08:00–18:00; Lee — London, 08:00–18:00; Priya — Bangalore, 09:00–19:00; Marco — São Paulo, 09:00–18:00. Avoid starting before 08:00 or after 19:00 local for anyone. Generate 8 candidate start times in UTC within the next 10 days. For each candidate: convert to each person’s local time; score fairness using this rule: start at 100, subtract 10 points for each person outside their window, and subtract 1 point per 15 minutes outside (floor at 0). Flag any daylight‑saving or holiday risks you notice. Return the top 3 ranked options with one‑line reasons, and provide a ready‑to‑send poll message with the 3 options in local times for each attendee. Also suggest a simple rotation rule for recurring meetings so no region gets more than 25% of slots outside their window over 4 meetings.”

Why this works

• You define fairness once; the AI does the math every time.
• Everyone sees their local times up front, which kills the back‑and‑forth.
• A rotation rule avoids the same team always taking the hit.

What you’ll need

• Names and cities (or precise time zones) for each participant.
• Each person’s preferred working window (earliest/latest) or a 2‑hour “best block.”
• Meeting length and any hard constraints (no Fridays, must end by 17:00, etc.).

Step‑by‑step

1. List the people, cities, and windows in one note.
2. Paste the prompt above into your AI tool and run it.
3. Skim the top 3 ranked options, check any DST flags, and pick 2–3 to propose.
4. Send the AI’s poll text as a single message and ask for a 24‑hour reply.
5. Book the winning slot. Save the fairness score so you can rotate next time.

Worked example (what you should expect back)

• Three options like “13:00 UTC” with conversions (e.g., 08:00 New York, 13:00 London, 18:30 Bangalore, 10:00 São Paulo), each with a fairness score and a short note such as “Priya +30 minutes past window.”
• A clear nudge like “Rotate burden to APAC next meeting; keep within 60 minutes of window for all.”
• A poll you can paste into email or chat listing Option A/B/C with everyone’s local times.

Insider upgrades for recurring meetings

• Weight key roles: Add “Weight Dana (host) x1.5 in fairness scoring; if ties, prefer options that keep Dana within window.”
• Shoulder‑hours budget: Add “Track minutes outside window per person; ensure no attendee exceeds 90 minutes outside window across 4 meetings.”
• Holiday awareness: Add “Flag if any option lands on common public holidays in those cities and suggest an alternate within 48 hours.”

Premium prompt for an 8‑week rotation

“Design an 8‑week, biweekly 45‑minute meeting for these participants: New York (08:00–18:00), London (08:00–18:00), Bangalore (09:00–19:00), Sydney (08:00–18:00). Produce 6 candidate start times per meeting, convert to local times, apply this fairness rule: start 100, minus 10 per person outside window, minus 1 per 15 minutes outside (floor 0). Choose the best slot each week so (a) average fairness ≥75, (b) no region has more than 2 meetings outside their window, (c) rotate which region is closest to 09:00 local. Output a simple schedule for 8 weeks with UTC starts, local conversions, fairness scores, and a note on who’s bearing the inconvenience each time. Flag DST changes and adjust within ±60 minutes if needed.”

Common mistakes and quick fixes

• Mistake: Using region codes (e.g., “ET”) without cities. Fix: Give city names; the AI will handle DST correctly.
• Mistake: Asking for one “best” time. Fix: Always ask for 3–5 options and a rotation rule.
• Mistake: Ignoring small overruns. Fix: Cap meetings at the hour and ask the AI to avoid end‑of‑day starts that push past windows.
• Mistake: Sharing full calendars. Fix: Collect a 2‑hour best block from each person instead.

Action plan

1. Today: Collect cities and preferred windows from your group (2 minutes).
2. Today: Run the quick prompt and send the AI‑generated poll with 3 options (3 minutes).
3. This week: Book the slot, note the fairness score, and record who was outside their window.
4. Next meeting: Use the rotation rule to shift the burden and keep average fairness at 75 or higher.

One more high‑value tweak

• Ask the AI to include a “backup within 48 hours” for each option. If someone declines, you switch instantly without restarting the whole process.

Shortlist, fairness score, rotation. Do this twice and you’ll never go back to manual conversions.

[Author]

Posts