The short answer: a time zone only tells you what the clock reads, not whether someone is available. When you give the scheduler each person's working hours, it can shade the day and find the window where everyone is genuinely at their desk. That turns a six-hour offset from a maths problem into a simple yes, no, or "only between 3 and 5".
Most timezone tools stop at the offset. They show you that London is eight hours ahead of San Francisco and leave the rest to you. But the offset alone never answers the real question, which is not "what time is it there?" but "are they free when I am?"
Why the offset alone isn't enough
Two cities can share a comfortable offset and still have almost no usable overlap. Imagine a colleague who starts at 7:00 AM and finishes at 3:00 PM, and another who works a standard 9-to-5. On paper they are in the same zone. In practice their shared window is just six hours, and if one of them also blocks mornings for deep work, it shrinks further.
The clock reading is a fact. Availability is a decision. Only the second one tells you when to send the invite, and the tool can't know it unless you tell it.
What working-hours shading actually does
When you set each person's hours, Atlas shades their working window directly on the world map. Daytime-for-them reads as light; outside their hours reads as dim. Line up several people and the answer becomes visual: the band where every shaded window agrees is your meeting slot. There is no arithmetic to do and nothing to second-guess.
- Green-light hours show where someone is genuinely at their desk, not merely awake.
- The shared band is the only stretch where all your shaded windows overlap.
- The edges make the trade-off honest: if the only overlap is someone's last 30 minutes, you see it before you book it.
How to set hours that are actually useful
The shading is only as good as the hours behind it. A few habits keep it honest:
- Set the hours you'll really take a meeting, not your contractual day. If you guard mornings for focus, start the window at 11.
- Reflect the real edges. An early finish on Fridays or a long lunch is exactly the kind of detail that decides whether a slot works.
- Be honest on behalf of others. When you pin a teammate, give them the hours they keep, not the hours you wish they kept.
It is tempting to set a wide 8-to-8 window so more slots light up. Resist it. A slot that looks shared but lands in someone's dinner is worse than no slot at all. For how Atlas turns these windows into a single suggestion, see finding your team's overlap window.
From raw difference to a real answer
This is the difference between a clock and a scheduler. A clock converts; a scheduler decides. The table below shows how the same offset reads very differently once working hours are involved.
| What you know | What it tells you |
|---|---|
| Time zone only | It is 5:00 PM there. Useful, but is that their end of day? |
| Zone + working hours | It is 5:00 PM and they finish at 6. You have one hour. |
| A whole group's hours | The only shared band is 3:00–5:00 PM your time. Book inside it. |
Where Atlas fits in
Once everyone's hours are set, Atlas finds and suggests the best overlapping time for you, then adds the meeting to your calendar in each person's correct local time, with daylight saving handled. You can do all of it from Quick Check, summoned with a keyboard shortcut, without leaving whatever you were doing. The shading is what makes the suggestion trustworthy: it is built on when people actually work, not just where they are.
Frequently asked
Why isn't a time zone enough to schedule a meeting?
What working hours should I set in a scheduling tool?
Does Atlas handle daylight saving when I set working hours?
Stop doing timezone math
Atlas finds the time everyone's awake and adds it to your calendar in one tap.
One-time purchase, yours forever.