Managing Across Time Zones

Distributed teams fail across time zones for a predictable reason: the overlap window is treated as free, filled with meetings, and the actual work is pushed to whatever is left.

A product-focused treatment of chronemics and time use is available in learn more.

Federal wage-and-hour guidance is maintained by the U.S. Department of Labor Wage and Hour Division.

Overlap is the scarcest resource a distributed team has. It should be budgeted like one.

Decide the model deliberately

Full overlap. Everyone works roughly the same hours regardless of location. Simple, and it means someone is working unsociable hours permanently. Sustainable only across narrow spreads, and it produces attrition on the disadvantaged side.

Partial overlap. A defined window when everyone is available; the rest is asynchronous. The common and usually correct answer.

Asynchronous by default. No required overlap. Requires genuine discipline in documentation and decision-making, and it works when it is real.

Follow-the-sun. Work handed between regions. Effective for support and operations, expensive in handover overhead, and generally poor for project work.

Pick one and say which. Teams that have not decided default to full overlap by accident, with the cost falling on whoever is furthest from headquarters.

Budget the overlap

If a team has three hours of overlap, that is three hours per day for everything requiring synchronous contact — for the whole team, for the whole day.

Protect it for what genuinely needs it. Decisions, problem-solving, difficult conversations, onboarding.

Keep status out of it. Written updates cost less to produce than a meeting costs to attend, and they serve people who were not there. See meeting load.

Do not fill it. An overlap window booked solid means nobody can raise anything unplanned, which is what the window was for.

Rotate the pain. Where a meeting must be outside someone's hours, rotate which region takes it. A recurring 6am call that always lands on the same people is a resignation being scheduled in advance.

The compliance layer

The part that is specific to employment rather than to collaboration, and the part most often missed.

Working hours are the employee's local hours. A 7am start in the employee's location is a 7am start, whatever the headquarters clock says.

Overtime is computed on the employee's applicable rules. For US employees, that means their state — including daily overtime in states that have it. See timekeeping for remote and hybrid staff.

Define the workweek per employee and state it. The FLSA workweek is a fixed, recurring 168-hour period, and it must be documented. For distributed teams it is easy to leave undefined, and it determines every overtime calculation.

Watch shifts crossing midnight in the employee's local time, and confirm your system attributes the hours to the right day. This is a common configuration error and it produces overtime miscalculation silently.

Time zone changes in the record. Daylight saving transitions, and employees who travel. A system that stores local time without an offset will produce a 23-hour or 25-hour day twice a year, and the reconciliation will be someone's manual problem.

Non-exempt employees on calls outside their hours are working. A 10pm call to accommodate another region is compensable time and must be recorded. See off-the-clock work.

That last point is the one that turns a scheduling inconvenience into a wage and hour exposure, and it is invisible in most distributed teams because nobody thinks of a call as work.

The load nobody accounts for

Two costs that do not appear anywhere and are borne unevenly.

The coordination tax. Someone in a minority time zone spends materially more effort scheduling, catching up, and reading back through conversations that happened while they slept. It is real work and it is invisible.

Delayed decisions. A question that would take two minutes in person takes a day when it crosses a zone boundary. The cost is not the two minutes; it is the work that waits.

The fix for both is the same: push decision authority outward. A team that must escalate across a time zone for routine decisions will be slow regardless of how well the overlap is managed.

What makes async actually work

Write decisions down, with reasoning. Not just what was decided — why, and what was rejected. This is the single highest-value habit in a distributed team.

Default to written proposals rather than meetings to decide.

State response expectations. "Not urgent, reply within a day" removes the pressure to monitor messages at night, which is both a wellbeing and a wage issue.

Record meetings and post notes. Missing a meeting should not mean missing the information.

Make status visible without asking. If someone has to be awake to know what is happening, the system has failed.

One source of truth per topic, and keep it current.

A short check

• [ ] The overlap model is decided and stated, not inherited
• [ ] Overlap hours are protected from status meetings
• [ ] Out-of-hours meetings rotate between regions
• [ ] Each employee's workweek is defined and documented
• [ ] Overtime rules configured per employee location, including daily overtime states
• [ ] Shifts crossing midnight attributed correctly
• [ ] Out-of-hours calls recorded as working time for non-exempt staff
• [ ] Decision authority pushed to where the work is