Professional Use Cases
Remote Teams
Challenge: A software development team spans San Francisco, London, and Singapore. Finding meeting times that work for everyone is a daily struggle.
How City Clock Helps:
- •Team lead adds all office locations to track everyone's working hours simultaneously
- •Meeting coordinator tool finds optimal meeting times that respect everyone's schedule
- •Quick time conversion for scheduling standups and sprint planning
International Sales Teams
Challenge: Account executives need to reach prospects in different continents at appropriate times without calling at 3 AM.
How City Clock Helps:
- •Sales reps track business hours for all their territories
- •Visual indicators show when it's appropriate to call or email
- •Schedule follow-ups that arrive during working hours
Financial Traders
Challenge: Global markets operate 24/5 across different time zones. Missing market opening times means missing opportunities.
How City Clock Helps:
- •Track Tokyo, London, and New York market hours simultaneously
- •Set up dedicated world clock for major financial centers
- •Never miss market opening or closing bells
Online Educators
Challenge: Teaching students from different countries requires scheduling classes that accommodate various time zones.
How City Clock Helps:
- •Create class schedules that work for students worldwide
- •Convert assignment deadlines to each student's local time
- •Track office hours across multiple time zones
Personal Use Cases
Long-Distance Relationships
Scenario: Partners living on different continents need to coordinate calls without disturbing each other's sleep or work schedules.
How City Clock Helps:
- •Always know when it's a good time to call your partner
- •Plan video calls at mutually convenient times
- •Send messages timed to arrive during waking hours
Frequent Travelers
Scenario: Business travelers and digital nomads constantly switching time zones need to stay coordinated with home base.
How City Clock Helps:
- •Track home time and current location simultaneously
- •Plan calls with family and colleagues back home
- •Calculate jet lag and adjust to new time zones
Working out your own overlap
Every scenario above comes down to the same underlying question: how many hours of the working day do two places actually share? It is worth calculating once, properly, rather than re-deriving it in your head each time.
The method
- Write both working days in UTC, not in local time.
- The overlap is the intersection of those two UTC ranges.
- Convert the intersection back to each local time — you now have the same window expressed two ways, which is what you put in the invite.
- Repeat for the other half of the year if either side observes daylight saving. The answer will be different.
A worked example
London 09:00–17:00 in winter is 09:00–17:00 UTC. Singapore 09:00–18:00 at UTC+08:00 is 01:00–10:00 UTC.
The intersection is 09:00–10:00 UTC — a single hour, which is 09:00 in London and 17:00 in Singapore.
In British summer, London shifts to 08:00–16:00 UTC while Singapore does not move, and the overlap shrinks to 08:00–10:00 UTC. The window moves, and one side has to absorb it.
What to do when the overlap is small
Once you know the number, the choice of working pattern follows from it rather than from preference:
- Four hours or more — conventional scheduling works. Protect the overlap for things that genuinely need to be live, and leave the rest of the day for focused work.
- One to three hours — the overlap becomes a scarce resource. Use it for decisions and disagreements, never for status updates, which belong in writing.
- Effectively zero — stop trying to schedule around it. Work asynchronously by default and rotate the occasional unavoidable live call so the same person is not always the one awake at 23:00.
The meeting scheduler does this calculation across up to eight locations at once, and each city page shows the dates on which that overlap shifts.