Coordinate Across Time Zones Without Confusion
Proposes meeting times across regions clearly, avoiding the classic AM/PM and date-line mix-ups.
Prompt
ROLE: You are a globally-minded coordinator who schedules across time zones with zero ambiguity. CONTEXT: - Participants and their cities/zones: [PEOPLE_AND_ZONES]. - The meeting purpose and length: [PURPOSE], [DURATION]. - My constraints and preferred windows: [MY_AVAILABILITY]. - Urgency and target week: [TIMEFRAME]. TASK: 1. Propose 2-3 specific slots that are reasonable for everyone (avoid anyone's late night where possible). 2. State each slot in every participant's local time plus a neutral anchor (UTC), with the date spelled out to avoid 03/04 confusion. 3. Note who is being asked to stretch outside normal hours and acknowledge it. 4. Ask them to confirm or counter, and offer a scheduling-link fallback. OUTPUT FORMAT: - Subject: clear, with the topic and 'scheduling'. - Body: 70-110 words. - A small table: Slot | [Person A local] | [Person B local] | UTC. CONSTRAINTS: - Always use 'Tue, 12 Mar, 14:00' style dates, never 12/03 alone. - Spell out AM/PM or use 24-hour time consistently. - Do not default every meeting to my own time zone; share the burden fairly.
How to use this prompt
- 1
Copy the prompt above and paste it into ChatGPT, Claude, or Gemini — or open it in the visual Studio to edit each part on a canvas and run it with your own key.
- 2
Replace any bracketed placeholders with your specifics. The more concrete your context and constraints, the sharper the result — see the 5-part prompt structure.
- 3
Run it, then refine. Ask the model to critique and improve its own answer with self-critique prompting.
Techniques in this prompt
Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.
Learn this techniqueRecommended models
Build on this prompt
Open it in the visual Studio to wire it into a full workflow with your own API key — or learn the craft behind prompts like this.
More in Email & Professional Communication
Cold Outreach Email That Earns A Reply
Writes a researched, personalized cold email built around the prospect's problem instead of your pitch.
Reply To An Angry Customer Without Escalating
De-escalates a furious customer email with empathy, ownership, and a concrete next step.
Decline A Meeting And Protect The Relationship
Says no to a meeting request gracefully while keeping the door open and offering an alternative.
Follow Up Without Sounding Desperate
Crafts a value-adding follow-up to a non-responsive contact that gives a reason to reply now.