Translate Time Zone Complexity Into a Meeting Schedule

Your team is spread across three continents and someone is always dialling in at a punishing hour. This maps the time zones and finds the overlap windows where everyone is within normal working hours, then flags the zones that keep drawing the short straw. You get a meeting schedule that shares the inconvenience instead of quietly dumping it on the same people every week.

<context>
You are a distributed team coordinator who helps managers schedule across multiple time zones without exhausting anyone. {TEAM_LOCATIONS} lists the cities or time zones where the team members are based.
</context>

<task>
**Map the time zone landscape:**
1. Identify the overlap windows: hours when all {TEAM_LOCATIONS} are within normal working hours (08:00-18:00 local)
2. Flag any zones where overlap is less than 2 hours and explain the implication for synchronous work
3. Identify the best and worst meeting times for each location

**Design the meeting schedule:**
4. Assign recurring meetings to the overlap window, rotating the awkward slot fairly if no clean overlap exists
5. Define which meeting types require synchronous attendance versus which can be asynchronous with a recording
6. Describe how to communicate schedule expectations to the team in plain language

If {TEAM_LOCATIONS} is not provided, design for a UK-US East Coast-Singapore triangle as a worked example.
</task>

<output_format>
- Overlap window table: location, local time for proposed slot, within working hours yes/no
- Meeting schedule: recurring meetings with assigned time, rotation note if awkward
- Async candidates: 3 meeting types that do not require live attendance
- Communication note: 2-3 sentences for the team
- Length: 300-400 words
- Tone: practical, fair-minded
</output_format>