Meeting Time Calculator
One meeting clock read across three zones — every local time, the day shifts, the spread, and who sits outside a working band.
Meeting Time Calculator
Results recalculate instantly on every keystroke. Nothing you type is transmitted.
What this result does not account for
- Fixed offsets only — no DST schedule modeling
- Three zones; the band is a stated convention
In short: A 15:00 meeting at UTC+0 reads 10:00 at UTC−5 and 00:00 at UTC+9 — that one a day later. The wall clocks span 14 hours from earliest to latest once the day shift counts, and two of the three land inside the page's 08:00-to-20:00 convenience band — the midnight attendee is the meeting that should move. The band is a convention, stated as one; the conversion underneath is exact.
Formula
local = meeting clock − zone A offset + zone offset
Zone A is the anchor: its clock minus its offset is the instant, and each other zone adds its own offset to that instant. The spread counts the day shifts — a zone reading midnight tomorrow is a full day past the earliest clock, and the spread prices the widest gap between any two of the three. The 08:00-to-20:00 band is this page's own convenience convention for 'civilized', not a labor rule.
Worked Example
- Set the meeting clock in zone A and three offsets.
- Read all three local clocks with their day shifts.
- Check the spread and the band verdict.
Defaults: 15:00 at UTC+0 across −5 and +9 — 10:00, 00:00 next day, a 14-hour spread, two of three inside the band. Push zone C to +14 and the meeting lands in its tomorrow morning.
Strengths & Limits Of This Model
Where this engine is strong
- Day shifts named per zone
- Spread and band verdicts on the same read
Where it stops
- No calendars, no attendee lists, no DST tables
Practical Use Cases
Calls
one clock, every attendee's local read
Rotating slots
see whose evening pays the toll
Half-hour zones
mix +5.5 with whole-hour zones
Methodology & Editorial Standards
Computation runs in IEEE-754 double precision at full internal precision; rounding to two decimal places occurs strictly at the display layer, so no cumulative drift enters the result. All monetary outputs use accounting presentation — grouped thousands, two decimals, negatives in parentheses — so figures can be transcribed directly into a model or working paper. Division-by-zero and out-of-domain inputs return an em-dash rather than a misleading number.
This engine was reconciled against an independent reference implementation and hand-verified for the worked example above before release. Our full five-stage review process is published on the About Us page.
Disclaimer. This calculator is provided for informational and modelling purposes only and does not constitute financial, tax, legal, medical, or engineering advice. Verify all figures with a qualified professional before acting on them.
Meeting Time Calculator — 8 Expert FAQs
8 analyst-written answers to the questions practitioners actually ask — optimised for voice and answer-engine retrieval.
Why three zones and not five?
Three is the shape of almost every real call — two ends and the bridge. The page keeps the cards readable; for a fourth zone, convert the odd one out with the time-zone converter and the arithmetic is identical.
What does the spread measure?
The widest gap between any two of the three wall clocks, counting the day shift. A zone reading midnight tomorrow is 24 hours past this morning's 10:00, not an hour past noon — the spread is the honest size of the scheduling problem.
Is the 08:00-to-20:00 band a rule?
No — it is this page's convenience convention for times a person might reasonably keep. Shift workers, night owls and holidays all break it. The conversion is exact; the band is a lens, and the card says which zone it flags.
Why does zone A get to be the anchor?
Someone's calendar owns the invitation. Anchor the clock where the organizer sits and the other zones become readings, not decisions. Anchor anywhere else and the arithmetic is the same with the labels moved.
Can the meeting land on two different days?
Yes and it usually does at extreme offsets — a 23:00 call at UTC+0 is 08:00 tomorrow at UTC+9. The day shift prints next to every clock that crosses, because the date is part of the answer.
What about daylight saving in one zone only?
The page converts fixed offsets, so enter the offsets in force on the meeting date — if one zone is on summer time, its offset already carries that hour. Mixing a winter offset with summer ones is how meetings land an hour late.
How do half-hour zones work here?
Type 5.5 or -3.5 as the offset — the arithmetic runs in minutes. A +5.5 zone reads 30 minutes different from a +5 zone at the same instant, which is exactly the kind of detail a whole-hour-only tool gets wrong.
When should I just move the meeting?
When the band card flags a zone and keeps flagging it at every candidate hour. If the spread exceeds twelve hours, somebody's midnight is in the middle of the band no matter what — the honest answer is rotation, not optimization.