> For the complete documentation index, see [llms.txt](https://help.swarmia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.swarmia.com/definitions/frequently-asked-questions/how-do-you-treat-weekends-in-metrics.md).

# How do you treat weekends in metrics?

Whether weekends are included in duration metrics depends on your organization's weekend exclusion setting. When weekends are included, a pull request cycle time of 14 days means two full calendar weeks.

You can exclude weekends under **Organization settings → General → Weekend Exclusion** by enabling **Exclude weekends from duration metrics**. When enabled, Swarmia removes Saturdays and Sundays from supported duration metrics.

The setting applies to pull request cycle time and its stages, as well as issue cycle time. These durations follow the setting in code and issue insights, detailed pull request and issue views, key metrics, the Max Pull Request Age and Max Issue Age working agreements, signals, daily digests, and issue summaries. It also changes the small pull request throughput chart from an average per calendar day to an average per business day. The number of merged pull requests doesn't change.

The pull request duration fields in [Data cloud exports](/settings/integrations/data-export/data-cloud.md#parquet-schemas) also follow this setting.

Existing and historical records are recalculated using the current setting. The selected reporting timeframe and the records included in it stay the same. For example, a 90-day report still covers 90 calendar days; only the durations within the report change.

Weekend boundaries follow the timezone used by the view. Most metrics use the organization's timezone, although Issue Flow currently uses the viewer's browser timezone and signals use UTC. This can cause small differences around weekend boundaries.

## What isn't excluded?

Only entire Saturdays and Sundays are removed. Evenings, public holidays, vacations, and other non-working hours still count. Custom workweeks and organization-specific weekend days aren't currently supported.

The setting doesn't affect DORA metrics, counts such as merged pull requests or completed issues, WIP counts, or reporting cohorts. Flow efficiency, Focus and FTE calculations, timesheets, and scheduling rules have their own business-day logic and don't follow this setting.

## Which metrics always exclude weekends?

Time to first review and the Max Pull Request Review Time working agreement always exclude weekends, regardless of the organization setting. Pull request review reminders also have their own weekend handling that is independent of this setting.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.swarmia.com/definitions/frequently-asked-questions/how-do-you-treat-weekends-in-metrics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.