# Meeting Timezone Fairness Calculator — Best Time Across Zones > Find the fairest meeting time for a global team. Enter each person's UTC offset and rank every slot by how evenly it shares the off-hours burden. Free, no DST guesswork. - **Category:** Date & Time - **Interactive calculator:** https://youcalc.com/en/date-time/meeting-timezone-fairness/ - **Price:** Free, no sign-up required ## Overview When a team is spread across the world, no single meeting time works perfectly for everyone — someone always ends up dialling in early, late, or in the middle of the night. This calculator scores every half-hour slot of the day and finds the one that shares that inconvenience most fairly. You enter each person's raw UTC offset (the gap between their local clock and UTC), set a workday window, and it ranks the fairest times to meet. ## How to read your result The headline is the fairest meeting start time, shown in UTC. The fairness score (0–100) is a quick at-a-glance measure: 100 means everyone is comfortably inside their workday, and the number falls as more people are pushed into evenings or, worse, the middle of the night. The per-participant breakdown shows each person's local start and end time with a badge — green for in work hours, blue for off-hours, and amber for night. The shortlist offers the next-best UTC slots so you can pick one that suits a particular person if needed. ## Method The calculator uses a fixed UTC-offset model — pure arithmetic, no timezone database and deliberately no daylight-saving adjustment. For each candidate meeting start hour H in UTC (every half hour from 00:00 to 23:30) it computes each participant's local start as ((H + offset) mod 24). The meeting occupies [localStart, localStart + duration) on a 24-hour clock; if it runs past midnight the overhang wraps to the next morning. For every participant it measures two things: the hours that fall outside the workday window, and the hours that fall in sleeping time (00:00–07:00 or 22:00–24:00). The participant penalty is outsideHours × 1 + nightHours × 3 — night counts triple because asking someone to join at 3 a.m. is far worse than an hour after work. Summing across participants gives the candidate penalty; the fairest slot is the one with the lowest total (ties broken by the earlier UTC time). The 0–100 fairness score is a presentation heuristic derived from the average penalty per person — it is a relative comparison aid, not a statistical guarantee. ## Example - **Setup:** Three teammates: New York (UTC-5), London (UTC+0) and Mumbai (UTC+5:30), a 9:00–17:00 workday and a 1-hour meeting. - **Result:** The fairest slot is 14:00 UTC, scoring 96/100. That is 09:00 in New York and 14:00 in London — both squarely inside the workday — and 19:30 in Mumbai, just a couple of hours after work (off-hours, but well clear of the night). No slot puts all three inside 9–17 because their clocks span more than ten hours, so the tool picks the time that keeps two people in work hours and pushes only one person a short way past it, with nobody asked to join in the middle of the night. ## Frequently asked questions ### Does this handle daylight saving time? No — and that is by design. The tool uses the fixed UTC offsets you type in, with no timezone database and no DST logic, which keeps it simple and free of the subtle bugs that DST rules cause. The trade-off is that you must enter each person's current offset yourself. For a one-off meeting that is easy. For a recurring meeting, remember that when a region springs forward or falls back, its offset changes by an hour and the fairest slot can shift — so re-check around late March and late October (Northern Hemisphere) or the equivalent dates elsewhere. ### What does the fairness score actually mean? It is a 0–100 convenience score for the chosen slot, where 100 means every participant is inside their workday with no off-hours or night time at all. As the meeting pushes people into evenings the score drops, and night hours pull it down three times faster. It is meant for comparing one slot against another at a glance, not as a precise statistic. A score of 70 across a team that literally spans the globe can still be the best humanly possible answer. ### Why is night time weighted more heavily than just being off-hours? A meeting an hour after someone finishes work is an inconvenience; a meeting at 3 a.m. costs them sleep and is genuinely unhealthy if it recurs. To reflect that, every hour the meeting falls inside sleeping hours (before 07:00 or after 22:00) is counted three times as heavily as an ordinary off-hours hour. This steers the calculator away from "fair on paper" slots that quietly dump the cost on whoever is asleep. ### What if no time works for everyone? With teams spanning more than about ten hours of offset, that is normal — there is simply no slot where everyone is inside a standard workday. The calculator still returns the least-bad option and flags it honestly. In those cases consider rotating who takes the awkward slot from meeting to meeting, recording the session for whoever cannot attend, or splitting into two overlapping sub-meetings. ## Related calculators - [Business Days Calculator](https://youcalc.com/en/date-time/working-days-counter/) - [Project Deadline Planner](https://youcalc.com/en/date-time/deadline-planner/) - [Time Card Calculator with Overtime](https://youcalc.com/en/date-time/time-card-overtime/) ## Sources - https://www.timeanddate.com/worldclock/ - https://en.wikipedia.org/wiki/List_of_UTC_offsets --- Interactive version: https://youcalc.com/en/date-time/meeting-timezone-fairness/ · From YouCalc — https://youcalc.com