About CrossClock
A time zone meeting planner built for the specific moment when a team spread over four continents has to agree on one hour — and somebody has to be the one who picks it.
What it does
CrossClock puts every participant's day on a single 24-hour timeline and scores each possible start time by how many people are inside their working hours, awake, or asleep. It then proposes the best few windows, warns about daylight-saving changes near the chosen date, and exports the result as a calendar file, a text summary or a share link.
The whole application is a static page. There is no account system, no backend API, no uploaded file and no database of teams. What you type stays in the tab and, if you save it, in this browser's local storage.
Why it exists
Most scheduling advice assumes everyone works 9-to-5 and that a city's offset is a fixed number. Neither holds for distributed teams: a teammate in Manila may work 14:00–23:00 to overlap with Europe, and a country can change its clock rules with a few months' notice. A clock grid that only displays “current time in X” leaves the user to do the arithmetic that actually decides the meeting — and that arithmetic is where the mistakes happen.
So the design goal was narrow: make the trade-off visible, make the scoring explainable, and keep the data on the user's device.
How the times are calculated
City names and IANA zone identifiers are stored in one small data file. Offsets, weekday boundaries and daylight-saving transitions are read at runtime from the time zone database of the browser you are using, through the standard Intl API. That means the timeline follows the same rules as your operating system: no offset table to go stale, and a new transition is handled as soon as your device updates its tz data.
Scoring is deliberately simple and documented: two points for a participant inside working hours, one for awake, zero for asleep, weekends never counted as working hours. You can see the reasoning behind a recommendation instead of accepting a black box.
What it does not do
- It does not connect to your calendar, so it cannot see existing bookings or other people's availability.
- It does not know public holidays, company closures or individual leave.
- It does not send invitations. It produces a file and a summary that you send yourself, from whatever tool you already use.
- It does not keep a copy of anything you enter.
Who runs it
CrossClock is an independent, ad-supported project. It is not a company product with sales staff or an account team. Fixes and questions go to one address and are read by the person who maintains the site.
Contact
Email opyheb@icloud.com with a bug report, a missing city, a translation offer or a privacy question. Including your browser and a screenshot makes a bug much faster to fix. The contact page lists what is most useful to send.
Try it with your own team — no sign-up, nothing uploaded.
Open the planner