Time Zones

Ensure consistent shift generation and display for distributed teams.

In Upstat, each roster defines its own timezone. That timezone is used to schedule shifts and align coverage to local time for the team assigned to the roster.


Roster Timezones

When creating or editing a roster, you select a timezone from the IANA timezone database (e.g., America/New_York, Europe/London, Asia/Tokyo).

This timezone:

  • Determines when shifts begin and end
  • Acts as the authoritative schedule reference for that roster
  • Remains fixed regardless of the viewer’s local settings

How Times Are Stored

All times are stored internally in UTC for consistency. When displayed:

  • Shifts appear in the roster’s configured timezone
  • The calendar view shows times according to the roster timezone
  • Date boundaries respect the roster timezone, not UTC

Multi-Region Coverage

For teams spanning multiple regions, create separate rosters for each timezone:

Roster Timezone Coverage
APAC Support Asia/Singapore 08:00-17:00 SGT
EMEA On-Call Europe/Berlin 08:00-17:00 CET
US Coverage America/Los_Angeles 08:00-17:00 PST

Each roster runs on its local time, and users only need to think in their own timezone.


Follow-the-Sun Example

To achieve 24/7 coverage with business-hours-only shifts:

  1. Create 3 rosters, one per region
  2. Set each roster’s timezone to the local region
  3. Configure 8-10 hour shifts during business hours
  4. Use Single Shift mode (not Fill Gaps)

Coverage flows naturally around the globe as each team’s business day begins.


Daylight Saving Time

Rosters using timezones that observe DST automatically adjust:

  • When clocks spring forward, shifts adjust accordingly
  • When clocks fall back, shifts adjust accordingly
  • No manual intervention required

Best Practices

Use descriptive roster names that include region context (e.g., “EU Primary Support” not just “Primary Support”).

Coordinate handoff times if you have overlapping regional coverage. Consider 30-60 minute overlap for smooth transitions.

Document expectations for which roster handles which hours, especially during transition periods.


Summary

Aspect Behavior
Storage UTC internally
Display Roster’s configured timezone
DST Automatic adjustment
Multi-region Separate rosters per timezone