--- title: "Time Zone Friction Scorer for Remote Teams — Geo-Parity" description: "Score how hard your remote team's timezones are to work across (0–100), find the golden hour everyone shares and flag the member left isolated. DST-accurate." canonical: "https://geo-parity.com/meeting-planner/" generator: geo-parity markdown twin --- Remote Teams · Timezone Parity # How much timezone friction does your team have? Enter where each teammate works and their hours. Get a **Friction Score** for the whole team, the exact **golden hour** everyone shares, and a flag for the **lone wolf** — the member whose hours isolate them from the rest. For deciding who to hire and where. ## Team Timezone Friction Scorer Add each team member's city and working hours. Get a **Friction Score**, the exact **golden hour** where everyone's online, and a flag for the **lone wolf** — the member most isolated from the rest. 10 / 100 Broken friction score — higher is easier 0h of shared working time per day · 2/4 can be online together ⚠ No common window 0 minutes overlap · — - No slot works for everyone within their hours. Try widening working hours or removing a city. High friction? Three ways to fix a scattered team: [Deel →](https://www.deel.com/)[Remote.com →](https://remote.com/)[Loom →](https://www.loom.com/)[SurfOffice →](https://www.surfoffice.com/) Hire in a friendlier timezone, go async, or meet IRL. Links may be affiliate links. ## How the overlap is found Each person's working day (e.g. 09:00–18:00 local) is converted to UTC using their timezone's offset for the chosen date — which automatically accounts for **Daylight Saving Time**. The tool then finds the longest stretch of UTC time during which *every* participant is simultaneously inside their local working hours. That intersection is the golden hour. overlap = ⋂ᵢ [ workStartᵢ − offsetᵢ , workEndᵢ − offsetᵢ ] (mod 24h) ## Tips & FAQ - No common window? Widen one person's hours or drop the hardest timezone. - Offsets are DST-accurate for the selected date — change the date to plan ahead. - Fractional zones (India +5:30, Nepal +5:45) and midnight-wrapping windows are handled. - "Next day" means the local clock has rolled past midnight for that person. ## For AI agents & schedulers Scheduling and hiring/team-design bots can resolve a team in one request: `GET /api/meeting.json?zones=Europe/London,America/New_York,Australia/Sydney`. The response returns the golden-hour window (UTC + each local time, or `overlap: null` with the best partial) plus a `friction` block: the 0–100 score, grade, daily shared hours and the `loneWolf`. Declared in [/.well-known/mcp.json](https://geo-parity.com/.well-known/mcp.json) and described in [/llms.txt](https://geo-parity.com/llms.txt). Timezone offsets are computed from your browser/server's IANA data for the selected date. Double-check critical meetings against an authoritative calendar. --- Source: Geo-Parity — https://geo-parity.com/meeting-planner/