How do working hours and timezones factor into Span metrics?

Span determines business hours using a standard 8-hour (9-5) business day model with timezone-aware weekend detection. Here's how it works:

Where to Configure

This is set as a single, organization-wide timezone in your Organization Settings during initial setup. You can check your current setting in Organization Settings → Org Calendar.

This means metrics don't account for individual working hours across different timezones - everyone is measured against the same 8-hour standard day in the organization's configured timezone.

How It Works

All timestamps from various sources (calendar meetings, commits, PRs, etc.) are converted to your organization's timezone before being grouped by day. Then the standard 8-hour business day formula is applied uniformly to everyone.

Configurable Settings

You can customize several aspects in Organization Settings → Metrics:

1. Weekend Inclusion in Cycle Time (Enabled by default)

• Controls whether PR cycle time, issue cycle time, and review response time exclude weekend hours

• Default: weekends are excluded

2. Fragmented Time Threshold (Default: 90 minutes)

• Defines the minimum free time block between meetings that counts as "fragmented"

• Options: 30, 60, 90 (recommended), or 120 minutes

• Directly impacts focus time calculations

3. Organization Timezone

• Sets the reference timezone for determining local business days and weekends

• Configured in Organization Settings → Org Calendar

4. Out-of-Office Source

• Calendar or HRIS

• Determines where OOO information comes from (typically calendar integration)

• Affects which days are counted as "active weekdays"

What's NOT Customizable

Span currently does not support:

• Custom business hours (e.g., specific start/end times like 9am-5pm)

• Holiday calendars or regional business day definitions

• Different business hours by team or region

• Alternative weekend definitions (e.g., Friday-Saturday for some regions)