Clockjumper

Research Methodology

How the Clockjumper Workday Overlap studies are built — the city list, the overlap engine, and the shared dataset that every study reads from.

City selection: four gates

The overlap dataset uses one shared city list. A city is included only when it passes all four gates:

  1. Population / economic weight. Metro area meets a documented population and economic-activity threshold.
  2. Time-zone stability. The city has a stable IANA zone, no ongoing zone-boundary dispute, and unambiguous DST rules.
  3. Coverage. Every inhabited region is represented; the list is not skewed to any single continent.
  4. Registry integrity. The city passes the build-time registry validation (IANA zone resolves, region derives cleanly from country code, no duplicate slugs).

Dataset

The shared dataset backs every overlap study. Row count and format are the same everywhere they're cited because they're read from the same registry entry at build time.

Overlap engine

Overlap is computed by projecting both cities' local working windows onto a shared UTC axis and intersecting the intervals. The engine handles the international dateline explicitly — when a pair's overlap window wraps past 00:00 UTC, both halves are counted, so no pair is silently zeroed out because of wraparound. DST is evaluated per-date, not per-city, so January and July figures reflect the actual clocks in each city.

Studies

Editorial context

Research is subject to Clockjumper's editorial policy. Substantive corrections are logged on the corrections page. Series-specific methodology pages provide the exact code paths and column definitions for each series.