# Vacation

## How does Distro handle vacations?

Distro can automatically detect vacations from a team member's calendar. It looks for full-day busy events (24-hour slots with no gaps). These can be single days or recurring events. Partial day blocks are not counted as vacation time.

When a team member has a full-day block, Distro will skip them in the round-robin assignment and give leads to other available team members.

Distro treats distribution rules and ownership rules differently:

{% tabs %}
{% tab title="Distribution Rules" %}

* Use the "cover for colleague" logic by default
* This means if the assigned person is unavailable, Distro will try to find a suitable replacement
  {% endtab %}

{% tab title="Ownership Rules" %}

* Simply skip unavailable users based on the settings
* No attempt is made to find a replacement; it just moves to the next available person in the rotation
  {% endtab %}
  {% endtabs %}

This distinction allows for more flexibility in how leads are handled when team members are unavailable, depending on which type of rule is being applied.

## Distribution Rules <a href="#distribution-rules" id="distribution-rules"></a>

Toggle the vacation calibration setting if you want to remove users from metting assignments during their vacation.

<figure><img src="/files/2vP5dJm1Y2P6mQfcWVfx" alt=""><figcaption></figcaption></figure>

### **Vacation Buffer**

The vacation buffer setting controls when team members are removed from and re-added to lead distribution around their vacation periods.

<figure><img src="/files/VTdQ8xNRsC2QaEdYGoFL" alt=""><figcaption></figcaption></figure>

Let's say Emma has a vacation from March 10th to March 20th, and the vacation buffer is set to 2 days before and 1 day after.

* Emma will stop receiving leads on March 8th (2 days before vacation starts)
* She'll start receiving leads again on March 19th (1 day before vacation ends)

#### **Key Points**

1. **Zero Buffer**: If set to "0", the team member is removed on the first day of vacation and added back on the last day.
2. **Buffer Longer than Vacation**: If the buffer is longer than the vacation (e.g., 5-day buffer for a 3-day vacation), the team member remains in the distribution.
3. **Different Before/After Settings**: You can set different numbers for the before and after buffers.
4. **Partial Days**: The system only considers full days for vacation and buffer calculations.

## Ownership Rule <a href="#matching-rule" id="matching-rule"></a>

Toggle the Cover for colleagues on vacation setting if you want to re-route meeting assignments to a designated colleague during their vacation.

<figure><img src="/files/flc4Os1XIWL8PwJovrmK" alt=""><figcaption></figcaption></figure>

### Cover for colleagues on vacation buffer <a href="#cover-for-colleagues-on-vacation-buffer" id="cover-for-colleagues-on-vacation-buffer"></a>

{% hint style="danger" %}
Distro will never update lead/contact owner in the CRM when cover for colleagues is triggered.
{% endhint %}

The cover for colleagues on vacation buffer set how many days before/after the vacation the colleague should receive meeting assignments.

<figure><img src="/files/y6Qmx0bMRsZImgI4T6kI" alt=""><figcaption></figcaption></figure>

## Design a colleague <a href="#design-a-colleague" id="design-a-colleague"></a>

Users can set up a colleague themselves. Head to Settings -> Profile

<figure><img src="/files/LKC4rGhqj2RbzWJWBmTi" alt=""><figcaption></figcaption></figure>

Admins can also manage the users settings. Head to Settings -> Members

<figure><img src="/files/m2Ti7IrXB2bzLQQ7h8B1" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/f5xU4JuS9Rf7y1lIuTC8" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.distro.so/settings/workspace-settings/vacation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.