Earlier quoted context omitted.
>Most of us who have to deal in multiple time zones have a Web Page/Dashboard/App of clocks with all the time zones that we deal with. 45' away from me I actually have a physical wall of clocks with cities noted above them. ... which you could dispense with if everyone went on the same time base.
Here is my current Algorithm for setting up a meeting (which I do a lot): o What City are they in, (Say, Melbourne) o Hit F4 (Dashboard on my MBAir) o It's 7:40 in Melbourne. 5 Hour Behind. Set meetings starting no early than 9:00 AM + 5 Hours. I repeat that algorithm (as do our partners) 2-3 times a week, and have done so for the last 2+ years that I've been in emerging markets. It works really well. I know, for ins…
The easy way would be to just keep a list of the other party's available hours in UTC. If you had to deal with a lot of people in a lot of different places, you could keep a list by major city the same way you do with time zones. The fact that you need to apply an "algorithm" to something that's inherently static should tell you the situation as it stands is inefficient.