> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/settings/workspace-settings/calibration.md).

# Calibration

Open **Settings → Calibration** to choose the assignment-history period and compensation rules for distribution rules and Click Router round robin. Review the settings, then click **Save**.

<figure><img src="https://2442454418-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQA3GQNrIYVrPQ90NBwRa%2Fuploads%2FVj8i6cTi5RAi7PGeFOtt%2FCleanShot%202026-09-10%20at%2021.20.36%402x.png?alt=media&amp;token=78ddd233-3aca-467d-939f-b0ad8742f296" alt=""><figcaption></figcaption></figure>

## Reset frequency

Under **Reset frequency**, choose **Frequency**:

| Frequency | History used for balancing                                                            |
| --------- | ------------------------------------------------------------------------------------- |
| Monthly   | Assignments since the start of the current month.                                     |
| Quarterly | Assignments since the start of the current quarter: January, April, July, or October. |
| Yearly    | Assignments since the start of the current year.                                      |

This changes the period used for assignment balancing. It does not delete bookings or promise equal meeting counts. Member weights, eligibility, availability, recent assignments, and credits also affect who receives a meeting.

## Compensation rules

Credits give a member priority for a future eligible assignment. They apply within the relevant distribution rule or Click Router.

| Rule                      | Effect when enabled                                                                                                                           |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| **Vacation and holidays** | Adds credit when vacation handling skips a member selected by strict round robin. Flexible distribution does not award vacation compensation. |
| **Cancelled meetings**    | Returns a credit to the host when a prospect cancels an eligible distributed booking.                                                         |
| **No-show meetings**      | Returns a credit when the booking is marked as a no-show. Undoing the no-show reverses that adjustment.                                       |
| **Reassigned meetings**   | Returns a credit to the original host and records an assignment for the new host.                                                             |

These settings do not create compensation for personal or group links, or for meetings assigned through CRM ownership matching. Vacation compensation is separate from the [Vacation](https://help.distro.so/settings/workspace-settings/vacation.md) controls that remove members from assignments.

Open a distribution rule’s [Distribution history](https://help.distro.so/routing-rules/distribution-rules/distribution-history.md) to review assignments, weights, and credits.


---

# 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.distro.so/settings/workspace-settings/calibration.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.
